Atmega 328p memory
-
So I have not done anything yet with the nRF51 or 52's. Can I just drop nRF51/52 nodes in to my nRF24 gateway setup and have them work? I am currently using MySensors 2.0. Have not yet upgraded to 2.1 or 2.2. 2.2 from the things I have seen seems a bit buggy right now, but I could upgrade my gateway to 2.1.

As can be seen in the image above, the outer header connections are what I would like to be able to mimic to be backwards compatible with my old board setups. If I was going to move to an nRF51 or 52 board, that is something that I would like to keep the same. I have not looked too much at these yet, but it is my understanding that the nRF51/52 boards contain the MCU and radio in one package. Can anyone that has used these recommend a good reasonably priced module that would work with my setup? I will look at designing a new board around these if things look good..@dbemowsk I like this device because it has headers so no soldering strictly required. Note that the distance is smaller than the "standard" 2.4mm.
-
@dbemowsk I like this device because it has headers so no soldering strictly required. Note that the distance is smaller than the "standard" 2.4mm.
@mfalkvidd said in Atmega 328p memory:
@dbemowsk I like this device because it has headers so no soldering strictly required. Note that the distance is smaller than the "standard" 2.4mm.
The 2mm pitch is a pain if you do not use the BLE400 motherboard that goes with it.
It took me ages to source a 2mm pitch protoboard then sockets to plug it into.
But it is easy to use.:relaxed: -
@mfalkvidd said in Atmega 328p memory:
@dbemowsk I like this device because it has headers so no soldering strictly required. Note that the distance is smaller than the "standard" 2.4mm.
The 2mm pitch is a pain if you do not use the BLE400 motherboard that goes with it.
It took me ages to source a 2mm pitch protoboard then sockets to plug it into.
But it is easy to use.:relaxed:@rmtucker Even if I do design a new board, I would at least like to do a protoboard version first like I usually do, so you have a good point. Will the MySensors library work with a 52832 board like this one? I haven't read up on the differences between the nRF51 and the nRF52 series boards yet. I am going to do more research this weekend.
-
@rmtucker Even if I do design a new board, I would at least like to do a protoboard version first like I usually do, so you have a good point. Will the MySensors library work with a 52832 board like this one? I haven't read up on the differences between the nRF51 and the nRF52 series boards yet. I am going to do more research this weekend.
@dbemowsk Very few people use MySensors on nrf5, so there are probably some problems that are yet to be discovered - as with any new technology. With that said, 51822, 51422, 52832 have been confirmed working at some point.
@scalz has had success with the 52840, but it seems there is not full support for all IO ports
@NeverDie has experimented with the 52810 -
@rmtucker Even if I do design a new board, I would at least like to do a protoboard version first like I usually do, so you have a good point. Will the MySensors library work with a 52832 board like this one? I haven't read up on the differences between the nRF51 and the nRF52 series boards yet. I am going to do more research this weekend.
@dbemowsk you can also consider the NRF52 DK it's more expensive (32$ at Arrow) but you have jlink included on it to program and debug the onboard nrf52 but also any external nrf51 and nrf52 chip (and also NFC antenna and interface, and 4 extra nrf52 chips if you like SMD soldering). It also has a few LEDs and buttons to quickly make some tests, as well as nice things like jumpers to let you measure current consumption when you want to optimize a battery powered sensor.
Nrf51 is a cortex M0 with 16K or 32K RAM and 256K flash.
Nrf52 is a cortex M4F with 64K RAM and 512K flash. Way more powerful and with more advanced features. -
@rmtucker Even if I do design a new board, I would at least like to do a protoboard version first like I usually do, so you have a good point. Will the MySensors library work with a 52832 board like this one? I haven't read up on the differences between the nRF51 and the nRF52 series boards yet. I am going to do more research this weekend.
@dbemowsk If you're in the USA (which I seem to recall that you are), I recommend the Fanstel modules, because they have passed FCC: http://www.fanstel.com/bluenor-summaries/ Also, most of them share the same pinout, which makes them easy to upgrade.
-
Here's a breakout board that would get you started with most of the Fanstel's:
https://www.openhardware.io/view/489/BT832X-Power-Amplified-nRF52832-Remote-Control-with-LNA -
If you just want to quickly get a feel for the nRF52, though, I'd recommend getting two nRF52 DK's (one for each end of a radio link). It's probably the least frustrating way to get started, and as @nca78 mentioned, you can use them more generally later as programmers if you take a liking to nRF5's.
-
If you just want to quickly get a feel for the nRF52, though, I'd recommend getting two nRF52 DK's (one for each end of a radio link). It's probably the least frustrating way to get started, and as @nca78 mentioned, you can use them more generally later as programmers if you take a liking to nRF5's.
-
@mfalkvidd Perfect. As I mentioned, I am going to look over the modules this weekend and see if I can find one that is suited for my board.. From there I will look at fabricating a new PCB.
-
@dbemowsk said in Atmega 328p memory:
@neverdie Will the nRF52s work on my nRF24 network?
You mean is it backward compatible? Yes, if you use the mysensors code base. You can thank @d00616 for that. :) Otherwise it wouldn't be.
-
So looking at a dev board like this one to test things, one thing that I do not see is any analog inputs. I am also wondering about an I2C connection. I am also assuming that the black connector is the programming header.
-
So looking at a dev board like this one to test things, one thing that I do not see is any analog inputs. I am also wondering about an I2C connection. I am also assuming that the black connector is the programming header.
@dbemowsk Most of the GPIO pins can be assigned to be whatever you want. For instance, only one pin can serve as RESET (pin 21), but it can be re-assigned to work as an analog pin if you prefer to use it that way. Likewise, pins can be re-assigned to serve as I2C if you prefer that. All this gives you more freedom in the trace layouts. i.e. it's a good thing.
-
@dbemowsk Most of the GPIO pins can be assigned to be whatever you want. For instance, only one pin can serve as RESET (pin 21), but it can be re-assigned to work as an analog pin if you prefer to use it that way. Likewise, pins can be re-assigned to serve as I2C if you prefer that. All this gives you more freedom in the trace layouts. i.e. it's a good thing.
@neverdie So they are not strictly data lines... That is nice. So what you are saying is that if I wire them to the headers on my board, I can just wire the header pins to the closest GPIO lines and then just reference them to what they are in the sketch. Can any of them be SPI bus lines also?
-
@neverdie So they are not strictly data lines... That is nice. So what you are saying is that if I wire them to the headers on my board, I can just wire the header pins to the closest GPIO lines and then just reference them to what they are in the sketch. Can any of them be SPI bus lines also?
-
For instance, I would suggest not using the NFC pins if you can avoid it. They can be redefined, but they aren't 100% equivalent to the other pins.
-
For instance, I would suggest not using the NFC pins if you can avoid it. They can be redefined, but they aren't 100% equivalent to the other pins.