Out of FLASH memory!

My daisy run out of flash to store my code!
compilation error :
./usr/lib/gcc/arm-none-eabi/9.2.1/…/…/…/arm-none-eabi/bin/ld: region `FLASH’ overflowed by 812 bytes

I’m wondering if I can use QSPIFLASH to store few functions (specially the one that don’t need to be fast)?

I’m used to speed optimisation, but not to space optimisation. Does anyone have any tips?

Yes! libDaisy has grown quite a bit, and with a lot of peripherals in use (USB, SD card, etc.) the memory can disappear pretty quickly.

We are very nearly ready to release our custom bootloader that will allow storing programs on the external flash chip with the following configurations:

  • Execution from AXI SRAM - allowing for binaries up to 512kB with no compromise in code performance. Only difference is that there is less on-board SRAM available within the program, but the 64MB external memory is still fully accessible).
  • Execution directly from external QSPI flash allowing for even larger programs if necessary. We are still tuning this for performance, but there is some performance loss compared to running on the internal memories right now.

The Bootloader can be programmed:

  • via DFU similar to how it is currently done over USB
  • by loading a .bin file onto an SDCard connected to the Daisy board
  • by loading a .bin file onto a USB drive connected to the Daisy’s external USB pins

We may add additional programming methods (including MIDI sysex, and qspk audio) in later versions.


Somewhat separate from the bootloader project we have recently started looking into having specific functions, be located in QSPI and executed either from the QSPI directly, or the ITCMRAM within the Daisy. This will likely see more action once the bootloader is released.

2 Likes

thanks for the good news!

1 Like