• State Resolved
  • Locked Locked
  • Replies 14 replies
  • Answers 2 answers
  • Subscribers 82 subscribers
  • Views 485 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.

TMS320F28379D: How to connect emulator and erase the chip

Piotr Romaniuk
Expert 2830 points
Part Number: TMS320F28379D
Other Parts Discussed in Thread: UNIFLASH

Hi,

I am trying to explore security features in TMS320F28379D. I already programmed some bootloader into device FLASH memory.
Next I programmed OTP registers:
1) Z1-GRABRAM,
2) Z1-GRABSECT
3) Z1- CMPSWD0-3 (I know that password)

How can I connect the emulator and erase the chip using tools like UniFlash or the CCS?

Kind regards,
Piotr Romaniuk

  • +1
    TI__Guru** 113655 points

    Hi,

    In CCS, you can connect and then open OnChip Flash Tool (Tools -> OnChip Flash) and provide correct password in the password GUI field and then should able to erase the flash. Please note that you can not erase the security settings because that is stored in OTP (One Time Programmable) Flash. If you are facing issue with connect phase then you will need to change the BOOTMODE pin setting to WAIT BOOT (refer device TRM to check WAIT BOOT setting) and then try to connect.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2830 points

    Hi,

    I have no "OnChip Flash" in menu Tools. The menu is present in debug perspective only. 
    I use CCS 11.1.0.00011

    I cannot connect, and when I try I receive the message:

    How to connect without programming?

    Kind regards,
    Piotr Romaniuk

  • 0 in reply to Piotr Romaniuk
    TI__Guru** 113655 points

    Hi,

    Piotr Romaniuk said:
    How to connect without programming?

    You need to use TargetConfiguration view and select the correct target configuration file, right click on it and launch it. After launching the target configuration, right click on the CPU target and click on connect. 

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2830 points

    Hi,

    When I launch the configuration as you instructed it starts fine.
    Unfortunatelly, when I try to connect I have following error:

    Regards,
    Piotr Romaniuk

    PS
    I upgraded CCS to v12.

  • 0 in reply to Piotr Romaniuk
    TI__Guru** 113655 points

    Do you have WAIT BOOT mode on the board ?

  • 0 in reply to Vivek Singh
    Expert 2830 points

    No, I have not. I have no jumpers to change it. I don't know what is set in boot ROM.

    My bootloader in flash is started and it sets up at the beginning of the main():

    //EMU_BOOTCTRL = EMU_BOOT_FLASH | EMU_KEY
    *(Uint32 *)0xD00 = 0x0B5A;

    Regards,

    Piotr Romaniuk

  • 0 in reply to Piotr Romaniuk
    Expert 2830 points

    I found boot pins on the board, I was able to control them. 

    I hold following logic states during power on (they correspond to wait boot mode):

    GPIO72 1
    GPIO84 0

    and the program from BootROM did not start my bootloader (that one in flash memory) but remained in its space at address 0x3FF16A.
    Then I connected to target as you said in CCS. Next in On-Chip Flash tab there was Unlock button.

    Thank you for your help.

    I found in the chip documentation that wait boot should happen if the emulator is connected. Why it was not in my case?
    (I use xds100v3)

    Regards,
    Piotr Romaniuk

  • 0 in reply to Piotr Romaniuk
    TI__Guru** 113655 points

    Hi,

    Piotr Romaniuk said:
    I found in the chip documentation that wait boot should happen if the emulator is connected. Why it was not in my case?

    Can you please send the snapshot from documentation which has this reference.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2830 points

    Hi,

    I have GPIO72 and 84 pulled up, so they are logic ones at power up. This means that GetBootMode/Flash is selected. In the documentation there is a statement:

    So I concluded that connection the emulator is enought to enter wait mode in bootROM.

    Regards,
    Piotr Romaniuk

  • 0 in reply to Piotr Romaniuk
    TI__Guru** 113655 points

    Hi,

    What this says is that when emulator is connected to device (not physical connection but actual connect) and then user want to boot the device (by issuing a soft reset or any other CPU reset), the Get boot mode will default to Wait Boot.

    Now in this case you are not able to connect to device at all so this is not applicable. 

    Hope this is clear.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2830 points

    Thank you for information.

    Regards,
    Piotr Romaniuk

  • 0 in reply to Piotr Romaniuk
    TI__Guru** 113655 points

    If there are no further queries on this, please mark this resolved.

    Regards,

    Vivek Singh

  • 0 in reply to Vivek Singh
    Expert 2830 points

    Hi,

    Thank you for your help.
    Yestarday, I did marked by 'This resolved my issue' your first answer - there was everything about the question. Further discussion were detailes and the help me to understand. I thought about another people when they find the question and what is the main resolution that will be highlighted. 

    Should I mark the last one as well? or close this question some another way?

    Regards,
    Piotr Romaniuk

  • 0 in reply to Piotr Romaniuk
    TI__Guru** 113655 points

    Thank you for the confirmation. I'll close the post.

    Regards,

    Vivek Singh