Finally get it working. I needed to swap TX and RX on that CH340G (WCH) USB-to-TTL or the GPIO Pinout on Khadas wiki is wrong, or what probably best answer is, is how USB-to-TTL works: USB TX → Board RX, USB RX → Board TX, GND → GND?
Did Not Connect: Potential Security Issue
Firefox detected an issue and did not continue to cryptobin.co. The website is either misconfigured or your computer clock is set to the wrong time.
It’s likely the website’s certificate is expired, which prevents Firefox from connecting securely.
What can you do about it?
cryptobin.co has a security policy called HTTP Strict Transport Security (HSTS), which means that Firefox can only connect to it securely. You can’t add an exception to visit this site.
The issue is most likely with the website, and there is nothing you can do to resolve it. You can notify the website’s administrator about the problem.
I update-ed the links, can you check I you can get them now? weird message. I used yesterday also Firefox and did not have had such message. Now I got it to.
will be next time - but so we distributed image as gzipped image and md5sum already not really needed gzip provide crc check and corrupted image will be detected
I did tried again the Krescue image, and it looks like the same. Can it have something to do that my Edge-V is an Pro with 4GB RAM? Or is my board broken, which is weird as libreelec or ubuntu boots fine from mSD, or Android from eMMC.
Boot log from Krescue. No auto start of Kresuce need to press tripple Function to start. Password: khadas
I tried new mSD card bought today, but still no luck in booting oowow from it. Which Edge-V board do you have? Does it matter which U-Boot is inside SPI or eMMC?
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 9499648 Bytes = 9.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Uncompressing Kernel Image
Loading Ramdisk to f15fc000, end f1f0b400 ... OK
Loading Device Tree to 00000000f15e6000, end 00000000f15fb9a2 ... OK
and on my side i have:
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (uncompressed)
Data Size: 9499648 Bytes = 9.1 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... Bad Data CRC
Ramdisk image is corrupt or invalid
the md5sum is not same. I burn image to mSD, check sums, put it on khadas edge-v, it does not boot. I powered off Khadas board, check again md5sum od mSD and it is not the same. Do you seen in last Boot log something what does write to mSD?
@hyphop seems I can finaly boot oowow. What I did is flashed an emmc image by using usb-c method, then boot mSD image and used emmc-install, more info on what I did and which image I used, can be found in another forum post, and now your last poste image boots fine, I can see Menu on TV and in regard to serial boot log it can be found here , password: khadas.
In that log you will see that first try boot did not work and crashed, but the second worked fine.
Starting kernel ...
[ 0.238357] rockchip-usb2phy ff770000.syscon:usb2phy@e450: failed to create phy
[ 0.239565] rockchip-usb2phy ff770000.syscon:usb2phy@e460: failed to create phy
[ 5.251729] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
Thu Sep 8 00:00:00 UTC 2022
[i] INITRD INIT :: UPTIME: 5.68 28.41 Linux (none) 5.14.0-rc5 #1 SMP PREEMPT Mon Nov 15 12:39:34 CST 2021 aarch64 GNU/Linux
[i] init display
failed to find a module named meson_ee_pwrc
failed to find a module named meson_dw_hdmi
#MANUAL
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
Illegal instruction
[ 6.001417] modprobe: failed to find a module named meson-cpufreq
[ 6.420042] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
[ 9.385318] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[ 9.387223] CPU: 2 PID: 1 Comm: procd Not tainted 5.14.0-rc5 #1
[ 9.388658] Hardware name: Khadas Edge-V (DT)
[ 9.389701] Call trace:
[ 9.390297] dump_backtrace+0x0/0x18c
[ 9.391204] show_stack+0x18/0x64
[ 9.392019] dump_stack_lvl+0x68/0x84
[ 9.392919] dump_stack+0x18/0x34
[ 9.393726] panic+0x140/0x314
[ 9.394475] do_exit+0x1a4/0x8d8
[ 9.395266] do_group_exit+0x50/0x9c
[ 9.396136] get_signal+0x1dc/0x5b4
[ 9.396983] do_notify_resume+0x118/0x3d4
[ 9.397951] work_pending+0xc/0x438
[ 9.398813] SMP: stopping secondary CPUs
[ 9.399774] Kernel Offset: disabled
[ 9.400613] CPU features: 0x10001011,20000842
[ 9.401657] Memory Limit: none
[ 9.402416] Rebooting in 10 seconds..
DDR Version 1.24 20191016
PS: I am having whole time fan working on 100% (its laud).