I haven't looked in much detail, but In STM32F407xG.ld it appears there's about 44k (ram) + 8k (SRAM2, for DMA) + 10k (CCMRAM) assigned, which is less than 64k, whereas the STM32F427 used has a total of 256 kbyte of RAM. But perhaps some of the RAM (e.g. the RAM used for patch storage) is not specified in the .ld file?
Ok, I hadn't understood that. I'll have to look closer.
Yes, that makes a lot of sense, especially since the P6 has a similar character display and knob interface (albeit smaller) concept as the Push 1 in that respect.
Yes that would be nice. Especially since there already is a scope in the Patcher, a lot of the infrastructure must already be in place. And synths like the Korg Minilogue have shown how useful such a feature can be in the actual hardware.
Thanks.
Do you mean using the P6 as a remote UI (via USB for instance), or actually integrating the Axoloti Core into the P6, removing the P6 CPU and connecting the Axoloti to the P6 UI? I haven't thought about that, but it would actually be doable. The Axoloti board fits inside the P6 enclosure, and if the CPU, DAC and voltage regulators were removed from the P6, and the rear panel reworked, it would make a nice little package. The P6 is sold as a kit, so it would probably be better to purchase just the P6 PCB, mount the necessary components for the UI (most of which are on the top of the board so the Axoloti would fit underneath), and connect the P6 CPU socket to the appropriate Axoloti I/O's via wires. Definitely worth thinking about.
No, unfortunately not, which is one of the reasons I've been keen to getting the Axoloti running on it. I really like the user interface concept on the P6, and would like to experiment with synth design in that format. The whole concept of being able to implement a complete polyphonic synth on a microcontroller like the STM32F4 is very exciting, especially looking back and realizing that back in 1995 a synth such as the first Nordlead needed a DSP for that type of a job, and still only mustered 4 voices.