Bricked my Board?

[jjkunce]

I got a used striso board (model 2020 #51). All basic functions seemed fine. But then I tried to update the firmware.

Original settings (from INFO_FW and INFO_UF2):

• UF2-ChibiOS Bootloader 2021-03-05_v1.1.2-0-g32b1c18
• Model: Striso / Striso dis v2.0.2 H743
• Board-ID: Striso board v2.0
• Firmware version: striso_control_2021-12-03_v2.1.4-0-ge78a789

I copied striso_control_2025-07-04_v2.2.2-0-gb2e467c.uf2 to the Striso drive. It just turned off instead of rebooting. I unplugged/replugged.

new settings

• Firmware version: striso_control_2025-07-04_v2.2.2-0-gb2e467c
• (INFO_UF2.TXT unchanged)
• CONFIG.HTM just shows the firmware version, doesn’t open an app
• INDEX.HTM just redirects to striso.org

But, it will only turn on in settings board. Nothing happens if I plug it in to power without pressing the square key.

I tried copying the firmware again. Both 2.2.2, and then the original 2.1.4. Same results - won’t turn on stand-alone.

Then I tried bootloader 1.1.3 (strisoboard_v2_bootloader_v1.1.3-0-g771e2c8.uf2). It copied to the board, the board turned off. Now it won’t turn on at all

Any help would be appreciated. Here or privately.

Thanks so much.

– Jeff

[FranklyFlawless]

@pierstitus

[thetechnobear]

I don’t have a Striso , but I did a quick search here, and seems someone may have had something similar, which @pierstitus helped fix:

Striso board Firmware updates

For clarity: There’s a bug in the bootloader that was shipped in the first batch. For those boards it’s important to update the bootloader that can be found in the first post. If that fails the backup bootloader can be used, let me know if you have problems. I’ll also open a troubleshooting topic later. Here’s a new bugfix release that fixes the midi aftertouch which broke in the last release. Aftertouch is now a bit more sensitive too. Here it is: striso_control_2021-03-14_v2.0.3-1-g9328d67.uf…

(important: read the whole topic… to see if it applies to you))

[jjkunce]

Thanks! I’ll try the dfu-util technique that he suggests.

[pierstitus]

Hmm, I’m sorry to hear you have an issue. Thanks @thetechnobear for pointing to the bootloader issue. However since you already had 1.1.2 it should be something else, but the dfu-util method might still work, did you try it already?

[jjkunce]

I tried it using a raspberry pi (because dfu-util instructions for windows look sketchy)

The output looked good up until the end:

  dfu-util: Invalid DFU suffix signature
  dfu-util: A valid DFU suffix will be required in a future dfu-util release!!!
  Opening DFU capable USB device...
  ID 0483:df11
  Run-time device DFU version 011a
  Claiming USB DFU Interface...
  Setting Alternate Setting #0 ...
  Determining device status: state = dfuIDLE, status = 0
  dfuIDLE, continuing
  DFU mode device DFU version 011a
  Device returned transfer size 1024
  DfuSe interface name: "Internal Flash   "
  Downloading to address = 0x08000000, size = 41328
  Download	[=========================] 100%        41328 bytes
  Download done.
  File downloaded successfully
  dfu-util: Error during download get_status
  (light turned off)

I plugged it back into the PC with the square button pressed: no light, no drive.
Any ideas? Thanks.

[pierstitus]

Strange. The error is normal, so the bootloader seems to flash correctly.

There is another failsafe feature in the bootloader for when there are flash errors, which is triggered by pressing both the square and the round buttons while connecting. That should give you the drive back, but with only the INFO_UF2.TXT file.
If that works there’s probably a flash error, which can be in firmware, in the configuration, or in the calibration (or maybe even in the unused flash).
So first try to flash the firmware, if it still doesn’t work flash a config file. Here’s an empty one: CONFIG_empty.UF2.txt (512 Bytes)

If that still doesn’t work the flash error may be in the calibration data, which I can send you if it’s necessary.

If the flash error persists the flash may be broken, which can happen if you write it thousands of times.

I hope that works, please let me know.

[jjkunce]

Sorry for the delay, I was waiting until I could try dfu-util on a real linux machine. I finally did, and still no luck. dfu-util loads the bin bootloader with the same results as when I used the raspberry pi,

I get no lights or drive at all, when plugging in my striso with square button held down, or plugging in with square plus round buttons held down.

The only response I get is when I plug in with UP button held down. That displays the red lights to load the bin bootloader.

Do you have any more suggestions for me? Thank you.