I’ve had this Edge2 v12 board for about two months, and it has worked fine until now. Yesterday it was working as expected. The last time I used it I created a device tree overlay for a custom i2c peripheral device, but that shouldn’t have killed the SBC, and it worked fine on reboot after adding the DT overlay. Today it doesn’t seem to boot. If it is booting I’m not getting anything from the HDMI port. I’ve tried entering OOWOW by holding FUN and clicking RES, but still nothing from the HDMI port.
When power is connected to the Edge2 via one of the USB-C ports LED2 is solid red. When the device is powered on using the PWR button, or from the power connector being connected for the first time, LED1 is solid white and LED2 breathes white. When I try to go into OOWOW both LEDs will blink white as the buttons are being pressed, but immediately go back to LED1 being solid white and LED2 breathing white.
Thanks for the reply. I guess that is possible, but normally when it boots the fan runs for a couple seconds, and that’s not happening. I tried connecting the TS050 touchscreen, which also didn’t work, but to be honest I can’t remember if I have the mipi-panel overlay added to the overlay config file. I also went into my router to see if the Edge2 was connecting to Wifi (it should connect automatically), and that isn’t happening, so getting in through SSH is out. If it is the HDMI do you know of a way to troubleshoot/fix it? Otherwise, is there another way to get a display or at least console access?
@Electr1 I have the IO board from Khadas, and I tried to get a console through UART, but I can’t connect. Any other suggestions? Otherwise, is it possible to get this replaced under warranty, and what is the procedure and timeline for that?
This is the second Edge2 board that has failed on me… admittedly the first one that failed may have been my fault for hot swapping a mipi screen while the device was plugged into power (it wasn’t on though). I’ve been working on a prototype using the Edge2 for some time now, and these failures are concerning to me as I need a reliable sbc for my product. The interruption of my development process is also a bit annoying. Have these boards had a high failure rate?
Please note, care must be taken when working with sensitive electronics, especially bare open PCBs. They will have the chance of failing when being exposed due to shorting of components etc.
It’s recommended to disconnect all power sources when connecting or disconnecting any peripherals or introducing a hardware change to the device, it will harm the functioning of both the peripherals and the board itself.
I understand what you are saying. I take several precautions to protect the equipment. I’ve been working with sensitive electronics for a long time. I also have an electronics workbench with ESD safeguards.
The first Edge2 I had burned up was possibly because of plugging into the mipi port with the power cable still plugged in. It was a mistake I made because I was having issues with the screen and I got a little impatient… **it happens. Therefore we bought the second Edge2 on our own dime.
This time is different. This is the 2nd Edge2 we’ve bought. I’ve been extra careful not to make any hardware changes while the power is connected, I’m always grounded when working with the PCB (i.e. ESD wristband), etc. It worked fine one day, and the next day it didn’t.
It’s not prudent for me to purchase the workstation because it seems to me I’m not going to be able to get the HDMI working anyway, and that is too much of a hassle to deal with. I also don’t think it’s a good idea to have some janky wiring going to the pogo pads in an attempt to connect through the pogo pads.
Can you tell me if Khadas will replace this under warranty? If so, what is the procedure and timeline for that?
Thank you.
P.S. I don’t think the board is actually booting anyway. When the Edge2 was working properly I seem to remember a sequence of LEDs as it was booting and the fan turning on for a couple seconds prior to the following:
Now it instantly goes to that when I turn the power on.
I put the sd card in the Edge2 (i.e. the IO board) and powered it on. I got the same message I did before on the serial console.
Is there a button combination I’m supposed to press on startup? Does the sd card need to be formatted a certain way before running the dd command, or does the dd command format the disk as well?
I will mark this as solved, but before I do hopefully you will be kind enough to look at the questions below. This episode has made me realize that it might be beneficial for me to have a little understanding of how the OOWOW works.
Since burning the OOWOW fixed the problem, does that mean that the SPI flash was corrupted?
Is u-boot on the SPI flash as well?
Is there anything you know of that would be likely to cause a failure like this, or is it just a random failure more or less?
Without thinking about it too much I cleared the emmc and reinstalled the OS. I wasn’t really losing much in this case. However, if a similar issue appended in the future would it be possible to reburn or restore the OOWOW and retain the state of the OS?
maybe yes maybe not
if you start OOWOW by pressing FUNCTION + RESET doesn’t work - in this case, it looks like spi-flash content was corrupted
Is u-boot on the SPI flash as well?
yes sure
SPI flash has uboot and oowow content
Is there anything you know of that would be likely to cause a failure like this, or is it just a random failure more or less?
maybe OOWOW update or upgrade - but in this case you will be noticed and must press agree
or some other manipulation with SPI flash content
Usually, users didn’t have access to spi flash
Without thinking about it too much I cleared the emmc and reinstalled the OS. I wasn’t really losing much in this case. However, if a similar issue appended in the future would it be possible to reburn or restore the OOWOW and retain the state of the OS?
SPI content and eMMC always separated
u can update or delete of them without losing other one
