search

adafruit / Adafruit_nRF52_Bootloader

USB-enabled bootloaders for the nRF52 BLE SoC chips
MIT License
445 stars 401 forks source link

Trying to use on nRF52840 DK (PCA10056) [Bug] #138

Closed tusharvb19 closed 4 years ago

tusharvb19 commented 4 years ago

Not working for me

Set up

To Reproduce Steps to reproduce the behavior:

  1. Connect DK and Flash bootloader using J-Link(Select board as nRF52840 DK, Tools - Burn bootloader while selecting Programmer as J-Link)
  2. Now Flash the example bleuart using Upload using Programmer
  3. No sign of working in nRF Connect mobile app

Additional Also, Can you help to find the UART pins on nRF52840 DK?

JoeBakalor commented 4 years ago

Did you program the SoftDevice too or just the bootloader?

tusharvb19 commented 4 years ago

The Softdevice and Bootloader is included when we burn the bootloader, right? I will confirm if both are installed using nRF connect pc-> Programmer!

I checked:

image

It is having all - bootloader, softdevice and application when I flashed the bootloader using Arduino-Tools-Burn bootloader

tusharvb19 commented 4 years ago

Now when I flashed the code using Sketch--> Upload using Programmer

image

No sign...LED1 slowly blinks continuously! And not showing anything in nRF Connect mobile app!

What are the pins for TX and RX for serial port to check for serial prints!

tusharvb19 commented 4 years ago

Anyone here to help me?

hathach commented 4 years ago

you need to upload using Serial/Uf2 at least once or write magic number to bypass firmware integrity check. For more question, please post on the support forum.

huddy987 commented 4 years ago

@hathach I am seeing the same issue. I tried uploading using UF2 as well, can you confirm that this should work?

  1. make board=pca10056 all
  2. make board=pca10056 sd
  3. make board=pca10056 flash

Then upload S140 to the device using UF2. I am able to see the drive in USB cdc, but when I load an app, it does not jump to app (led stays pulsing for some reason)

Edit: You can ignore this, it appears to be an issue somewhere in the platformio toolchain. I fixed it by redownloading all the platformio packages I needed.