• State Verified Answer
  • Replies 12 replies
  • Subscribers 72 subscribers
  • Views 1935 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 303064
Options

UART RX_PIN_NUMBER issue.

Neeraj Dhekale

Hello All,

I am using nrf5_SDK 17.0.2 softdevice. And using this example examples\ble_central\ble_app_uart_c I am able to Tx data from BE33 to external, but I am not able to Rx data from external.

I am using BE33 nRF52833-based controller. I have attached the datasheet of BE33 for your reference.

BE33 Datasheet REV02 - Celium Devices(3)-9.pdf

As you can see in there is no pin number 8 so I have tried to give pin number 4. But it shows the error "Communication error occurred while handling UART". If you tried to change anything from 8. It seems it is not accepting any pin number except 8. My issue is similar to this issue posted here.

Let me know if I am doing anything wrong.

Thanks and regards,

Neeraj Dhekale

Parents
  • 0

    Hello,

    In regard to the link you sent on the BE33 module, please review page 8. 

    Pin 8 on the module relates to GPIO P0.28 on the Nordic device.  Pin 9 is P0.29.  If you are using the Nordic SDK then I suggest, try changing your code to use the actual GPIO number (minus the P0.  Such as in this case the module's pin 8 should be entered in your firmware as 28.  Good luck

  • 0 in reply to Jay Tyzzer

      

    Thanks for your reply.

    I am trying to do the same thing. As per the datasheet attached, I want to give Rx pin that is 17 number but I am giving pin number 4 (that is P0.04). But the surprising thing here is, that any pin number except 8 will give you the error "Communication error occurred while handling UART". That I did not understand.

    Thanks and reagards,

    Neeraj Dhekale

  • 0 in reply to Neeraj Dhekale

    Hi Neeraj

    You said earlier you tried to measure the voltage on the pin, but you had no luck. Do you mean you were unable to measure the voltage on the pin? 
    Are you able to put a probe on GPIO17 on the module to see if it is high or not?

    In your picture, is the UART lines coming through the 4 wire connector on the left side? 

    Have you been able to make the CP2102 USB work with the nRF52833DK when using the default pin (P0.08), but not with P0.04? 
    If it works with the DK on the standard pin it is very strange that it should not work on P0.04. 

    Best regards
    Torbjørn

  • +1 in reply to ovrebekk

    Hello  

    Thank you so much and sorry for the late reply. The problem is solved. I was used to flash firmware directly to nRF. But when I Erased All and re-programmed, then it starts to work as expected.

    ovrebekk said:
    Are you able to put a probe on GPIO17 on the module to see if it is high or not?

    Yes, it shows high.

    ovrebekk said:
    In your picture, is the UART lines coming through the 4 wire connector on the left side? 

    Yes, VCC, Tx, Rx, and GND.

    ovrebekk said:
    Have you been able to make the CP2102 USB work with the nRF52833DK when using the default pin (P0.08), but not with P0.04? 

    it was not working but now it is working.

    Thanks and regards,

    Neeraj Dhekale

Reply
  • +1 in reply to ovrebekk

    Hello  

    Thank you so much and sorry for the late reply. The problem is solved. I was used to flash firmware directly to nRF. But when I Erased All and re-programmed, then it starts to work as expected.

    ovrebekk said:
    Are you able to put a probe on GPIO17 on the module to see if it is high or not?

    Yes, it shows high.

    ovrebekk said:
    In your picture, is the UART lines coming through the 4 wire connector on the left side? 

    Yes, VCC, Tx, Rx, and GND.

    ovrebekk said:
    Have you been able to make the CP2102 USB work with the nRF52833DK when using the default pin (P0.08), but not with P0.04? 

    it was not working but now it is working.

    Thanks and regards,

    Neeraj Dhekale

Children
Related