I think when you mention dvi+audio and then you have your own PWM, I think there may be a problem with the amounts of buffer memory or arrays used by the code. When I look at PicoDVI, everything is well written and high-speed stuff are tagged with __not_in_flash_func(). But you have added your own PWM stuff, and something like this:
and the bit shifts makes no sense to me. Then you say:
[Edit] Most coders with some experience writing non-trivial programs (say >1000 LOC), when faced with such an error, would have an earlier version of the program to fall back to. Then troubleshoot incrementally from there. Usually it's not hard to troubleshoot such things, and it's well worth your while to practice such troubleshooting skills. We are assuming many things about your code. If we assume wrongly about your code (quality etc), we may well be fixating on the wrong thing.
Code:
if (wav_position < (one11k_u8_LENGTH<<3) - 1) {pwm_set_gpio_level(AUDIO_PIN, one11k_u8_DATA[wav_position>>3]); So it may not even be a problem with the audio data. PicoDVI is high quality code, so more likely it's your code that is the problem. Most of the time we assume the coder knows all the buffer sizes being allocated. How much memory is being allocated/used by DVI, how much memory is being allocated/used by your own (PWM etc) code. Without clear and precise information, it's hard to pinpoint the issue -- we can only make educated guesses. I'm sure many here can solve this problem, if we can see more of the code.I´ll put in all used files, i´ve put in only 3 files, but same capacity overflow:
region `RAM' overflowed by 15240 bytes
[Edit] Most coders with some experience writing non-trivial programs (say >1000 LOC), when faced with such an error, would have an earlier version of the program to fall back to. Then troubleshoot incrementally from there. Usually it's not hard to troubleshoot such things, and it's well worth your while to practice such troubleshooting skills. We are assuming many things about your code. If we assume wrongly about your code (quality etc), we may well be fixating on the wrong thing.
Statistics: Posted by katak255 — Sun May 25, 2025 2:40 am