MSP432P401R: BSL Scripter RESET pulse

It appears that for the P401R Scripter does not initiate the BSL process using the special pattern on /Reset and Test.  But I wonder if you could get it to generate a reset if a Mode command pretends that it's some other part that does use that pattern.  Of course it would fail, but maybe you could follow up the invalid Mode command with a valid one.  Might have to run Scripter twice though.  Well I'm just guessing.  The problem is that Scripter doesn't do a reset directly.  It instructs the MSP-FET to do that.  I just don't know how to make that happen.  By the way, you should probably click on the "did not solve my problem" button if you want TI to stay involved.

Jeffrey, George,

   It is important to remember that the scripter does not invoke the BSL but communicates with the BSL once invoked.  The REBOOT_RESET command simply resets the device as described in the source code:

/**
 * Triggers a REBOOT_RESET that causes the device to re-initialize ifself and causes bootcode to execute again.
 *
 * \return None
 */
void BSL432_API_rebootReset()
{
#if defined (__MSP432P401R__) || defined (__MSP432P401M__)
    MAP_SysCtl_rebootDevice();
#elif defined (__MSP432P4111__) || defined (__MSP432P411V__) || defined (__MSP432P411Y__)
    MAP_SysCtl_A_rebootDevice();
#else
#error Device not defined.
#endif
}

Regards,

Chris

But I think Jeffrey's point is that REBOOT_RESET is a command sent to the P401R to reboot itself, and can take place only after communications have been established.  Perhaps I misinterpreted his question, but it appeared to me that he wanted to transmit a low pulse to the chip's /Reset pin before attempting to communicate at all, and wanted Scripter to make that happen.