Sandor Zsuga

I confirmed this now. The 1st bootloader certainly can use my SD cards, I compiled a smaller example program into RAM (LINKER_RAM = 1 in the Makefile), and naming it...

I did some experiments on the 2nd bootloader. As far as I could track, the program dies in an infinite loop within game_init(), there within f_mount(), and there within find_volume()....

"or the fatfs to lower layer adapter" - I am also thinking that the most possible, however the way I attempted to debug it would be necessary to go through...

I tracked the execution path further, finding this: game_init() -> ff.c/f_mount() -> find_volume() -> diskio.c/disk_initialize() -> stm32f4_discovery_sdio_sd.c/SD_Init() -> SD_EnableWideBusOperation() -> SDEnWideBus(ENABLE) -> FindSCR() There it gets stuck in the loop...

Hi Both, Thanks :) I was guessing the same for the error, maybe it simply tries to use one of my more esoteric compilers for some reason. avr-gcc for example...

I attached both the output of CMake and Make called with adding the verbosity parameters. CMake itself doesn't seem to do anything regarding it, still doesn't show how it can...

I am totally clueless what is going on here. I have Emscrpiten stuff added in my .bashrc, removed them, checked that they are all indeed removed by looking through my...

Huh, nevermind. git clean -**d**f. I can finally build and run it! It would still be nice to know why it picks Emscripten if it is available, or if it...

It works! (no CC or CXX environment variable set up at all) Interestingly it doesn't try to use my RISC-V compiler while that's also similarly installed locally like Emscripten. (I...

I changed the order in $PATH, and it indeed picks the proper compiler if Emscripten was behind! But it is odd that it wouldn't pick the RISC-V compiler which is...