Can't Read Device Signature on Custom Board

Log in or register to post comments
Go To Last Post
7 posts / 0 new
Author
Message
hardE
hardE's picture
Level: New Member
Joined: Wed. Mar 31, 2021
Posts: 5 View posts
#1
Posted by hardE: Thu. Apr 1, 2021 - 12:34 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hi, I'm a newbie making a custom board for the first time and I realize I've made several somewhat serious mistakes, but I'm hoping to learn from them.

 

I'm trying to program the ATSAMD21E17A using Microchip Studio with JTAG. My (known) crimes are that I didn't use any bypass capacitors on the microcontroller and I didn't add a pull up to the SWD clock (the datasheet says to for reliability) or the reset pin. I checked that the microcontroller was adequately powered with a 3.3 V supply on board and I was able to read it with Microchip Studio using the JLink EDU. I've attached a schematic for reference.

 

Does anyone know if I can still program this somehow? If not, what is really causing the problem- the caps, the reset, or something I missed?

 

Any help is greatly appreciated and critiques so I can improve as an engineer are welcome.

Attachment(s): 

Image icon schematic.jpg
This topic has a solution.

Tags:

Tools, In-System Debuggers and Programmers (ARM-related), solved
Last Edited: Sat. Apr 3, 2021 - 07:52 PM
Top
ki0bk
ki0bk's picture
Level: 10k+ Postman
Joined: Mon. Sep 8, 2014
Posts: 10609 View posts
Location: Over the rainbow
Posted by ki0bk: Thu. Apr 1, 2021 - 01:24 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hardE wrote:
Hi, I'm a newbie making a custom board for the first time

Welcome to AVRFreaks!

 

I'm not sure when the practice of putting individual parts on a drawing and linking with net names began, but a real schematic tells a story, a complete story!

It's no surprise to see/hear you have left critical parts off your schematic drawing, had it been a schematic it would have been obvious to anyone there is something missing from the story.

My suggestion would be, go back, start over and DRAW a schematic with all the lines needed to connect ALL of the parts that make up the project.  This will be the best way to fix the problem, and in the end you will have a working board.

At least you now know the process of getting a drawing to a layout, to a physical board, so that is a start and further then many other beginners that have not done that. 

Making PCB, is a lot like making pancakes, you throw the first one away!

Good luck.

Jim

 

 

 

FF = PI > S.E.T

 

Top
hardE
hardE's picture
Level: New Member
Joined: Wed. Mar 31, 2021
Posts: 5 View posts
Posted by hardE: Thu. Apr 1, 2021 - 05:42 PM (Reply to #2)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thanks for the feedback, Jim, I'll certainly do that in my next iteration to make it professional.

 

Do you know if this one is still programmable though or what is really preventing Microchip Studio from reading the device signature?

 

Best,

Neil

Top
hardE
hardE's picture
Level: New Member
Joined: Wed. Mar 31, 2021
Posts: 5 View posts
Posted by hardE: Fri. Apr 2, 2021 - 10:07 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Update: I've soldered a pull-up resistor on the board and got a new error. I still can't get the device signature, but now I get the following message:

 

Timestamp:    2021-04-02 15:00:24.316
Severity:        ERROR
ComponentId:    20100
StatusCode:    3
ModuleName:    TCF (TCF command: Device:startSession failed.)

'ArmDev_4' is not a device context.

 

The StatusCode changed from 1 to 3 and, interestingly, the number following "ArmDev_" (I'm on 4 now) increments every time I try to read the device signature. It's safe to say I'm very confused and would appreciate any insight into what is going on here.

Top
hardE
hardE's picture
Level: New Member
Joined: Wed. Mar 31, 2021
Posts: 5 View posts
Posted by hardE: Fri. Apr 2, 2021 - 10:33 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Nevermind, I drove the reset low and I'm back to the same error

 

Timestamp:    2021-04-02 15:31:09.212
Severity:        ERROR
ComponentId:    20100
StatusCode:    1
ModuleName:    TCF (TCF command: Device:startSession failed.)

Error connecting to device over SWD

Top
Lajon
Lajon's picture
Level: Raving Lunatic
Joined: Fri. Mar 12, 2004
Posts: 2920 View posts
Location: Linköping, Sweden
This reply has been marked as the solution. 
Posted by Lajon: Sat. Apr 3, 2021 - 09:49 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 1

SWCLK is on PA30, SWDIO on PA31, you have this swapped.

/Lars

 

Top
hardE
hardE's picture
Level: New Member
Joined: Wed. Mar 31, 2021
Posts: 5 View posts
Posted by hardE: Sat. Apr 3, 2021 - 07:53 PM (Reply to #6)
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Wow I can't believe I did that. Thank you Lars!

Top