Other Parts Discussed in Thread: UNIFLASH
Hello experts,
I have a new sk-am62a-lp evm board, there are several issues when I start to using it:
1) I found there might be some problem about its emmc device, because I can't flash its internal emmc device via uart_uniflash.py:
Parsing config file ... Parsing config file ... SUCCESS. Found 10 command(s) !!! Executing command 1 of 10 ... Found flash writer ... sending sbl_prebuilt/am62ax-sk/sbl_uart_uniflash_stage1.debug.hs_fs.tiimage Sent flashwriter sbl_prebuilt/am62ax-sk/sbl_uart_uniflash_stage1.debug.hs_fs.tiimage of size 281703 bytes in 28.51s. Executing command 2 of 10 ... Command arguments : --file=../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debug.appimage.hs_fs --operation=flash --flash-offset=0x0 Sending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debuSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debuSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debuSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debuSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debuSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debuSending ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debu Sent ../../examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.debug.appimage.hs_fs of size 154302 bytes in 16.03s. [STATUS] SUCCESS !!! Executing command 3 of 10 ... Command arguments : --file=sbl_prebuilt/am62ax-sk/sbl_emmc_linux_stage1.debug.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0 Sent sbl_prebuilt/am62ax-sk/sbl_emmc_linux_stage1.debug.hs_fs.tiimage of size 299495 bytes in 31.16s. [STATUS] SUCCESS !!! Executing command 4 of 10 ... Command arguments : --file=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000 Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimage.hs_fs: 138917bytes [00:15, 10722.44bytes/s]recv error: getc timeout in start sequence Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimage.hs_fs: 138918bytes [00:34, 10722.44bytes/s]recv error: getc timeout in start sequence Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimage.hs_fs: 138919bytes [00:35, 217.78bytes/s]recv error: getc timeout in start sequence Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimage.hs_fs: 138920bytes [00:45, 132.19bytes/s]recv error: getc timeout in start sequence Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimagSending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62ax-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.debug.appimage.hs_fs: 138921bytes [00:56, 84.69bytes/s]recv error: getc timeout in start sequence
so, I have to flash it in slices one by one. After I flashed all items into emmc and booting, it sometimes hung at start point of sbl:
DMSC Firmware Version 9.1.8--v09.01.08 (Kool Koala) DMSC Firmware revision 0x9 DMSC ABI revision 3.1
I attached with CCS and found it's blocking in reading emmc. It can go ahead mostly
2) In mostly, the sbl can go ahead successfully, but will reset while logging into linux at :
[ OK ] Finished Expand the rootfs…full size of the boot device.. [ 8.633401] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 8.665509] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ OK ] Started User Login Management. [ OK ] Started Network Configuration. Starting Network Name Resolution... [ 8.836010] am65-cpsw-nuss 8000000.ethernet eth0: PHY [8000f00.mdio:00] driver [TI DP83867] (irq=POLL) [ 8.845� DMSC Firmware Version 9.1.8--v09.01.08 (Kool Koala) DMSC Firmware revision 0x9 DMSC ABI revision 3.1
and, the mcu-r5, wk-r5 all print nomal logs via other uart channels. When I attached any cpu target via CCS, all the cores will reset, so, I can't find the right point the board's reset.
So, I want to get the right way to find the reason and reset point of the board.
3) Some other informations:
a) If I hit enter key at the u-boot stage, it will not reset.
b) The board will always reset if I booting into the linux in any boot mode.
c) For emmc boot mode, all the image versions (the default sbl-prebuilt or my own builds) will get the same problem,
and, there were two times, it logged into linux successfully without reset(with the same images)
So, How to debug it? Thanks