Re: [ECOS] App works in RAM but not in flash memory

Re: [ECOS] App works in RAM but not in flash memory

[Fano Ramparany]

I'm currently addressing the same problem (i.e. my application works
fine when built
for "RAM" startup type and don't works when built for "ROM" startup
type).

My application uses the TCP/IP stack, and used to work (even under ROM
startup, but
with apparently some time out problems (see. a previous thread in the
mailing list
under subject "TCP/IP and rom startup mode")), until a major
reconfiguration of our intranet.
(incl. a change in our IP address). Now even the ping_test doesn't work
in ROM  startup mode, although
it works ok in RAM startup mode (using gdb).

Daniel, as far as your cyg_mbox application is concerned, you could
perhaps test the
small application a send you off-line, and check whether is works in
both startup mode. I've just
checked that it works on my target (a Cirrus Logic EDB7212 board)

More generally, Jonathan, what is the best way to find out why a ROM
startup application
doesn't work when its RAM startup version runs ok?

Fano

Re: [ECOS] App works in RAM but not in flash memory

[Jonathan Larmour]

Fano Ramparany wrote:
> 
> I'm currently addressing the same problem (i.e. my application works
> fine when built
> for "RAM" startup type and don't works when built for "ROM" startup
> type).
> 
> My application uses the TCP/IP stack, and used to work (even under ROM
> startup, but
> with apparently some time out problems (see. a previous thread in the
> mailing list
> under subject "TCP/IP and rom startup mode")), until a major
> reconfiguration of our intranet.
> (incl. a change in our IP address). Now even the ping_test doesn't work
> in ROM  startup mode, although
> it works ok in RAM startup mode (using gdb).
> 
> Daniel, as far as your cyg_mbox application is concerned, you could
> perhaps test the
> small application a send you off-line, and check whether is works in
> both startup mode. I've just
> checked that it works on my target (a Cirrus Logic EDB7212 board)
> 
> More generally, Jonathan, what is the best way to find out why a ROM
> startup application
> doesn't work when its RAM startup version runs ok?

My guess is it's something to do with the eth driver initialization.
Perhaps the MAC address was set in the redboot config before.

You could see if it also fails for RAM startup if you enabled the
"CLAIM_COMMS" virtual vector option in the HAL config.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] App works in RAM but not in flash memory

[Fano Ramparany]

Jonathan Larmour wrote:

> Fano Ramparany wrote:
> >
> > I'm currently addressing the same problem (i.e. my application works
> > fine when built
> > for "RAM" startup type and don't works when built for "ROM" startup
> > type).
> >
> > My application uses the TCP/IP stack, and used to work (even under ROM
> > startup, but
> > with apparently some time out problems (see. a previous thread in the
> > mailing list
> > under subject "TCP/IP and rom startup mode")), until a major
> > reconfiguration of our intranet.
> > (incl. a change in our IP address). Now even the ping_test doesn't work
> > in ROM  startup mode, although
> > it works ok in RAM startup mode (using gdb).
>
> My guess is it's something to do with the eth driver initialization.
> Perhaps the MAC address was set in the redboot config before.

Yes I used fconfig to set it (I've attached the current parameters below).
Curiously, it seems that init_all_network_interfaces doesn't take into
account the setup of the "ethernet station address" done with
ecos configuration tool (see hw_addr value in the second attachment)
either under RAM or ROM startup modes.

If the MAC address should not be set for the ip stack to work properly,
do you know how I can unset it?

> You could see if it also fails for RAM startup if you enabled the
> "CLAIM_COMMS" virtual vector option in the HAL config.

I've just done the test  with CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_COMMS
macro enabled under RAM startup mode, and ping_test runs just fine.

Fano

Re: [ECOS] App works in RAM but not in flash memory

[Prasad Kamath Nala]

Hi All,
        I am trying to download the eCos1.3.1 for Windows from the site.  But,
It says that "authorization failed".  What has to be done in order to download
the eCos?

regards
Prasad

Re: [ECOS] App works in RAM but not in flash memory

[Jonathan Larmour]

Prasad Kamath Nala wrote:
> 
> Hi All,
>         I am trying to download the eCos1.3.1 for Windows from the site.  But,
> It says that "authorization failed".  What has to be done in order to download
> the eCos?

This is probably your FTP client failing to report properly that there are
too many connections. Try a mirror site:
http://sources.redhat.com/ecos/mirror.html

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

Re: [ECOS] App works in RAM but not in flash memory

[Fano Ramparany]

(with the attachments this time... sorry)

Jonathan Larmour wrote:

> Fano Ramparany wrote:
>
> > My application uses the TCP/IP stack, and used to work (even under ROM
> > startup, but
> > with apparently some time out problems (see. a previous thread in the
> > mailing list
> > under subject "TCP/IP and rom startup mode")), until a major
> > reconfiguration of our intranet.
> > (incl. a change in our IP address). Now even the ping_test doesn't work
> > in ROM  startup mode, although
> > it works ok in RAM startup mode (using gdb).
> >

> My guess is it's something to do with the eth driver initialization.
> Perhaps the MAC address was set in the redboot config before.
>

Yes I used fconfig to set it (I've attached the current parameters below).
Curiously, it seems that init_all_network_interfaces doesn't take into
account the setup of the "ethernet station address" done with
ecos configuration tool (see hw_addr value in the second attachment)
either under RAM or ROM startup modes.

If the MAC address should not be set for the ip stack to work properly,
do you know how I can unset it?

>
> You could see if it also fails for RAM startup if you enabled the
> "CLAIM_COMMS" virtual vector option in the HAL config.

I've just done the test  with CYGSEM_HAL_VIRTUAL_VECTOR_CLAIM_COMMS
macro enabled under RAM startup mode, and ping_test runs just fine.

Fano

RE: [ECOS] App works in RAM but not in flash memory

[Daniel.Andersson]

> Daniel.Andersson@combitechsystems.com wrote:
> > 
> > Hi,
> > 
> > I have some problem with my messages (cyg_mbox_*) in eCos 
> and hope that some
> > of you maybe can give me a hint of what maight be wrong. 
> Currently I am
> > running the entire application in RAM and it works fine. 
> However, when i
> > download the program it into flash then it starts acting 
> very strange. With
> > a trace enabled i can see that some (not all...) messages 
> that are sent
> > between threads dont have any valid data in their header. 
> Every message
> > contains of a header and the data that it contains is just 
> garbage. The
> > first thing i check was that if some process sends an 
> unfilled message but
> > that was not the case.
> > 
> > What can be wrong when an application works fine in RAM but 
> not in flash? I
> > have tried to set the clock to half the speed to give the 
> flash more time to
> > fetch data but the error was still present.
> > 
> > I am using a custom build AT91EB40 with external flash.
> 
> Seems odd certainly. I can't imagine a situation where it 
> would mostly but
> not completely work, in that way. If you had a support 
> contract I could
> look more closely by trying it myself, but otherwise I don't 
> have the time,
> sorry.
> 
> Which situation are you talking about: is it built for "ROM" 
> startup type
> and is running direct from Flash? Or is it built for RAM 
> startup, and being
> loaded into RAM from flash using "fis load"?
> 
> Jifl

I think i have located a few things that causes this error. I have had the
option "include gdb stub in HAL" marked and this is not a good combination
since they interfere with the rest of the code. When i disabled the above
options then I got less strange mbox messages. However, i still get a few
and i think that if i disable all the debug options (and GDB support) in
eCos then my app will run much better. However, I can't get all the debug
info to disaper. I have removed all the debug-flags in the makefiles, both
when building eCos and when building my application. I still get some "debug
info" and "debug lines" in my map-file on address 0x00. How can i remove all
such information?

Regards, Daniel

Re: [ECOS] App works in RAM but not in flash memory

[Jonathan Larmour]

Daniel.Andersson@combitechsystems.com wrote:
> 
> I think i have located a few things that causes this error. I have had the
> option "include gdb stub in HAL" marked and this is not a good combination
> since they interfere with the rest of the code. When i disabled the above
> options then I got less strange mbox messages. However, i still get a few
> and i think that if i disable all the debug options (and GDB support) in
> eCos then my app will run much better.

GDB debugging support (i.e. -g) should never affect the run-time operation
of a program.

> However, I can't get all the debug
> info to disaper. I have removed all the debug-flags in the makefiles, both
> when building eCos and when building my application. I still get some "debug
> info" and "debug lines" in my map-file on address 0x00. How can i remove all
> such information?

That's source code debugging as used by GDB. They shouldn't be marked as
loadable and thus shouldn't be loaded onto your target at all. If they are,
that would be a bug :). You could remove them with objcopy, but I really
don't think this is likely to be your problem.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

[ECOS] App works in RAM but not in flash memory

[Daniel.Andersson]

Hi,

I have some problem with my messages (cyg_mbox_*) in eCos and hope that some
of you maybe can give me a hint of what maight be wrong. Currently I am
running the entire application in RAM and it works fine. However, when i
download the program it into flash then it starts acting very strange. With
a trace enabled i can see that some (not all...) messages that are sent
between threads dont have any valid data in their header. Every message
contains of a header and the data that it contains is just garbage. The
first thing i check was that if some process sends an unfilled message but
that was not the case.

What can be wrong when an application works fine in RAM but not in flash? I
have tried to set the clock to half the speed to give the flash more time to
fetch data but the error was still present.

I am using a custom build AT91EB40 with external flash.

Regards, Daniel

Re: [ECOS] App works in RAM but not in flash memory

[Jonathan Larmour]

Daniel.Andersson@combitechsystems.com wrote:
> 
> Hi,
> 
> I have some problem with my messages (cyg_mbox_*) in eCos and hope that some
> of you maybe can give me a hint of what maight be wrong. Currently I am
> running the entire application in RAM and it works fine. However, when i
> download the program it into flash then it starts acting very strange. With
> a trace enabled i can see that some (not all...) messages that are sent
> between threads dont have any valid data in their header. Every message
> contains of a header and the data that it contains is just garbage. The
> first thing i check was that if some process sends an unfilled message but
> that was not the case.
> 
> What can be wrong when an application works fine in RAM but not in flash? I
> have tried to set the clock to half the speed to give the flash more time to
> fetch data but the error was still present.
> 
> I am using a custom build AT91EB40 with external flash.

Seems odd certainly. I can't imagine a situation where it would mostly but
not completely work, in that way. If you had a support contract I could
look more closely by trying it myself, but otherwise I don't have the time,
sorry.

Which situation are you talking about: is it built for "ROM" startup type
and is running direct from Flash? Or is it built for RAM startup, and being
loaded into RAM from flash using "fis load"?

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine