Dear Dialog Support Team,
we are currently evaluating your DA14583 SoC, using the IoT Sensor Development Kit but are running into some problems.
I am trying to re-flash the firmware to the Bluetooth dongle (UM-B-064), using the provided Communication Interface Board (UM-B-065). I have downloaded and installed all the required software.
First things first, when I open SmartSnippets Studio and press "Detect conncted Device(s)" both the D4 and D5 LED's on the board start to flash a couple of times. Then, SmartSnippet Studio displays that no devices are detected. When I check the Windows Device Manager and the J-Link Configurator the port is correctly recognized by both applications as a JLINK CDC UART Port.
When opening SmartSnippets Toolbox, again, no devices can be found, using the provided button. When opening a project to connect via UART the COM-Port is correctly recognised but upon pressing the "Connect" button in the SPI Programmer interface I receive the following output:
[INFO SPI Flash @17-09-20 14:16:37] Firmware File C:\DiaSemi\SmartSnippetsStudio\Toolbox\common_resources\flash_programmer.bin has been selected for downloading.
[INFO SPI Flash @17-09-20 14:16:37] Connection to COM22 port has successfully opened.
[INFO SPI Flash @17-09-20 14:16:37] Started download procedure...
[ACTION SPI Flash @17-09-20 14:16:38] Please press the hardware reset button on the board to start the download process.
However, upon pressing the reset button on the board nothing happens and the process eventually times out:
SPI Flash @17-0[错误9-20 14:16:53] Timeout: Reset signal not detected for more than 16000 msecs.
[INFO Booter @17-09-20 14:16:53] Successfully disconnected from port COM22.
SPI Flash @17-0[错误9-20 14:16:53] Failed downloading firmware file to the board.
SPI Flash @17-0[错误9-20 14:16:53] Failed configuring SPI Flash ports and pins.
When I use Keil uVision 5 with the associated firmware I press the reset button on the board and the debug button in Keil to make sure the Controller does not enter sleep mode, like pointed out in another post. However, after some flashing from the LED's D4 and D5 (so there is some kind of communication) I am promted with the error that no Cortex M0 device has been found.
I have looked through related posts and have checked that the connection is set up correctly. Also, the heartbeat LED blinks like it is supposed to and the blue LED on the Bluetooth dongle board (with the switch in OFF-position like mentioned in the manual but I have tried it in ON position, too) signals that power is available. All jumpers are connected as well.
Can this be a software issue with the JTAG/USB controller or a hardware issue with one of the boards?
Best regards,
lukgla
嗨lukgia,
Even if the CIB board is in off state the Smart Snippets tool should be able the detect the jlink device (if you open the Smart Snippets in the initial dialog box if you select the JTAG radio button then you should see the number or the jlink device that the Smart Snippets is about to connect to) if that doens't happen then something else is the issue, a driver perhaps or something is wrong with the Jlink device on the CIB, also please make sure that the switch on the CIB is in on state. Regarding the downloading via the UART, you should be able to do so with the CIB through the virtual com port that jlink provides, although this can be enabled or disabled, but if it was disabled you should be able to see the virtual com port through the device manager, please make sure that you are connecting to the proper COM port. If the timeout occurs that means that Smart Snippets didn't get the 0x02 generated by the 583 bootloader, this is how the Smart Snippets detects that the reset but is issued. If you are not able to download fw with keil, please check via keil if its capable of finding the device via the "Target Options" and the "Debug" Tab, hit the settings button, and you should be able to see the IDCODE od the ARM in the SW Device section. If you are not able to see that then apparently something is wrong either with the hardware (CIB or the dongle) or with the driver of jlink.
由于MT_dialog