@neverdie for us - yes. For other folks, I think the advantage is the number of targets it supports and the license. Equivalent Segger costs hundreds of $
BTW, Sandeep added BMP support into his core after I raised the issue
Toyman
@Toyman
Best posts made by Toyman
-
RE: nRF5 action!
-
RE: nRF5 action!
@neverdie said in nRF5 Bluetooth action!:
else go square
if you ask me, go this way given the BT module itself is already beyond the circular footprint
-
RE: nRF5 action!
@alowhum there is a whole "movement" of people who are trying to reprogram them. Key issue is openability (how hard is to open it)
The last easily openable watches are based on nrf51822, but the good thing is that programming pins are easily accesable and even marked SWD/SCLCK.
Search Ali for ID107HR and google for "roger clark smartwatch"
I am yet to find a watch that would be both nrf52 based AND easily openable -
RE: nRF5 action!
https://github.com/micooke/arduino-nRF5-smartwatches
Mark is a fantastic guy
-
RE: nRF5 action!
@alowhum just buy a real Blue Pill (around $2) and convert it into BMP.
Then you''ll get both a programmer and an USB-serial that you can use to get data from NRF52 UART -
RE: nRF5 action!
@nca78 BTW, HolyIoT makes a similar beacon but nrf52 based. Should be much more energy efficient. The price is about $7
-
RE: 💬 NModule
Guys, pls. have in mind that Ebyte short NON pa+lna module uses pa+lna pinout.
Took me some time to figure it out -
RE: my first nrf5 ... NRF51/NRF52 which is better for MySensors ?
@rozpruwacz I would strongly encourage you do start with nrf52832 ebyte mosule coupled with Nevrdie's breakout board. It is a) proven b) cheap c) breadboard friendly
-
RE: Why don't you write mysensors library for ESP8266 similar to the nRF one ?
Got it, thx. Just to clarify: if I want eg 5 x esp8266 nodes, do I need to add them as 5 gateways, or I add one as a a gateway and other 4 connect to it?
Latest posts made by Toyman
-
RE: GUIDE - NRF5 / NRF51 / NRF52 for beginners
@sancho119 said in GUIDE - NRF5 / NRF51 / NRF52 for beginners:
Hello,
Some news !
i buy a Jlink, and success in erase my nrf52832 with nrf prog, using method of berkseo.Next i try to upload a basic sketch (blink) :
#define MY_RADIO_NRF5_ESB
#include <nrf.h>
#include <MySensors.h>void setup() {
Serial.begin(9600);
hwPinMode(LED_BUILTIN,OUTPUT_H0H1);
}void loop() {
digitalWrite(LED_BUILTIN, HIGH); // turn the LED on (HIGH is the voltage level)
delay(1000); // wait for a second
digitalWrite(LED_BUILTIN, LOW); // turn the LED off by making the voltage LOW
delay(1000); // wait for a second
}I have this :
Open On-Chip Debugger 0.10.0-dev-00254-g696fc0a (2016-04-10-10:13)
Licensed under GNU GPL v2
For bug reports, read
http://openocd.org/doc/doxygen/bugs.html
debug_level: 2
0
adapter speed: 10000 kHz
cortex_m reset_config sysresetreq
Info : No device selected, using first device.
Info : J-Link ARM-OB STM32 compiled Aug 22 2012 19:52:04
Info : Hardware version: 7.00
Info : VTarget = 3.300 V
Info : clock speed 10000 kHz
Info : SWD IDCODE 0x2ba01477
Info : nrf52.cpu: hardware has 6 breakpoints, 4 watchpoints
nrf52.cpu: target state: halted
target halted due to debug-request, current mode: Thread
xPSR: 0x01000000 pc: 0x0000051c msp: 0x20010000
** Programming Started **
auto erase enabled
Warn : Unknown device (HWID 0x00000139)
Warn : not enough working area available(requested 32)
Warn : no working area available, falling back to slow memory writes
wrote 12288 bytes from file C:\Users\Sancho\AppData\Local\Temp\arduino_build_76789/NRF5_blink_led8.ino.hex in 4.155332s (2.888 KiB/s)
** Programming Finished **
** Verify Started **
Warn : not enough working area available(requested 52)
verified 10812 bytes in 0.165932s (63.632 KiB/s)
** Verified OK **
** Resetting Target **
shutdown command invokedI think its good, but when i put a led with a resistance on P0.08, nothing
could you help me more ?
LED_BUILTIN corresponds to po17
-
RE: 💬 MySensors NRF5 Platform
I thought I mastered nrf5 platform bit it looks I am not.
I have a PCB where i2c sensor is hardwired to po30 and po31 of nrf52832.
What changes I have to make in MyBoardNRF5.cpp?
Shall I bring lines 28/29 that have "A4" and "A5" in their desciption to 30th and 31st position in the list? -
RE: nRF5 action!
@omemanti said in [nRF5 action!]Maybe that's the €3 solution for unlocking.
BMP is enough to unlock. BluePill costs ca. €2 and it's easily convertable to BMP
-
RE: nRF5 action!
@mr_red said in nRF5 action!:
Is there any way to do this over the programmer?
Not in Arduino. In KEIL you can use RTT (pretty cool stuff, debug via SWD)
But if you just want to decrease a number of programmers, you can use Black Magic Probe, made from BluePill ($2 at Ali). It is 2-in-1 SWD and USB-UART converter on one PCB -
RE: 💬 nRF52832 ESP-LINK Shield for ESP8266 Wemos D1 Mini
Can you pls. upload the design files?
-
RE: my first nrf5 ... NRF51/NRF52 which is better for MySensors ?
@rozpruwacz said in my first nrf5 ... NRF51/NRF52 which is better for MySensors ?:
So smd modules are no good for me
If so, your only choice is nrf52DK. Solid investment given you get jlink programmer with it
-
RE: my first nrf5 ... NRF51/NRF52 which is better for MySensors ?
how do you guys solder nrf52840 modules without reflow oven?
they have many pads at the bottom -
RE: my first nrf5 ... NRF51/NRF52 which is better for MySensors ?
@hugob said in my first nrf5 ... NRF51/NRF52 which is better for MySensors ?:
- The programmer on the Arduino IDE is not working for me ("No J-Link" error, while there is a J-Link interface available), so I export a HEX fle form Arduino IDE and program the board with the nRFConnect tool from Nordic.
if read sandeep's notes on Githun, you'll find you have to replace the driver with Zaddig but then Jlink will stop functioning in Keil.
That's why I use BMP for Arduino-style programming as it has its own drivers and do not ruin jlink installation -
RE: my first nrf5 ... NRF51/NRF52 which is better for MySensors ?
@rozpruwacz I would strongly encourage you do start with nrf52832 ebyte mosule coupled with Nevrdie's breakout board. It is a) proven b) cheap c) breadboard friendly