-
-
Notifications
You must be signed in to change notification settings - Fork 279
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing 'NRF5 Flash Softdevice' entry in tools menu #512
Comments
Try IDE 1.8.x |
Thanks, that does indeed work. The readme should be updated to mention that this requires the legacy arduino IDE. |
What board/nRF are you using? |
Generic nrf51822, it's a cheap one (holyiot) from eBay just for experimentation. By default it didn't seem to have Bluetooth enabled firmware, but using the legacy ide I was able to flash the example counter which does indeed work as expected and I can subscribe to its updates via the nrf connect app on android |
When you pair it with windows, does it say "connected"? Does it create a port? (device manager -> Ports (COM & LPT)) |
i'm not on windows, but ubuntu. I'm connecting to it via ST-link V2, which doesn't create a serial port, it connects as just a regular USB device. |
Once you finish programming the module and deploy your code. Can you connect to it using Bluetooth? |
As i already mentioned, yes, it works. |
I am not very sure that this is how BLE serial works.
"Serial" as you are thinking is a butchered adaptation of the GATT
profiles. With data being exchanged via advertising packets.
This takes some glue on the other end, I've never - to my memory - seen
anyone using it to talk to windows like this.
Actuall Bluetooth serial was a thing in older pre-LE profiles. But you'll
probably want to look at the various chrome examples from adafruit etc for
"Web Bluetooth" if you want an easy path to doing what I think you're
trying to do.
You won't get much from the standard windows Bluetooth API here for serial
port usage.
It's not an issue with the Nordic side of things. But an issue with the PC
OS
…On Tue, 1 Aug 2023, 02:55 M.B, ***@***.***> wrote:
When you pair it with windows, does it say "connected"? Does it create a
port? (device manager -> Ports (COM & LPT))
I can't get my nRF52833 to connect. However, I can access it using the nRF
connect app.
—
Reply to this email directly, view it on GitHub
<#512 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADEBE3CQLGHKJRTDJWFJY3XTBOXPANCNFSM6AAAAAA2ZRZ62E>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Did you fix the original problem for this issue. Did you copy the flashsoftdevice jar into the new folder you need to make according to the instructions in the ReadMe. Doing this will give you the Flash softdevice menu option, but at the moment it doesn't seem to work, as when it tries to download the softdevice zip file, there is a HTTP error 403 So you have to manually download the S130 or S110 softdevice zip file from Nordic and unzip it and put it onto the appropriate location in the %appdata% local arduino15 core etc etc etc location |
if i remember correctly then i did follow all of the logical steps, like moving the manually downloaded file to the required and other folders that seemed logical. But only downgrading the ide helped. |
Hi,
i have this strange issue where in my arduino ide (2.1.1) there's no 'NRF5 Flash Softdevice' menu entry under the tools menu:
I've followed the readme and downloaded the jar, placed it in the path: ~/Arduino/tools/nRF5FlashSoftDevice/tool/
and installed the board from the boardmanager. It seems i can almost successfully upload sketches (uploading the blink sketch succeeds, even though nothing blinks on my board afterwards, but that's probably just an LED mapping issue).
Only the softdevice upload tool menu entry is missing.
Edit: i also downloaded both S110 and S130 manually and placed them in:
~/.arduino15/packages/sandeepmistry/hardware/nRF5/0.7.0/cores/nRF5/SDK/components/softdevice/s1[1/3]0/hex/
which didn't change anything
What could be the issue?
The text was updated successfully, but these errors were encountered: