Unable to get custom DA14580 Board to be visible to JTAG

10 posts / 0 new
Last post
johncharris
Offline
Last seen: 1 day 13 hours ago
Joined: 2018-07-16 17:12
Unable to get custom DA14580 Board to be visible to JTAG

I have been working on this for quite some time and I am unable to get my custom board working. When I attach my board through the development board I get the message "No devices have been detected."

My custom board is .4mm thick if it matters.

C1 - C4 CL05A105MQ5NNNC
Crystal - 7M-16.000MEEQ-T
Inductor - CV201210-2R2K

I think the most likely area of problem would be around C3 and C4 with the meander line. This is a pretty simple design and I'm not sure where else to check.

I have tried both the newest version of JTAG and the one recommended by SmartSnippets Studio.

Thank you,

John

Attachment: 
Device: 
PM_Dialog
Online
Last seen: 4 min 43 sec ago
Staff
Joined: 2018-02-08 11:03
Hi johncharris,

Hi johncharris,

Regarding the schematic, the VDCDC and VDCDC_RF have to be connected with a min 7mm long meander line, but it seems to be connected on the PCB. Can you please make sure that the VDCDC and VDCDC_RF are connected? Also, I would strongly suggest you to follow our design recommendation for the PCB.  The RF performance might be low and you should improve the grounding of the XTAL. By the way, I would highly recommend you to check the supply voltages and make sure the he 16MHz oscillator is running. Also, you mentioned that you connected your custom board with our DK, so can you please make sure that your connections are according to the “How to program a custom board using a development kit (basic or pro)?” from the FAQs page?

https://support.dialog-semiconductor.com/guide/faq-dev-kits-ref-designs

 

Thanks, PM_Dialog

johncharris
Offline
Last seen: 1 day 13 hours ago
Joined: 2018-07-16 17:12
How should the meander line

How should the meander line be connected? I haven't been clear on this. Should this be a separate wire instead of a trace on the board?

VDCDC and VDCDC RF are connected between the pads of C3 and C4. I didn't know the right way to handle this.

Where are the design recommendations for the board?

Thank you,

John

CYibin
Online
Last seen: 2 min 17 sec ago
Staff
Joined: 2017-12-14 02:48
Hi johncharris,

Hi johncharris,

Please find the design recommendations in the document: https://support.dialog-semiconductor.com/system/files/resources/AN-B-054...

johncharris
Offline
Last seen: 1 day 13 hours ago
Joined: 2018-07-16 17:12
I tried to incorporate the

I tried to incorporate the design recommendations found at the link sent as well as the document AN-B-061. I made several improvements, particularly with the grounding and moving C4 to the other side of the meander line. I'm still not able to get this to do anything. I plug it in and SmartSnippets says there is no device attached.

I added some photos of this connected into the dev board in the attached zip file.

Thank you,

John Harris

Attachment: 
PM_Dialog
Online
Last seen: 4 min 43 sec ago
Staff
Joined: 2018-02-08 11:03
Hi johncharris,

Hi johncharris,

Could you please check all the power rails of your custom board? Be aware that should be according to the specifications of the DA14580 datasheet. Also, are you able to download firmware into the System RAM? Your custom board doesn’t have a USB port, does it?

Thanks, PM_Dialog

johncharris
Offline
Last seen: 1 day 13 hours ago
Joined: 2018-07-16 17:12
I tested and there is power

I tested and there is power getting to the board.

Right now I'm just trying to get this to work. Although this board has headers for usb, I don't have any components attached there. The only parts on the board are:
* DA14580
* 2.2uH Inductor
* 4 - 1uF Capacitors
* 16mhz crystal

I do not have a 32 khz crystal or anything else attached. I'm just working on getting the most basic circuit working. The only external connections are the 4 connections to the dev board for power, ground, TMS and TCK.

I am unable to program the board. Smart Snippiets just says that no devices have been detected.

[INFO General @19-01-10 10:07:57] Could not measure total IR len. TDO is constant high.
[ERROR General @19-01-10 10:07:57] Could not read memory address 0x50003200 with function JLINKARM_ReadMemHW
[ERROR General @19-01-10 10:07:57] No known chip found while opening JLink connection. Terminating proccess...

Thank you,

John

PM_Dialog
Online
Last seen: 4 min 43 sec ago
Staff
Joined: 2018-02-08 11:03
Hi johncharris,

Hi johncharris,

If I am able to understand correct, you are trying to program your custom board  through JTAG using the Basic DK and Smart Snippet. Could you please make sure that your connections between your board and the Basic DK are according to the connections of the “How to program a custom board using a development kit (basic or pro)?” from the FAQs page? Did you check this link?

https://support.dialog-semiconductor.com/guide/faq-dev-kits-ref-designs

Also, could you please let know if you tried to connect the Smart Snippet through UART?

Thanks, PM_Dialog

johncharris
Offline
Last seen: 1 day 13 hours ago
Joined: 2018-07-16 17:12
I have wired it up according

I have wired it up according to that FAQ with the exception of TP 2, since I'm just trying to run something from RAM from now.

I have not tried UART, I don't have the pins on the chip connected for that.

PM_Dialog
Online
Last seen: 4 min 43 sec ago
Staff
Joined: 2018-02-08 11:03
Hi johncharris,

Hi johncharris,

This is an indication from the Jlink software and not from Smart Snippets (when connected via JTAG, Smart Snippets uses the jlink in order to access the device). I highly recommend you to check if you have configured correctly the SPI Flash pins in the Board Setup tab of SmartSnippets toolbox. Probably there is no connection between the processor on the custom PCB and the Jlink fw that tries to communicate with the device. That could be anything from connections up to problems with the PCB that make the 580 unable to operate. My suggestion is to check if the bootloader is executing in order to verify that the 580 is operating correctly. You could probe the P04 and P05 pins, and that pins should be toggled executing part of the bootloader, so when connecting to a terminal you should see the device printing garbage. Also i would suggest you to connect the board using the Jlink itself, instead using Smart Snippets and also i would try to download code via Keil.

Thanks, PM_Dialog