Carlos Pereira Atencio

Another related question I have is about the "not main flash" blocks. Are these meant to include the FamilyID and be included in the block count? Some UF2 bootloader implementations,...

> But it would totally make sense to define a FamilyID eg for embedded MakeCode source. Does MakeCode currently include a FamilyID for the not-in-flash blocks? If they start including...

I've found an issue in this PR with the KL27 of the micro:bit V2 + battery pack, where sometimes inserting the USB cable doesn't start the USB connection with the...

The CI was failing because the `kl27z_bl` was running out of `.text` memory, as a build from the main branch only has around 320 bytes left from the 32 KBs...

Thanks @mathias-arm! I've removed the PR https://github.com/ARMmbed/DAPLink/pull/1097 commit, rebased, and force pushed. I'll look into the `vfs-tests` once I find some time this week.

@mathias-arm just to let you know that I'm looking into this again. Currently looking at integrating and expanding the tests from https://github.com/mbrossard/DAPLink/tree/feature/vfs-tests .

## Analysis With macOS 14 and older, hex files were written by the OS into continuous FAT sectors. On macOS 15 the hex file blocks are sent in order, but...

> is it worth fixing this if it makes the experience significantly slower for v1 users in this scenario? Using the example programme in my dev laptop each compilation takes...

The V1 device name contains 3 spaces at the end `MICROBIT `(11 characters in total): https://github.com/ARMmbed/DAPLink/blob/82dc31d09456710ad0610db5b0ee2a73282f6acc/source/board/microbit.c#L78 And V2 does not have the spaces present: https://github.com/ARMmbed/DAPLink/blob/82dc31d09456710ad0610db5b0ee2a73282f6acc/source/board/microbitv2/microbitv2.c#L475 Switching the strings between the...

Thanks Mathias! I wrongly assumed perhaps the volume name was null terminated anyway, but yeah, it's just 11 characters and no need to null terminate it. Still a bit weird...