Recent Posts

91

General Discussion / Incorporating TinyCircuits on Arduino IDE

« Last post by sarahtimmon on February 23, 2024, 04:06:12 AM »

Hello,
I am looking to implement a step counter feature using TinyZero, and Accelerometer TinyShield. How can I achieve this on Arduino IDE? Would appreciate some pointers here.

92

General Discussion / FTDI chips

« Last post by plonkarchivist on February 22, 2024, 10:25:03 PM »

After being soldered onto the board, does the small FTDI chip on the TinyUSB board require programming to function? I observed that it features a 6-pin programming header. While I've programmed bootloaders into Atmel microcontrollers using USBtinyISP, I have no prior experience with FTDI chips.

93

TinyTV & Tiny Video Player / Max Audio Codec Settings?

« Last post by ryanswiftjoyner on February 22, 2024, 05:56:57 PM »

Hey there! I see that the default converter puts the audio at pcm_u8 standard with a 10000hz sample rate. I'm trying to do something that requires a bit more articulation in the audio: playing sped up audio that the user needs to slow down after recording externally. What is the highest quality/bit rate/sample rate I can get into the video?

Cheers,

Ryan

94

TinyTV & Tiny Video Player / ESP32 with Tiny Circuits

« Last post by dorothycrad on February 22, 2024, 05:04:15 AM »

Hello,
I wonder whether I use ESP32 with Tiny Circuits together or rather communicate via Bluethooth or Wifi. Any  idea?

95

TinyTV & Tiny Video Player / Tinytv Mini colors inverted

« Last post by bowchicawahwow on February 21, 2024, 12:18:01 AM »

I just received my TinyTv Mini and it works most of the times but sometimes all of the videos colors are inverted. It won’t change until I let the battery die and restart it. Any suggestions?

96

General Discussion / AST1041 Pulse Ox sensor R2

« Last post by malindaurith on February 19, 2024, 05:38:44 PM »

Hi all,

I received the AST1041 Pulse Ox sensor (MAX30101). But I can't find schematic of the PCB due to this a revision 2 . As I see all the recourses are for revision 1.
due to I don't have time to return the  components. can you please help me to find the revision 2 schematic.  I will upload the sensor images.

Thank you.
Malinda.

97

Thumby / Re: Doom

« Last post by henryg 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.

98

Thumby / Re: Doom

« Last post by AncientJames on February 11, 2024, 08:51:55 PM »

Oh! I'd convinced myself that wasn't the problem after all. Thanks for that!
The way I packaged it up into a single UF2 was pretty shaky, and I'd love to learn of a better approach. What I did was to package the doom1.whx file into its own UF2 file using uf2conv, and then concatenate that with doom_tiny.uf2. From my understanding of the spec this should be a valid UF2 file, but the RP2040 bootloader refused to accept it. However, using uf2conv to convert the combined file to raw binary and then converting it back produced a file that did work.
I'll update the repo when I'm back on the relevant machine.

99

Thumby / Re: Doom

« Last post by henryg 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);

100

Thumby / Re: Doom

« Last post by AncientJames on February 09, 2024, 05:11:42 PM »

For that last one, I lowered the spi transfer rate and turned off the frame syncing (although I doubt the transfer rate was a factor here). It sounds as though your device would work just with different settings for PARK_LINES and FRAME_PERIOD. Failing that, getting the frame period approximately right and skipping the sync trick doesn't look too bad.

If you're able to build your own version that's probably the way to go, since I don't have the hardware to test on.