Other Parts Discussed in Thread: UNIFLASH,
I am trying to use UniFlash 6.3.0.3193 to flash my MSP432E401Y via a USB to Serial converter IC chip, the FT232R. After a few days of debugging, it appears there is a bug between UniFlash and the converter IC itself causing the UniFlash software to timeout saying the BSL is not responding, even though it is.
I captured some of the traffic with a serial monitor when it works with the eval kit via the XDS110 UART port, and when it doesn't with the FT232R port and there is something going on with the handshaking between UniFlash and the IC I think. Can anyone confirm that UniFlash is compatible with FTDI chips?
Here is a capture of a successful transaction with Uniflash via the XDS110 UART. You see it sends the 03 20 20 ping request and the MSP432 Acks with 00 cc. There is then something where it tries to read a status and times out instantly. It then proceeds to successfully flash the chip via UART.
Here is a capture of a failed transaction with Uniflash via the FTDI chip. You can see that Uniflash sends the 03 20 20 ping and my BSL Acks it with 00 cc. But then there is a 5 second delay and it fails. In real time while it is failing this will show "STATUS_PENDING", and then switch to "STATUS_CANCELLED" after 5 seconds, at which point Uniflash aborts the process and closes the COM port, even though it is clear as day that the BSL responded appropriately.
All in all I have shown that the COM path is there, and that the BSL is operating correctly because it Acks the Ping request correctly. But then Uniflash times out waiting for something and refuses to continue sending the next transactions.
Can anyone confirm or point out what I am missing here that could salvage this line of design for me? At this point it seems I have to abandon using UART for flashing and attempt either ethernet or USB.
