This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: App works in RAM but not in flash memory


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]