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.

TMDSCNCD263P: UNIFLASH : Run Actions Ineffective

Part Number: TMDSCNCD263P
Other Parts Discussed in Thread: UNIFLASH

Tool/software:

Hello,

After flashing the EVM in 1S OSPI boot mode, the following selection doesn't do anything. At least it doesn't run the target:

To run the target I have to pull the power or press the PORz button.


How can I run the target "remotely" please?

  • Hi Kier,

    Thank for your query,

    Could you please elaborate your requirement more? 


    How can I run the target "remotely" please?

    What do you mean by remotely?

  • Hi Nilabh,

    The requirement is for Run Target to work in UNIFLASH via USB.

    I just say "remote" because the EVM may be out of reach when deployed so I cannot press the PORz button in the case.

  • Hi Kier, Please refer to this video on steps to use Uniflash: Getting started with TI UniFlash tool with MCU_PLUS_SDK | Video | TI.com

  • Hi Nilabh,

    Thank you for the video but how does it address the problem?

    Please confirm how to run the application after flashing via XDS110 USB.

    Kier.

  • Hi Kier,

    Flashing using Uniflash is done via either JTAG or UART,: AM263Px MCU+ SDK: Flashing Tools, depending on interface you select you can choose boot mode(DEV boot mode or UART boot mode). 

    Once the flashing has been done successfully,  you need to change the boot mode to OSPI boot mode, then the execution will start.

  • After flashing the EVM in 1S OSPI boot mode,

    This is not correct, as stated in previous reply you need to put boot mode in either UART or dev for flashing to properly work. I am suspecting the flashing has been done properly.

  • This is not correct, as stated in previous reply you need to put boot mode in either UART or dev for flashing to properly work.

    In practice, flashing the board in 1S OSPI mode works just fine. Try it for yourself.

    Let's focus on the question. The assertion is that the UNIFLASH Run Actions are not effective. This is true even if I use DevBoot mode.

    you need to change the boot mode to OSPI boot mode

    The use case is that this EVM may be in an enclosure in a high voltage environment where I cannot change the boot mode switches so it must remain in 1S or 8S OSPI mode. Is this an unusual use case? I don't think so.

    My back up plan is to simply cycle the power but the UniFlash GUI offers the Run Target feature. I would like to use the feature. So the questions are:

    • DevBoot or not, why doesn't 'Run Target' work? Could I be doing something wrong?
    • If there is a technical reason why it doesn't work, what is the reason?
    • Is there a plan to address the reason for future UNIFLASH or EVM?
  • Hi Kier,

    Thank you for te detailed explanation, Now I am able to understand the issue better.

    The reset button in uniflash is not tied to device reset API yet. You will need to manually power cycle the board.

    The use case is that this EVM may be in an enclosure in a high voltage environment where I cannot change the boot mode switches so it must remain in 1S or 8S OSPI mode. Is this an unusual use case? I don't think so.

    True, it will work in 1s also, I initially misunderstood the query.

    Is there a plan to address the reason for future UNIFLASH or EVM?

    I have created an internal backlog ticket for this, I will work on getting back with a feature implementation date.

  • The reset button in uniflash is not tied to device reset API yet. You will need to manually power cycle the board.

    OK, understood. Thank you.

    I have created an internal backlog ticket for this, I will work on getting back with a feature implementation date.

    That's great. Many thanks!

  • Hi Kier,

    I got an feedback from the team today that it is already implemented for AM26x device and I was able to do the same. With AM263Px-cc and Uniflash:

  • Hi Nilabh,

    it is already implemented

    What is already implemented? Reset or Run Target?

    It's not clear what you're showing me in your video. Anyway, reset is not the end objective. The objective is to run the program.

    Let's take a simple example. The LED blink project attached can be flashed in 1S OSPI mode. The LED does not blink after flashing if 'Run Target' is selected. It does blink after cycling the power.

    The question is about the Run Target feature. Is Run Target implemented for this device or not please?rti_led_blink_am263px-cc_r5fss0-0_nortos_ti-arm-clang.zip

  • The question is about the Run Target feature. Is Run Target implemented for this device or not please?rti_led_blink_am263px-cc_r5fss0-0_nortos_ti-arm-clang.zip

    Hi kier Apologies for the delay, Run Target is not implemented, You would need to manually power cycle the board.

  • Run Target is not implemented

    Hi Nilabh,

    OK, thank you. If I'm asked about this then I can at least quote your response that it's not implemented.

    Is there a plan to implement 'Run Target'?

    Meanwhile, we shall arrange to cycle the power.

  • Is there a plan to implement 'Run Target'?

    I have created an internal ticket to track the same. Current estimate is to get it implemented by end of Q12025

    The thing I need to get a clarity is that in OSPI boot mode as soon as system reset happens the bootloader starts running there is not even a need to do run target, so I am inclined to believe that some how rest is not happening properly, Can you try the CCS IDE system reset to do that same.