Oopsy program > 128kb compiles but doesn't run

Hi

We have been working with the seed for a while now on a University project. We have gotten the 4051 Mux;s working to allow 24+ knobs and today got the PCA9685 PWM controller working to allow 24+ Leds. We are using the bootloader-additions branch of oopsy and believe that the bootloader is installed correctly. Programs smaller than 128kb compile and run correctly. Programs larger than 128kb compile correctly but they are not actually being executed, i.e., no audio, no leds etc.

If we try the same thing in the non bootloader setup then we get compile errors whenever the app is larger than 128kb so the bootloader environment is definitely set up.

There are no compilation errors and the lights on the seed seem to go thru the identical sequence in both the working and non working examples.

We have added the “app_type”: “BOOT_SRAM”, line to the JSON file. We can take the same gen~ project, remove a few elements to get the size under 128kb and it all works, add the extras back in and it still looks like it works, compiles, copies etc, but doesn’t execute (or at least does nothing)

Any suggestions ? anything else that needs to be done to support size > 128kb ??

thanks

Paul

Hey Paul!

Are you still using the Daisy Bootloader for this test?

What I would also recommend is flashing a basic patch (something simple like [cycle 440] → [out 1]) using the Bootloader and see if you hear a sound. This will confirm that you’re flashing successfully with the Bootloader.

Hello Takumi

We have done that and can confirm that a simple patch, a basic sine wave connected to the output and flashing a led (<128kb) does load and work correctly while the seed is flashed with the bootloader.

It is only when we push the size over 128kb that we see the issue. It is very confusing as the log from oopsy seems to imply that it compiles correctly and successfully uploads to the board. It just doesn’t actually execute, or at least all the external signs of execution, audio or led activity, are missing.

Paul

Thank you for the confirmation!

Then it sounds like the part of the patch that makes the size exceed 128kb could be causing an issue.
Could you tell me more about what that part of the patch is doing?