AW: [ECOS] Huge memory footprint for a simple "hello world"

["Ram Sudhir Tadavarthi" <ram.tadavarthi@netco.de>]

> > 1.Instead of using gdb, can you try to load the image through redboot
> using
> > "load" command and test?
> ~/work/atmel/020606-ARM/install/bin$ arm-elf-gdb redboot.elf
> GNU gdb 5.3 (eCosCentric)
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "--host=i686-pc-linux-gnu --target=arm-elf"...
> (gdb) tar rdi /dev/ttyS0
> Angel Debug Monitor (serial) 1.04 (Advanced RISC Machines SDT 2.5) for
> AT91EB40 (2.00)
> Angel Debug Monitor rebuilt on Apr 07 2000 at 12:40:31
> Serial Rate:   9600
> Connected to ARM RDI target.
> (gdb) set $cpsr=0xd3
> (gdb) load
> Loading section .rom_vectors, size 0x40 lma 0x2020000
> Loading section .text, size 0xb1bc lma 0x2020040
> Loading section .rodata, size 0x1c37 lma 0x202b1fc
> Loading section .data, size 0x404 lma 0x202ce34
> Start address 0x2020040, load size 53815
> Transfer rate: 6331 bits/sec, 498 bytes/write.
> (gdb) cont
> Continuing.
> 
> [1]+  Stopped                 arm-elf-gdb redboot.elf
> ~/work/atmel/020606-ARM/install/bin$ minicom
> RedBoot> AT S7=45 S0=0 L1 V1 X4 &c1 E1 Q0
> 
> ** Error: Illegal command: "AT"
> RedBoot> load -m xmodem
> C*** Abort! Attempt to load ELF data to address: 0x02020000 which is not
> in RAM
> xyzModem - CRC mode, 257(SOH)/0(STX)/0(CAN) packets, 3 retries
> RedBoot>
> 


[Ram ] Well!!! This suggests that you might have memory layout problems/
linker script problems. 

1. What is the memory layout of your platform? 

2. Does your linker script correctly reflect the memory layout of your
platform?




> > 2.Can you check if there is any signal movement on your serial port
> using an
> > oscilloscope or similar ?
> I've no access to an oscilloscope

[Ram ] Well!!! If your company doesn't provide you proper tools to debug,
you will take lot of unnecessary time to bring up the board which might be
expensive than the oscilloscope itself. Anyway try to get access to it.

If you can see any signal movement, then most probably, it might be a wrong
baud rate generation or related.

> 
> >
> > 3.Can you verify your virtual vectors configuration?
> I am new to this, so I would not know which is correct or not.
> 
[Ram ] Yep!!! Try to read the documentation and post here what exactly you
don't understand. Maybe someone would help you if they some time.


Warm regards,
ram



-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss