AM6411: The device cannot be found after burning tispl.bin

user6481287

Part Number: AM6411
Other Parts Discussed in Thread: TMDS64EVM

Tool/software:

Please let us yocto mirror burn TMDS64EVM can burn normally. However, the same image burned to our custom board above the abnormal, the abnormal performance is mainly described as follows:
After the bootloader is burned, it can also be scanned through sudo dfu-util -l, as shown in Figure A.

However, the device cannot be found after tispl.bin is burned, and sometimes the device is abnormally stuck when the

tispl.bin is burned in half, as shown in Figure B.

The serial port output is shown in Figure C below.

May I ask what is the possible cause of this?

1 month ago

0 Nick Saulnier 1 month ago

TI__Guru* 87385 points

Hello,

Did you do anything to port the filesystem image to your new hardware?

Please refer to the AM64x academy, "Porting Linux to Custom Hardware"
https://dev.ti.com/tirex/explore/node?a=7qm9DIS__LATEST&node=A__AThRbFKhWJhPbBm.8vM64w__AM64-ACADEMY__WI1KRXP__LATEST

Regards,

Nick

0 user6481287 29 days ago in reply to Nick Saulnier

Intellectual 760 points

After burning the image by dfu, it is found that the boot0 space of emmc is too small and the image is too large, which leads to the failure of burning. I found that modifying the burning environment variables and then burning, you can burn normally. But the starting position of the image has changed. Can I change the loading address of the image?