• State Resolved
  • Locked Locked
  • Replies 37 replies
  • Answers 1 answer
  • Subscribers 99 subscribers
  • Views 1270 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SK-AM62B-P1: SK-AM62B-P1 : Queries regarding the MCU SDK kit and the examples

Shreyan Jain
Intellectual 265 points
Part Number: SK-AM62B-P1
Other Parts Discussed in Thread: UNIFLASH,

I've got a few queries regarding the AM62X evalutation kit:

1. While running the SBL EMMC Linux Multistage on the evaluation kit,it gets stuck while trying to send the secondary bootloader file.
Here's what I'm doing:

  1. Building the example from the example files
  2. including the appimages in the config files
  3. using uart_uniflash.py present in the MCU SDK to flash it into the board. I've tried all 3 config files: default,hs-se and hs-fs,and none of them are working

2. What's the order of running IPC examples?

As far as I'm concerned,this involves pushing the .appimage files ,but I'm not quite sure if I'm supposed to flash them or load them through the ccs IDE's launch target method

I'm open to all suggestions.

Thanks in advance

  • 0
    TI__Guru 73281 points

    Hi Shreyan,

    Shreyan Jain said:
    it gets stuck while trying to send the secondary bootloader file

    Could you please share flashing logs showing the issue you are facing?

    Shreyan Jain said:
    2. What's the order of running IPC examples?

    The IPC examples for multiple cores can be run in any order. They have a sync mechanism in place that helps the examples know if every core participating in the IPC is up & running.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    This is what I get:

    Executing command 4 of 8 ...
Command arguments : --file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112163bytes [00:22, 10716.94bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112164bytes [00:23, 398.47bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112165bytes [00:33, 182.36bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112166bytes [00:43, 102.78bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112167bytes [00:53, 63.34bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112168bytes [01:03, 40.93bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112169bytes [01:13, 27.21bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112170bytes [01:23, 18.41bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112171bytes [01:33, 12.61bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112172bytes [01:43,  8.72bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112173bytes [01:53,  6.06bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112174bytes [02:03,  4.24bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112175bytes [02:13,  2.98bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112176bytes [02:23,  2.11bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112177bytes [02:33,  1.50bytes/s]recv error: getc timeout in start sequence
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112178bytes [02:43,  1.08bytes/s]recv error: getc timeout in start sequence
error_count reached 16, aborting.
Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 1121Sending /home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112180bytes [02:53,  1.27s/bytes]
[ERROR] XMODEM recv failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!

    The 4th command isn't being being executed,this one to be precise:

    -file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

    I also wanted to know,how to check if the device is hs-fs,hs-se or a gp device?

    Regarding the IPC example,it says that we need to load the program into the cores(after connecting to the targets) using CCS,and then run them,but it even says that it needs to be flashed. I've tried loading it and flashing it,but the output doesn't appear.

    I'd be extremely grateful if you could simplify the steps on how to run this example ,emphasizing on which file needs to be loaded and what needs to be flashed,apart from the additional steps.

    All suggestions are welcome,thanks in advance.

    Regards,
    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    Please follow the below thread for the flashing issue. This thread is for AM62A but the same steps & the updated mmcsd_v1.c works for AM62X as well.

    SK-AM62A-LP: flash EMMC using default_sbl_emmc_hs.cfg error - Processors forum - Processors - TI E2E support forums

    Shreyan Jain said:
    I also wanted to know,how to check if the device is hs-fs,hs-se or a gp device?

    The following FAQ should help here

    [FAQ] [AM6XX]: How to check if device type is HS-SE, HS-FS or GP? - Processors forum - Processors - TI E2E support forums

    Shreyan Jain said:
    Regarding the IPC example,it says that we need to load the program into the cores(after connecting to the targets) using CCS,and then run them,but it even says that it needs to be flashed. I've tried loading it and flashing it,but the output doesn't appear.

    Assuming you are working with HSFS device, which should be the case given you are using SK-AM62B-P1, the default flash cfg file default_sbl_emmc_linux_hs_fs flashes IPC examples on both R5F core & M4F core. So, all you need is to successfully flash these images & then IPC example should be up and running.

    Please note the WKUP R5F & M4 core examples UART logs come on different UART ports than the UART port used by the SBL. So, keep all the four UART ports open to capture logs from different cores.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I've did the things mentioned in this link,but even when I load the program,it just shows "Break at address "0x0" with no debug information available, or outside of program code"
    Here are the steps I followed:

    1.Flashed the emmc,got the same error

    2.connected to the R5 core(the image is attached below)

    3. Cleared the CPU using Shift+Cntrl+R,paused it using the "Run" option in the toolbar

    4.Loaded this program:

    /root/workspace_v121/sbl_emmc_linux_stage2_am62x-sk_r5fss0-0_nortos_ti-arm-clang/Debug/sbl_emmc_linux_stage2_am62x-sk_r5fss0-0_nortos_ti-arm-clang.out

    5. It resumes on it own and gives the break error.

    This is the processor I'm dealing with:

    I'm just getting "Break at address "0x0" with no debug information available, or outside of program code.",could you please let me know if I'm going wrong in any step or anything along those lines?

    Thanks in advance.
    PS: Does the IPC example dependent on the sbl_emmc_hs_fs  config file being succesfully flashed,or is there any other process where we can achieve the IPC example,which is completely abstracted from the emmc one?

    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    The SBLs & WKUP R5F examples are not CCS loadables. These need to be booted over some media. For example, here you are flashing the eMMC. If the flashing had been successful then on changing boot mode to eMMC, the SBL & all images would boot successfully.

    Shreyan Jain said:
    is there any other process where we can achieve the IPC example,which is completely abstracted from the emmc one?

    You can boot IPC examples from OSPI & UART as well. Please refer to the following guides:

    AM62x MCU+ SDK: SBL UART (ti.com)

    AM62x MCU+ SDK: SBL OSPI Linux Multistage

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I did,and it worked,but I'd like to boot the arago linux from the internal memory of the EVM. Is there any way you could fix the flashing issue?
    Regards,
    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    Shreyan Jain said:
    Is there any way you could fix the flashing issue?

    We can now focus on making the flashing working on your side.

    I have attached a ZIP file containing two sets of SBL_UART_UNIFLASH binaries. Can you try the flashing with both sets & see if any of them is working?

    sbl_uart_uniflash_images.zip

    In case neither works, can you follow the previously shared thread to debug the SBL_UART_UNIFLASH_STAGE2 to see where exactly it is failing. Once we have the root cause of the failure, we can move quickly to a resolution.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I tried flashing the emmc file with the files you sent,and they did work.

    However,I'm unable to flash the HSM image,which isn't getting in.

    here's the error message:


    here's the config file(default_sbl_emmc_linux_hs_fs.cfg,with the files you sent):

    #-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVM
# - The application image points to relative path of the ipc rpmsg linux application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify-emmc if you just want to verify the flash contents and not flash the file.
#


# First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
#--flash-writer=sbl_prebuilt/am62x-sk/sbl_uart_uniflash_stage1.release.hs_fs.tiimage
--flash-writer=/home/shreyan/ti/prebuilt-images/sbl_uart_uniflash_stage1.release.hs_fs.tiimage


# When sending sbl_uart_uniflash_stage2 binary make sure to flash at SOC memory offset 0x0.
# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
#--file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/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 --operation=flash --flash-offset=0x0
--file=/home/shreyan/ti/prebuilt-images/sbl_uart_uniflash_stage2.release.appimage.hs_fs --operation=flash --flash-offset=0x0

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0 of eMMC
--file=sbl_prebuilt/am62x-sk/sbl_emmc_linux_stage1.release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0

# 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
#--file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/#r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

--file=../../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 --operation=flash --flash-offset=0x0


# When sending application image, make sure to flash at offset 0x100000 (default) or to whatever offset your bootloader is configured for
#--file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/ipc/ipc_notify_echo/#am62x-sk/m4fss0-0_nortos/ti-arm-clang/ipc_notify_echo.release.appimage.hs_fs --operation=flash #--flash-offset=0x100000

#--file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/ipc/ipc_notify_echo/#am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_notify_echo.release.appimage.hs_fs --#operation=flash --flash-offset=0xA00000

# HSM image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/HSMAppimageGen/board/am62x-sk/hsm.appimage.hs_fs --operation=flash-emmc --flash-offset=0x800000

# DM image is flashed at 0xa00000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0xA00000

# Linux image is flashed at 0xC00000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/linux.appimage.hs_fs --operation=flash-emmc --flash-offset=0xC00000

# u-boot.img is flashed at 0x280000
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/u-boot.img --operation=flash-emmc --flash-offset=0x280000


    I tried to reflash it a couple more times,it gets stuck on the very first command. Please let me know if I've to make any chances in the config file. Looking forward on hearing from you.
    Regards,
    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    I am noticing some inconsistencies in the config file like I am not getting why you have commented out the flashing command for sbl_emmc_linux_stage2.release.appimage.hs_fs.

    # 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
#--file=/home/shreyan/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/#r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

--file=../../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 --operation=flash --flash-offset=0x0

    Can you try fresh with the following steps:

    1) Pick the default config file (default_sbl_emmc_linux_hs_fs.cfg) as it is without any changes.

    2) Change only the paths for sbl_uart_uniflash images keeping everything else the same. More specifically, only change the paths of the following to wherever you have saved the previously shared uniflash images from the ZIP file.

    # First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
--flash-writer=sbl_prebuilt/am62x-sk/sbl_uart_uniflash_stage1.release.hs_fs.tiimage

# When sending sbl_uart_uniflash_stage2 binary make sure to flash at SOC memory offset 0x0.
# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
--file=../../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 --operation=flash --flash-offset=0x0

    3) Perform the flashing procedure.

    Please perform the above three steps for both sets of uniflash images I shared. Let me know if any of them works. In case neither works, please share the full flashing logs of failure.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,
    I tried the procedure,fresh,but it's giving the same error:

    Executing command 4 of 9 ...
Command arguments : --file=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112163bytes [00:13, 10713.64bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112164bytes [00:31, 10713.64bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112165bytes [00:33, 217.77bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112166bytes [00:43, 132.20bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112167bytes [00:53, 84.70bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112168bytes [01:03, 55.98bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112169bytes [01:13, 37.73bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112170bytes [01:23, 25.76bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112171bytes [01:33, 17.74bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112172bytes [01:43, 12.30bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112173bytes [01:53,  8.56bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112174bytes [02:03,  5.99bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112175bytes [02:13,  4.21bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112176bytes [02:23,  2.97bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112177bytes [02:33,  2.10bytes/s]recv error: getc timeout in start sequence
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112178bytes [02:43,  1.50bytes/s]recv error: getc timeout in start sequence
error_count reached 16, aborting.
Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_Sending ../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs: 112180bytes [02:53,  1.08bytes/s]
[ERROR] XMODEM recv failed, no response OR incorrect response from EVM OR cancelled by user,
Power cycle EVM and run this script again !!!


    Here's my config file:

    #-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVaM
# - The application image points to relative path of the ipc rpmsg linux application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify-emmc if you just want to verify the flash contents and not flash the file.
#


# First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
--flash-writer=/home/shreyan/ti/prebuilt-images/sbl_uart_uniflash_stage1.release.hs_fs.tiimage

# When sending sbl_uart_uniflash_stage2 binary make sure to flash at SOC memory offset 0x0.
# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
--file=/home/shreyan/ti/prebuilt-images/sbl_uart_uniflash_stage2.release.appimage.hs_fs --operation=flash --flash-offset=0x0

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0 of eMMC
--file=sbl_prebuilt/am62x-sk/sbl_emmc_linux_stage1.release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0

# 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

# When sending application image, make sure to flash at offset 0x100000 (default) or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/m4fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x100000

# HSM image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/HSMAppimageGen/board/am62x-sk/hsm.appimage.hs_fs --operation=flash-emmc --flash-offset=0x800000

# DM image is flashed at 0xa00000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0xA00000

# Linux image is flashed at 0xC00000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/linux.appimage.hs_fs --operation=flash-emmc --flash-offset=0xC00000

# u-boot.img is flashed at 0x280000
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/u-boot.img --operation=flash-emmc --flash-offset=0x280000


    Please do let me know the further steps I need to take

    Regards,
    Shreyan

  • +1 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    I only see the prebuilt-images output here. Have you also tried flashing with the patched images that were there in the ZIP file?

    Regards,

    Prashant

  • +1 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    The patched images did work,and I was able to flash,thank you. I just wanted to know if these are the correct outputs,and what exactly are passed through the cores,and if we can actually view them.


    I think I'm missing the "All tests have passed!!" message.
    PS: The evm kit doesn't boot up without the SD card,doesn't flashing it with the emmc config file cause it to boot throught the emmc instead of the sd card(after setting the boot mode to emmc mode)
    Regards,
    Shreyan

  • +1 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    Shreyan Jain said:
    I just wanted to know if these are the correct outputs,and what exactly are passed through the cores,and if we can actually view them.

    The output is correct. The default code just communicates the current message number as the payload. You can adapt it according to your use case & print the messages being sent & received with the DebugP_log macro.

    And there is no "All tests have passed!!" message because there is no such string in the IPC_RPMSG_ECHO_LINUX example

    ~/ti/mcu_plus_sdk/am62x 09.01.00.39
❯ grep -r "All tests have passed" -- examples/drivers/ipc
grep: examples/drivers/ipc/ipc_rpmsg_echo/am62x-sk/system_freertos_nortos/ipc_rpmsg_echo_system.debug.appimage.hs_fs: binary file matches
grep: examples/drivers/ipc/ipc_rpmsg_echo/am62x-sk/system_freertos_nortos/ipc_rpmsg_echo_system.release.appimage.hs_fs: binary file matches
grep: examples/drivers/ipc/ipc_rpmsg_echo/am62x-sip-sk/system_freertos_nortos/ipc_rpmsg_echo_system.debug.appimage.hs_fs: binary file matches
grep: examples/drivers/ipc/ipc_rpmsg_echo/am62x-sip-sk/system_freertos_nortos/ipc_rpmsg_echo_system.release.appimage.hs_fs: binary file matches
examples/drivers/ipc/ipc_rpmsg_echo/ipc_rpmsg_echo.c:    DebugP_log("All tests have passed!!\r\n");
examples/drivers/ipc/ipc_rpmsg_echo/ipc_rpmsg_echo.c:    DebugP_log("All tests have passed!!\r\n");
examples/drivers/ipc/ipc_rpmsg_echo_qnx/ipc_rpmsg_echo_qnx.c:    DebugP_log("All tests have passed!!\r\n");
grep: examples/drivers/ipc/ipc_notify_echo/am62x-sk/system_freertos_nortos/ipc_notify_echo_system.debug.appimage.hs_fs: binary file matches
grep: examples/drivers/ipc/ipc_notify_echo/am62x-sk/system_freertos_nortos/ipc_notify_echo_system.release.appimage.hs_fs: binary file matches
grep: examples/drivers/ipc/ipc_notify_echo/am62x-sip-sk/system_freertos_nortos/ipc_notify_echo_system.debug.appimage.hs_fs: binary file matches
grep: examples/drivers/ipc/ipc_notify_echo/am62x-sip-sk/system_freertos_nortos/ipc_notify_echo_system.release.appimage.hs_fs: binary file matches
examples/drivers/ipc/ipc_notify_echo/ipc_notify_echo.c:    DebugP_log("All tests have passed!!\r\n");

    Shreyan Jain said:
    The patched images did work

    I would like you to know that the patched uniflash images were generated with the updated mmcsd_v1.c from the other previously shared thread. However, you previously said this did not work for you. I guess you might have missed something due to which uniflash images didn't work for you even after updating mmcsd_v1.c

    I would recommend you to update the mmcsd_v1.c source file in your installed SDK to ensure any example using the eMMC driver works. I will iterate the steps here:

    1) Replace the mmcsd_v1.c source file in the SDK with the updated mmcsd_v1.c in the other thread.

    2) Rebuild the libraries for both profiles.

    make -s libs PROFILE=release all
make -s libs PROFILE=debug all

    3) Rebuild any example you are using.

    4) Test the sbl_uart_uniflash images to see if they are working.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    I did that and used the patched images,and yes they work. Nevertheless,I can't seem to boot it up without the SD card,even though it's emmc flash,what could be the reason for that?
    Thanks and regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    Shreyan Jain said:
    Nevertheless,I can't seem to boot it up without the SD card,even though it's emmc flash,what could be the reason for that?

    I am not sure if I understand the issue. Are you not able to boot the Linux without the SD card? If you can share some logs showing the issue that will be of help.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    Yes,I'm not able to boot the Linux without the SD card. Say,I power up the board without the SD card(after booting the emmc example with the ipc application),this is what I get:


    The successful results that I've shared in the previous replies are the ones that I got after putting the SD card. Is there any way to get the same without the SD card?

    Thanks and regards,
    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    This is expected. You have to flash the Linux rootfs filesystem into eMMC. Please follow the below guide

    Flash Linux to eMMC (ti.com)

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,
    Say,I flash the rootfs to the emmc,will the emmc linux program be flashed alongside it,or will it rewrite it?
    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    The eMMC is hardware partitioned as follows

    +---------+---------+--------+----------------------------------+
|  boot0  |  boot1  |  rpmb  |          User Data Area          |
+---------+---------+--------+----------------------------------+

    When you flash Linux into eMMC, you flash it to UDA partition. The UART Uniflash on the other hand flashed the images into BOOT0 partition.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,

    Thank you for the detailed insights,and your valuable time. Would you mind recommending some additional documents about the whole emmc flow, and prequisites to know before working on it?

    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    TI__Guru 73281 points

    Hello Shreyan,

    You may find the following resource helpful

    https://dev.ti.com/tirex/explore/node?node=A__Acn8P30tycjABW-cmbqdOw__AM62-ACADEMY__uiYMDcq__LATEST

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM62X/09_01_00_39/exports/docs/api_guide_am62x/EXAMPLES_DRIVERS_SBL_EMMC_LINUX_MULTISTAGE.html

    If you have specific queries, you can search around the E2E or raise another thread with the query.

    Regards,

    Prashant

  • 0 in reply to Prashant Shivhare
    Intellectual 265 points

    Dear Prashant,
    I tried following this thread but I'm getting the following errors while trying to fix it:

    root@am62xx-evm:/home# sudo dd if=tiboot3.bin of=/dev/mmcblk0boot0 seek=0
sudo: unable to resolve host am62xx-evm: Temporary failure in name resolution
dd: writing to '/dev/mmcblk0boot0': Operation not permitted
1+0 records in
0+0 records out
0 bytes copied, 0.000396535 s, 0.0 kB/s

    Any suggestions on how to proceed further from this?
    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    Intellectual 870 points

    Hi ,

     Please tell your exact problem is 2nd stage bootloader error your using emmc boot mode please confirm first.

    Regards,

    Veerapandiyan V.

  • 0 in reply to veerapandiyan v
    Intellectual 265 points

    Dear Veerapandiyan V,

    Yes,my issue lies in the secondary bootloader.

    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    Intellectual 870 points

    Hi Shreyan,

    Please tell your board version, proccessor version and MCU+SDK version send me.

    Regards,

    Veerapandiyan V.

  • 0 in reply to veerapandiyan v
    Intellectual 265 points

    Dear Veerapandiyan V.,
    My MCU sdk version is am62x09010039

    Processor SDK version is 09.01.00.08

    Board is AM62B-p1
    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    Intellectual 870 points

    Hi Shreyan,

    Your using AM62B-P1 HS-FS board correct please confirm. Please send your default_sbl_emmc_linux_hs_fs.cfg  file.

    Regards,

    Veerapandiyan V.

  • 0 in reply to veerapandiyan v
    Intellectual 265 points 

    #-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVaM
# - The application image points to relative path of the ipc rpmsg linux application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify-emmc if you just want to verify the flash contents and not flash the file.
#


# First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
--flash-writer=/home/shreyan/ti/patched-images/sbl_uart_uniflash_stage1.release.hs_fs.tiimage

# When sending sbl_uart_uniflash_stage2 binary make sure to flash at SOC memory offset 0x0.
# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
--file=/home/shreyan/ti/patched-images/sbl_uart_uniflash_stage2.release.appimage.hs_fs --operation=flash --flash-offset=0x0

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0 of eMMC
--file=sbl_prebuilt/am62x-sk/sbl_emmc_linux_stage1.release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0

# 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

# When sending application image, make sure to flash at offset 0x100000 (default) or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/m4fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x100000

# HSM image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/HSMAppimageGen/board/am62x-sk/hsm.appimage.hs_fs --operation=flash-emmc --flash-offset=0x800000

# DM image is flashed at 0xa00000 or to whatever offset your bootloader is configured for
--file=../../examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0xA00000

# Linux image is flashed at 0xC00000 or to whatever offset your bootloader is configured for
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/linux.appimage.hs_fs --operation=flash-emmc --flash-offset=0xC00000

# u-boot.img is flashed at 0x280000
--file=../../tools/boot/linuxAppimageGen/board/am62x-sk/u-boot.img --operation=flash-emmc --flash-offset=0x280000

    hope this is okay.

    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    Intellectual 870 points

    Hi Shreyan,

    Please change the line 29,32,35,38,41,44 below format :

    #-----------------------------------------------------------------------------#
#                                                                             #
#      DEFAULT CONFIGURATION FILE TO BE USED WITH THE FLASHWRITER SCRIPT      #
#                                                                             #
#-----------------------------------------------------------------------------#
#
# By default this config file,
# - points to pre-built flash writer, bootloader for this EVM
# - The application image points to relative path of the ipc rpmsg linux application image for this EVM
#   - Make sure this application is built before running this script
# - You can customized this config file to point to your own bootloader and/or application images
# - You can use --operation=flashverify-emmc if you just want to verify the flash contents and not flash the file.
#


# First point to sbl_uart_uniflash_stage1 binary, which initialises DDR and receives sbl_uart_uniflash_stage2 binary
--flash-writer=sbl_prebuilt/am62x-sk/sbl_uart_uniflash_stage1.release.hs_fs.tiimage

# When sending sbl_uart_uniflash_stage2 binary make sure to flash at SOC memory offset 0x0.
# Points to sbl_uart_uniflash_stage2 binary, which function's as a server to flash one or more files to eMMC
--file=/home/bpt/ti/mcu_plus_sdk_am62x_09_01_00_39/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 --operation=flash --flash-offset=0x0

# Now send one or more files to flash or flashverify as needed. The order of sending files does not matter

# When sending bootloader make sure to flash at offset 0x0. ROM expects bootloader at offset 0x0 of eMMC
--file=sbl_prebuilt/am62x-sk/sbl_emmc_linux_stage1.release.hs_fs.tiimage --operation=flash-emmc --flash-offset=0x0

# 2nd stage bootloader is flashed at 0x80000 or to whatever offset your bootloader is configured for
--file=/home/bpt/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/boot/sbl_emmc_linux_multistage/sbl_emmc_linux_stage2/am62x-sk/r5fss0-0_nortos/ti-arm-clang/sbl_emmc_linux_stage2.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0x80000

# When sending application image, make sure to flash at offset 0x100000 (default) or to whatever offset your bootloader is configured for
--file=/home/bpt/workspace_v09.01/gpio_led_blink_am62x-sk_m4fss0-0_nortos_ti-arm-clang/Debug/gpio_led_blink_am62x-sk_m4fss0-0_nortos_ti-arm-clang.appimage.hs_fs --operation=flash-emmc --flash-offset=0x100000

# HSM image is flashed at 0x800000 or to whatever offset your bootloader is configured for
--file=/home/bpt/ti/mcu_plus_sdk_am62x_09_01_00_39/tools/boot/HSMAppimageGen/board/am62x-sk/hsm.appimage.hs_fs --operation=flash-emmc --flash-offset=0x800000

# DM image is flashed at 0xa00000 or to whatever offset your bootloader is configured for
--file=/home/bpt/ti/mcu_plus_sdk_am62x_09_01_00_39/examples/drivers/ipc/ipc_rpmsg_echo_linux/am62x-sk/r5fss0-0_freertos/ti-arm-clang/ipc_rpmsg_echo_linux.release.appimage.hs_fs --operation=flash-emmc --flash-offset=0xA00000

# Linux image is flashed at 0xC00000 or to whatever offset your bootloader is configured for
--file=/home/bpt/ti/mcu_plus_sdk_am62x_09_01_00_39/tools/boot/linuxAppimageGen/board/am62x-sk/linux.appimage.hs_fs --operation=flash-emmc --flash-offset=0xC00000

# u-boot.img is flashed at 0x280000
--file=/home/bpt/ti/mcu_plus_sdk_am62x_09_01_00_39/tools/boot/linuxAppimageGen/board/am62x-sk/custom/u-boot.img --operation=flash-emmc --flash-offset=0x280000

    Regards, 

    Veerapandiyan V.

  • 0 in reply to veerapandiyan v
    Intellectual 265 points

    Pardon me,change to what exactly?
    Have you changed it in the one you sent or should I make any additional changes?
    Regards,

    Shreyan

  • 0 in reply to Shreyan Jain
    Intellectual 870 points

    Hi Shreyan,

    I did not edit ur file please check my referce file to edit your pc ok. I send file is my pc location. please edit for your pc location.

    Regards,

    Veerapandiyan.

  • 0 in reply to veerapandiyan v
    Intellectual 265 points

    Dear Veerapandiyan,

    What's the purpose of LED blinking image's appimage(line 32),and does it affect sudo and dd command not working ?
    Can I replace it with any other image file?
    Regards,
    Shreyan

  • +1 in reply to Shreyan Jain
    Intellectual 870 points

    Hi Shreyan,

    No problem.you edit your application code. I implemented for led blink code you change it no problem after you send the file once verify after that load the file.

    Regards,

    Veerapandiyan V.

  • 0 in reply to veerapandiyan v
    Intellectual 870 points

    Hi Shreyan,

    Any update tell me.

    Regards, 

    Veerapandiyan V.

  • 0 in reply to veerapandiyan v
    Intellectual 870 points

    Hi Shreyan,

    Your problem solved.

    Regards, 

    Veerapandiyan V.

  • 0 in reply to Shreyan Jain
    Intellectual 870 points

    Hi Shreyan,

    Ok.

    Regards, 

    Veerapandiyan V.