nRF5 action!
-
In the next version I'm going to use a somewhat unusual shaped solder jumper, in case I want to use just a single coin cell battery (not two) and therefore bypass the LDO (well, not install an LDO at all).
-
@NeverDie I'm thinking about making the jump from NRF24s and RFM69s to the NRF5 eco system. I see you have tried quite a few different modules. If you had to pick now, would you go with the Fanstel BT832X for a gateway and BT832 for most modules?
-
@nagelc said in nRF5 Bluetooth action!:
@NeverDie I'm thinking about making the jump from NRF24s and RFM69s to the NRF5 eco system. I see you have tried quite a few different modules. If you had to pick now, would you go with the Fanstel BT832X for a gateway and BT832 for most modules?
Yes. If cost and space were no issue, I'd probably use the BT832X on everything, because it also has the best antenna. For nRF52's, for what I'm doing I like Fanstel's stuff the best. If I needed a module with more exposed pins, then the EByte would be my choice. But nothing I'm doing requires that many exposed pins, and I think the Fanstel will likely be drop-in upgradeable to the final nRF52840 modules when final silicon for that becomes available. Of course, there's no guarantee of that, but it seems very likely.
Also important, at least to me, is that the Fanstel modules have FCC approval, and being based in the US, I don't think they're lying about it (unlike random stuff from China).
That said, the nRF51822-04's are a lot of fun, because they're small and relatively cheap.
-
Great. I have some on order. Can't wait go start playing around with them.
-
@nagelc said in nRF5 Bluetooth action!:
Great. I have some on order. Can't wait go start playing around with them.
Great! I invite you to start making posts to this thread when you do, as fresh perspectives are always welcome.
-
Hello, I want to build battery powered modules (with sleep). I found on Ebay NRF51822 round module with case (https://www.ebay.com/itm/hello/112650665753) - only $6.50 with shipping. Is this module is good choice? Any pitfalls?
I planning to use water leak sensor, BME280 (I2C), ds18b20(1-wire), maybe MH-Z19 later.
I don't have enough experience, I have only used ESP8266 NodeMcu V3 and Arduino before.
I can see one I2C (for programator and sensors?) and one GPIO as button for water leak (right?) + LED pin. Does this module have more pins? Shall I connect to chip legs to obtain more pins (GPIO) (does I need to connect resistors?) for 1-wire or better use some sort of I2C GPIO expander?
-
@alexey-strelnikov
Looks nice, but any hardware mods and it probably won't fit the case anymore.
-
@alexey-strelnikov I have one and there are pads to program it but nothing more, it's not really a "module" but a Bluetooth beacon, the only 2 I/Os available are those from the button and the led, there's a footprint for an accelerometer also but the pads are too tiny to solder any wire.
If you're planning to use other sensors don't buy that one. It's great as a button sensor but any other use will need soldering to LGA-sized pads...
-
I received the "holyiot" modules and they are really, really tiny. 2 attached together are exactly the same size than the 51822-04 module. WL-CSP package is very impressive: small, very thin and with a cool shinny surface.
This module has inductors for DC/DC mode, and pins .00 and .01 are mapped so it's possible to add low frequency crystal for Bluetooth mode.
-
Nice!
I'll be very interested to know how the range compares. At least so far, in my own comparisons, smaller has meant less range. Not necessarily a deal killer though, as you only need range that's "good enough," and you can compensate with a better antenna on the gateway.
-
@neverdie said in nRF5 Bluetooth action!:
Nice!
I'll be very interested to know how the range compares. At least so far, in my own comparisons, smaller has meant less range. Not necessarily a deal killer though, as you only need range that's "good enough," and you can compensate with a better antenna on the gateway.
Yes I'll try to test next week to have an idea of the range, if it's "good enough" to be usable at least with a central pa/lna gateway or if it's better to stick with bigger PCB antennas.
nrf51822-04 is small enough but this one has a better chip and 11 I/Os available, that's precious for a multisensor board.
-
@nca78 said in nRF5 Bluetooth action!:
nrf51822-04
What I've noticed is that Rx range was much more compromised with a reduction in size than the Tx range is. Or, to put it differently, Tx range isn't as dramatically compromised. That's potentially good news for a sensor, which may Tx only anyway (i.e. "passive" in the mysensors jargon). But even if it does Rx, your gateway can be much more powerful on its Tx. So, it potentially works out rather nicely, if you know what I mean.
-
Just received my Fanstell modules. Yikes! 1.1mm pin pitch didn't look that small in the pictures. Do you solder these by hand? I thought my soldering skills were getting pretty good, but I can see I'm going to have to up my game.
-
@nagelc Yes, I solder it by hand. It's easier than it looks. Just use a narrow tip and maybe extra flux if you need it.
-
Here's my latest gateway sheild for the Wemos D1 Mini:
In the interest of both belt and suspenders, I gave it its own 300ma LDO so that it won't be competing with the Wemos D1 Mini for current. Earlier measurements of this Fanstel ldo-pa nRF52832 shows that it can draw up to 250ma.
It's designed to work well with ESP-LINK, which can also be used to remotely reset the nRF52832 if that's ever needed. Presently, I'm using ESP-LINK's built-in MQTT to send MQTT to a Mosquito MQTT broker. This offloads that task from the nRF52832, which just inputs/outputs serial.
By the way, I soldered the entire thing using a wide chisel point solder tip, so it turns out you don't really need a narrow solder tip after all. I do use Rosin flux, though, and it does a great job. The only inconvenience is that the excess Rosin flux should be cleaned off afterward, but, meh, I don't find that to be much of a bother.
-
@nca78 said in nRF5 Bluetooth action!:
@neverdie said in nRF5 Bluetooth action!:
Nice!
I'll be very interested to know how the range compares. At least so far, in my own comparisons, smaller has meant less range. Not necessarily a deal killer though, as you only need range that's "good enough," and you can compensate with a better antenna on the gateway.
Yes I'll try to test next week to have an idea of the range, if it's "good enough" to be usable at least with a central pa/lna gateway or if it's better to stick with bigger PCB antennas.
nrf51822-04 is small enough but this one has a better chip and 11 I/Os available, that's precious for a multisensor board.Any update?
Also, what is the size of the pads? The only info I've found is what appears on the aliexpress website, which only seems to express the distance (center to center) between the pads. I just received some of these modules, so I'd like to maybe do a prototype PCB using my CNC machine.
BTW, I notice that the price went up from $3.20/module to $4/module.
And something tells me it will probably go higher still.
-
@neverdie said in nRF5 Bluetooth action!:
@nca78 said in nRF5 Bluetooth action!:
@neverdie said in nRF5 Bluetooth action!:
Nice!
I'll be very interested to know how the range compares. At least so far, in my own comparisons, smaller has meant less range. Not necessarily a deal killer though, as you only need range that's "good enough," and you can compensate with a better antenna on the gateway.
Yes I'll try to test next week to have an idea of the range, if it's "good enough" to be usable at least with a central pa/lna gateway or if it's better to stick with bigger PCB antennas.
nrf51822-04 is small enough but this one has a better chip and 11 I/Os available, that's precious for a multisensor board.Any update?
Also, what is the size of the pads? The only info I've found is what appears on the aliexpress website, which only seems to express the distance (center to center) between the pads. I just received some of these modules, so I'd like to maybe do a prototype PCB using my CNC machine.
BTW, I notice that the price went up from $3.20/module to $4/module.
And something tells me it will probably go higher still.Sorry I was busy with other things. Now my switch seems to work I will quickly finish other atmega projects and make the switch to nrf5x.
For pad sizes, I believe from the pictures below it's 1mm width (grid size is obviously 0.5mm)
-
@nca78 do you move your fantastic Nmodules to nrf5 platform?
-
@toyman said in nRF5 Bluetooth action!:
@nca78 do you move your fantastic Nmodules to nrf5 platform?
Probably, and I will switch to MYSX connector too.
-
I was just about to make a test board using my CNC when out of the blue my CNC died during setup. So, I did this board instead and will have it fabbed:
-
@neverdie for a test board why are you not using standard headers and mapping all pins available ?
-
@nca78 Because originally I was going to do the board on my CNC (that is, before my CNC dropped dead on me), and I wanted to make it as easy as possible for the CNC to succeed. Also, for testing purposes, I'm most interested in how well it sends/receives, and I don't need many pins to test that. Also, soldering this module may be tricky, so I wanted only the minimum number of pins in case soldering it proves to be difficult.
-
Just received these tiny NRF51822 devices and would like to turn them in to MySensors 1 button scencontroller.
Where should I start?- I guess I will need some kind of USB adapter ti program them. Think I read somewhere about JLink. Would this do?
-
@korttoma did you check here ?
https://forum.mysensors.org/topic/6705/mysensors-nrf5-platformFor programming the best solution is probably the NRF52 DK, it's not very expensive (30€) and you avoid all the problems related to license of the fake JLINKs (and bricking of the device if you happen to accept the invitation to update the outdated firmware on it), as it includes official licence for programming all nrf5 chips.
https://www.arrow.com/en/products/nrf52-dk/nordic-semiconductor
-
Hi,
Working without problem with mysensors, I use STLink v2 from Aliexpress. LED and Button are mapped on pins 28 and 29
-
Now I feel stupid ordering the NRF52 DK for 28€. Well atleast I don't need to worry about bricking any devices.
Do you have an example sketch for the device you can share?
Is it possible to somehow monitor the battery status?
-
@korttoma said in nRF5 Bluetooth action!:
Is it possible to somehow monitor the battery status?
One of @d00616 's demo sketches allows you to read the voltage that's powering the nRF5. Assuming there is no booster involved on this device (seems unlikely), that would be the same as the battery voltage.
-
@korttoma do you have an Aliexpress link to them?
-
-
@korttoma thx. Do they have a CR2032 slot? Sorry, it's not clear from the pictures
-
@toyman yes
-
It would probably do well as a "one button scene controller," but is it good for anything else I wonder?
-
@neverdie does not seem to be any easy way to get access to any of the pins on the board but who does not need a bunch of "one button scene controllers"?
-
I was tempted to try adding the missing accelerometer too, but in the end it's easier and cheaper to make a board with the 2$ module.
-
Speaking of which, I shrunk the HolyIOT board a bit and added the small buzzer:
Hopefully this is small enough that it can be used as a locator beacon.It turns out this is pretty nearly the minimum size, even if the HolyIOT were smaller, because of the CR2032 battery underneath it. Anyway, that's an interesting result, because the BC182 is smaller than the HolyIOT, but I wouldn't get the benefit of it.
-
@neverdie said in nRF5 Bluetooth action!:
small buzzer:
CR2032 batteryIf I'm not wrong this buzzer needs over 100mA, not sure it's a good match for a CR2032 ?
-
@mika said in nRF5 Bluetooth action!:
Hi,
Working without problem with mysensors, I use STLink v2 from Aliexpress. LED and Button are mapped on pins 28 and 29Im just reporting sketch from NeverDie
https://www.openhardware.io/view/510/Multi-Sensor-TempHumidityPIR-LeakMagnetLightAccel
-
@nca78 said in nRF5 Bluetooth action!:
@neverdie said in nRF5 Bluetooth action!:
small buzzer:
CR2032 batteryIf I'm not wrong this buzzer needs over 100mA, not sure it's a good match for a CR2032 ?
I like how nothing slips past you! Yes, it's a pretty severe trade-off in exchange for its small size. So, I'll be using two CR2032's and make it run only in very short bursts. I honestly don't know how well or badly it will turn out.
-
@neverdie said in nRF5 Bluetooth action!:
I like how nothing slips past you! Yes, it's a pretty severe trade-off in exchange for its small size. So, I'll be using two CR2032's and make it run only in very short bursts. I honestly don't know how well or badly it will turn out.
I don't see anything to co trim such a high current on your board ? Maybe it's the reason the sound level is low on your other board, max current of the MCU pin is much lower than what the buzzer needs ?
-
@nca78 said in nRF5 Bluetooth action!:
@neverdie said in nRF5 Bluetooth action!:
I like how nothing slips past you! Yes, it's a pretty severe trade-off in exchange for its small size. So, I'll be using two CR2032's and make it run only in very short bursts. I honestly don't know how well or badly it will turn out.
I don't see anything to co trim such a high current on your board ? Maybe it's the reason the sound level is low on your other board, max current of the MCU pin is much lower than what the buzzer needs ?
What does "co trim" mean?
-
@neverdie said in nRF5 Bluetooth action!:
What does "co trim" mean?
Sorry phone rewriting what I type.
"Control".
MCU pins can't source that much current and I see no transistor on your board to do it ?
If you put a reserve capacitor big enough to supply 100+mA long enough to make some sound on the buzzer, will you not fry the pin ?
-
The present design uses a TPS22860 load switch to turn on and off the buzzer. I'm not trying to power the buzzer directly from one of the nRF52832 pins, because the current would be outside the maximum limits for the nRF52832 pin. I'm hoping the two CR2032's will give enough headroom that the voltage (after the LDO) will be stable.
-
@neverdie didn't now this chip, nice one thank you I've added it to my next order.
Seems I should have a better look at your designs
-
@nca78 said in nRF5 Bluetooth action!:
I received the "holyiot" modules and they are really, really tiny. 2 attached together are exactly the same size than the 51822-04 module. WL-CSP package is very impressive: small, very thin and with a cool shinny surface.
This module has inductors for DC/DC mode, and pins .00 and .01 are mapped so it's possible to add low frequency crystal for Bluetooth mode.
Have you tried uploading anything to the HolyIOT modules? I've now tried on two different HolyIOT modules, both without success.
-
@neverdie said in nRF5 Bluetooth action!:
Have you tried uploading anything to the HolyIOT modules? I've now tried on two different HolyIOT modules, both without success.
Sorry not yet, I've just re-plugged my NRF5 board and I'm figuring out how to program external board. I'll do it with a board I know works, then try the holyiot module;
-
@nca78 It's a tricky module to solder (probably the most tricky of them all that I've tried so far), so to eliminate that concern on the second module I flipped it over and soldered wires directly to the four essential pads. That way I could visually confirm that it was soldered correctly. Still fails. So, just FYI.
-
I think I see the problem. These pinouts are inconsistent:
I had been basing it on the first one, whereas I'm now guessing that the second one is probably the correct one.
-
Confirmed. That was the problem. Using the second pinout, it now uploads.
-
I have the HolyIOT blinking an LED and receiving packets now. Range, as I suspected, is rather mediocre, but that's probably an inherent trade-off for its small size. For my purposes I don't think it will matter.
-
@neverdie was the difference that they were mirrored along vertical axis? Or am I missing a difference in labelling?
-
@mfalkvidd said in nRF5 Bluetooth action!:
@neverdie was the difference that they were mirrored along vertical axis? Or am I missing a difference in labelling?
Yes, in the first picture the pin labels should have been mirrored, but weren't. Or, to put it your way, they were mirrored from what they should have been. Either way, it's just wrong.
The second picture is the correct one.
-
Anyone heard anything about when the nrf52840 might be released? I had thought we'd have heard something by now. Surely sometime in 2018 at least? What's the nearest competing chip?
-
afaik (and I got a confirmation from Nordic too), there is no plan for other nrf52840 package than AQFN.
If you're searching for the ic, you'll have to use this footprint, which needs premium pcbs (micros vias, and multilayers for escaping routes and better plane).
It's also more tricky to solder than a fanstel BT840s and its bottom pins. BT840s edge pins are easy to solder sure but there are not so many. All others pins are on bottom as you know. Of course, it's the same for BT840, easier&better perf when using 4layers, but that can be done with 2layers (also explained in datasheet though).
From what I saw, others nrf52840 module sellers are going on same road, lot of tiny pads on bottom of the module, yes you can't do small things with big things, and there are lot of pins!There is another thing to know. no arduino core for nrf52840 yet. Yes, it's possible to use radio, some pins too, but no spi, i2c etc. that's because it needs some code refactoring to handle multiple io ports (nrf52832 one io port, whereas 840 has two).
imho there are better mcu
some silabs mcu for example.. but not arduino compatible, out of scope here, and lot of people would say, "not interested, it's two bucks more expensive", way of talking (not mine) as i don't remember the exact price .
-
@scalz To get smaller size, I expect we'll see modules with reduced pin counts for the 52840, just as we already do for the 52832. Have you heard anything about when final silicon for the 840 will be shipping?
-
@neverdie said in nRF5 Bluetooth action!:
@scalz To get smaller size, I expect we'll see modules with reduced pin counts for the 52840, just as we already do for the 52832. Have you heard anything about when final silicon for the 840 will be shipping?
yes sure. reduced IO pin counts.. and maybe even more reduced if they try to fit new features instead of IO (like usb etc). The above holyiot module example:
- replace two IOs by USB pins.
- keep same pinouts, but no USB, pity for a new interesting feature, but i can imagine not all people interested in it
- need to enlarge the module for same pinout + usb pins
- same module size and pinout, +usb, -> add bottom pads
I still don't get the point of a holyiot module, and chip antenna modules, when it's not for wearables though!
Complete waste of specs
a 840 like that would be "funny", not much pins, with a chip ant..what would be the point then to buy a 840?? short ble5 range, no usb or just a few ios etc, yuk!
If you're after range, then take a look at the range comparison fanstel made. it's explicit how their different module design impact range. But if you don't need all the new bells&whistles of 840, then it may be smarter to use 832 or nrf24pa, and a good module, too bad to buy a module with degraded RF..I asked Nordic two months ago, I don't think their eta changed. should be soon I imagine.
-
@scalz said in nRF5 Bluetooth action!:
I still don't get the point of a holyiot module, and chip antenna modules, when it's not for wearables though!
Not really disagreeing with you, but it's nonetheless interesting that if you do a search on Aliexpress for nrf52832 and sort the results by number of orders, the HolyIOT has gotten by far the biggest number of orders:https://www.aliexpress.com/premium/nrf52832.html?spm=2114.search0204.0.0.631303423oXjxi&site=glo&groupsort=1&SortType=total_tranpro_desc&g=y&SearchText=nrf52832&tc=ppc&initiative_id=SB_20180117073832&needQuery=n&filterCat=100000201,200010206,200084026[Edit: I'm wrong. The Ebyte module got the most orders.]
-
I measured the Fanstel BTC832X at maximum Tx, and it draws more current than I had thought: around 330ma. As you would expect, though, the range and coverage is excellent, even at 2mbps, and even for diminutive receivers like the HolyIOT.
For that reason, I think it generally beats the RFM69's performance, which IIRC consumes around 100ma at max Tx power, but has a max transmit speed of 300kbps. i.e. Total mah to transmit a payload should be less with the Fanstel BT832X.
-
Since the Fanstel's don't come with the low frequency crystal oscillators already installed, when it is worthwhile to install them? I'm blithely running off the built-in RC oscillator, and I'm not noticing problems.
-
Even with two CR2032's in series, I can't get 330ma out of them for very long, if at all, before internal resistance becomes severe and it plummets to 110ma or less. Nonetheless, at least some of the preliminary testing suggests that the initial burst may be good enough to extend the Tx range for long enough (100ms) to reliably wake a sleeping receiver node that sits outside the range of a non-amplified transmitter.
-
@neverdie The internal RC Osc will allow you to keep your BOM costs lower. However when using the Bluetooth Softdevice the Crystal will lower the power consumption as the BT window will be narrower.
-
@jokgi said in nRF5 Bluetooth action!:
@neverdie The internal RC Osc will allow you to keep your BOM costs lower. However when using the Bluetooth Softdevice the Crystal will lower the power consumption as the BT window will be narrower.
Is the choice of RC osc or crystal of any consequence at all for Nordic's proprietary radio modes? For instance, I wasn't sure whether or not the cyrstal's greater accuracy might achieve a lower bit error rate at 2mbps.
-
@neverdie I suppose the radio is using the high frequency clock, so it doesn't have any influence ?
-
@nca78 said in nRF5 Bluetooth action!:
@neverdie I suppose the radio is using the high frequency clock, so it doesn't have any influence ?
The LFCLK is required for BLE timing. Without the MCU required more energy to generate (synthetic) or calibrate (RC) the 32kHz signal.
-
@d00616 said in nRF5 Bluetooth action!:
@nca78 said in nRF5 Bluetooth action!:
@neverdie I suppose the radio is using the high frequency clock, so it doesn't have any influence ?
The LFCLK is required for BLE timing. Without the MCU required more energy to generate (synthetic) or calibrate (RC) the 32kHz signal.
Since Mysensors isn't using BLE, then it doesn't matter?
-
Where can i get a Kicad component for Ebyte nrf52832?
-
You can find it in my kicad repo: symbol and footprint
I didn't used it in any design so please double check.
-
Any suggestions how can I get serial debug messages out of the NRF52832 (Fanstel BT832)? I can upload the program over the SWD interface. I'm using a black magic probe with the Arduino NRF5 package on Windows 10. I know it works because the node shows up in my controller.
-
@nagelc said in nRF5 Bluetooth action!:
Any suggestions how can I get serial debug messages out of the NRF52832 (Fanstel BT832)?
Define one of the pins as serial TXO. Then connect it to RXI on an FTDI TTL-USB converter and read it that way. That's what I do, and it works.
-
@neverdie
Do you define the pins in MyBoardNRF5? In MyBoadNRF5.cpp, I replaced the 0 in the first line with10, thinking this will map Arduino TX0 to P010. This did not seem to work. How do you map the TX0 pin?
-
@nagelc No, you want to change the values in the MyBoardNRF5.h file instead. For an example, see the source code in: https://www.openhardware.io/view/499/10-years-wireless-PIR-Sensor-on-just-one-set-of-3-AAs#tabs-source
So, in your case, you'd want:
#define PIN_SERIAL_TX (10)and, to avoid conflicts, make sure that pin P0.10 isn't defined anywhere in the same .h file as something else already. If it is, you may need to change that as well.
-
Thanks. I'll give that a try.
-
Yesterday, I 've got a mailing from my components' supplier featuring new type of cells, Li-MnO2. The cell has all the features needed for nRF5:
- 1200mah capacity
- 1.8-3.0v range
- low cost (ca. $3)
- 41,0 x 24,5 x 5,2 dimensions and, importantly
- up to 120mah peak discharge current.
The link to manufacturer:
http://www.fanso-battery.com/Ultra-thin-Li-MnO2-battery-CP502440-3V1200mAh-pd1905.html
-
@toyman said in nRF5 Bluetooth action!:
Yesterday, I 've got a mailing from my components' supplier featuring new type of cells, Li-MnO2. The cell has all the features needed for nRF5:
- 1200mah capacity
- 1.8-3.0v range
- low cost (ca. $3)
- 41,0 x 24,5 x 5,2 dimensions and, importantly
- up to 120mah peak discharge current.
The link to manufacturer:
http://www.fanso-battery.com/Ultra-thin-Li-MnO2-battery-CP502440-3V1200mAh-pd1905.htmlMhmhmh, a disposable battery that you have to solder I can't see it as a good idea for a node...
-
@nca78 said in nRF5 Bluetooth action!:
@toyman said in nRF5 Bluetooth action!:
Yesterday, I 've got a mailing from my components' supplier featuring new type of cells, Li-MnO2. The cell has all the features needed for nRF5:
- 1200mah capacity
- 1.8-3.0v range
- low cost (ca. $3)
- 41,0 x 24,5 x 5,2 dimensions and, importantly
- up to 120mah peak discharge current.
The link to manufacturer:
http://www.fanso-battery.com/Ultra-thin-Li-MnO2-battery-CP502440-3V1200mAh-pd1905.htmlMhmhmh, a disposable battery that you have to solder I can't see it as a good idea for a node...
well, 1200mah will last AT LEAST for a year (two in real life). I have no issues resoldering 2 joints once a year, given it gives AAA capacity in a much smaller package
-
Speaking of batteries, I found only one proper holder for holding two CR2032's in series:
It turns out you pretty much need the plastic carrier to guarantee that the edge of the button cell doesn't short out against the side of the metal holding bracket.
-
@neverdie said in nRF5 Bluetooth action!:
Speaking of batteries, I found only one proper holder for holding two CR2032's in series:
There are CR2477 (560mAh) or CR2450 (950mAh) 3V cells. Maybe its's better to handle.
-
@toyman said in nRF5 Bluetooth action!:
41,0 x 24,5 x 5,2 dimensions and, importantly
Footprint seems kinda large, at least for nodes intended to be small. It trades off length in order to get thin. In contrast, a CR123 is shorter (34.5mm), but thicker (17mm), but can deliver 1.5a continuous (which makes it very tempting for powering a PA):
https://www.batteryjunction.com/energizer-cr123a.html
On the other hand, when you add the CR123 holder, the length may be comparable.If you decide to try out the fanso, please do let us know how you like it.
-
@d00616 said in nRF5 Bluetooth action!:
There are CR2477 (560mAh) or CR2450 (950mAh) 3V cells. Maybe its's better to handle.
Good point. I think maybe the only actual justified use of two CR2032's in series is to power the AM612, which requires a voltage of at least 2.7v.
-
Did someone get an NRF52 working with an ESP8266(ESP32) and successfully connected it to a controller?
Since my controller is something stuffed away in a closet, Id like to have a gateway that's positioned more centralized. An ESP+NRF52832 would be a lovely cost-efficient solution.
-
@omemanti said in nRF5 Bluetooth action!:
Did someone get an NRF52 working with an ESP8266(ESP32) and successfully connected it to a controller?
Yes: https://www.openhardware.io/view/491/PA-LNA-nRF52832-ESP-LINK-Shield-for-Wemos-D1-Mini-ESP8266
Works great!
-
@neverdie ah thnx. I'll try it out with my nodemcu+ebyte
-
@neverdie
It worked! I used pin 26 as in your example and now can get the debug messages. Also thanks for the many other NRF5 routines you had in the example.
-
How can I connect to DEC5 as an I/O when using MyBoardNRF5?
The Ebyte Module Datasheet says: 14 DEC5 Input/Output MCU GPIO to it should be possible?
-
@omemanti Suggest you check the Nordic datasheet on that rather than rely on the Ebyte documentation. IIRC, the DECT pins are not GPIO, but it's worth your double checking the nRF52 datasheet if it's important to you.
-
@neverdie, Indeed, I checked and it was false. well goes to show that late-night prototyping has some disadvantages, my bad,
Deleted Following up question..
DK =>Ebyte module
GND(detect) => GND
SWDIO => SWDIO
SWDCLK => SWCLK
VTG => 3,3V
3,3V => 3,3V
GND =>GND
-
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
I pulled a lot of hair trying to find out what I did wrong with my board, I soldered an adapter to make sure I didn't have problems with faulty jumper wires etc, I reinstalled JLink and Nordic software, in the end I desoldered everything on my board, then the module itself to program it independantly. It always failed and JLink couldn't connect to it. I tried the other spare one I had, same result. I tried the one I'm sure I managed to program long ago with a jlink clone, always the same result.
Then I tried with an old nrf51822 module I bought long ago on AliExpress, and no problem !Has anyone had similar problems ? Is there something special hardware wise that I should check ?
-
@nca78 said in nRF5 Bluetooth action!:
Has anyone succeeded in programming the WT51822-S4AT module (the cheapest and tiny nrf51822 module on AliExpress) using NRF52 DK ?
Yes. Haven't had a problem.
A couple things:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I know you know these things, but sometimes we forget to do what we know.
-
@Nca78
Do you have the J-Link with only 4 pins? And if so, is the module a QFAAH0? In this konstalation I have the same problem, but with the J-Link V8 and ST-Link V2, the module can be programmed without any problem.
-
@Nca78
Also, what board type in the arduino IDE are you using to program it? That could be throwing you off as well.
-
@neverdie said in nRF5 Bluetooth action!:
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
if bulk erase is needed, then it means it was programmed
a fresh new mcu is usually not programmed unless you ask for it to the manufacturer..Like said above, it could be a problem with module, power issue, usb & cable, dupont cable, jlink, jlink setup, arduino core etc.
-
@neverdie said in nRF5 Bluetooth action!:
- Are you powering the nRF51 module externally (separate from the nRF52DK)? It's highly advisable that you do, even though by random luck, you can sometimes succeed without it.
I was at the beginning, but after that I tried with power from the DK. I will try again with external power.
- Especially for new, unprogrammed modules, you need to do a bulk erase at the beginning. I do this by the d00616 trick of saying "Burn bootloader" with a null bootloader. The burning bootloader process fails, as expected, but the side-effect is that it does a bulk-erase before failing.
I can't even reach that step, JLink can't establish the SWD connection so there's no way to erase the chip.
-
@nca78 said in nRF5 Bluetooth action!:
I was at the beginning, but after that I tried with power from the DK. I will try again with external power.
I use a battery pack with a 3.3v regulator as the external power source. Don't just use 2xAA. If the voltage is too low, it will fail to program.
-
@scalz said in nRF5 Bluetooth action!:
if bulk erase is needed, then it means it was programmed a fresh new mcu is usually not programmed unless you ask for it to the manufacturer..
Well, you would think so, and yet it seems I always need to do it anyway on a new module. Go figure.
-
@sarg666 said in nRF5 Bluetooth action!:
Do you have the J-Link with only 4 pins? And if so, is the module a QFAAH0? In this konstalation I have the same problem, but with the J-Link V8 and ST-Link V2, the module can be programmed without any problem.
I use the JLink included on the NRF52DK.
@scalz said in nRF5 Bluetooth action!:
if bulk erase is needed, then it means it was programmed
a fresh new mcu is usually not programmed unless you ask for it to the manufacturer..No because the <3$ modules are made to be controlled with an external MCU using serial commands, the same way than ESP8266 for Wifi, so they have a firmware installed.
-
For those interested, only 2.55$ for the CDEByte NRF52832 modules
[edit] Limited to 2 / customer, but you can buy 2 more in the other CDEByte store here
https://www.aliexpress.com/store/product/CDEBYTE-E73-2G4M04S-BLE-4-2-5-0-long-distance-100m-2-4GHz-SMD-ARM-Core/2077046_32820692238.html
-
@NeverDie @Nca78
then buy a fresh mcu on Mouser and you'll see by yourself
You don't get what I meant, I'm not talking about a specific module design, but in general. the mcu can be accessed by jlink no matter, else how would you program it in first place ..
-
@scalz said in nRF5 Bluetooth action!:
@NeverDie @Nca78
then buy a fresh mcu on Mouser and you'll see by yourself etc
You don't get what I meant, I'm not talking about a specific module design, but in general. the mcu can be accessed by jlink no matter, else how would you program it in first place ..Yes, but when there's a firmware it can be locked, so you must unlock it and erase it to remove softdevice and be able to write something.
-
@nca78 said in nRF5 Bluetooth action!:
I tried with power from the DK.
I don't know why, but I seem to recollect that doing it that way may confuse it. Otherwise, I don't know how I would have ended up using a battery pack instead.
-
@nca78 said in nRF5 Bluetooth action!:
@scalz said in nRF5 Bluetooth action!:
@NeverDie @Nca78
then buy a fresh mcu on Mouser and you'll see by yourself etc
You don't get what I meant, I'm not talking about a specific module design, but in general. the mcu can be accessed by jlink no matter, else how would you program it in first place ..Yes, but when there's a firmware it can be locked, so you must unlock it and erase it to remove softdevice and be able to write something.
are you sure it's locked? I thought neverdie suggested to erase it with jlink.
well, you should choose a better module than funky design modules.. just my opinion, for saving?? 2bucks!
-
@scalz Well, what do you think he should use instead? Bare chips? That's not as easy to solder.
Suggested Topics
-
Welcome
Announcements • • hek
