802.15.4 Test dev migration to 52840

RE: 802.15.4 Test dev migration to 52840

Jørgen Holmefjord — Mon, 23 Sep 2019 10:30:41 GMT

Have you considered using the nRF-IEEE-802.15.4-radio-driver? You can find transmitter and receiver example applications in the Wiki pages.

RE: 802.15.4 Test dev migration to 52840

Pietro Beraldini — Mon, 23 Sep 2019 10:07:25 GMT

If I am correct, the post is regarding the 802.15.4 transmitter. What about the receiver?

I am trying to modiry the radio transmitter and receiver nordic example in order to use with 802.15.4.Can you give me any suggestions?

Thanks

RE: 802.15.4 Test dev migration to 52840

Jørgen Holmefjord — Tue, 05 Jun 2018 14:43:06 GMT

Great! Thank you for the feedback, and apologies for the delayed response on the issue.

RE: 802.15.4 Test dev migration to 52840

zzzLNAWS2 — Tue, 05 Jun 2018 14:32:13 GMT

That did it. It appears as though there are 3 things that need to be changed from the toggle source:

1. PCNF1_BALEN CANNOT be set to 3. I just left it there as an artifact of a copy/paste from the BLE source. The PS says it has a valid range of [2..4]. I didn't even notice that it's default is actually 0 if you never write it. So, I guess 0 is also a valid (and important) value in this case. i.e. it's not disregarded while only being used for BLE.

2. PCNF0_CRCINC must be 1. I was leaving it at default (0) under the assumption that it was unnecessary because it's not used for the BLE packets and that CRC doesn't live in RAM. Also, if you ctrl+F CRCINC in the PS, there is exactly 1 result in the section covering registers. There should probably be a little better explanation of its use as it pertains to 802.15.4.

3. Up the EIGHT02_TOGGLE_CONTENT_SIZE to 18 from 16. With 16 set, the data gets truncated to 0x0D + CRC. Changing to 18 gets all data to 0x0F + CRC.

Thank you very much for your help!

RE: 802.15.4 Test dev migration to 52840

Jørgen Holmefjord — Tue, 05 Jun 2018 13:10:14 GMT

There seems to be some issue with your packet configuration registers. Please try with the following:

NRF_RADIO->PCNF0    = (Eight02_packetHeaderLFlen    << RADIO_PCNF0_LFLEN_Pos) |
                      (Eight02_packetHeaderPlen     << RADIO_PCNF0_PLEN_Pos)  |
                      (RADIO_PCNF0_CRCINC_Include   << RADIO_PCNF0_CRCINC_Pos);

NRF_RADIO->PCNF1    = (EIGHT02_PAYLOAD_MAX_SIZE     << RADIO_PCNF1_MAXLEN_Pos);

I'm able to sniff the packets with these configurations.

RE: 802.15.4 Test dev migration to 52840

zzzLNAWS2 — Mon, 04 Jun 2018 13:28:37 GMT

Any news JH? I'm running out of time.

Thanks

RE: 802.15.4 Test dev migration to 52840

Jørgen Holmefjord — Tue, 29 May 2018 13:40:38 GMT

I did try out your application, and it does not seem to send any valid 802.15.4 packets. I will debug the application some more to figure out why it is not working. I cannot see any obvious issues at the moment.

RE: 802.15.4 Test dev migration to 52840

zzzLNAWS2 — Fri, 25 May 2018 14:21:25 GMT

Any news JH?

Thanks

RE: 802.15.4 Test dev migration to 52840

zzzLNAWS2 — Wed, 23 May 2018 16:49:51 GMT

devzone.nordicsemi.com/.../BLE_5F00_802154_5F00_packet_5F00_toggle.zip

This is about as simple as I could make it because I'm sure you have better things to do than surf through mountains of comments from all that I have tried for the migration. Not to mention, other components are required in the real source and you don't need to be bothered with that. This file also has no issues with remaining public; maybe it will help someone else. I stripped out everything to leave only a loop in main that:

1. Executes transmission of a 16-byte payload BLE packet formatted 0x00 0x01 0x02......0x0F. As mentioned earlier, PHY BLE packet structure for testing(not standard BLE packet).

2. Executes transmission of a 16-byte payload 802.15.4 packet formatted 0x00 0x01 0x02......0x0F. Ditto on PHY only.

3. The 2 protocols will toggle back and forth every 500ms.

4. LED1 of the pca10056 will flash when BLE is TXing and LED2 will flash when Eight02 is TXing.

5. UART_DBG_INT(0xXX) outputs //DBG ints for simple UART debugging.

6. pca10056 #defines EXT_UART_RX_PIN 30, EXT_UART_TX_PIN 31 using 921,600 8N1.

7. BLE packet sends fine. Visible to RX code running on 52832.

8. I only added DBG in Eight02_send_packet() since that is where my problem is. DBG out is 0x02 0x04 0x05 0x06 0x0A...then repeats.

Let me know if you need anything else. Thanks!

RE: 802.15.4 Test dev migration to 52840

Jørgen Holmefjord — Wed, 23 May 2018 10:51:55 GMT

Yes, the process in the PS is supposed to work. Just make sure you follow the guidelines in 6.20.12 (IEEE 802.15.4 operation). Could you upload your test project?

The driver does come with some arbitration and resource requirements, but this is a standalone driver which do not depend on any softdevice/SDK/libraries/etc. The sample applications are quite simple and straight forward.

RE: 802.15.4 Test dev migration to 52840

zzzLNAWS2 — Tue, 22 May 2018 15:37:11 GMT

Thanks for you response JH. I have read through this. And, although it may fit nicely, it still doesn't really answer the question as to whether or not direct register control will actually work to TX/RX an 802.15.4 PHY packet. The process outlined in 6.20.12.6/7 of the PS seems pretty straight forward. Is the outlined process supposed to work per the PS? (otherwise, why include the process).

My entire approach has used direct register control for the testing procedure. As stated, I appreciate your response. But, adding this driver muddies the water with other secondary issues like resource allocation, arbitration, softdevice requirements, new peripheral dependencies, etc. etc. etc.... most of which i'm not even sure of at this point considering the driver implementation has its' own NEW learning curve....as apposed to just setting up a few registers and dumping bytes into PACKETPTR.

So, can you help? Thanks again

RE: 802.15.4 Test dev migration to 52840

Jørgen Holmefjord — Tue, 22 May 2018 14:03:07 GMT

Hi,

Have you looked at the 802.15.4 driver available on our GitHub page? This should fit in quite nicely between using the registers directly, and the 802.15.4 libraries in the SDK.

Best regards,
Jørgen

RE: 802.15.4 Test dev migration to 52840

zzzLNAWS2 — Mon, 21 May 2018 22:22:52 GMT

No takers? All I want to do is send some dummy info for RF testing. But, that seems like a MAJOR task. Migration for BLE testing from 52832>52840 works fine but I can't get an 802.15.4 packet out of the radio no matter what I try. PLEASE HELP.

Thanks!