• State Suggested Answer
  • Replies 10 replies
  • Answers 2 answers
  • Subscribers 69 subscribers
  • Views 6270 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 208105
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Programming prototype board from 52 DK

mark waldin

I have a Nordic 52832 chip in an integrated module form from Fanstel.  I have the NRF 52 DK, the Fanstel evaluation board, and a custom prototype board I built.

I can program the Fanstel evaluation board through the 52 DK with no problem.

The custom board runs the Fanstel module transmitting Bluetooth with default software installed on the module without problem.

I included a 6 pin Tag Connect interface on the custom board and am trying to load my program onto the custom board through the 52 DK but the board is not being recognized and instead commands from nRF Go Studio is writing the code directly to the 52 DK.  The connections I am supporting are Vdd, GND, SWIO, and SWCLK. 

My assumption was a hardware connection problem.  The only possible errors being SWDIO and SWDCLK connections or the cable itself since Vdd and GND must be working or the chip would not transmit at all.

Traces seem fine and all pinouts correct.  Anything else that could be causing the problem besides hardware connections?

Parents
  • 0
    • By using the power supply from the DK 52 instead of the lithium ion battery I was able to program the Fanstel module.  That did the trick. Thank you.  Now I am back to programming the prototype board as the next final step.  I built a connection from the DK 52 to the prototype in order to supply the power from the DK 52 instead of the on board battery.  For SWIO and SWCLK I am connecting the boards via Debug Out on the DK 52 and Tag Connect on the prototype board.  nRFGo does not see the prototype board even though there is (measured) 3.2V on the Tag Connect Vdd pin.  To test I tried bridging Vdd and VTG on the DK 52 and nRFGo shows "Chip not detected".  Layout photos and schematic below.  I did not populate the board with the external crystal or the detection circuit yet.  
Reply
  • 0
    • By using the power supply from the DK 52 instead of the lithium ion battery I was able to program the Fanstel module.  That did the trick. Thank you.  Now I am back to programming the prototype board as the next final step.  I built a connection from the DK 52 to the prototype in order to supply the power from the DK 52 instead of the on board battery.  For SWIO and SWCLK I am connecting the boards via Debug Out on the DK 52 and Tag Connect on the prototype board.  nRFGo does not see the prototype board even though there is (measured) 3.2V on the Tag Connect Vdd pin.  To test I tried bridging Vdd and VTG on the DK 52 and nRFGo shows "Chip not detected".  Layout photos and schematic below.  I did not populate the board with the external crystal or the detection circuit yet.  
Children
  • 0 in reply to mark waldin

    Then maybe there was a mismatch between the battery's voltage and the Segger MCU's supply voltage (VDD_SAM) on the nRF52 DK. When I measure VDD_SAM on my kit it is around 2.9 V. In general I would assume it works as long as you are above VDD_SAM * 0.7 = ~2 V. Make sure that you use a fresh battery. The battery voltage might drop when you insert it into your module, so at least make sure that you measure its voltage while inserted. 

     

    So now you are able to program the Fanstel, but not see it with nRFGo Studio? Is that correct? How do you program it?

Related