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.

F28M36P63C2: Concerto F28M36 unable to access the DAP problem

Part Number: F28M36P63C2

Hello,

We use a custom board with Concerto F28M36P63C2 and a XDS200 USB debugger.

After a flash programming procedure with our custom tool we cannot connect to M3 core anymore and the CCS displays the following message

We tried to put device in "wait-in-reset" mode by setting EMU0 = 0 and EMU1 = 1 but we still cannot connect to M3 core.

Also, we tried all suggestions from the forum but without success (eg connect to IcePick and then reset device).

Is there any solution in order to overcome this problem?

Regards,

Kostas

  • I finally achieved to connect to M3 core but when I try to unlock or erase flash using Tools -> On-Chip Flash the following message appears

    "Target is not connected or does not support current Flash operation."

    Any help would be appreciated.

    Kostas

  • Kostas,

    When you programmed the flash, did you also program a value to the DCSM passwords, enabling security.  Can you give more details on the steps you needed to get the connection to work.

    Best,

    Matthew

  • Matthew,

    I put device in WIR by using EMU0 = 0 and EMU1 = 1 when coming out of reset and I connected to M3 core as shown below.

    DCSM passwords have wrong values and I am trying to unlock and erase flash doing the following:

    In On-Chip Flash dialog, I press Unlock button

    and the following message appears.

    Some times the following message appears in console

    and finally

    and the target disconnects.

    Regards,

    Kostas

  • Kostas,

    Sorry for the delay here, I'm trying to get some more information on our side how the DCSM is implemented on this device.  If the passwords are non 0xFFFFFFFF(erased) and unknown then the device is usually considered permanently locked and must be replaced.  Sometimes this can happen if the program operation is interrupted or there is a power fault during this operation.

    I think on this device, however, it shouldn't be very likely unless you were programming the passwords when something like the above occurs.  Do you have any knowledge if this could have happened?

    The WIR will keep the code from starting its normal operation, which default is boot to flash.  Since the Flash is part of the secure zone, the emulation connection will terminate if the code is in this region and the device is locked.  So while WIR allows us to connect, we still have to unlock the device.

    Best,

    Matthew