Search Results
8/5/2025, 1:52:48 PM
Calibration.
Now, all the peripherals are connected and tested(except sdcard). Next, I will try to get rig off ESP-IDF and FreeRTOS and try to get it all running on baremetal with embassy. I hope this will enable me to do get high framerate and sound in the background while main task will be taking care of Lua side of things.
>>2935876
>Why not include a minidisc player
That would require dedicated hardware and emulating real console is too much work.
Now, all the peripherals are connected and tested(except sdcard). Next, I will try to get rig off ESP-IDF and FreeRTOS and try to get it all running on baremetal with embassy. I hope this will enable me to do get high framerate and sound in the background while main task will be taking care of Lua side of things.
>>2935876
>Why not include a minidisc player
That would require dedicated hardware and emulating real console is too much work.
8/4/2025, 8:47:42 PM
>>106139536
Basically, I want a build system and command runner that is rather simple, succinct and language agnostic. For example, I really like how clean and short ninja files are, but it lacks many features useful to writing these by hand nor can it function as a command runner.
Currently, I have rules/tasks for the following:
>some tasks to run bunch of scripts like cargo script scripts/whatever.rs "$@" so I can do $ fizzbuzzmake script-whatever input output
>bunch of tasks for building assets, often multi step, eg calling imagemagick or ffmpeg to transcode and then one of the scripts mentioned above to compress. These tasks should not run if the artifact is newer than its source.
>some task that builds all these assets
>some tasks that first does all the build commands and then cd into specific crate's folder and runs cargo run "$@" so I can pass extra arguments if needed
>some tasks that builds everything and then runs some command to launch tests
>some task to run bunch of commands to clean temporaries
I checked out taskfile and from what I have seen, it "suffers" from similar issues as cargo-make that I am currently using. Namely, you have to write sources and destination manually alongside the command, splitting across multiple lines, repeating same thing over and over. I really would like something like ninja's rules where you can specify generic way of processing something and then just list files to extend from.
>>106139554
I am making a handheld console together with a friend. The plan is to make it relatively small and cheap but also but whatever feature we can into it. It will be based on esp32 and support Pico-8 game cartridges. Here is the calibration in action that I just finished recently. I really have no idea why does the physical pixel grid doesn't align with logical ones on the screen. Physical 0x0 is addressable as 1x2.
I have a thread on /diy/ where I post updates every now and then. >>>/diy/2932429
Basically, I want a build system and command runner that is rather simple, succinct and language agnostic. For example, I really like how clean and short ninja files are, but it lacks many features useful to writing these by hand nor can it function as a command runner.
Currently, I have rules/tasks for the following:
>some tasks to run bunch of scripts like cargo script scripts/whatever.rs "$@" so I can do $ fizzbuzzmake script-whatever input output
>bunch of tasks for building assets, often multi step, eg calling imagemagick or ffmpeg to transcode and then one of the scripts mentioned above to compress. These tasks should not run if the artifact is newer than its source.
>some task that builds all these assets
>some tasks that first does all the build commands and then cd into specific crate's folder and runs cargo run "$@" so I can pass extra arguments if needed
>some tasks that builds everything and then runs some command to launch tests
>some task to run bunch of commands to clean temporaries
I checked out taskfile and from what I have seen, it "suffers" from similar issues as cargo-make that I am currently using. Namely, you have to write sources and destination manually alongside the command, splitting across multiple lines, repeating same thing over and over. I really would like something like ninja's rules where you can specify generic way of processing something and then just list files to extend from.
>>106139554
I am making a handheld console together with a friend. The plan is to make it relatively small and cheap but also but whatever feature we can into it. It will be based on esp32 and support Pico-8 game cartridges. Here is the calibration in action that I just finished recently. I really have no idea why does the physical pixel grid doesn't align with logical ones on the screen. Physical 0x0 is addressable as 1x2.
I have a thread on /diy/ where I post updates every now and then. >>>/diy/2932429
Page 1