TC4xx promo banner Banner_Aurix_Competition Banner_AURIX_Security-Solution Banner_AURIX_Safety_Products ShieldBuddy TC275 Banner_AURIX_DevelopmentStudio


+ Reply to Thread
Results 1 to 6 of 6

Thread: TC37x Error Debug Port Secured after flashing wrong .s19 HSM Sw and then enabled HSM.

  1. #1

    TC37x Error Debug Port Secured after flashing wrong .s19 HSM Sw and then enabled HSM.

    I am getting the error "Debug Port Secured" on TC37x.
    I was trying to flash HSM software using Lauterbach after checking that HSM is disabled. By mistake I did flashed the wrong .s19 as HSM software and then enabled the HSM.
    Now I am not able to do any thing. It seems I am locked out of the ECU.

    Is any body know any procedure so that I can unlock the ECU ?

  2. #2
    Intermediate Intermediate
    Infineon Employee
    Infineon Employee
    Darren Galpin is on a distinguished road
    Join Date
    May 2020
    Posts
    119
    Points
    2475
    Are you able to read the CBS_COMDATA register at all, where the system software reports an error during boot, or is it completely locked out?
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

  3. #3
    Intermediate Intermediate
    Infineon Employee
    Infineon Employee
    Darren Galpin is on a distinguished road
    Join Date
    May 2020
    Posts
    119
    Points
    2475
    So the error message is generated by the Lauterbach software - see https://www2.lauterbach.com/pdf/error.pdf.
    It then says to see the "Processor Architecture Manual" on how to unsecure the debug port of the processor, which isn't too helpful!

    Please could you take a look at chapter 8.2.2.3 Halt After Reset of the architecture manual, and specifically the sub-section "Halt after Power on Reset", and see whether this allows you to then access things via the debug?
    Last edited by Darren Galpin; Jan 22nd, 2021 at 09:34 AM.
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

  4. #4
    Could you attach the TC37x Architecture Manual where you are pointing these section.

    chapter 8.2.2.3 Halt After Reset of the architecture manual, and specifically the sub-section "Halt after Power on Reset".

    What do you mean by completely locked out.
    Right now I am not able to interact with the target as the Debug port is not allowing me to connect.
    Though I have bootloader and Application flashed into it but the problem I believe HSM UCBs are corrupted since I have flashed wrong .s19 file for HSM sw and then enabled the HSM.

    It will be really helpful if you could tell if it is really possible to again connect through that secured debug port.

  5. #5
    Intermediate Intermediate
    Infineon Employee
    Infineon Employee
    Darren Galpin is on a distinguished road
    Join Date
    May 2020
    Posts
    119
    Points
    2475
    The UCBs are in DFlash, but S19 is in PFlash - you have not corrupted the UCBs here.

    The Aurix TC3xx user manual is at https://www.infineon.com/dgdl/Infine...717d3605221d96

    I do not know enough to know whether you can or cannot connect through the debug port now. By changing S19, you have changed the HSM boot code, but not the device boot up sequence. Hence the start up software should still evaluate, and should have set up the device correctly until the HSM starts running, which is when you then potentially have the incorrect code.
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

  6. #6
    Advanced Advanced
    Infineon Employee
    Infineon Employee
    MoD is on a distinguished road
    Join Date
    Feb 2012
    Location
    Munich
    Posts
    234
    Points
    4709.375
    Enabling HSM with invalid code for HSM will lock the device for ever. There is no possibility to recover the device. You must exchange the device.
    The views expressed here are my personal opinions, have not been reviewed or authorized by Infineon and do not necessarily represent the views of Infineon.

+ Reply to Thread

Tags for this Thread

Disclaimer

All content and materials on this site are provided “as is“. Infineon makes no warranties or representations with regard to this content and these materials of any kind, whether express or implied, including without limitation, warranties or representations of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. No license, whether express or implied, is granted by Infineon. Use of the information on this site may require a license from a third party, or a license from Infineon.


Infineon accepts no liability for the content and materials on this site being accurate, complete or up- to-date or for the contents of external links. Infineon distances itself expressly from the contents of the linked pages, over the structure of which Infineon has no control.


Content on this site may contain or be subject to specific guidelines or limitations on use. All postings and use of the content on this site are subject to the Usage Terms of the site; third parties using this content agree to abide by any limitations or guidelines and to comply with the Usage Terms of this site. Infineon reserves the right to make corrections, deletions, modifications, enhancements, improvements and other changes to the content and materials, its products, programs and services at any time or to move or discontinue any content, products, programs, or services without notice.