⚠️
Hi there.. thanks for coming to the forums. Exciting news! we’re now in the process of moving to our new forum platform that will offer better functionality and is contained within the main Dialog website. All posts and accounts have been migrated. We’re now accepting traffic on the new forum only - please POST any new threads at https://www.dialog-semiconductor.com/support . We’ll be fixing bugs / optimising the searching and tagging over the coming days.
4 posts / 0 new
Last post
Wed, 2020-11-25 10:14
#1
Thieny
Offline
Last seen: 1 year 8 months ago
Joined: 2020-11-13 06:59
JTAG/SWD Connection

Hi,

I want to flash the CodeLess image on a DA14531MOD module mounted on a custom pcb.
To do so I tried to connect to the module via JTAG/SWD using the SmartSnippet Toolbox (V5.0.14).

I connected the VBAT, GND, SWDIO (J9/P0_10) and SWCLK (J10/P0_2) pins to my Segger J-Link debug probe and the moudle is powered up. The debug probe is connected via USB to the PC. Drivers are installed.

When I now start the SmartSnippet Toolbox (V5.0.14), select JTAG and click on detect I get the following notice:
"Detected device: Unknown chip on JTAG dongle [801021111] using Board [unknown].

The user manuals and the getting started guides for CodeLess on the Dialog website only describe how to connect to the development kit.

What am I doing wrong? How can i connect to the module on a custom pcb? Are there other ways to flash the CodeLess image for example over UART?
Are there any native bootloader routines on the module and how can I start/access them? Is there a default pin configuration delivered with the module for 2-wire UART?

Thanks in advance.

Keywords: 
SmartSnippet Toolbox
Codeless
Device: 
DA14531 SmartBond TINY Module
Wed, 2020-11-25 14:40
PM_Dialog
Offline
Last seen: 5 months 1 week ago
Staff
Joined: 2018-02-08 11:03
Hi Thieny,

Hi Thieny,

Thanks for your question online.

Normally, if the SWDIO and SWDCLK are connected ( of course with common GND), this should be enough to have access on the JTAG. If the custom board already has a power supply, then powering the module via the JLink is not required.

  1. When opening the SS Toolbox, are you able to detect the JTAG Serial Number?
  2. What is the version of the Segger J-Link?
  3. Does the GDB server detects the DA14531?
  4. Do you have any of the Dialog DKs, so you can do a quick test?
  5. Additionally, what is the clock speed of the JTAG?

The TINY module can be also programmed via 1-wire UART on P05, but you will need a USB  to UART “bridge”. In our designs, we are using

Accepted answer
Wed, 2020-11-25 15:00
(Reply to #2)
Thieny
Offline
Last seen: 1 year 8 months ago
Joined: 2020-11-13 06:59
I had also connected the RST

I had also connected the RST Pin (P0_0) to the debug probe. With an seperate testing construction (only SWDIO, SWCLK connected, without RST) it works without any problems.

Wed, 2020-11-25 15:14
PM_Dialog
Offline
Last seen: 5 months 1 week ago
Staff
Joined: 2018-02-08 11:03
Hi Thieny,

Hi Thieny,

Glad that you figured it out and thanks for your indication. Yes, probably the Segger J-Link was continually resetting the module, so you were not able to attach it via JTAG.

This is very helpful info for the other community :  the RESET is not required – see more info in the following tutorial.

http://lpccs-docs.dialog-semiconductor.com/Tutorial_SDK6/debug_probe.html

An FYI - When trying to program DA14531 SMARTBOND TINY™ MODULE using Keil IDE, an error may occur when you are trying to open the debugger session. To solve this, you should lower down the JTAG clock speed to 2MHz.

In case this error occurs, please follow the steps described in Section 6.1 Keil JTAG default Clock Speed in UM-B-141 user manual to solve it. 

https://www.dialog-semiconductor.com/sites/default/files/um-b-141_da14531_smartbond_tinytm_module_development_kit_hardware_user_manual_1.1.pdf

Thanks, PM_Dialog