Messages

1

Thumby / Re: Doom

« on: February 12, 2024, 03:48:13 PM »

I see what you mean by shaky. I was able to throw something together using python (that could still use more work to be 'public release" quality) that calls the python version of uf2convert from https://github.com/microsoft/uf2/tree/master/utils . The main drawback is that you have to call it from the folder where the script resides and have uf2conv.py and uf2families.json in the same folder.

What it does is take the .bin file from the compiled output, pad it with zeros to the specific length needed, and then concat the whx file. After this I run it through uf2conv to create the final flashable file.

the script can be run like:

~/rp2040-doom/uf2conv$ ./single.py ../thumby-build/src/doom_tiny.bin ../doom1.whx doom.uf2

since the actual work of the script is fairly simple (and there is a c version of uf2conv), I'm sure it can be ported to be included in the workflow of the make files or however you want to handle it.

2

Thumby / Re: Doom

« on: February 10, 2024, 04:05:44 AM »

It actually was the spi rate!

here is the diff file of the only change I made and it started running. I messed around with some FRAME_PERIOD settings to find the best, one, but that will wait until after sleep. Prior to this change, no matter what I set FRAME_PERIOD or PARK_LINES to, it would not work. So I can now compile and mess with stuff on my own to get everything working as smoothly as possible for my devices.

I guess the only question I have left is if there there is an easy to way to build it into a single file with the whx, like the release on github?

Thank you sooo much for helping troubleshoot this even though you weren't able to replicate it.

--- ../src/pico/i_video.c.orig   2024-02-10 01:57:59.954548400 -0600
+++ ../src/pico/i_video.c   2024-02-10 02:43:46.964548400 -0600
@@ -438,7 +438,7 @@
 
     gpio_set_function(PICO_DEFAULT_SPI_SCK_PIN, GPIO_FUNC_SPI);
     gpio_set_function(PICO_DEFAULT_SPI_TX_PIN, GPIO_FUNC_SPI);
-    spi_init(spi0, 62500000);
+    spi_init(spi0, 62000000);
     spi_set_format(spi0, 8, SPI_CPOL_0, SPI_CPHA_0, SPI_MSB_FIRST);
 
     gpio_put(J_OLED_CS, 1);

3

Thumby / Re: Doom

« on: February 04, 2024, 03:02:01 PM »

That worked! (The most recent doom_tiny.uf2). The sync needs tweaking, but I was able to play the game! What ended up being the problem and can I pull the updated code somewhere (didn't see it on GitHub)? Thank you so much for your effort troubleshooting this!

4

Thumby / Re: Doom

« on: February 03, 2024, 08:20:47 PM »

I got the splash image!!! The screen just went black after, but it at least got that far.

5

Thumby / Re: Doom

« on: January 23, 2024, 04:32:11 PM »

After messing with it more, I got greytest to work (I didn't have the folder it was in named 'greytest'). This is making me hope I did something equally stupid getting Doom running. With greytest, I got noticable desync lines at 5500, but was still able to see the image. I still need to figure out the best frequency, but around 6100 seems to be it for me. But this makes me wonder why I am getting no image at all for doom. Is there a place I should start poking to see if I can just get a splash screen or something after flashing uf2 image?

Again, I'm really hoping I am simply missing something, but I am just booting into  BOOTSEL and copying the uf2 file to the drive that pops up. When it is done copying, I unplug and restart the thumby and get no image.

Thank you again!

6

Thumby / Re: Doom

« on: January 19, 2024, 01:28:18 AM »

First, thanks for helping me out.

Ok, well I am having trouble getting that running as well, so that might be part of it. When running greytest on the thumby, it just looks like it restarts and reloads the main menu. Same thing happens when using the sample code in the readme for ugrey .

Trying it in the emulator on https://code.thumby.us/, doesn't seem to work either. After figuring out i needed to mark /lib/ugrey.mpy as emulatable, it seems to run without error (including not exiting), but nothing appears on the emulated screen. Also, adding print statements doesn't seem to work, even the simple program below doesn't print anything to the console and the program doesn't exit. Even if I put invalid code below 'import ugrey' it doesn't seem to be evaluated and give an error

import sys
import ugrey
print ('hello world')
sys.exit()

The version info I can find is MicroPython v1.19.1 on 2022-06-18

I did try https://github.com/TinyCircuits/TinyCircuits-Thumby-Games/tree/master/Fireplace and could calibrate the greyscale in that program (but I know it is using a different driver).

7

Thumby / Re: Doom

« on: January 17, 2024, 07:16:08 PM »

I just got a thumby to put doom on, and am having trouble. I tried using the most recent one file release, and when turning it on, I get nothing on the display. I tried the older release and got the same thing, both with and without the whx file (tested without just in case I messed something up with loading that file). I then saw the note about setting FRAME_PERIOD, and so set that to 6400 (and PARK_LINES to 2), compiled it, and tried loading it onto my thumby, again with no change on the screen when turning it on. I have 2 thumbys and I am getting the same result on both. I can go into bootsel and load the factory firmware and get them working again with that.

Unfortunately I don't really know where to start with troubleshooting this, so was hoping you might have some ideas, or at least get something to display on the screen. Thank you!