docs is right ! and for uart RX must be connected to TX ( RX is receiver and TX is transceiver like IN and OUT after what more easy to understand why 
can u share logs by another way
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.
ok much easy already
Ramdisk image is corrupt or invalid
OOOOPS
SCRIPT FAILED: continuingā¦
are you sure SD disk in good quality ?
if u know how works with linux - write image by dd
and check writed content by md5sum and compare with original image
PS: i will check on monday maybe was uploaded broken image from my side
I did it, md5sum match the image, if this is correct and not corrupted uploaded image
check mSD card content, the md5sum must be same for both cases
[xps13 ~]# sfdisk --dump /dev/sda
label: dos
label-id: 0x00000000
device: /dev/sda
unit: sectors
sector-size: 512/dev/sda1 : start= 3200, size= 127872, type=e
[xps13 ~]#
[xps13 ~]# dd count=131072 if=/dev/sda | md5sum
131072+0 records in
131072+0 records out
67108864 bytes (67 MB, 64 MiB) copied, 5,78164 s, 11,6 MB/s
3888eef6178b24cd9e1aa33c8c859d3f -
[xps13 ~]# gzip -dc edge-oowow-latest-sd.img.gz | md5sum
3888eef6178b24cd9e1aa33c8c859d3f -
[xps13 ~]#
Can you please start uploading also md5 and sha256 sums in future? Here I donāt see them
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
PS: any way i will check it at Monday
@hyphop thank you for that, I can only wait.
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
on my side last image ( http://dl.khadas.com/firmware/oowow/system/versions/edge/edge-oowow-220726.000-sd.img.gz ) boot without problem
Hit SPACE in 2 seconds to stop autoboot
..
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot.ini
9439 bytes read in 4 ms (2.2 MiB/s)
## Script run a:00500000 l:9411 c:0
..
[i] rescue loading via fatload mmc 1 ...
[w] hwver not defined
[w] maxcpus not defined
** OOWOW load... by fatload mmc 1 FROM // sd+ post: // // **
load env
fatload mmc 1 0x32000000 /rescue/80_user_env.txt
580 bytes read in 4 ms (141.6 KiB/s)
env import -t 0x32000000 244
addrs: UIMAGE_ADDR :: UINITRD_ADDR :: DTB_ADDR
addrs: 0x02080000 :: 0x06000000 :: 0x01f00000
setenv kernel_addr_r 0x02080000; setenv ramdisk_addr_r 0x06000000; setenv fdt_addr_r 0x01f00000;
:::::::::::::::
load dtb
fatload mmc 1 0x01f00000 /rescue/fdt.kresq/rockchip/rk3399-khadas-edge-v.dtb
76195 bytes read in 9 ms (8.1 MiB/s)
fdt addr 0x01f00000
libfdt fdt_path_offset() returned FDT_ERR_BADPATH
** port mode is **
load packed initrd
fatload mmc 1 0x06000000 /rescue/uInitrd
9499712 bytes read in 407 ms (22.3 MiB/s)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
[i] bootargs: rw panic=10 net.ifnames=0 loglevel=4 fbcon=font:TER16x32 video=HDMI-A-1:1920x1080@60e kresq_type=sd config_test=sd booted=sd hwver= no_console_suspend consoleblank=0 dtb=/rescue/fdt.kresq/rockchip/rk3399-khadas-edge-v.dtb osd12
[i] bootcmd: run distro_bootcmd
load packed kernel
bootm 0x02080000 0x06000000 0x01f00000
fatload mmc 1 0x02080000 /rescue/uImage
6547316 bytes read in 283 ms (22.1 MiB/s)
## Booting kernel from Legacy Image at 02080000 ...
Image Name: kernel
Image Type: AArch64 Linux Kernel Image (gzip compressed)
Data Size: 6547252 Bytes = 6.2 MiB
Load Address: 0d080000
Entry Point: 0d080000
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
Starting kernel ...
[ 0.239238] rockchip-usb2phy ff770000.syscon:usb2phy@e450: failed to create phy
[ 0.240484] rockchip-usb2phy ff770000.syscon:usb2phy@e460: failed to create phy
[ 5.155432] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed
Tue Jul 26 00:00:00 UTC 2022
[i] INITRD INIT :: UPTIME: 5.60 27.71 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
link/ether 12:c6:40:1a:8a:b1 brd ff:ff:ff:ff:ff:ff
[ 5.925051] modprobe: failed to find a module named meson-cpufreq
[ 6.356117] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout!
BusyBox v1.30.1 () built-in shell (ash)
OOWOW system ## hyphop ## khadas
build 220726.000 from Tue Jul 26 00:00:00 2022
[i] Device: Edge rockchip:rk3399 ver:0x0001 6 cores 4GB ram 128GB eMMC
[w] root password undefined
[i] just type > system < to start gui menu
root@edge-a8ab1
No auto start of Kresuce need to press tripple Function to start. Password: khadas
yes if cant auto start need press FUNCTION x 3 times - must works for for any case
PS: i think something wrong with your SD card, plz try another one
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?
Boot log from oowow not working Password: khadas
is this correct way to prepare mSD with oowow?
[xps13 Downloads]# gzip -dc edge-oowow-220726.000-sd.img.gz > /dev/sda
[xps13 Downloads]# sfdisk --dump /dev/sda
label: dos
label-id: 0x00000000
device: /dev/sda
unit: sectors
sector-size: 512
/dev/sda1 : start= 3200, size= 127872, type=e
[xps13 Downloads]# gzip -dc edge-oowow-220726.000-sd.img.gz | md5sum
3888eef6178b24cd9e1aa33c8c859d3f -
[xps13 Downloads]# dd count=131072 if=/dev/sda | md5sum
131072+0 records in
131072+0 records out
3888eef6178b24cd9e1aa33c8c859d3f -
67108864 bytes (67 MB, 64 MiB) copied, 0,753453 s, 89,1 MB/s
[xps13 Downloads]#
why does your boot say:
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
please check crc sum again after sd card usage, maybe have some rewriting by somebody ?
if no lucky again ! i will try to find another recommendation
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?
Seems triple Function is needed to boot from mSD. But it still does not boot. You guys have any Edge-V Pro with 4GB RAM to try this yourself.
Does it matter which U-Boot is on eMMC? How do you write this image to mSD and verify it? See my method in Boot log on beginning.
Boot Log from that image
Password: khadas
@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).
oowow command line fan control fan
@hyphop other then that, do you see why it crashed first boot time? And was second boot ok for you?
Second, how to get now ArchLinuxArm scripts to oowow?
Right problem exist !
how-to use custom scripts
- fork GitHub - khadas/krescue-scripts: krescue scripts to new user name
- goto oowow shell
- use custom scripts
SCRIPTS_REPO=USER/krescue-scripts scripts - modify or make new custom scripts
- send pull request for me if u sure your changes tested and works well
NOTE: need make tag release because scripts download by last tag