CODECOMPOSER: how to erase all flash when using j-link programmer

Kazola,

I am not sure that this functionality is available.

When launching a debug session with an XDS110 I can see that a GEL file called cc26x2_xds.gel gets loaded into the debugger.  This has a MassErase function in it.

menuitem "CC13x2_CC26x2"
/**
 * \brief    This function issues a board reset before erasing the device flash.
 *           This function disconnects from target after completion.
 *           NOTE: If CM4 DAP is locked, make sure to disable "Custom configuration"
 *                 from all sub paths in the device's target connection file (.ccxml).
 */
hotmenu MassErase()
{
    GEL_TextOut("Initializing.\n", "MassErase()");
    _isMassErase = 1;

    // Disconnect from target. This must be done for each module in the device debug sub-system hierarchy.
    DisconnectIfConnected(); // Cortex
    GEL_EvalOnTarget("<parent>", "DisconnectIfConnected()", 1); // DAP (Cortex' parent)
    GEL_EvalOnTarget("<parent>", "GEL_EvalOnTarget(\"<parent>\",\"DisconnectIfConnected()\", 1)", 1); // Icepick (DAP's parent)

    // Do board reset
    GEL_TextOut("Issuing Board Reset.\n", "MassErase()");
    GEL_AdvancedReset("Board Reset");

    // Reconnect to Icepick
    GEL_EvalOnTarget("<parent>", "GEL_EvalOnTarget(\"<parent>\",\"ConnectIfDisconnected()\", 1)", 1);

    // Issue mass erase from Icepick and disconnect
    GEL_EvalOnTarget("<parent>", "GEL_EvalOnTarget(\"<parent>\",\"IP_CC26xx_CHIPERASE = 1\", 1)", 1);
    GEL_EvalOnTarget("<parent>", "GEL_EvalOnTarget(\"<parent>\",\"DisconnectIfConnected()\", 1)", 1);

    // Workaround on engineering devices. Disconnect and reconnect for chip erase to take effect.
    ConnectIfDisconnected();
    DisconnectIfConnected();
    _isMassErase = 0;

    GEL_TextOut("Mass erase complete.\n", "MassErase()");
}

When using a jlink a different GEL file cc26x2_jlnk.gel gets loaded. It does not have an equivalent function.  Looking at the function it seems to use the ICEPick to do the mass erase.  It could be that the JLink is not able to use the ICEPick to do that as it is TI specific debug IP.  I will need to loop in the connectivity team to comment.  I suspect that is also impact which flash options are available from CCS.

Regards,

John