[quote=“glaeken, post:4, topic:259833”]
Subsequent attempts to boot have both PWR and SYS light illuminated, and the heat sink will again get very hot, so something is happening. No lights on the ETH port, even when connected to a network.
I’ve done some digging around to see if it might be the rpi or the host board that might be the issue. Even after imaging the eMMC (so we kind of know the CM4 still works), I still can’t get any output from the screen. I’ve attempted installing RISC OS and RaspberryPi OS (latest).
Same issue here… New reTerminal successfully boots out of the box, goes through an initial setup process that includes: localization, setting up a new password, setting up the network (WiFi), and guides you to upgrade.
Everyone good luck fixing this issue. I had hoped to use these on a product we’re rolling out. I ordered one and it is a complete disappointment. Shifting my initial 200 units to something that works from a company that cares.
Anyone who wants my brand new screen doesn’t work shitTerminal… $50 and its yours, message me.
Are you shipping products using the default distribution from the manufactures? Please don’t do this, this is how botnets are created. And don’t use the RPi standard image either. The reTerminal is about the hardware. You’re expected to re-spin / create your own distribution. Yes it’s a shame that this has happened, mine had the same issue and I just received it. So not been fixed in the last month. But I always planned to be using my own distribution that has been tailored for the customers requirements.
We apologize for any inconvenience caused after updating the reTerminal for the very first time. There was a major problem of the LCD not working after doing an update through the initial configuration window. However, if you have checked the wiki carefully, I have mentioned under Step 9 inside Quick Start with reTerminal that you need to skip this step and update the reTerminal through command line separately. Otherwise, if you directly update from this configuration screen and reboot, all the drivers will not load again properly, causing the LCD to not work.
However, I understand that most people, when they buy the reTerminal, they just power on, and will go through the initial configuration screen just as they would with a Raspberry Pi without checking any manual.
So now we have fixed this bug from the Raspberry Pi OS factory image and you can find the latest images here. Please flash the OS using this wiki, and then you can update the reTerminal as usual.
Also, we will ship our latest reTerminals with this image already pre-installed. In that way, future customers will not face this issue.
We hope you understand this matter and hope to see you all doing great projects with reTerminal!
I welcome you all to join our Discord as well and ask any reTerminal related question in the cm4-related product channel. If you have questions for other Seeed products, you can choose a different channel.
Hallo everyone,
I had the same problem with the screen black out, SSH and the RS232 connection did not work. Then I followed lakshan’s advice, downloaded the special images (32/64 bit version, see Question 2 of FAQ of the reTerminal Introduction web site) and wrote the 64 version to the eMMC. It worked and the screen is back now. Thank you!
Hobe
I was able to get past the blank screen issue by re-imaging the reTerminal with the seeed image as described. However, now I’m unable to use the buttons, led, or buzzer in Python. It seems that these devices don’t exist as files in the linux filesystem. Whenever I try to utilize one of them, I get:
No such file or directory: '/sys/class/leds/usr_led2/brightness'
I checked the folder /sys/class/leds, and there is in fact no usr_led2 (or anything similar) present. Any ideas how to get these devices back?
Thanks for the reply. Yes, I am trying to use the seeed-python-reterminal library.
I was unfamiliar with evtest, but I installed it and this is the output:
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0: Riitek Micro Keyboard Mouse
/dev/input/event1: Riitek Micro Keyboard
/dev/input/event2: seeed-tp
/dev/input/event3: Riitek Micro Keyboard Consumer Control
/dev/input/event4: vc4
/dev/input/event5: ST LIS3LV02DL Accelerometer
/dev/input/event6: vc4
Select the device event number [0-6]:
I did not see the device to test, so I did not proceed.
I also ran i2cdetect -y 1. Here is the output of that:
Came here to say I’ve had the same experience:
Was working fine (didn’t let it do the updates during setup), I had setup SSH keys, connected to WiFi etc.
Decided to do the old “apt update && apt upgrade”, next time I rebooted (which was a while later so I didn’t realized that was the cause at first) the screen stayed blank and the SYS light stayed on.
Using the instructions linked above fixed the issue but I don’t expect to have to reinstall the display drivers every time I do an update. Definitely a disappointing user experience.
Why am I having this problem with the WIO Terminal (3 units no usable screen in the Arduino IDE but usable screen with circuit python). Is there a fix for this? I don’t want to convert my programs from C to CP.
