DA14681 development kit -basic, QSPI program issue

Hi howardwong,

This is something that came up when using older revision chips or older SDKs, can you please have a look at the chip and report what is the indication on the package or try to download the a fresh copy of the SDK from the support site in case you are using an older one ? Also please make sure that the COM that you are using is the one that should be used, when the pro kit is attached use the COM port with the smaller number among the two ports that appear on the device manager. Additionally i can see the 137 in your com port assignment, can also try to clean up previous registered com ports, perhaps this is causing you some problems as well.

Thanks MT_dialog

Hi howardwong,

Since you have the basic kit of the 681 make sure that the jumpers on the J13 are placed at the proper position. If the problem still persists, try to have the reset button pressed and release it when the "Connecting to device...." indication pops up. Seems that the basic kit has this issue since i can replicate what you are experiencing. I will check with the team and let you know for any further guidance.

Thanks MT_dialog

Hi howardwong,

正如前面提到的,我复制你的这个问题is something that we are checking, what you can also try in order to increase the success rate on your downloading attemps (at least it works on my side) is to try to download via UART and try again immediatelly after the first attemp fails. By doing this the programming success should be about 50% (since on the second attempt it downloads the code with no error) or you can use the JTAG script in order to download code to the basic kit.

Thanks MT_dialog

Hi howardwong,

Got some feedback from the hw team. Seems that this issue is caused because of the Segger chip only on the basic kit (since the pro kit uses an FTDI for the UART interface). The root cause of this is the Segger firmware, which doesn't initialize the UART pins at start up, and the initialization occurs when the first data is sent out. While initializing the port the driver will toggle once before sending data, and this is interpreted from the bootlaoder either as a framing error or as a break condition, causing it to hang. The second time you try to donwload fw the port is allready initialized and the booting works ok.

So there a couple of workarounds on this:

1) You can either program your device twice, one will fail and the other one will succeed.

2) You can add the following command "@echo a > COM%comprtnr%" at the scripts\qspi\program_qspi_serial.bat, please check bellow for the exact location that the line should be placed:

@echo.
= COM % comprtnr % @echo相称
@echo a > COM%comprtnr% <---additional command that should be placed
@echo on

Thanks MT_dialog