AM625: Issue with Sending sbl_uart_uniflash_stage2.release.appimage.hs_fs to AM625 via UART Uniflash and Picocom

VINAYAK M K

Part Number: AM625
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello Team,

We are able to send the sbl_uart_uniflash_stage1.debug.hs_fs.tiimage to the chip and it received successfully , but when sending /examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs it fails using both the uart_uniflash.py and using picocom and sending file /resized-image/__size/2560x1600/__key/communityserver-discussions-components-files/791/5672.image-_2800_2_2900_.png

picocom v3.1port is        : /dev/ttyUSB0
flowcontrol    : none
baudrate is    : 115200
parity is      : none
databits are   : 8
stopbits are   : 1
escape is      : C-a
local echo is : no
noinit is      : no
noreset is     : no
hangup is      : no
nolock is      : no
send_cmd is    : sx -vv
receive_cmd is : rz -vv -E
imap is        :
omap is        :
emap is        : crcrlf,delbs,
logfile is     : none
initstring     : none
exit_after is : not set
exit is        : noType [C-a] [C-h] to see available commands
Terminal ready
02000000011a0000616d3632780000000000000048534653010001000100010002a6000000000000d68ecb2c055dff11ade95bd927e837d2a53bc23b0a2800cebce4f106bcf309df2213912d77a157a8b7c2df40672a06a918034aa4c7d603e462481475225d49b8ad0bc40b000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e64ef15c7c00a1b97cb0fbad55cd8d6bacd7bf6d209f8aa8a17537e01684776aCCC
*** file: art_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs
$ sx -vv /home/vipinr/ti/examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs
Sending /home/vipinr/ti/examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs, 1013 blocks: Give your local XMODEM receive command now.
Xmodem sectors/kbytes sent: 14/ 1kRetry 0: CancelledTransfer incomplete.

output of using the uart_uniflash Python script /resized-image/__size/2560x1600/__key/communityserver-discussions-components-files/791/2843.image-_2800_3_2900_.png

This is the log file we are getting when using the uart_uniflash_gui tool
/cfs-file/__key/communityserver-discussions-components-files/791/uart_5F00_uniflash_5F00_gui.log

Kindly help us resolve the above-mentioned issue.

Thank you

8 months ago

0 Vaibhav Kumar 8 months ago

TI__Mastermind 44306 points

Hi,

Thanks for your patience.

Please allow me sometime to read through the logs and get back to you.

Regards,

Vaibhav

+1 Vaibhav Kumar 8 months ago

TI__Mastermind 44306 points

Hi Vinayak,

Can you tell me if you are using a custom EVM or is it a TI EVM?

Additionally check if the device type is HS FS or GP: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1228618/faq-am6xx-how-to-check-if-device-type-is-hs-se-hs-fs-or-gp

Sincerely,

Vaibhav

0 VINAYAK M K 8 months ago in reply to Vaibhav Kumar

Prodigy 20 points

Hi Vaibhav,

We are using a custom SOM designed by referring to the BeaglePlay design files. We have found a few issues in booting from SD card and now trying to explore the other possible ways to boot the device, you may find the details in here.

0 VINAYAK M K 8 months ago in reply to Vaibhav Kumar

Prodigy 20 points

Hi Vaibhav,

Kindly go through the log file I have shared for details. We have used the HS-FS links only here.

0 Vaibhav Kumar 8 months ago in reply to VINAYAK M K

TI__Mastermind 44306 points

Hi,

So you are using a custom SOM, on this note, I want to have one question clarified.

Did you rebuild this application/appimage? /examples/drivers/boot/sbl_uart_uniflash_multistage/sbl_uart_uniflash_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_uart_uniflash_stage2.release.appimage.hs_fs

Or you have the default one which comes in with the SDK?

Regards,

Vaibhav

0 VINAYAK M K 8 months ago in reply to Vaibhav Kumar

Prodigy 20 points

Hello Vaibhav,

We have rebuilt the stage2 file, we used the Makefile provided in the project and did not change anything.

The binary was built without any errors.

Also as per the logs the stage 2 binary is not getting uploaded. Stage1 we are able to upload even using picocom file transfer, but stage 2 upload errors out as shown in the logs.

Regards,

Vinayak

0 Vaibhav Kumar 8 months ago in reply to VINAYAK M K

TI__Mastermind 44306 points

Hi Vinayak,

Please read through: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1264559/am6442-use-the-uart_uniflash-tool-to-flash-the-sbl_null-program-to-qspi-flash-and-report-an-error/4788625#4788625

This makes sure the on chip MSRAM is used.

Let me know if this helps.

EDIT: We are not going to use the on chip MSRAM for AM62x, we are going to make use of the DDR itself, so you would need to replace the custom ddr file and then rebuild the application.

Sincerely,

Vaibhav

0 VINAYAK M K 8 months ago in reply to Vaibhav Kumar

Prodigy 20 points

Hi Vaibhav,

Thanks for the quick response!

Is DDR the issue? Or magic number is the issue?

Could you please recommend what steps to be taken here?

Regards,

Vinayak

0 Prashant Shivhare 8 months ago in reply to VINAYAK M K

TI__Guru 68961 points

Hi,

The default UART_UNIFLASH examples are provided for TI EVM. In case you are using custom EVM, you would have to customize the UART_UNIFLASH examples according to the custom DDR or FLASH part.

Please see the following thread:

https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1339280/am62a7-using-the-script-uart_uniflash-py-burning-am62a-starter-kit-evm-board-can-be-burned-normally-our-board-burning-failed

Regards,

Prashant

Processors

Processors forum

AM625: Issue with Sending sbl_uart_uniflash_stage2.release.appimage.hs_fs to AM625 via UART Uniflash and Picocom