Problems with 2018 purchase of nRF6700 and nRF24LE1-F16Q24-DK from Mouser Australia - Advice on how nRF6310 Firmware issue was resolved 3743 > 7000

RE: Problems with 2018 purchase of nRF6700 and nRF24LE1-F16Q24-DK from Mouser Australia - Advice on how nRF6310 Firmware issue was resolved 3743 > 7000

PeeDub5178 — Tue, 09 Oct 2018 03:57:41 GMT

Hi Kenneth, thanks for your advice. I'll look into the 51/52 series but we are trying to avoid Bluetooth if possible. I think our application is more suited to plain vanilla 2.4Ghz RF - the requirements are modest: 12 byte packet to be transmitted every 10mS. Further, many of the packets would contain redundant data so we expect to aggressively power down the chip to save battery life.... hence, a main requirement is that we can power up and reconnect within 2-4mS. I'm not hopeful that this will be possible in many environments when the IoT is more ubiquitous. I understand that plain vanilla RF is sharing the same bandwidth (2.4GHz), but believe it may be possible to achieve reconnection faster if we're not running a BLE protocol. I would appreciate any thoughts you or others have on that topic. Also, if anyone has contemporary experience with the nRF24 series (and any problems with the O/S) I'd love to hear abput that too. Thanks again......... Peter

RE: Problems with 2018 purchase of nRF6700 and nRF24LE1-F16Q24-DK from Mouser Australia - Advice on how nRF6310 Firmware issue was resolved 3743 > 7000

Kenneth — Mon, 08 Oct 2018 17:22:47 GMT

Is there any way I can persuade you to use the nRF51- or nRF52-series?

The nRF24L-series have not received an update for quite some years, and unless you are using the specific operating system it was built for at the time, there may be issues I suppose.

Best regards,
Kenneth

RE: Problems with 2018 purchase of nRF6700 and nRF24LE1-F16Q24-DK from Mouser Australia - Advice on how nRF6310 Firmware issue was resolved 3743 > 7000

PeeDub5178 — Fri, 05 Oct 2018 07:36:33 GMT

Thanks Runar... I figured that out (I was following the Getting Started Guide - which is completely out of date and shouldn't be shipped with the product. I now have a different problem: The rf6310 motherboard firmware is out of date (Rev 3743) so the bootloader fails. I followed an old post by Hakon to update with a cmd line version of DFU-programmer... but that didn't recognise the device... so I reset the board (as per Hakon again) so it now enumerates as: AT90USB128. That doesn't help as the DFU doesn't recognise that either. The other alternative seems to be Atmel FLIP method, which I haven't figured out yet. Surely if this is a Studio "issue' (as it was described) that would have been fixed by now? I have Studio Rev 1.21.2.10 and DFU: 0.4.5. Any help greatly appreciated... there must be an easy solution? P.s. I suggest it is not appropriate for Nordic to be selling products which take days of investigation just to get them running?

RE: Problems with 2018 purchase of nRF6700 and nRF24LE1-F16Q24-DK from Mouser Australia - Advice on how nRF6310 Firmware issue was resolved 3743 > 7000

run_ar — Fri, 05 Oct 2018 07:27:53 GMT

Hi,

As far as I know you do not need a product key anymore. Please check if you can access the downloads without a key:

https://www.nordicsemi.com/eng/Products/2.4GHz-RF/nRFgo-SDK

https://www.nordicsemi.com/eng/Products/2.4GHz-RF/nRFgo-Studio