9 posts / 0 new
Last post
Craig Flanagan
Offline
Last seen:1 year 11 months ago
Joined:2016-04-25 20:17
IOT and Keil

Hello I was searching through the posts and Dialog stated:
"You dont need any extra cable or a Jtag since you have the interface board, the board has a debugger, you just plug in the USB cable turn it on and you should be able to step and run the IoT
fw with keil, you dont need anything extra. The interface you indicate in the picture is another interface in order to program reference designs with different Jtag connection plugs."

I have the interface board/IOT sensor combo. I have tried downloading the code through smart snippets but was not successful then I noticed this post. I would like to use the debugger
that is mentioned here but when I boot keil and compile the IOT project and try to open the debugger I get the error: No Cortex-M Device Found. My Keil works fine with the DA14580 development kit. Any ideas? Thank you. Craig

Device:
MT_dialog
Offline
Last seen:2 months 4 days ago
Staff
Joined:2015-06-08 11:34
Hi Craig,

Hi Craig,

伴随着物联网传感器的接口板is the one indicated in the UM-B-063 sensor development kit documentation in figure 5. Please open keil and choose the options for target, go to the debug tab and click settings, there you should see the SN of the JTAG (make sure that the port is set to SW and not JTAG). The problem is, if the 583 has firmware inside the internal flash and the fw implements sleep, the JTAG wont be able to attach to your processor. So if you dont see under the SW Device text box your processor, hit the ok or cancel button to go back in the Debug tab, hit the reset on the the interface board and click again the settings options before the 583 goes to sleep, in order to make sure that keil is able to communicate with your processor. Now in order to program the via keil before hitting the debug button on keil, hit the reset button on the interface board and hit the debug button from keil within approximatelly 2 seconds. I remind you that the above are necessary because the fw implements sleep and the debugger can't attach to the 580. You can remove the fw that is programmed into the flash by using smart snippets and the connect via JTAG, hit the flash option, hit connect, and then erase, that way you dont have to hit the reset button every time you want to program your board.

Thanks MT_dialog

Craig Flanagan
Offline
Last seen:1 year 11 months ago
Joined:2016-04-25 20:17
Thank you for the detailed

Thank you for the detailed response. That will help a number of people who will encounter this issue. As for me, I am still having troubles with my current board, I cannot program it with Smart Snippets or program it through Keil- I believe it is the board itself so I sent for a new one from Mouser and will recontact you if
I encounter any problems with that board. Many thanks again. Craig

Mahesh
Offline
Last seen:3 years 3 months ago
Joined:2016-01-04 14:03
Hi,

Hi,

How much current will be drawn by "IoT Sensor Development Kit - 9 axis + Temp/Pressure/humidity" while sampling all sensors at high frequency.
Is any document regarding the current/power consumption details.

Regards,
Mahesh Chandana.

MT_dialog
Offline
Last seen:2 months 4 days ago
Staff
Joined:2015-06-08 11:34
Hi Mahesh,

Hi Mahesh,

You can find the power consumtion measurements in the UM-B-063_DA145_IoT_sensor_development_kit.pdf at section 12.1 Power measurements along with the rates of the sensors that the measurement is done. Those are the available measurements that have been performed on the IoT

Thanks MT_dialog

Craig Flanagan
Offline
Last seen:1 year 11 months ago
Joined:2016-04-25 20:17
Hello, I am having trouble

Hello, I am having trouble programming my new boards. The boards were just manufactured and have the same pinouts/pin connects for programming
(including the 10 pin header) as your DA14583 IOT board. I cannot program them using either UART/SPI mode or JTAG mode. My existing
IOT sensor from Dialog programs fine in both of those modes. I think I really need support as these boards were very expensive to have
fabricated and there seems to be a hardware issue on them. The following errors were obtained from Smart Snippets: I am looking for
a strategy to debug them at this point. Thank you. Craig

JTAG MODE:
[INFO @16-12-25 14:00:27] Header records have been removed from hex file wrbl_sfl_583.hex.
[INFO @16-12-25 14:00:27] Read 32688 bytes from file wrbl_sfl_583.hex.
[INFO @16-12-25 14:00:28] Core is locked-up, trying to disable WDT.
[WARNING @16-12-25 14:00:29] Could not set S_RESET_ST
[WARNING @16-12-25 14:00:29] CPU did not halt after reset.
[WARNING @16-12-25 14:00:29] CPU could not be halted
[INFO @16-12-25 14:00:29] Core did not halt after reset, trying to disable WDT.
[WARNING @16-12-25 14:00:29] CPU did not halt after reset.
[WARNING @16-12-25 14:00:29] CPU could not be halted
[WARNING @16-12-25 14:00:29] Could not set S_RESET_ST
[INFO @16-12-25 14:00:29] SYSRESETREQ has confused core. Trying to reconnect and use VECTRESET.
[WARNING @16-12-25 14:00:30] Failed to reset CPU. VECTRESET has confused core.
[WARNING @16-12-25 14:00:30] CPU did not halt after reset.
[WARNING @16-12-25 14:00:30] CPU could not be halted
[INFO @16-12-25 14:00:30] Core did not halt after reset, trying to disable WDT.
[WARNING @16-12-25 14:00:30] CPU did not halt after reset.
[WARNING @16-12-25 14:00:30] CPU could not be halted
[WARNING @16-12-25 14:00:30] Could not set S_RESET_ST
[ERROR @16-12-25 14:00:30] Failed writing value A7 at address 50000012.
[INFO @16-12-25 14:00:30] Failed downloading firmware file to the board.
[INFO @16-12-25 14:00:30] Failed configuring SPI Flash ports and pins.

UART/SPI Mode:
[INFO @16-12-25 14:55:30] Header records have been removed from hex file wrbl_sfl_583.hex.
[INFO @16-12-25 14:55:30] Read 32688 bytes from file wrbl_sfl_583.hex.
[INFO @16-12-25 14:55:35] Failed downloading firmware file to the board.
[INFO @16-12-25 14:55:35] Failed configuring SPI Flash ports and pins.
[INFO @16-12-25 14:55:44] Failed downloading firmware file to the board.
[INFO @16-12-25 14:55:44] Failed configuring SPI Flash ports and pins.
[INFO @16-12-25 14:55:57] Failed downloading firmware file to the board.
[INFO @16-12-25 14:55:57] Failed configuring SPI Flash ports and pins.
[INFO @16-12-25 14:56:13] Failed downloading firmware file to the board.
[INFO @16-12-25 14:56:13] Failed configuring SPI Flash ports and pins.
[INFO @16-12-25 14:56:17] Failed downloading firmware file to the board.
[INFO @16-12-25 14:56:17] Failed configuring SPI Flash ports and pins.
[INFO @16-12-25 14:56:28] Failed downloading firmware file to the board.
(信息@16-12-25 14:56:28]失败配置SPI Flash ports and pins.

MH_Dialog (not verified)
Hi Craig,

Hi Craig,

Regarding to the flash programming, please check the SPI flash pin configuration in Board Setup to match DA14583 pin assigement and use UART mode instead of UART/SPI mode when there is no function of current measurement. Smartsnippets usually ask users to press reset button in UART mode in order to download a flash_programmer.bin before programming a flash image, but I dont see it in the console you provided. So there might some incorrect steps in your setup. Please also confirm both of the UART and JLink driver are installed correctly.

Flash download is not supported in Keil. Please use "debug" and download the image to RAM.

Thanks Morris

Craig Flanagan
Offline
Last seen:1 year 11 months ago
Joined:2016-04-25 20:17
Thanks for your help. I

Thanks for your help. I realized I am missing the central solder pad for the 40VFQFN processor. Routed
some lines underneath the pad. I think this is the issue. I looked at the datasheet and there is not much
mention of the central pad and I was unaware of this need this being my first time using this chip
format.

For the sake of my fix where I have to be a bit creative in dealing with the central ground pad, I need to know (and couldn't
find in the datasheet), if pin 16 (DA14583 GND pin 16) is connected internally to the central ground pad? If not, can I get away with not grounding
that central ground pad or is that an absolute necessity? Thank you in advance. Craig

MH_Dialog (not verified)
Hi Craig,

Hi Craig,

The pin 16 is the DCDC ground and is not connected to the substrate ground which is the central ground pad. So it is necessary to have ground pad connection. The layout of evaluation board may provide you a good reference.

Thanks Morris