libDaisy icon indicating copy to clipboard operation
libDaisy copied to clipboard

SRAM Bootloader Breaks SW1 and SW2 on Daisy Field

Open byronellis opened this issue 2 years ago • 2 comments

Hi, switching to the SRAM-based boot loader (BOOT_SRAM) appears to break SW_1 and SW_2 on the Daisy Field. Specifically it seems like RisingEdge() is always true. Not sure if this is intentional or if there is a workaround, but the same code will work fine if you load the same code without the custom daisy boot loader.

byronellis avatar Jun 30 '22 16:06 byronellis

@byronellis thanks for the bug report, we'll look into this!

stephenhensley avatar Jul 11 '22 23:07 stephenhensley

No problem! If you need a minimal reproduction I can make one but it's pretty much "switches don't seem to work" so it's almost trivial 🙂

byronellis avatar Jul 13 '22 01:07 byronellis

Oh wow, I've been scratching my head around this for weeks/months!

Had totally missed this issue report and it's exactly what I'm seeing! -> with the bootloader sw1 and sw2 on the Field always present as high.

I'll see if I can test the new bootloader.

dromer avatar Dec 06 '23 09:12 dromer

Ok can confirm that with this new branch of libDaisy and the bootloader the switches work as expected.

Really hope this gets merged/released soon, but at least I know the cause of the issue and that it will get resolved at some point.

dromer avatar Dec 06 '23 09:12 dromer

I suppose this ticket can now be counted as resolved. Or should it need a release tag for libDaisy first?

dromer avatar Dec 22 '23 20:12 dromer

This works now on bootloader v6 and beyond :)

dromer avatar Feb 23 '24 12:02 dromer

@dromer Thanks for confirming!

stephenhensley avatar Feb 23 '24 15:02 stephenhensley