MCIMX6S5DVM10AD image entry point

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

MCIMX6S5DVM10AD image entry point

583 Views
hailiu
Contributor IV

I am debugging a bare-metal board with MCIMX6S5DVM10AD processor, using ARM compiler v6 and ARM link v6.0. I build the code with default image layout settings successfully, When I debug the code, I got the error:

ERROR(CMD16-TAD274-NAL18):
! Failed to load "myboardtest.axf"
! Failed to write 5,032 bytes to address S:0x00008000 while writing block of 4,096 bytes to address S:0x00008000
! Bus error on memory operation.

It seems that the address:0x00008000 is used by boot ROM, I tried to set the image entry point to :0x00900000, which is the on chip RAM address, but I got an error:

L6206E: Entry point (0x00900000) lies outside the image.

what is the image entry point should I set? Do I need to set  the RW, RO, etc address also?

 

0 Kudos
4 Replies

571 Views
weidong_sun
NXP TechSupport
NXP TechSupport

Hi Hai Liu,

1. If you do not use an operating system on the i.MX6S board, we will not provide you with support.
2. If you need to know Entry Point, these 2 Links will help you.

--https://community.nxp.com/t5/i-MX-Processors/u-boot-bin-and-u-boot-imx/m-p/276485#M30879

--https://blog.csdn.net/zhaoyun_zzz/article/details/84990606

Have a nice day!

B.R,

Weidong

0 Kudos

560 Views
hailiu
Contributor IV

Weidong,

I already find the solution for this issue. I still need a solution for the USB, my question is: the alternate USB_OTG_ID pin (which is not used by NXP board) matters to boot the device through serial downloader?

0 Kudos

564 Views
hailiu
Contributor IV

Because the USB OTG does not work right now and you gus can not give a solution, I need to debug the hardware to find the problem so that I can load the operation system. the only way to debug the hard ware problem is to run some test code, that's why I need the image entry point.

0 Kudos

579 Views
hailiu
Contributor IV

the linking error issue is resolved by setting RO=0x00900000, in this case, the image entry point is 0x00900000, and the debugger stoped at 0x00900000. It seems the image entry point can be set to 0x00900000.

0 Kudos