»
Quick Links
Page 1 of 1
Could not run axf formatted u-boot for ARM11 mpcore using RealView developer suite V2.1
#1
Posted 29 November 2011 - 10:39 AM
Dear experts,
I need to update uboot of CNS3420(core arm11) cavium networks Econa processor(target board is CNS3420 Evb 2.x).
for which i have successfully connected target board from realview debugger through realview ICE.
then after i am loading cli command file xxx.inc from "Include Commands from file...." tab, and it also get completed successfully.
then after i am loading axf formatted u-boot. at that time it gives warning like....
Warning: entry point is 0 - may be undefined.
is it normal?
after that i tried to run it from debug->run(go), but could not start it .
the output of debugger is like....
> go
No source available for module START_S\.
Stopped on Illegal Instruction
Stopped at 0x1000001C: <No Module>
Please put your comment on this or any suggestion to resolve this issue.
I have attached out put log of debugger with it.
Thanks,
Darshan Prajapati.
I need to update uboot of CNS3420(core arm11) cavium networks Econa processor(target board is CNS3420 Evb 2.x).
for which i have successfully connected target board from realview debugger through realview ICE.
then after i am loading cli command file xxx.inc from "Include Commands from file...." tab, and it also get completed successfully.
then after i am loading axf formatted u-boot. at that time it gives warning like....
Warning: entry point is 0 - may be undefined.
is it normal?
after that i tried to run it from debug->run(go), but could not start it .
the output of debugger is like....
> go
No source available for module START_S\.
Stopped on Illegal Instruction
Stopped at 0x1000001C: <No Module>
Please put your comment on this or any suggestion to resolve this issue.
I have attached out put log of debugger with it.
Thanks,
Darshan Prajapati.
#2
Posted 30 November 2011 - 02:42 PM
<quote>
Warning: entry point is 0 - may be undefined.
</quote>
Yep...An ELF image usually contains something called an entry point. This is the address the debugger should set the PC when it loads the image. When no entry point is specified at build time the field typically gets left at 0. Of course its also possible that you specify an entry point of 0. Several debuggers I've used have warned when the entry point is 0, because it doesn't know whether its actually 0 or just blank. Given what you're loading, 0 seems sensible - but might be worth checking.
<quote>
> go
No source available for module START_S\.
</quote>
It couldn't find the source code to display for the current PC location.
<quote>
Stopped on Illegal Instruction
Stopped at 0x1000001C: <No Module>
</quote>
The target stopped due to an Undef exception (probably)
Warning: entry point is 0 - may be undefined.
</quote>
Yep...An ELF image usually contains something called an entry point. This is the address the debugger should set the PC when it loads the image. When no entry point is specified at build time the field typically gets left at 0. Of course its also possible that you specify an entry point of 0. Several debuggers I've used have warned when the entry point is 0, because it doesn't know whether its actually 0 or just blank. Given what you're loading, 0 seems sensible - but might be worth checking.
<quote>
> go
No source available for module START_S\.
</quote>
It couldn't find the source code to display for the current PC location.
<quote>
Stopped on Illegal Instruction
Stopped at 0x1000001C: <No Module>
</quote>
The target stopped due to an Undef exception (probably)
Share this topic:
Page 1 of 1















