Hello,
I use B2_config, the image created confused me.
Here is the log:
#arm-linux-gdb u-boot GNU gdb 6.2.1 Copyright 2004 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-linux"... (gdb) file u-boot Load new symbol table from "/project/u-boot/u-boot"? (y or n) y Reading symbols from /project/u-boot/u-boot...done. (gdb) info address _start Symbol "_start" is at 0xc100000 in a file compiled without debugging. (gdb) info address reset Symbol "reset" is at 0xc100030 in a file compiled without debugging. (gdb) info address cpu_init_crit Symbol "cpu_init_crit" is at 0xc1000b0 in a file compiled without debugging.
The address of '_start', supposed would be 0x00000000, however it is 0xc100000, so does the 'reset'/'cpu_init_crit"/all the other symbols....
When i cp this image into the flash, and use BDI2000. The BDI2000 looks like can't recognize the 0xc10.... address, it always announce 'hardware breakpoints full', while the arm-linux-gdb prompts 'invalid memory address accessed....'
I have a little experience with the U-boot on PPC platform, i recall _start/entry-point always be at the 0x00000000, which BDI2000 fetch it from the start point of the flash. However i am brand newbie to the arm platform, so i guess i might have this or that mistake on the image creation.
Am i breaking some building rules when i create the image? Could any big brother give me a hand?
Really appreciated!!!
_______________________________ Do you Yahoo!? Declare Yourself - Register online to vote today! http://vote.yahoo.com