nRF5 action!
-
@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.
-
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 ?
-
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 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.
@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.
-
@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.
@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.
-
@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.
-
@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.
@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.
-
@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.
@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 :o
[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 -
@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.
-
@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 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.
-
@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!:
@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! -
@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!
