• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Answers 2 answers
  • Subscribers 30 subscribers
  • Views 228 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LP-AM243: AM243x HS device -> access PRU cores with load_dmsc.js script not possible

Thomas Mauer
Expert 4860 points
Part Number: LP-AM243

Dear support team,

We face some problem / difference when using HS device vs. using non-HS device of AM243x.

Our objective is to access ICSS via JTAG. When we enabled NO BOOT MODE, and run the load_dmsc.js script on a non-HS device, then we are able to connect to the PRU of ICSS0 and ICSS1.

  • loadJSFile "C:/ti/mcu_plus_sdk_{soc}_{sdk version}/tools/ccs_load/am243x/load_dmsc.js"

 

When we do the same sequence with a HS device, the PRU connect be accessed. JTAG says that they PRU are held in reset.

  • loadJSFile "C:/ti/mcu_plus_sdk_{soc}_{sdk version}/tools/ccs_load/am243x/load_dmsc_hsfs.js"

 

Can you advice how to access ICSS PRU cores on HS device, or provide/add a new .js file?

Regards,

 Thomas

  • 0
    TI__Mastermind 25975 points

    Hi ,

    Thomas Mauer said:
    Can you advice how to access ICSS PRU cores on HS device, or provide/add a new .js file?

    You need to update the sciclient_ccs_init project at this location - <MCU_PLUS_SDK>/examples/drivers/sciclient/sciclient_ccs_init/am243x-evm/r5fss0-0_nortos/ti-arm-clang

    1. Enable the PRU cores in the syscfg.

    2. Rebuild the example and update the *.out file into the existing .js file.

    Try with the updated file. Hope it helps.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Expert 4860 points

    Hi Aakash,

    Thanks for your response. I think I understand your workaround, which is to enable PRU-ICSS in the ARM application.

    However, we would like to don't use any ARM application, but directly enabler the PRU JTAG access via script. This is used to prototype PRU application code, which does not need any ARM setup to get started.

    The non-HS device was enabling PRU after the load_dmsc.js script was sent. But with the HS device, the latest load_dmsc_hsfs.js seem to not enable PRU.

    Is this a setting in the load_dmsc_hsfs.js that was forgotten to be add, like enabling the clock for the PRU-ICSS subsystem? 

    Regards,

     Thomas 

  • 0 in reply to Thomas Mauer
    TI__Mastermind 25975 points

    Hi ,

    There is a slight misunderstanding here.

    The load_dmsc_hsfs already uses a initialization application -

    My ask was to update this application so the PRU clocks are initialized by the initialization application.

    Hope that makes sense.

    Best Regards,
    Aakash

  • 0 in reply to Aakash Kedia
    TI__Expert 4860 points

    Hi Aakash,

    Thanks for the clarification. This fixes the PRU-ICSS access.

    Just to summarize: The sciclient_ccs_init_am243x-lp_r5fss0-0_nortos_ti-arm-clang, which is used by the .js script, must be updated to enable PRU-ICSS support, and must be rebuild.

    - Import the project into CCS

    - Enable PRU-ICSS support

    - Copy the .out file to the <SDK>\tools\ccs_load\am243x folder, and .out file rename to sciclient_ccs_init.release.out

    - Use the .js startup script as before, but now the updated sciclient_ccs_init.release.out does initialize the PRU cores.

    Thanks and best regards,

     Thomas