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.

TMS320F280049: Code can't run after implementing the DCSM feature in F280049

Part Number: TMS320F280049

Hi Team,

  My customer has implemented the DCSM secure and unsecure feature in their code as previous E2E post https://e2e.ti.com/support/microcontrollers/c2000/f/171/t/752952 suggested, and verified with CCS&JTAG for debug;  Very appreciated for Vivek's support.

  Another issue is while disconnected with JTAG, powered off then powered on F280049 again, the code seems didn’t run as the LED in their board is not flashing(there is a LED flashing periodic while code run).  Could you kindly give comments for how to solve this issue?

  Expect for your reply, thanks.

Best Regards

Benjamin

  • Hi Banjamin,

    Have you checked the BOOTMODE pins setting on board to make sure it's set to "GetMode" (which default to Flash BOOT) ? Also I hope all the code is programmed in Flash only.

    Regards,

    Vivek Singh
  • Benjamin, Let me know your finding on the question I asked.

    Regards,
    Vivek Singh
  • Hi Vivek,
    Sorry to reply so later due to the traditional Chinese New Year holiday.
    Double confirmed that the code only programmed to FLASH with correct .cmd file, and the customer side used FLASH boot mode configuration(GPIO24/GPIO32 are both set to 1), also double checked the OTP boot pin configuration which is used as default value.
  • Hi Vivek,
    Double checked follow things:
    Power Supply:
    --VDDIO: 3.3V -> kept as 3.25V;
    --VDD: 1.2V -> used internal LDO, tested as 1.2V;
    --Power up sequence: followed datasheet description;
    XRS:
    --While run the code with DCSM for standalone without JTAG debug, the XRS would periodic pull to GND every 27ms;
    TMS:
    --While run the code with DCSM for standalone without JTAG debug, the TMS kept as High state;

    The issue seems caused by the XRS. Could you kindly help give comments on the XRS things?

    Best Regards
    Benjamin
  • Hi Vivek,
    I have the same problem as this one.
    If there is any progress, please let me know. Thank you.
  • Hi Vivek,
    This issue has been solved by below steps:
    1) Secure All RAM Zone by change the .long 0x55555555 ;B0_Z1OTP_GRABRAM
    2) Secure FLASH Bank1 by change the .long 0x55555555 ;B1_Z1OTP_GRABSECT
    3) change the CMD file for bank1 part:
    b1_dcsm_otp_z1_linkpointer : > B1_DCSM_OTP_Z1_LINKPOINTER PAGE = 0
    b1_dcsm_zsel_z1 : > B1_DCSM_ZSEL_Z1_P0 PAGE = 0

    It seems that the secure zone can't read/write the unsecure zone, could you kindly give comments for such items?

    Best Regards
    Benjamin
  • Benjamin,

    Secure code can read /write the locations in unsecure RAM but unsecure code can not do the same. I feel where all the RAMs were not secure, some unsecure code was trying to access secure area which did not work but when you made everything secure then it worked.

    Regards,
    Vivek Singh
  • Benjamin, any further update on this?