• State Verified Answer
  • Replies 13 replies
  • Subscribers 73 subscribers
  • Views 5352 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 128604
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Any special steps for first use - n52832

MattFL

Is there anything special required to make a n52832 work the very first time the chip is programmed? Fuses to set, etc?

I'm new to nordic chips and I was handed a board with a working chip, I program it and it works fine. I was handed a new board, same design and same chip, and using the same code the chip programs fine but does not run, and draws no current. The low frequency clock crystal (32kHz) is not oscillating and since both pins of the crystal connect to the processor (XL1, XL2 pins) I'm trying to determine if it's due to a hardware problem, or a step that I missed programming the chip for its first use. I'm just flashing code to it using a Segger through uVision IDE.

Parents
  • 0

    No, if you verify that SWD programming with certain FW works on one board then it should work on another unless you change something in the HW design such as LF/HF clock source, LDO/DCDC components, some components on GPIOs which you use in booting sequence to intialize interfaces such as I2C/UART/SPI/I2S... (but in that case your FW would boot to main loop and it would be your custom assert which would cause it "failing"). If you have two boards with identical PCB schematics and components then they should work the same.

    If you really think that it's rather FW then HW issue then program it with some simple debugging FW which uses LED or GPIO/UART interfaces to signal that it boots to main loop at least.

Reply
  • 0

    No, if you verify that SWD programming with certain FW works on one board then it should work on another unless you change something in the HW design such as LF/HF clock source, LDO/DCDC components, some components on GPIOs which you use in booting sequence to intialize interfaces such as I2C/UART/SPI/I2S... (but in that case your FW would boot to main loop and it would be your custom assert which would cause it "failing"). If you have two boards with identical PCB schematics and components then they should work the same.

    If you really think that it's rather FW then HW issue then program it with some simple debugging FW which uses LED or GPIO/UART interfaces to signal that it boots to main loop at least.

Children
No Data
Related
Terms of service