 This is a blinking TFT. This is a round 2.1 inch TFT. And I just have it turning on all the pixels white and off. And the reason I'm doing that is I'm actually trying to debug this, which is trying to get the large four inch screen working with the ICN 6211. And it's not working. And I don't know what's up. And I think it has to do with the screen initialization, which happens over SPI. But the problem is I've got Raspberry Pi, but I don't know what's up with this screen. And I don't know what's up. And I think it has to do with the screen initialization, which happens over SPI. But the problem is I've got Raspberry Pi, kernel, device overlay, ICN configuration, SPI configuration, ATT, there's too many variables. So what I do is I'm actually testing this up first on a known working platform because I'm always like start with a known working thing, change one little tweak to figure out what's going on and then adjust and adapt until you figure out exactly what your root cause is. And I actually don't have the ESP generating any TFT signal. What I'm just doing is the SPI configuration. And if you look over here on the data sheet, sorry, all pixels on, there you go. There is this mode called all pixels on, which will turn on all the pixels for you. And you don't have to have TFT signal, it just does it directly from the SPI commands. And so over here, what I've got is a little bit of code that sends the init sequence, init sequence, but then it appends to the init sequence, the command to turn all the pixels on and off. So now that I know that that init sequence is good, I'm going to move that code over to the ATTIME over here, and that'll let me know whether I've got the SPI init code and wiring working and then I can work backwards, fix the ICN, fix the device tree overlay, and basically get it all working with a Raspberry Pi. Lady, what is this? This is the biggest flinking ever. No, this is a low world. This is a four inch round TFT display, and I'm trying to get it working through the ICN 6211 with a Raspberry Pi 5 through the DSI converter, DSI converted to the ICN, to TTL, to this TFT. And there's three things I've got to get working. I've got the device tree working on the Raspberry Pi, I've got to get the ICN config burned into this over iSquared C, and I've got to get the SPI configuration on this TFT. And what I'm testing now is the SPI configuration. So what I've done here is, you know, I write the SPI init code, I'm using it to ATTIME, and then I have a loop down here where I'm just sending the MIPI SPI commands 22 and 23. And what those do is turn all the pixels on and all the pixels off. So I've isolated just making sure the SPI init working. Next, I'm going to do the ICN config. All right, Lady, what's this? There's some beautiful color bars. This is the color bar demo register setting for the ICN 6211, which is the chip that I'm using to convert DSI from the Raspberry Pi 5 to this RGB TTL display, this four inch round 720 by 720. I just got the SPI init code working. Turns out you have to set the bits in the order that they come in. So once that got working and had all the LEDs turn on and off, the next step is to verify that this config works. And so you have to set the resolution and the v-sync, h-sync, you know, whatever, porches, PLLs. And then there's a bit you can set called the BIST mode where you can set different tests. So this is the, oh wait, searching color bar, chessboard, outline, and color switch. And these allow you to test that the TTL connection works. So I'm still not using data from the Raspberry Pi yet. This is just running directly from the ICN 6211. I am programming it using Blinka from the Raspberry Pi using I2C so I can trial the different settings. So far, so good. So SPI works, I2C works, the last piece is to get the device to be overlay going. Really, Data, what's this? This is the Raspbian Bookworm desktop working on this large round 720 by 720 display. I got the SPI networking, I got the ICN 6211, I2C working, and I've got the device tree overlay working. All three things together mean that we now have a working display and I've got a little mouse plugged in. And what's cool is, you know, this is a full Raspbian build, so it's got like, you know, all Linux support. So you sent me a file you wanted me to play on here. I just regularly just send you Stargate. You just send me, you basically send me a Stargate every morning. Yeah, Stargate. It's kind of weird what's over that. So just because the screen is small. What I can do is I'll loop it and I'll make it full size. And wait a second and the other thing will disappear. And now we've got your very own video Stargate. Something you've always wanted. Yeah, look at this. Yay. That's cool. Yeah. It's so far so good. So just have to repeat this for every display. But so far this cool round display is working very nicely. Yeah. On Linux Raspberry Pi. There you go. Going into space. So everyone's locked. Do they make a noise? What? They do. I don't know. They do. Okay. Activated. Let's go. Yeah. Into space. Cool. All right, Lady. What's this? A 3.5 inch 480 by 320 capacitive touch screen. So we just wrapped up the revision for our 3.5 inch 480 by 320 version of the resistive touch feather wing and the breakout. And I realized that I actually had like a bunch of these kind of nice capacitive touch displays. So this is one part of the test where I load a image off of an SD card. Let me reset it. You can see it's a little slow because this is running off of a mega. And that tests the SPI interface mode. And then I can flip this switch over here. Let's see, 8. And then it will test it in 8-bit mode. And that's also testing the capacitive touch interface. This is actually a multi-touch, although this demo only shows a single touch. It actually can recognize five fingers. So this is built on a mega. And you can see like there's a lot of GPIO used here. That's why I need a mega. So that's a big because it's using both the SPI and I2T and 8-bit interface. But so far so good. So this is ready to rock. I'm going to finish the adjustments for the tester. And I'm going to order this and I'll be in the Adafruit shop soon. Really? What's all this? I am updating a whole bunch of testers. Not only did I do hardware revisions for boards like the Clue, which I'm still working on, the Feather NR52-840 and the Itzy Bitsy. But, well, I'm supposed to actually also be Picoifying the testers. But more importantly for me right now, I am updating these testers to install the latest TDUF2 bootloader onto these boards because the bootloader needs a couple of adaptations to be able to load the latest version of Circuit Python because the binary got larger. And so it's not trivial for people to update the bootloader, although you can do it. I have to run it in Arduino. So instead, what I've done is I have re-burned the test binaries and I'm updating this SD card. So now when I program it, it still does all the same programming and test, but the final version of the code that gets loaded onto the Feather is going to have the most latest bootloader. So let's see it's programming final and past. So we're going to reprogram all these boards and get them back into the Adafruit shop updated. What's going on this week? Back in the vault.