MiSTer FPGA Forum

Hackula wrote: ↑Fri Feb 17, 2023 2:53 pm

@RealLarry
I am trying to find out the folder structure. Issue I am having is the cores images function fine however upon initial boot, its shows the error I attached.
Now like I said once I open a core, all is fine.
Folder structure and format I have setup is
Root of SD card formatted in fat:
jpg/480x320/#,A,B,C etc
mjpeg/480x320/#,A,B,C etc
It matches what your folder structure is from the files found on GitHub.
I do have wifi on so I can upload any images needed.

Hi Hackula. I sent you a PM about this. The display module is looking for a file called "Menu.jpg" in the M folder on the card. You should have some custom graphics for that which go with my cases. Plz lmk if you have any other questions.

Hackula wrote: ↑Fri Feb 17, 2023 2:53 pm

@RealLarry
I am trying to find out the folder structure. Issue I am having is the cores images function fine however upon initial boot, its shows the error I attached.
Now like I said once I open a core, all is fine.
Folder structure and format I have setup is
Root of SD card formatted in fat:
jpg/480x320/#,A,B,C etc
mjpeg/480x320/#,A,B,C etc
It matches what your folder structure is from the files found on GitHub.
I do have wifi on so I can upload any images needed.

Folder structure is correct, but are there any pictures and videos in /[folder]/# ?
If in doubt have a look at project site here, there and compare with yours...

Update time! I just released the source and the "open binary" 230331

This update is specific for the ILI9341 SPI touch screen. No functional update for all others, but IF you are going to keep your ESP board up to date, read on also!

Changes in detail:

• Three touch screens

• Initial rotation of screen is definable by wifi.txt now

• Divisor for swiping definable by wifi.txt

• Overhaul of tty2tft-system.ini regarding to the touch screen buttons

• A new set of touch screen pictures and templates for GIMP

• You can now use your own initial animation!

Is is essential to re-read the documentation, especially the part SOFTWARE, where the changes and additions for wifi.txt are documented!
Also have a look at for the new touch screen files and templates you might have to copy to your tty2tft's SD card.

If you want to use your own initial animation, just follow the hints in the documentation, save your MPJEG as "000-arcade.mjpeg" to SD overwriting my original one and change the 6th line of wifi.txt from ORG to OWN, which disables additional text output over your video after playing.

Update time! I just released the source and the "open binary" 230421

Only two small changes:

• The parameter OWN in wifi.txt can be extended to OWN0 (<- a "zero") to not display any text overlay on initial video

• OTA update reworked

OTA update seemed to had a problem after some time and declined the flash process. This is now splitted into a two-part flash process.

Hi! This is a call for help.

I’ve just bought these board and tft:

https://www.amazon.es/dp/B07MBZMYCX

https://www.az-delivery.de/es/products/ ... ch-display

I’ve wired the required 3 pins in the board and put the files from sd_card_content into a 32Gb sd card that goes Into the tft.

From the MiSTer console I try to run the first test for ILI9341 but after succesfully saving the file to STDOUT I receive the following message: “Could not connect to interface. Please check USB connection and run script again”.

The screen remains white from the moment I connect it to the MiSTer. I’ve tried with different usb cables with the same result. Any suggestion? Thanks

chipster wrote: ↑Sat Apr 29, 2023 4:21 pm

Hi! This is a call for help.

I’ve just bought these board and tft:

https://www.amazon.es/dp/B07MBZMYCX

https://www.az-delivery.de/es/products/ ... ch-display

I’ve wired the required 3 pins in the board and put the files from sd_card_content into a 32Gb sd card that goes Into the tft.

From the MiSTer console I try to run the first test for ILI9341 but after succesfully saving the file to STDOUT I receive the following message: “Could not connect to interface. Please check USB connection and run script again”.

The screen remains white from the moment I connect it to the MiSTer. I’ve tried with different usb cables with the same result. Any suggestion? Thanks

Well, okay, I had some troubles (=mistakes and errors) with the updater until this morning GMT+2, but thought I'd it resolved after testing with my 9331SPI - but, alas, Venice (from tty2oled) just mailed to me that he has the same problems like you with his 9341 (not SPI).
Gimme a day...Hope is not lost and the ESP/Display isn't brickable. There must be still an issue I am overlooking.

I could resolve the issue regarding the detection of the device. It wasn’t until the fourth cable I tested but at the end the device was finally detected. But yes, the screen remains white. I tested the board and the tft with Arduino IDE and the TFT_eSPI library and both of them work correctly.

I wait then until the issue can be resolved. Thanks!

chipster wrote: ↑Sun Apr 30, 2023 4:27 pm

I could resolve the issue regarding the detection of the device. It wasn’t until the fourth cable I tested but at the end the device was finally detected. But yes, the screen remains white. I tested the board and the tft with Arduino IDE and the TFT_eSPI library and both of them work correctly.

I wait then until the issue can be resolved. Thanks!

Venice reported back that in fact he hadn't an issue but a mistyped variable which draw the wrong firmware
Have you read the documentation, specially We will do a quick first test in the paragraph Software? This a small gfx test and also build upon the TFT_eSPI library.

If this is working, everything should be fine to follow the next steps in the documentation to get the device up and running tty2tft.
But if you (respectively the device) are still failing, report back what steps you have done (and where: MiSTer? PC? Arduino IDE?), maybe screenshots of any error, the files tty2tft-system.ini and tty2tft-user.ini (if existing) etc.pp.

Another problem I'm wondering of is that I can see only one downloaded install from unknown users like you on Saturday and Sunday and this one was an ILI9486 display...

Ok, this is what has happened:
Last saturday I was trying to run the quick first test for ILI9341 directly from the MiSTer console but after succesfully saving the file to STDOUT I received always the following message: “Could not connect to interface. Please check USB connection and run script again”.

Yesterday my device was finally detected by the MiSTer after testing different cables. I continued trying to run the quick first test for ILI9341. The file was written to stdout, the device was checked as available, the test ran but the screen remained white.

I decided to test the esp32 and the screen from th PC with Arduino IDE and TFT_eSPI as they were new and maybe some of them didn't work or the mod was not well done but all worked correctly.

I've tried the same now again with the MiSTer from a ssh-shell with the same result. The screen doesn't reboot.

/root# wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- TEST-ILI9341
--2023-05-01 07:31:14-- https://raw.githubusercontent.com/ojaks ... staller.sh
Resolving raw.githubusercontent.com... 185.199.109.133, 185.199.111.133, 185.199.108.133, ...
Connecting to raw.githubusercontent.com|185.199.109.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7311 (7.1K) [text/plain]
Saving to: 'STDOUT'

• 100%[===================>] 7.14K --.-KB/s in 0.004s

2023-05-01 07:31:15 (1.98 MB/s) - written to stdout [7311/7311]

Checking for device at /dev/ttyUSB0: available

Trying to identify device... 1st Test of your setup

Flash progress completed. Have fun!

chipster wrote: ↑Mon May 01, 2023 7:54 am

[...]
I've tried the same now again with the MiSTer from a ssh-shell with the same result. The screen doesn't reboot.
[...]

Strange...you installation isn't (trying to) download(ing) any of the needed files. Log snippet of your tries:

xxx.yyy.zzz.249 - - [01/May/2023:09:13:52 +0200] "GET /MiSTer_tty2tft-installer/buildver HTTP/1.1" 200 5170 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.249 - - [01/May/2023:09:13:53 +0200] "GET /MiSTer_tty2tft-installer/esptool.py HTTP/1.1" 200 277150 "-" "Wget/1.20.3 (linux-gnueabihf)"

xxx.yyy.zzz.249 - - [01/May/2023:09:14:51 +0200] "GET /MiSTer_tty2tft-installer/buildver HTTP/1.1" 200 5170 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.249 - - [01/May/2023:09:14:52 +0200] "GET /MiSTer_tty2tft-installer/esptool.py HTTP/1.1" 200 277148 "-" "Wget/1.20.3 (linux-gnueabihf)"

xxx.yyy.zzz.249 - - [01/May/2023:09:15:13 +0200] "GET /MiSTer_tty2tft-installer/buildver HTTP/1.1" 200 5170 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.249 - - [01/May/2023:09:15:14 +0200] "GET /MiSTer_tty2tft-installer/esptool.py HTTP/1.1" 200 277150 "-" "Wget/1.20.3 (linux-gnueabihf)"

xxx.yyy.zzz.249 - - [01/May/2023:09:31:16 +0200] "GET /MiSTer_tty2tft-installer/buildver HTTP/1.1" 200 5170 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.249 - - [01/May/2023:09:31:17 +0200] "GET /MiSTer_tty2tft-installer/esptool.py HTTP/1.1" 200 277149 "-" "Wget/1.20.3 (linux-gnueabihf)"

xxx.yyy.zzz.249 - - [01/May/2023:09:43:05 +0200] "GET /MiSTer_tty2tft-installer/buildver HTTP/1.1" 200 5170 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.249 - - [01/May/2023:09:43:06 +0200] "GET /MiSTer_tty2tft-installer/esptool.py HTTP/1.1" 200 277149 "-" "Wget/1.20.3 (linux-gnueabihf)"

And it should look like my test:

xxx.yyy.zzz.185 - - [01/May/2023:10:56:28 +0200] "GET /MiSTer_tty2tft-installer/buildver HTTP/1.1" 200 5170 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.185 - - [01/May/2023:10:56:29 +0200] "GET /MiSTer_tty2tft-installer/esptool.py HTTP/1.1" 200 277149 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.185 - - [01/May/2023:10:56:30 +0200] "GET /MiSTer_tty2tft-installer/boot_app0.bin HTTP/1.1" 200 13423 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.185 - - [01/May/2023:10:56:30 +0200] "GET /MiSTer_tty2tft-installer/bootloader_dio_80m.bin HTTP/1.1" 200 17872 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.185 - - [01/May/2023:10:56:30 +0200] "GET /MiSTer_tty2tft-installer/partitions.bin HTTP/1.1" 200 3378 "-" "Wget/1.20.3 (linux-gnueabihf)"
xxx.yyy.zzz.185 - - [01/May/2023:10:56:30 +0200] "GET /MiSTer_tty2tft-installer/gfx-test_ILI9341.bin HTTP/1.1" 200 286152 "-" "Wget/1.20.3 (linux-gnueabihf)"

also the progress from you try to flash the test is different in two points. It should look like (differences coloured)

# wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- TEST-ILI9341
--2023-05-01 10:56:27-- https://raw.githubusercontent.com/ojaks ... staller.sh
Resolving raw.githubusercontent.com... 185.199.109.133, 185.199.110.133, 185.199.111.133, ...
Connecting to raw.githubusercontent.com|185.199.109.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7311 (7.1K) [text/plain]
Saving to: 'STDOUT'

• 100%[====================================================================================================>] 7.14K --.-KB/s in 0.007s

2023-05-01 10:56:27 (1013 KB/s) - written to stdout [7311/7311]

Stopping tty2tft.sh...
Checking for device at /dev/ttyUSB0: available
Trying to identify device... ESP32 selected/detected.
1st Test of your setup

esptool.py v3.3.2
Serial port /dev/ttyUSB0
Connecting....
Chip is ESP32-D0WDQ6 (revision 1)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 10:52:1c:68:4c:4c
Uploading stub...
Running stub...
Stub running...
Changing baud rate to 921600
Changed.
Configuring flash size...
Auto-detected Flash size: 4MB
Flash will be erased from 0x0000e000 to 0x0000ffff...
Flash will be erased from 0x00001000 to 0x00005fff...
Flash will be erased from 0x00010000 to 0x00055fff...
Flash will be erased from 0x00008000 to 0x00008fff...
Compressed 8192 bytes to 47...
Wrote 8192 bytes (47 compressed) at 0x0000e000 in 0.1 seconds (effective 637.2 kbit/s)...
Hash of data verified.
Warning: some reserved header fields have non-zero values. This image may be from a newer esptool.py?
Compressed 17520 bytes to 12170...
Wrote 17520 bytes (12170 compressed) at 0x00001000 in 0.8 seconds (effective 170.7 kbit/s)...
Hash of data verified.
Compressed 285072 bytes to 158652...
Wrote 285072 bytes (158652 compressed) at 0x00010000 in 7.2 seconds (effective 317.2 kbit/s)...
Hash of data verified.
Compressed 3072 bytes to 146...
Wrote 3072 bytes (146 compressed) at 0x00008000 in 0.1 seconds (effective 375.0 kbit/s)...
Hash of data verified.

Leaving...
Hard resetting via RTS pin...

Flash progress completed. Have fun!

What OS and ssh client are you using? I'm just in the dark about what the problem could be for you...

What OS and ssh client are you using? I'm just in the dark about what the problem could be for you...

I’m using PuTTY in w11.

I have the MiSTer PLUS by Antonio Villena with the oled using i2c2oled.

I really appreciate your help trying to fix my issue.

...I'm still waiting for your tty2tft-system.ini and tty2tft-user.ini
But while waiting for the bus please logon again to you MiSTer, type

ls -alh /dev/ttyU*

and post it's output.

type ls -alh /dev/ttyU* and post it's output.

crw-rw---- 1 root dialout 188, 0 May 1 11:18 /dev/ttyUSB0

I had not touched tty2tft-system.ini and tty2tft-user.ini. I just put the files from sd_card_content into a 32Gb sd card that goes Into the tft as I red in the documentation. Did I skip any step?

But after reading your post I've typed wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- FORCE ILI9341 and wget https://raw.githubusercontent.com/ojaks ... tty2tft.sh -O - | bash. from the shell. Maybe i shouldn't have done it

If I run the test now the result is the same.

chipster wrote: ↑Mon May 01, 2023 11:29 am

type ls -alh /dev/ttyU* and post it's output.

crw-rw---- 1 root dialout 188, 0 May 1 11:18 /dev/ttyUSB0

That is correct and indicates that "a tty device" is found and set to ttyUSB0. Good to know that this isn't the culprit.

I had not touched tty2tft-system.ini and tty2tft-user.ini. I just put the files from sd_card_content into a 32Gb sd card that goes Into the tft as I red in the documentation. Did I skip any step?

Not that I know. Sound also correct, and even if you did a mistake (wrong subfolder etc), the display itself should work and show "something" - even if this would be an error message.

But after reading your post I've typed wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- FORCE ILI9341 and wget https://raw.githubusercontent.com/ojaks ... tty2tft.sh -O - | bash. from the shell. Maybe i shouldn't have done it

If I run the test now the result is the same.

The first wget-thingi is correct to force the flash of a specific firmware. The second wget (after a successful flash!) line is installing all needed things to run tty2tft on the MiSTer (=the so called Daemon). Maybe that you are running now the Daemon w/o a working firmware which interferes the communication to the USB bus. SSH agin to the MiSTer and type

/media/fat/tty2tft/S60tty2tft stop

to stop the Daemon, then try to re-run

wget https://raw.githubusercontent.com/ojaksch/tty2tft/main/installer.sh -O - | bash -s -- FORCE ILI9341

If that still fails, I'l send you a PM with the needed files to flash the firmware locally on MiSTer - but first let us try to find and resolve your issue...

SSH again to the MiSTer and type /media/fat/tty2tft/S60tty2tft stop to stop the Daemon, then try to re-run wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- FORCE ILI9341

Ok, this is what I get:

/root# /media/fat/tty2tft/S60tty2tft stop
Stopping tty2tft.sh...
/root# wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- FORCE ILI9341
--2023-05-01 12:41:29-- https://raw.githubusercontent.com/ojaksch/tty2tft/main/ installer.sh
Resolving raw.githubusercontent.com... 185.199.110.133, 185.199.111.133, 185.199 .108.133, ...
Connecting to raw.githubusercontent.com|185.199.110.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7311 (7.1K) [text/plain]
Saving to: 'STDOUT'

• 100%[===================>] 7.14K --.-KB/s in 0.003s

2023-05-01 12:41:30 (2.03 MB/s) - written to stdout [7311/7311]

Checking for device at /dev/ttyUSB0: available
Trying to identify device... FORCED UPDATE
Version of your tty2tft device is , forced BUILDVER is 230421.
MCUtype is set to TFTESP32

esptool.py v3.3.2
Serial port /dev/ttyUSB0
Connecting.....
Chip is ESP32-D0WD-V3 (revision 3)
Features: WiFi, BT, Dual Core, 240MHz, VRef calibration in efuse, Coding Scheme None
Crystal is 40MHz
MAC: 24:d7:eb:0e:a9:70
Uploading stub...

A fatal error occurred: Failed to write to target RAM (result was 01070000: Operation timed out)

Flash progress completed. Have fun!

And after trying again wget https://raw.githubusercontent.com/ojaks ... staller.sh -O - | bash -s -- FORCE ILI9341 i got this:

--2023-05-01 12:44:21-- https://raw.githubusercontent.com/ojaksch/tty2tft/main/ installer.sh
Resolving raw.githubusercontent.com... 185.199.111.133, 185.199.109.133, 185.199 .108.133, ...
Connecting to raw.githubusercontent.com|185.199.111.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 7311 (7.1K) [text/plain]
Saving to: 'STDOUT'

• 100%[===================>] 7.14K --.-KB/s in 0.003s

2023-05-01 12:44:21 (2.10 MB/s) - written to stdout [7311/7311]

Checking for device at /dev/ttyUSB0: available
Trying to identify device... FORCED UPDATE
Version of your tty2tft device is , forced BUILDVER is 230421.
MCUtype is set to TFTESP32

esptool.py v3.3.2
Serial port /dev/ttyUSB0
Connecting......................................

A fatal error occurred: Failed to connect to ESP32: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esptool/en/ latest/troubleshooting.html

Flash progress completed. Have fun!

Could you please post the type/brand and a picture of your ESP Board.

Looks like his board has problems with highspeed upload of the firmware. Weird I/O error messages...

@chipster Take the attachment and transfer the archive to your MiSTer to /tmp ... Extract the archive there, enter the directory local_flasher and run

bash ./flasher.sh esp32de_230421_ILI9341.bin

This will run a local version of the flash tool, for you with reduced speed as it seems that your ESP board (also maybe your USB cable) has strange issues when tranferring data with high speed.

Could you please post the type/brand and a picture of your ESP Board.

The board is a ARCELI NO R3 D1 R32 ESP32 ESP-32 Development Board CH340G Dual Mode WiFi Bluetooth 4MB Flash DC 5V-12V with Micro USB for Arduino bought through Amazon: https://www.amazon.es/dp/B07MBZMYCX

But I've noticed the board is really a AZ-Delivery D1 R32 ESP32 board. The AZ-Delivery brand label has been covered but it you look at the board carefully it can be seen.

I've tried to run the local version of the flash tool without success. This is what I get:

/media/fat/temp/local_flasher# bash ./flasher.sh esp32de_230421_ILI9341.bin
esptool.py v3.3.2
Serial port /dev/ttyUSB0
Connecting......................................

A fatal error occurred: Failed to connect to ESP32: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esp ... oting.html

chipster wrote: ↑Mon May 01, 2023 1:54 pm

I've tried to run the local version of the flash tool without success. This is what I get:

/media/fat/temp/local_flasher# bash ./flasher.sh esp32de_230421_ILI9341.bin
esptool.py v3.3.2
Serial port /dev/ttyUSB0
Connecting......................................

A fatal error occurred: Failed to connect to ESP32: No serial data received.
For troubleshooting steps visit: https://docs.espressif.com/projects/esp ... oting.html

Meeeh... Does this board having a reset button? I had some cheap Chinese boards that are having persistent problems to enter the Boot Mode (to get access for flashing a firmware). These boards aren't having a rest button and one has to solder a 10k resistor and a push button between GPIO0<->GND to enter the Boot Mode.
But IF you already are having a reset button, push it when you see "Connecting.."

EDIT: Some boards are having a second button called "Boot". If you are having these, push "Boot" instead of "Reset".

Resolved!

I could flash the firmware at last. The problem seemed to be in the μmt32π I had connected to the MiSTer. Once I removed it all worked smoothly. At the end the problem was not related to the board. Thanks anyway @RealLarry for all your help!

Weird
What has the μmt32π to do with the tty2tft device?

What has the μmt32π to do with the tty2tft device?

I’ve asked Antonio Villena. He thinks that maybe the power supply is not enough for everything.

Glad that you ended up getting it going. A difficult birth. Was the power supply delivered from Antonio or bought by yourself?

A difficult birth.

Yes

Was the power supply delivered from Antonio or bought by yourself?

Delivered by Antonio. I think is the stock power supply that comes with the d-10 nano adapted to Europe by him. But this possible cause is just an assumption. Anyway, a PS with more amps is maybe better if you start pluggin many devices at the same time.

chipster wrote: ↑Tue May 02, 2023 7:25 am

Delivered by Antonio. I think is the stock power supply that comes with the d-10 nano adapted to Europe by him. But this possible cause is just an assumption. Anyway, a PS with more amps is maybe better if you start pluggin many devices at the same time.

Uuh, a big mistake from Antonio if he did so without any further notice. A simple DE-10 nano can draw up to 2 Ampere, tty2tft plus ~ 0.3A, mt32pi plus ~ 2.5A (depending on RPi used), plus WiFi/BT, plus other things like keyboard, mouse etc. The latter are drawing way less power but all things together adds up.
As you can see: a fully loaded MiSTer ends up with at least 3A, better 4A, even better go with 5A to have some reserve. And don't save on costs, it's not worth to save at the wrong end and then get angry. Buy or build a MeanWell power supply and you'll be hassle-free happy

RealLarry wrote: ↑Tue May 02, 2023 7:39 am

Uuh, a big mistake from Antonio if he did so without any further notice. A simple DE-10 nano can draw up to 2 Ampere, tty2tft plus ~ 0.3A, mt32pi plus ~ 2.5A (depending on RPi used), plus WiFi/BT, plus other things like keyboard, mouse etc. The latter are drawing way less power but all things together adds up.
As you can see: a fully loaded MiSTer ends up with at least 3A, better 4A, even better go with 5A to have some reserve. And don't save on costs, it's not worth to save at the wrong end and then get angry. Buy or build a MeanWell power supply and you'll be hassle-free happy

This is 1000% true. I always recommend a good PSU like a Triad or MeanWell with 4A or greater for my cases to avoid any issues being underpowered. I actually ran into a situation yesterday where I used a generic 3A PSU I have and the MiSTer wouldn't recognize my 2.5" HDD. At first I thought there might have been a problem with the drive itself. Then I realized that the PSU could be to blame. I switched to a Triad with the same amperage and the HDD functioned normally. Clearly the generic one isn't really putting out 3A.

Hi, it's been a while since I dont connected my screens to the mister and when today I'm ready to make the updates, the image turns upside down, as if vertically, if I set rotate to "yes" it's solved but it's completely upside down, which I can solve Physically rotating the screen but... what has changed so that when updating it doesn't show the images correctly? I have to say that I haven't changed anything on the sd, the same is there is the error but I only did an update, Larry let's see what you think about this

salamantecas wrote: ↑Mon Jun 19, 2023 8:14 pm

what has changed so that when updating it doesn't show the images correctly? I have to say that I haven't changed anything on the sd, the same is there is the error but I only did an update

You have missed the last updates and changes to their configursation(s)