Debugging DA14583 IoT Sensor Module

Learn MoreFAQsTutorials

8 posts / 0 new
Last post
boyina123
Offline
Last seen:3 years 3 weeks ago
加入:2018-01-08 16:44
Debugging DA14583 IoT Sensor Module

Hi,

I am using DA14583 IoT sensor development kit for my IoT application development.

I able to build wrbl_sfl project example using Kiel and download binary/firmware using Smar Snipper Studio.

But I couldn’t find information on how to program from Kiel/SW debug from kiel? Please provide any document for explaining debugging IoT sensor application.

Thanks & Regards
Ramakrishna.

Device:
MT_dialog
Offline
Last seen:1 day 23 hours ago
Staff
加入:2015-06-08 11:34
Hi boyina123,

Hi boyina123,

You will be able to find information regarding the IoT in the Development Kits Tab of the 14583 product, the documents regarding the IoT Software and Hardware are the UM-B-064 IoT sensor reference application and UM-B-063 IoT Sensor Development Kit. The kit comes preprogrammed but you can debug and update the currently loaded fw, check in the document UM-B-063 paragraph 4 Firmware Upgrade and offcourse you can also run fw directly in RAM using Keil.

Thanks MT_dialog

boyina123
Offline
Last seen:3 years 3 weeks ago
加入:2018-01-08 16:44
HI,

HI,

I able to load fw using smart snippet studio.
I have tried to run fw from RAM directly to debug the code, but i got the error. I have attached error popup message and my setup picture.
Any settings are required are in keil IDE? Any document is there describing how to run FW from RAM using kiel?

Thanks & Regards
Ramakrishna.

Attachment:
MT_dialog
Offline
Last seen:1 day 23 hours ago
Staff
加入:2015-06-08 11:34
Hi boyina123,

Hi boyina123,

The error that you get indicates that Keil is not able to find an MCU on the other side of the connection, i assume that the reason for that is because the device is allready running a sw and its in sleep mode and wake up in every advertising event. In order to be able to debug via keil is to either erase the flash using the Smart Snippets tool, so when powering up the 583 wont go in sleep mode and the debugger will be able to attach to the M0 or you can hit the reset on the board, before the device goes to sleep leaves a small (about 2 seconds window) where the device is fully awake, so in those two seconds you can hit the Start/Stop debug session so that the debugger attaches to the device before it goes to sleep.

Thanks MT_dialog

boyina123
Offline
Last seen:3 years 3 weeks ago
加入:2018-01-08 16:44
Hi,

Hi,

After erasing flash, tried to run FW using keil. Now device/mcu detected but I am getting error "Cannot access Memory". Please tell what could be reason? Any settings required?
Attached snapshot.

Thanks & Regards
Ramakrishna.

Attachment:
MT_dialog
Offline
Last seen:1 day 23 hours ago
Staff
加入:2015-06-08 11:34
Hi boyina123,

Hi boyina123,

这有点陌生的错误,如果你打the "Options for Target"-> Debug ->Settings are you able to trace the SN of your jlink and the IDCODE of the ARM attached on the debugger ? Can you also send me a screenshot of that ? The projects come with the corresponding settings so there is not much to do in order to start debugging.

Thanks MT_dialog

boyina123
Offline
Last seen:3 years 3 weeks ago
加入:2018-01-08 16:44
Hi,

Hi,

I have attached screenshot of Jlink settings.

Thanks & Regards
Ramakrishna.

Attachment:
MT_dialog
Offline
Last seen:1 day 23 hours ago
Staff
加入:2015-06-08 11:34
Hi boyina123,

Hi boyina123,

I dont see anything wrong with the settings that you have attached, have you builded the project before downloading it into the device. You will be able to find some guidance regarding the Keil tool in the following document UM-B-048 Getting started with Development Kit Basic on paragraph 4 (the document describes on how to debug the Blinky demo code so disregard the setting and the file paths indicated by the document, the settings should be ready for running the IoT code directly from RAM). So open the project, hit the "Build" button so that the project will compile and then hit the "Start/Stop Debug Session". Are you certain that you haven't changed any settings in keil from the default settings of the project ? Have you tried to run any other project from the SDK (builded for the 583 device) ?

Thanks MT_dialog