• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 5 answers
  • Subscribers 30 subscribers
  • Views 446 views
  • Users 0 members are here
Support feedback
Options
Options

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.

MCU-PLUS-SDK-AM243X: can't write sbl_null.realease.tiimage to launchpad flash via Uart

Jason Ding
Prodigy 520 points
Part Number: MCU-PLUS-SDK-AM243X
Other Parts Discussed in Thread: UNIFLASH

Hi experts,

I want to download sbl_null.realease.tiimage to launchpad through Uart.

But always get below errors.

I also try to use sbl_jtag_uniflash to flash the sbl_ospi into flash address 0x0, but the problems come from, When I run the JS script, I can't connect to DMSC-M3, but I can connect to R5

If I run load_dmsc_hsfs.js ,there is no errors occur ,But when I write the file through sbl_jtag_uniflash, after the launchpad is set to OSPI boot mode, the R5 actually does not start successfully, because there is nothing on my serial console 

Can you help me check where is wrong?

Thanks so much for your reply!

  • 0
    TI__Mastermind 25975 points

    Hi ,

    As you mention the device you are using is a HS-FS device and not a GP device. You should be using *.hs.tiimage instead of *.tiimage.

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/latest/exports/docs/api_guide_am243x/HSFS_MIGRATION_GUIDE.html

    Also, for running the load_dmsc_hsfs.js, are you in DEV BOOT MODE ?

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Prodigy 520 points

    Hi Aakash,

    Thanks for your reply, I know what your mean, but I'm using launchpad, so I'm afraid I can't run DEV BOOT MODE.

    So I can only use No boot mode, and use load_dmsc.js, but I can't connect to M3 how to solve it？

    Also, why can't I download the .tiimage file to my launchpad through the serial port in UART boot mode?

    Thanks and regards,

    Jason

  • 0 in reply to Jason Ding
    TI__Mastermind 25975 points

    Hi ,

    Jason Ding said:
    So I can only use No boot mode, and use load_dmsc.js, but I can't connect to M3 how to solve it？

    For Launchpad, the DEV-BOOT MODE and the NO-BOOT MODE settings are the same ones. You can use them.

    Use load_dmsc_hsfs.js instead of load_dmsc.js

    Jason Ding said:
    Also, why can't I download the .tiimage file to my launchpad through the serial port in UART boot mode?

    Because it only works with GP device. You need to use *.hs.tiimage for the same.

    For Eg -> Instead of sbl_null.tiimage use sbl_null.hs.tiimage

    Instead of sbl_uart_uniflash.tiimage use sbl_uart_uniflash.hs.tiimage

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Prodigy 520 points

    Hi Aakash,

    Thanks for your reply, After change sbl_uart_uniflash.tiimage to sbl_uart_uniflash.hs.tiimage  and .tiimage  in default_sbl_null.cfg file. I can boot launchpad successfully ,but in latest MCU+SDK documentation ,The description of the launchpad here is still not use *.hs.tiimage. Is it misleading?

    https://software-dl.ti.com/mcu-plus-sdk/esd/AM243X/08_05_00_24/exports/docs/api_guide_am243x/EVM_SETUP_PAGE.html

    By the way, The .hs.tiimage does not seem to start the PRU, in the previous launchpad, I can boot the PRU through the DMSC-M3 script file, and then I can connect the PRU in CCS for debugging.But now I can't connect to the DMSC-M3, and I have to start the PRU through R5, which will make debugging , can you provide a solution? And I don't understand why I can't connect to the DMSC-M3

    Thanks and regards,

    Jason

  • 0 in reply to Jason Ding
    TI__Mastermind 25975 points

    Hi ,

    Jason Ding said:
    Is it misleading?

    The official support for Launchpad with HS-FS device is planned for 08.06 release of MCU_PLUS_SDK. That is why the documentation does not cover the same.

    Jason Ding said:
    But now I can't connect to the DMSC-M3, and I have to start the PRU through R5, which will make debugging , can you provide a solution? And I don't understand why I can't connect to the DMSC-M3

    HS-FS device means the device is Field Secure. For the device to be field secure the DMSC core is closed for the debug access and it cannot be connect. Which script are you using to connect to PRU core ? If you are using load_dmsc.js, it won't work for HS-FS devices. You should be using load_dmsc_hsfs.js.

    Also, the fine solution would be to use SBL NULL. Flash the SBL NULL on the device and load the applications.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Prodigy 520 points

    Hi Aakash,

    In below E2E link, Explains why I need to connect DMSC, run AM243x GEL scripts.

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1045297/faq-am64x-am24x-how-to-use-code-composer-studio-ccs-to-connect-to-pru_icssg

         Also, the fine solution would be to use SBL NULL. Flash the SBL NULL on the device and load the applications

    Yes,I have flashed  sbl_null.release.hs_fs.tiimage to the board, but it doesn't seem to enable the PRU. I can't connect to PRU directly  in CCS 

    SDK vesion :mcu_plus_sdk_am243x_08_05_00_24

    Thanks and regards,

    Jason

  • 0 in reply to Jason Ding
    TI__Mastermind 25975 points

    Hi ,

    I understand your requirement. Ideally the GEL scripts are the debugger scripts which initialize the clocks of peripherals like PRU and that is why you were able to connect to the same.

    SBL NULL initializes the application CPUs. You can choose to run the GEL script which initializes the PRU to enable the PRU cores and connect to the same.

    Also, you can choose to use load_dmsc_hsfs.js as well. After loading the script, you need to load the GEL script that initializes the PRU.

    Hope this helps.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Prodigy 520 points

    Hi Aakash,


    Which script file can be used to enable the PRU? I tried running AM24x.gel on R5, after initializing R5 with SBL NULL, but it doesn't work on R5

    Thanks and regards,

    Jason

  • 0 in reply to Jason Ding
    TI__Mastermind 25975 points

    Hi ,

    Please check this example --> <MCU_PLUS_SDK>/examples/drivers/sciclient/sciclient_ccs_init/am243x-evm/r5fss0-0_nortos OR <MCU_PLUS_SDK>/examples/drivers/boot/sbl_null/am243x-evm/r5fss0-0_nortos

    In this example, before calling the Bootloader_bootSelfCpu, you can call PRUICSS_resetCore & PRUICSS_enableCore for all the PRU cores and this will enable the cores for PRU to load the firmware via CCS.

    Hope this helps.

    Best Regards,
    Aakash