@cwalther I'm not sure if hid requires different descriptors or something that might not be easily supported? You would probably find it easier to use my nimble support branch and then use aioble?

I need to read up on this more thoroughly, but https://www.bluetooth.com/specifications/specs/human-interface-device-profile-1-1-1/ seems to suggest that HID requires L2CAP, of which I see no mention in ubluepy (in contrast to the bluetooth module). But now I’m confused whether that specification is about BLE at all, or Bluetooth Classic.

At any rate, if your branch is complete enough for that, I’ll give it a try!

@andrewleech This sounds like your branch allows for using aioble already?
That's exciting. I saw that Circuitpython pulled your branch in.
All I want is to have a similar experience like on the other MP boards that support Bluetooth.
As I'm learning all this freshly I'm not interested in a lot of different APIs, of course.

How much work is to be done in your branch yet? Can someone not acquainted with Bluetooth yet help?

I rebased my branch last night, it was a fair bit harder than I expected there's been a reasonable amount of change to the nrf port in the last couple of years.

I've done just a basic test of the aioble temp_sensor example and that worked on my 52840 dongle, not sure if I've got any of the older / smaller chips around still to test on.

I'll need to re-run the multitests at some stage...

I have to confess I'm a Github layman still, unfortunately.
Can someone (of you?) combine the timer/RTC PRs and your last branch (of @andrewleech).
So I can clone this and compile?
I might try to run the multitests perhaps (if they are not too complicated).

Update: I see now the compilation was o.k.. because I could flash my firmware onto a second board:

MicroPython v1.23.0-preview.56.gf7f53f2b9.dirty on 2024-01-23; Adafruit ItsyBitsy nRF52840 Express with NRF52840
Type "help()" for more information.

but on that board was this bootloader:

UF2 Bootloader 0.7.0 lib/nrfx (v2.0.0) lib/tinyusb (0.12.0-145-g9775e7691) lib/uf2 (remotes/origin/configupdate-9-gadbb8c7)
Model: Adafruit ItsyBitsy nRF52840 Express
Board-ID: nRF52840-ItsyBitsy-revA
Date: Jul 13 2022
SoftDevice: S140 6.1.1

So this is at least partial success. I shall incorporate you pull requests @cwalther :-)

And now only this question remains: How do I get the right bootloader on my first board?
Thank you all for your help, btw.

Raul

When I wrecked the bootloader one on a Seeed device, I could restore it with my jlink adapter. You "just" need the hex file with the S140 6.1.1 soft device. Maybe you can copy it from the working board. Just get the address range up to 0x26000.

Thank you robert.
I just now found:
adafruit-nrfutil --verbose dfu serial --package itsybitsy_nrf52840_express_bootloader-0.8.2_s140_6.1.1.zip -p /dev/ttyACM0 -b 115200 --singlebank --touch 1200 and the bootloader got updated.
I could flash my firmware afterwards.

Good to hear that you got it sorted out. FWIW, on my board I have the same 0.7.0 as on your second one, and I had installed that using update-itsybitsy_nrf52840_express_bootloader-0.7.0_nosd.uf2. (I’m not sure why I hadn’t downloaded 0.8.x, maybe I just followed the link from the CircuitPython download page.)

It seems the serial update with adafruit-nrfutil is more universal in that you may flash a bootloader that is even for another board, so I needed that.

Just noticed there is no machine.freq().