This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
How to make a code from RAM startup to ROM startup?
- To: <ecos-discuss at sources dot redhat dot com>
- Subject: [ECOS] How to make a code from RAM startup to ROM startup?
- From: "Ling Su" <lingsu at palmmicro dot com>
- Date: Fri, 13 Apr 2001 20:29:16 -0700
- Organization: Palm Microsystems, Inc.
- Reply-To: "Ling Su" <lingsu at palmmicro dot com>
Hello everyone,
I am nearly finished debugging my code using RAM startup binary and GDB
stub, so I am looking for the method to make a ROM startup binary so that I
can burn it into a FLASH. Anyone can highlight me the steps I should follow?
Now I have a couple questions as following,
<1>. I changed the CYG_HAL_STARTUP from RAM to ROM in ecos.ecc, is that
enough?
<2>. If my code have some diag_printf() procedure call, should I remove
them?
<3>. Actually we I debugging my code, I find the serial port 1 is very
unstable due to the use of diag_printf(), since the call doesn't go through
serial driver, and some conflicts will happen easily when I am writing to
serial 1, and diag_printf write to serial 0. If I use GDB to debug, I am not
sure if gdb stub will keep polling the serial port if I doesn't set up any
break point and just let it free run after downloading the code, since I
always meet serial port write failure, I think this point might be
suspicious. Anyone know this? Please shed me some light! Thanks!
Best Regards,
-Ling