firmware update question

40acc8fb411523eb

Just tried using din with no luck. The query came back successful, but would not upload the firmware.

40acc8fb411523eb

Are those resistors located under the control PCB?

40acc8fb411523eb

Located the resistors and the proper values have been installed.

40acc8fb411523eb

Can’t seem to get connection via usb. I can get connection with midi din, but when it starts the process it states, ‘MIOS32 Bootloader Mode cannot be entered - try again?’. Not sure what to try now.

40acc8fb411523eb

The green led ‘in front’ lights up. When I close MIOS studio and reopen it with LoopA listed, and try and upload the hex file the three leds to the right of the green led, light up white. Not sure if that helps. Thanks for any help.

40acc8fb411523eb

Ok, I was able to complete the update to 2.09. I would suggest to PC users to try and remove the display/keys pcb and only use the bottom control pcb when attempting to update firmware. I had to open and close the MIOS Studio program 5 times before it will see it. And even after updating it, it will not successfully query LoopA with the top PCB installed. Not sure what the issue is with mine, or if anyone else has had a problem. Hope it helps someone.

17703227d9536da1

Glad you could get it working! It could be a power supply issue with your PC’s USB? Removing some of the boards would turn off the OLED and LEDs. A “noisy” USB PSU could also affect the transfer.

Anyway, enjoy using LoopA!

e405ee4b2cb7c716

Hi again - I’ve had similar results. Updating using a pc (Win10), I can successfully query the LoopA but when I try to upload the hex it says MIOS32 Bootloader mode cannot be entered - try again? Then it won’t query until I power cycle.
I will try on a mac next - would like to avoid taking it apart if possible.

0fc5608d995b44ff

@Sanjuro77 using a Mac should work better - sometimes there are Windows USB MIDI driver problems that vary between Windows OS releases.

Here’s a trick that will often help under Windows:
After connecting LoopA and starting MIOS studio, type “help” a few times in the command window to get some USB text output back from LoopA into the console - for whatever reason, this seems to “stabilize” the USB transfers between MCU and PC, then try the firmware upload. After the firmware upload, you’ll need to power-cycle LoopA.

If everything else fails, you can always update LoopA with a common ST-Link V2 adapter.

Best regards,
Peter

e405ee4b2cb7c716

Hi - thanks for the help. I tried it on my mac and it worked first time so all good now. Like you say, must be a pc related issue. Now time to start some music!

e6a3f429652d75c7

For anyone else struggling with this on Windows, I found that completely disabling all other MIDI devices/ports/etc was needed before MIOS studio would communicate with LoopA. Firmware upgrade appeared to complete as expected (on restart, v2.09 is now displayed).
The numbers puzzled me though:

Reading project.hex 
Trying to contact the core...
project.hex contains 270656 bytes (1058 blocks).
Range 0x08000000-0x08003fff (16384 bytes) - BL excluded
Range 0x08004000-0x080041ff (512 bytes) - STM32 Flash
Range 0x08010000-0x0804dfff (235952 bytes) - STM32 Flash
Upload of 254464 bytes completed after 5.03s (49.36 kb/s)
1 ignorable errors during upload solved (no issue!)

Where does 254464 come from?
Never mind, as long as it works 🙂

0fc5608d995b44ff

autopoiesis yes, the Windows MIDI drivers can be a bit tricky, it’s a good idea to unplug the other devices before flashing.

Indeed the calculation looks a bit strange, i believe the total transfer size is the full file size (270656 bytes) minus the bootloader (16384 bytes) plus some flash padding (+x bytes).

Best regards and enjoy v2.09!
Peter