Cart New Account Login

HomeAbout usProductsSupportForumsBlogCustomer Service

search inside this forum
search inside all forums
S32k142 Debug with OpenSDA
Emanuele V. Mar 24, 2020 at 07:52 AM (07:52 hours)
Staff: Zahar R.

  • Good Morning,

    Yesterday I received an S32k142 microcontroller. I flashed in some example code using OpenSDA debugger provided by S32DS IDE. I debugged it several times, and since everything was working like it was expected I took a break. When I was back I tried to connect with the debugger without changing the code. The IDE shows me a window with the following error message: Device is permanently secured (Mass Erase is Disabled). Try to unsecure anyways?. 
    Since then, even if I answer "Yes" the popup is just shown once more. I also tried to enable  Emergency Kinetis Device Recovery by full chip erase but I still cannot connect the debugger to the board even if the debugger shows the correct serial number for it.

    I would like to know if some of you are experiencing the same issue or if you have a solution for it.

    Thanks in advance for your help




    Comments

  • Hi Emanuele, 

    We did see some cases where default demo projects from NXP would leave the device in a permanently secured state.

    Can you please configure the project to generate .srecord object file and email it to zahar at pemicro dot com.

    How are you providing power to your board, from USB or from external power supply. Please take a picture of your setup and email it to the same email address.

    Actually, if you can share your whole project, that would be ideal.

    What version of S32DS are you using?

    What version of PEmicro plugin are you using? You can find out by going to Help -> Install New Software -> already installed and see what version of PEmicro plugin is installed within the IDE layout.

    Best Regards,
    Zahar
    PEmicro.

  • It looks like the device is bricked.

    One of the things that I do want to share, which is not documented in the manual, is the fact that if you secure the device with SEC and FSLACC bits in FSEC register at 0x40C, the device becomes bricked, even following an attempt to issue a mass erase FLASH command.

    Below, is a list of all value writes to FSEC that we are aware off, that will lead to device getting permanently secured.

    On each line, the second digit is an address, the third number is a mask, and a fourth value is an actual write value.

    TEST_VALUE=00/0000040C/00000033/00000020/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/00000033/00000021/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/00000033/00000023/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/0000000F/00000004/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/0000000F/00000005/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/0000000F/00000007/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/0000000F/00000008/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/0000000F/00000009/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/
    TEST_VALUE=00/0000040C/0000000F/0000000B/00/003/007/Data that is about to be programmed will permanently secure the device. Continue?/

    I hope this helps, please let me know if you have any questions.

    Best Regards,
    Zahar
    PEmicro.

Add comment


   Want to comment? Please login or create a new PEmicro account.







© 2020 P&E Microcomputer Systems Inc.
Website Terms of Use and Sales Agreement