This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

micro:bit became unable to talk to nrf52832 by RADIO

Dear Nordic Semiconductor support team

Hi, I got your support using micro:bit with nrf52832 by RADIO in the past as follows.

https://devzone.nordicsemi.com/f/nordic-q-a/41770/how-can-i-make-nrf52832-talk-to-microbit-by-radio-gazell

It did work, but recently, the following makecode editor was updated.

https://makecode.microbit.org/

 

If I built .hex file using this latest makecode editor and download it to micro:bit, nrf52832 Dev Kit cannot receive

any packet, while it works correctly if using the old editor https://makecode.microbit.org/v1

I cannot understand this problem.

I also reported this on Github repository of makecode micro:bit editor. 

https://github.com/microsoft/pxt-microbit/issues/2259

The following is JavaScript code by makecode editor.

(The same between the new editor and the old one.)

radio.setGroup(0)
basic.forever(function () {
    radio.sendNumber(0)
    basic.pause(100)
})

The following is nrf52832 code using RADIO.  

host.zip  

Parents
  • Hi,

    I see the same issue as you describe. The radio peripheral configuration does not seem to have changed, so there might be something with the payload in the new editor version that makes the gazell lib to not report the received packet. Further debugging could be to setup a radio peripheral example, and check if you are able to receive the packet, and check any differences in the payload.

Reply
  • Hi,

    I see the same issue as you describe. The radio peripheral configuration does not seem to have changed, so there might be something with the payload in the new editor version that makes the gazell lib to not report the received packet. Further debugging could be to setup a radio peripheral example, and check if you are able to receive the packet, and check any differences in the payload.

Children
No Data
Related