Ok I’ve been able to reproduce this.
Normal build:
Memory region Used Size Region Size %age Used
FLASH: 77740 B 128 KB 59.31%
DTCMRAM: 0 GB 128 KB 0.00%
SRAM: 409564 B 512 KB 78.12%
RAM_D2: 16896 B 288 KB 5.73%
RAM_D3: 0 GB 64 KB 0.00%
BACKUP_SRAM: 12 B 4 KB 0.29%
ITCMRAM: 0 GB 64 KB 0.00%
SDRAM: 0 GB 64 MB 0.00%
QSPIFLASH: 0 GB 8 MB 0.00%
Adding APP_TYPE = BOOT_SRAM:
Memory region Used Size Region Size %age Used
FLASH: 0 GB 128 KB 0.00%
DTCMRAM: 409572 B 128 KB 312.48%
SRAM: 77584 B 480 KB 15.78%
RAM_D2_DMA: 16896 B 32 KB 51.56%
RAM_D2: 0 GB 256 KB 0.00%
RAM_D3: 0 GB 64 KB 0.00%
BACKUP_SRAM: 12 B 4 KB 0.29%
ITCMRAM: 0 GB 64 KB 0.00%
SDRAM: 0 GB 64 MB 0.00%
QSPIFLASH: 0 GB 7936 KB 0.00%
What you can do is try BOOT_QSPI then the layout will look like this:
Memory region Used Size Region Size %age Used
FLASH: 0 GB 128 KB 0.00%
DTCMRAM: 0 GB 128 KB 0.00%
SRAM: 409572 B 512 KB 78.12%
RAM_D2_DMA: 16896 B 32 KB 51.56%
RAM_D2: 0 GB 256 KB 0.00%
RAM_D3: 0 GB 64 KB 0.00%
BACKUP_SRAM: 12 B 4 KB 0.29%
ITCMRAM: 0 GB 64 KB 0.00%
SDRAM: 0 GB 64 MB 0.00%
QSPIFLASH: 77584 B 7936 KB 0.95%
But basically the problem we see is because of DTCMRAM overflow trying to save large buffer - #8 by infrasonicaudio