TFT Gizmo stops working after flashing Eye Terminator UF2

[ross49]

Hello,
I have encountered a problem with my TFT Gizmo and I was advised to post my problem here.

Last week I bought a Circuit Playground Bluefruit BLE, along with a eInk display (154 version) and the TFT Gizmo. Everything was working fine until few days ago, I decided to flash the "CPB_Eye_Terminator.UF2" file, which as the filename describes, is compiled to work with bluefruit devices. When the flash finished, a preview of the last session was being shown on the TFT Gizmo instead of the EYE demo, and nothing else. I tried to reset the board with the reset button. Same problem. I then disconnected the device, plugged it back it and flashed Circuit Python again. But to my surprise, the TFT Gizmo screen would stop showing anything. The backlight is still on, but nothing is displayed. Even the TFT Gizmo UF2 demo doesn't work anything, which used to work before.

What's really weird is that it does not display any errors in the terminal. and I can toggle the A3 pinout with no error. I then tried my eInk display again, and it worked. So in my head, I understood that the screen somehow broke while trying to flash the terminator eye UF2. So I bought a replacement screen, thinking it went defective. But upon getting the replacement today, the problem still persist, and I'm not quite sure what went wrong.

Here are the things I've tried
1. Bought screen replacement. Same issue
2. Deleted everything on the USB and use a example TFT Gizmo code bundle
4. Reformatted the filesystem with import storage
3. tried both Circuit python 7 and 8
4. verified the ribbon was placed correctly. It was
5. Made sure the TFT Gizmo LOGO is placed where the USB is

I really don't know what is going on. I would buy another board, but the logic and executes just fine. It's just the TFT Gizmo that refuses to work. So I find it hard to justify the purchase , right after buying a replacement screen

here are some screenshots

The ribbons. The screen is brand new, so I doubt there's any issue there

1.png (624.7 KiB) Viewed 202 times

What it shows. RELP does not show anything either.

2.png (632.01 KiB) Viewed 202 times

the eInk display displaying image #2 not working.

3.png (615.63 KiB) Viewed 202 times

[adafruit_support_carter]

Thanks for posting summary. This was thoroughly investigated on discord before posting here. We'll take a look and respond back here with any updates.

[adafruit2]

ok just to check, you have one CPB and two displays. you had one TFT work with the CPB, you never had the other TFT work
do you have any other CPX type boards or arduino boards?

[ross49]

Both TFT I ordered now no longer work with the CPB I have. But the eInk one does, which makes me believe something happened on a hardware level when I flashed the UF2.

I do not have another board I can use, but I do have a rpi4 board.

[adafruit2]

ok and to check, the bolts are tightened - no looseless at all, there's nothing oily or dirty on the CPB contacts that could be causing interference?

[ross49]

The bolts are just are tight as when I switched to the eInk display, which works. The fact that I can also toggle the screen in RELP, and backlight is being displayed is undeniable proof that it's connected properly.

I don't think interference is causing the issue if I can swap to the eInk display and work as intended.

I really believe something happened on the hardware level when flashing that UF2

[adafruit2]

its extremely unlikely a UF2 caused a hardware failure - also the backlight is separate from the TFT data connection. however we'll try to replace the bluefruit
https://www.adafruit.com/product/4333
email support@adafruit for a new one

[ross49]

My email has been sent. I know it is extremely unlikely that a UF2 would break the board. But in my case, it is exactly what happened. Thank you for your help!

[adafruit2]

of course, if you are so sure - dont load the same UF2 ;)

[adafruit_support_carter]

It's also hard to imagine how it would only affect the TFT. The eink Gizmo still works.

[ross49]

That is exactly what I'm thinking too. Yet the TFT broke the moment I flashed that specific UF2. It is quite a head scratcher. I will not flash that UF2 again, you can be sure of that!

[ross49]

I got my replacement bluefruit today, and I tested both TFT Gizmo with the TFT Gizmo demo. Both of them work on the replacement board. I then switched to the old board. and same issue. So it's inevitable proof that this UF2 did something to the board. I'll provide the uf2 that potentially bricked my board, and hope this can be resolved in the future.

What I had prior to flashing the UF2:
Circuit Python 8, with a UART server code file, and some BMP images.

What happened when I flashed the UF2:
The previous screen of the UART server code was showing. It wasn't a reset, as screen said it was connected already with text from the code.
I pressed reset on the board. Same screen.
I disconnected the board.
Black screen ever since

[adafruit_support_carter]

What is the UART server code? It sounds like you did not copy the UF2 over in bootloader mode?

Not sure what you mean here:

What happened when I flashed the UF2:
The previous screen of the UART server code was showing. It wasn't a reset, as screen said it was connected already with text from the code.

Was the BOOT folder not showing up?

[ross49]

the code is working just fine, and the text does show up in serial and RELP. But the screen stays black (it is turned on) regardless of the code or RELP. I can power on and off the screen from code as well.

[adafruit_support_carter]

Not sure if things are working or not working? Is the replacement working as expected?