This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Re: Trash when running RAM image
Thanks Gary!
I really should have payed more attention.
Actually, the result was [almost] the same though :(
RedBoot> load -m xm redboot_RAM.srec
CCEntry point: 0x00020040, address range: 0x00020000-0x00046d5c
xyzModem - CRC mode, 3574(SOH)/0(STX)/0(CAN) packets, 5 retries
RedBoot> go
$T050f:54000200;0d:ec0ffd03;#e3
I have also tryed to up load the .bin image (using the -r) but it did
not work out either:
RedBoot> load -r -m xm -b 0x00020040 redboot_RAM.bin
CCRaw file loaded 0x00020040-0x00046d9b, assumed entry at 0x00020040
xyzModem - CRC mode, 1243(SOH)/0(STX)/0(CAN) packets, 2 retries
RedBoot> go
$T0a0f:0002014c;0d:ec0ffd03;#3e
I guess i am almost out of options ... Any other idea of what is still wrong ?
On 5/2/07, Gary Thomas <gary@mlbassoc.com> wrote:
alysson brito wrote:
> Hi
> I am newbie on RedBoot. I am using redboot on an intel board.
> I am [trying] to load and run a RAM image, since I do not want to mess
> up the currently [runnable] image that is on the rom memory and is
> working.
> But the image I got from intel and the image I built from the sources
> are showing up some trash on the console when i execute them
> [for instance: $T0a0f:0c002000;0d:ec0ffd03;#39]. This pattern goes on
> an on for each key I press.
> I am loading the file redboot_RAM.srec [load -v -r -m xmodem -b
> 0x00200000 redboot_RAM.srec] [I also tried via tftp, same result...]
> and shooting "go" ro make it run, but all the time I get this output.
> Would any know what might be wrong ? I'd guess I am executing a some
> memory position that has nothing there ... But I do not know how to go
> on. Any help would be really appreciated.
>
> I also tryed "go redboot_RAM.srec" but it did not work either...
The options you are using for the download is causing the problem.
Try this:
RedBoot> lo -m xm redboot_RAM.srec
RedBoot> go
Your options do two things wrong:
-r: downloads the image raw, which means you've loaded ASCII S-records
into memory - these are not executable instructions
-b: eCos programs are not relocatable, hence they must be loaded at
their native address. 0x200000 is probably not the correct address.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss