• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 6 replies
  • Subscribers 70 subscribers
  • Views 5375 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 212136
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

How to set the PIN 9 with 3.3v as output in nrf52810 ?

Kautham

I am working on a custom board based on nrf52810 that my client provided. In this board the accelerometer (Bosch BMA250E) power has been controlled by the PIN 9. However when i try to set the pin for gpio output in code i am getting only 0.6 volts as output. But my accelerometer needs 3.3 volts to power up and running (as low as 2.6 volts is good). In the nrf52810 Datasheet there is nothing mentioned about this. I own a nrf52DK which has nrf52832. In the nrf52832 Datasheet it has been mentioned these pins are NFC and GPIO multipurpose pins and they have limitations in used as GPIO pins which also seems like my problem. We searched the devzone and found this thread https://devzone.nordicsemi.com/f/nordic-q-a/29041/how-to-enable-p0-09-and-p0-10-as-gpio-pins-on-the-nrf52-instead-of-nfc-pins and tried all the steps. But still i cannot get high enough voltage to operate the accelerometer.

Parents
  • 0

    Hello,

    Have you tried any of the other pins, just to see if this is related to the NFC pins or not?

    Do you know how much current your sensor is drawing? The more current it draws, the lower the output voltage will be, due to the internal resistors on the pins.

    Have you tried to set the pin in High Drive? See this link.

    Setting the pin in high drive reduces the internal resistor, allowing to provide more current. If you need even more, you can set up to 3 pins in high drive, and provide 15mA. But I don't know if your PCB allows this, or how much current your sensor draws.

     

    But have you tested on another pin (not P0.09 or P0.10), to see whether this is an NFC-pin related issue or a current related issue?

     

    Best regards,

    Edvin

     

  • 0 in reply to Edvin

    In the nrf52 DK i tried with different PIns 25,24 and 6 with the accelerometer's dev board (shuttle board). And it worked. When i measured the output volts from these pins i got 2.8 to 3.3 volts and the TWI_Scanner sdk 15 example found my accelerometer I2C address 0x18 correctly. That's how i figured out the NFC pins problem. However in the Custom board this pin 9 is soldered to the accelerometer power so i couldn't disconnect it. But even weird happened when i shorted another free GPIO pin 20 with this pin 9 with necessary code changes. When i measure the P20 individually it shows 2.8 volts, but after shorting pin 20 with pin 9 physically with wires, the voltage goes down to 0.65 volts. 

  • 0 in reply to Kautham

    Have you checked the NFCPINS register in the UICR to be sure it's set with the least significant bit as zero? That is the best way to ensure that you HAVE actually set it into GPIO mode. If you haven't then go back and work out why setting the define hasn't worked for you. Just put a breakpoint at the start of main, then use your debugger to get the value in address 0x1000120C. 

    Your issue sounds like the pin is still in NFC mode. So do that test first before shorting pins together. 

Reply
  • 0 in reply to Kautham

    Have you checked the NFCPINS register in the UICR to be sure it's set with the least significant bit as zero? That is the best way to ensure that you HAVE actually set it into GPIO mode. If you haven't then go back and work out why setting the define hasn't worked for you. Just put a breakpoint at the start of main, then use your debugger to get the value in address 0x1000120C. 

    Your issue sounds like the pin is still in NFC mode. So do that test first before shorting pins together. 

Children
No Data
Related