technik007_cz
-
Posts
207 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by technik007_cz
-
-
I am suspicious that the SBC was overheating and that it was refusing to stay on 2GHz and rather dropped to a lower frequency of 1.8GHz.
-
Merged content of overlay file into main dtb file; rebooted and whoa... I rockpro64 jumped to 2GHz.
Overlay:
/dts-v1/;
/ {
compatible = "rockchip,rk3399";fragment@0 {
target-path = "/opp-table-0";__overlay__ {
opp06 {
opp-hz = <0x00 0x5a1f4a00>;
opp-microvolt = <0x124f80>;
};
};
};fragment@1 {
target-path = "/opp-table-1";__overlay__ {
opp08 {
opp-hz = <0x00 0x7829b800>;
opp-microvolt = <0x13d620>;
};
};
};
};Commands required to edit the main dts file:
sudo apt install -y device-tree-compiler
mv rk3399-rockpro64.dtb rk3399-rockpro64.dtb.orig -v
dtc -I dtb -O dts rk3399-rockpro64.dtb.orig -o rk3399-rockpro64.dts
nano rk3399-rockpro64.dts
dtc -I dts -O dtb rk3399-rockpro64.dts -o rk3399-rockpro64.dtb
reboot -
I found the same issue on my RockPro64 running on Noble, kernel 6.6.63-current-rockchip64. I tried different kernels and gave armbian-config a chance to recreate the line in armbianEnv.txt related to overlays, but it did not improve. As a result of this problem, my board cannot go over 1800Mhz.
But 2 different boards, Asus Tinkerboard-2S, with the same SoC, one Debian second Ubuntu runs on 2GHz fine.
I will try to edit dts file to get what I want I think.
-
Hi, I just want to remind you this topic is for Odroid C2 which does not have nothing in common with HC4.
Also original question for this one is answered and tested working.
It would be much better to open separate one with reference to this one but like I posted before this boards have in common just only "Odroid" and more likely low level changes needs more knowledge about certain hardware.
-
The firefox crashing is caused by special version firefox-esr using overlaid filesystem in /run/user/1000. After few cycles of turning it of/off it runs into state when it is unable to start. What helps is removing ~.mozilla folder and start again but it is quite annoying.
So I installed version from snap and this one will hopefully works for me.
-
The only one working kernel is the lowest version of vendor-rk35xx. Other ones cause the Firefox web browser to crash.
-
I found a 1-month-old arch/arm64/boot/dts/rockchip/rk3588-nanopc-t6-lts.dts. It is looking promising.
It is also part of dtb-6.11.0-edge-rockchip-rk3588 on armbian apt repo
-
On the LTS version of this board, there is no other chance than to run the vendor-rk35xx kernel if you want to see something on a screen.
I noticed strange behaviour when this SBC was attached to a 2k QHD screen with the latest vendor kernel. Display size was limited to FullHD instead QHD and Firefox were crashing. When I switched from desktop to terminal I saw the top left corner of the QHD terminal cut to the size of FullHD which was quite a problem because I could not see what I was writing.
Today I tried kernel downgrade from 6.1.75 to 6.1.43-vendor-rk35xx and now I can see QHD on QHD and the Firefox stopped crashing. Hopefully, they will patch the kernel soon. I saw some conversations about it recently.
-
I got it working again. Installed "current" kernel but the same issue was showing during an attempt to update initramfs. So I uninstalled initramfs-tools and did apt autoremove to remove package leftovers.
Then I installed armbian-bsp-cli-pine64-current and I got strange response 'version <none>' but then everything started working included broken initramfs update.
aptitude install armbian-bsp-cli-pine64-current
W: Package initramfs-tools had been marked to reinstall, but the file for the current installed version <none> is not available
The following NEW packages will be installed:
armbian-bsp-cli-pine64-current busybox-initramfs{a} dracut-install{a} fping{a} initramfs-tools{a} initramfs-tools-bin{a}
initramfs-tools-core{a} klibc-utils{a} libklibc{a} -
I am experiencing same problem but on pine64.
update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-6.7.12-edge-sunxi64
Invalid architecture, supported are:
alpha Alpha
arc ARC
arm ARM
arm64 AArch64
avr32 AVR32
blackfin Blackfin
ia64 IA64
invalid Invalid ARCH
m68k M68K
microblaze MicroBlaze
mips MIPS
mips64 MIPS 64 Bit
nds32 NDS32
nios2 NIOS II
or1k OpenRISC 1000
powerpc PowerPC
riscv RISC-V
s390 IBM S390
sandbox Sandbox
sh SuperH
sparc SPARC
sparc64 SPARC 64 Bit
x86 Intel x86
x86_64 AMD x86_64
xtensa XtensaError: Invalid architecture
Usage: mkimage [-T type] -l image
-l ==> list image header information
-T ==> parse image file as 'type'
-q ==> quiet
mkimage [-x] -A arch -O os -T type -C comp -a addr -e ep -n name -d data_file[:data_file...] image
-A ==> set architecture to 'arch'
-O ==> set operating system to 'os'
-T ==> set image type to 'type'
-C ==> set compression type 'comp'
-a ==> set load address to 'addr' (hex)
-e ==> set entry point to 'ep' (hex)
-n ==> set image name to 'name'
-R ==> set second image name to 'name'
-d ==> use image data from 'datafile'
-x ==> set XIP (execute in place)
-s ==> create an image with no data
-v ==> verbose
mkimage [-D dtc_options] [-f fit-image.its|-f auto|-f auto-conf|-F] [-b <dtb> [-b <dtb>]] [-E] [-B size] [-i <ramdisk.cpio.gz
>] fit-image
<dtb> file is used with -f auto, it may occur multiple times.
-D => set all options for device tree compiler
-f => input filename for FIT source
-i => input filename for ramdisk file
-E => place data outside of the FIT structure
-B => align size in hex for FIT structure and header
-b => append the device tree binary to the FIT
-t => update the timestamp in the FIT
Signing / verified boot options: [-k keydir] [-K dtb] [ -c <comment>] [-p addr] [-r] [-N engine]
-k => set directory containing private keys
-K => write public keys to this .dtb file
-g => set key name hint
-G => use this signing key (in lieu of -k)
-c => add comment in signature node
-F => re-sign existing FIT image
-p => place external data at a static position
-r => mark keys used as 'required' in dtb
-N => openssl engine to use for signing
-o => algorithm to use for signing
mkimage -V ==> print version information and exit
Use '-T list' to see a list of available image types
Long options are available; read the man page for details
run-parts: /etc/initramfs/post-update.d//99-uboot exited with return code 1
dpkg: error processing package initramfs-tools (--configure):
installed initramfs-tools package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
linux-image-current-sunxi64
initramfs-tools
E: Sub-process /usr/bin/dpkg returned an error code (1 -
or when I copied content of boot partition to /boot folder of same partition:
INFO : End of read dq deskew training
INFO : End of MPR read delay center optimization
INFO : End of write delay center optimization
INFO : End of read delay center optimization
INFO : End of max read latency training
INFO : Training has run successfully!
1D training succeed
Load ddrfw from SD, src: 0x00048200, des: 0xfffd0000, size: 0x0000c000, part: 0
Check phy result
INFO : End of initialization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D read delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : End of 2D write delay Voltage center optimization
INFO : Training has run successfully!channel==0
RxClkDly_Margin_A0==216 ps 11
TxDqDly_Margin_A0==256 ps 13
RxClkDly_Margin_A1==0 ps 0
TxDqDly_Margin_A1==0 ps 0
TrainedVREFDQ_A0==74
TrainedVREFDQ_A1==0
VrefDac_Margin_A0==31
DeviceVref_Margin_A0==40
VrefDac_Margin_A1==0
DeviceVref_Margin_A1==0
channel==1
RxClkDly_Margin_A0==216 ps 11
TxDqDly_Margin_A0==256 ps 13
RxClkDly_Margin_A1==0 ps 0
TxDqDly_Margin_A1==0 ps 0
TrainedVREFDQ_A0==74
TrainedVREFDQ_A1==0
VrefDac_Margin_A0==30
DeviceVref_Margin_A0==40
VrefDac_Margin_A1==0
DeviceVref_Margin_A1==0dwc_ddrphy_apb_wr((0<<20)|(2<<16)|(0<<12)|(0xb0):0004
soc_vref_reg_value 0x 00000017 0000001a 0000001a 00000017 0000001a 00000017 00000019 00000017 00000018 0000001b 00000019 00000017 0000001a 00000019 0000001a 00000015 00000017 00000019 0000001b 00000018 00000017 00000019 00000019 00000018 00000018 00000017 00000017 00000017 00000017 00000018 00000019 00000014 dram_vref_reg_value 0x 00000056
2D training succeed
aml_ddr_fw_vesion: LPDDR4_PHY_V_0_1_18 build time: Aug 28 2019 13:53:31
auto size-- 65535DDR cs0 size: 512MB
DDR cs1 size: 0MB
DMC_DDR_CTRL: 00c0002aDDR size: 512MB
cs0 DataBus test pass
cs0 AddrBus test pass100bdlr_step_size ps== 493
result report
boot times 0Enable ddr reg access
Load FIP HDR from SD, src: 0x00010200, des: 0x01700000, size: 0x00004000, part: 0
Load BL3X from SD, src: 0x0006c200, des: 0x0175c000, size: 0x000ec000, part: 0
bl2z: ptr: 05129330, size: 00001e40
0.0;M3 CHK:0;cm4_sp_mode 0
MVN_1=0x00000000
MVN_2=0x00000000
[Image: g12a_v1.1.3390-6ac5299 2019-09-26 14:09:46 luan.yuan@droid15-sz]
OPS=0x30
ring efuse init
28 0c 30 00 01 1f 25 00 00 17 35 36 32 43 46 50
[1.196461 Inits done]
secure task start!
high task start!
low task start!
run into bl31
NOTICE: BL31: v1.3(release):4fc40b1
NOTICE: BL31: Built : 15:57:33, May 22 2019
NOTICE: BL31: G12A normal boot!
ERROR: Error initializing runtime service opteed_fast
U-Boot 2021.07-24139-gdb6738fed92 (Jun 17 2024 - 21:13:15 +0100) radxa-zeroModel: Radxa Zero
SoC: Amlogic Meson G12A (S905Y2) Revision 28:c (30:2)
DRAM: 512 MiB
MMC: sd@ffe03000: 0, sd@ffe05000: 1, mmc@ffe07000: 2
Loading Environment from nowhere... OK
In: serial
Out: serial
Err: serial
Net: Net Initialization Skipped
No ethernet found.
starting USB...
Bus usb@ff500000: Register 3000140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus usb@ff500000 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 0
-
This is unfortunate thing for 512MB versions of Radxa Zero and latest Armbians. Mine is doing this:
bl2_stage_init 0x81:00000000
BPDDR4_PHY_V_0_1_18 buil21:45
board id: 2
Load FIP HDR farse done
Load ddrfw from SD, src: 0x00060200, des: 0xfffd0000, size: 0x0000c000, part: 0
Loa000, size: 0x00004000, part: 0
Pa verify
ve: 266
Cfg max: 2, cur: 1. Board id: 255. Force loop cfg
LPDDR4 probe
ddr clk to 792MHz
Load ddrfw from SD, src: 0x0003c200, des: 0xfffd0000, size: 0x0000c000, part: 0dmc_version 0000
Ct
INFO : ERROR : Training has failed!
1D traioard id: 255. Force loop cfg
LPDDRully!
Checad delay center optimization
INFOO : End of read delay center optim00048200, ded of 2D writ=1
RxClkDl01a 00000018 0000001a 00000017 00000019 000000000018 0000reg_value 0x 00000059
2D training succeed
aml_ddr_fw_veB
DMC_DDR_Ct pass1081
result raccess
LoaL3X from SD, src: 0x000se):4fc40b1U-Boot 2021.07-24139-gdb6738fed92 (Jun 17 2024 - 21:13:15 +0100) radxa-zero
Model: Radxa Zero
5
Skipped
No140 NbrPorts 3
Starting the controller
USB XHCI 1.10
scanning bus 0 for devices... 1 USB Dscanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot: 2 did not resp: -110Scanning mmc 1:1...
Found U-Boot script /boot.scr
8147 bytes read in 2 ms (3.9 MiB/s)
## Executing script at 08000000
U-boot default fdtfile: /meson-g12a-radxa-zero.dtb
Current variant:
** Reading file would overwrite reserved memory **
Failed to load '/armbianEnv.txt'
"Synchronous Abort" handler, esr 0x96000010
elr: 000000000105f154 lr : 000000000105d34c (reloc)
elr: 000000001dfb3154 lr : 00000000100402 x7 : 0000000000000000
x8 : 0000000000000008 x9 : 0000000000000008
x10: 00000001bf3e2c x17: 0000000000000000
x18: 000000001bf51dd0x21: 000000001bf7a4a0
x22: 0000000000000000 x23: 000000001dfd89a8
x24: 0000000000000000 x25: 0000000000000001
x26: 000000000000000a x27: 0000000000000000
x28: 0000000000001fd3 x29: 000000001bf3e330oot reason: 0xd
bl31 reboot reason: 0x0
system cmd 1.
G12A:BL:0253b8:61aa2d;FEAT:E0F83180:2000;POC:F;RCY:0;EMMC:800;NAND:81;SD?:0;SD:0;:0;x01
bl2_stage_init 0x81
hw id: 0stage_init 0x02no sdio debug bed
L0:00000000
L1:00000703
L2:00008067
L3:04000000
S1:00000000
NFO : End of 2D read delay Voltage center optimizationn
INFO : End 0==216 ps 11
TxDqDly_MClkDly_Margin_A1==0 ps 0
TxDqDly_Margin_A1==Dly_Margin_Agin_A1==0 ps
VrefDac_Margin_A0==30
DeviceVref_Margin_A0=1==0dwc_ddrphy_apb|(2<<16)|(0<<12)|(0xb0):0004
soc_vref_reg_value 0x 00000017 00000019 000000100017 00000000018 00000019 00000019 00000014 dram_vref_r
DMC_DDR_CTdrBus test pass100bdlr_step_size ps== 493
result rep ddr reg ac SD, src: 0size: 0x000ec000, part: 0
ze: 00001e4K:0;cm4_sp_mode 0
MV35 36 32 43 46 50
[1.193808 Inits done]
secure task start!
high task start!
low task start!
run intmal boot!
ERROR: Error initializing runtime service opteed_fast
2A (S905Y2) Revision 28:c (30:2)
DRAM: 00: 2
In: serialonment from nowhere... OK
Out: serial
Err: ller
USB X for device1 USB Dev Storage 1 -
Try this solutin:
-
Thanfully to @Javelin, I can confirm reboots working fine now with kernels 6.6.16-current-meson64 and 6.8.11-edge-meson64 on (custom) Armbian system flashed to microSD.
This is how updated section of dts file looks like:
gpio-regulator-tf_io {
compatible = "regulator-gpio";
regulator-name = "TF_IO";
regulator-min-microvolt = <0x1b7740>;
regulator-max-microvolt = <0x325aa0>;
gpios = <0x39 0x03 0x06>;
gpios-states = <0x00>;
states = <0x325aa0 0x00 0x1b7740 0x01>;
vin-supply = <0x3a>;
phandle = <0x28>;
}; -
In this case, I would try it again but with a USB meter plugged into 1 of 4 Odroid USB ports.
Then when it boots up watch for voltage drops, even if it was running fine with the other firmware or system.
Mine board even powered via J8 pin sometimes was not able to initialize the USB controller which is quite strange behavior and I would more likely to expect it when powered via crappy micro USB con.
-
It happens also with the latest Linux 6.7.4-edge-meson64 kernel. This problem could be related to a power switch which could be optionally connected to the J4 pin?
-
Hi, I am glad we have a working image for Rock 3C. I compiled mine and it also works. I have tested HDMI output, network, wifi, and USB. Also, lxd has no issue with the latest kernel.
Because it is an unofficial image I found a missing feature to get wifi working as a hotspot. There were a lot of disappeared lines in /etc/hostpad.conf and also there was a message from the console reporting the hostapd is masked in other words is not running during testing maximum wifi speed.
-
I had same problem with RTL9210 based NVME enclosure. But I could not find one of them boot.cmd or boot.scr.
So I did it old fashion way like on Raspbian OS and added usb-storage.quirks parameter into /boot/firmware/cmdline.txt and after reboot UAS driver was replaced with basic usb one.
Note: I tried to edit /boot/armbianEnv.txt but it did not work.
-
I bought few Geobooks 1E and all had regardless distro same issue. Random hangups immediately or few minutes after boot finished or after few days of run or hours.
On Armbian distro after trying some other things I enabled kernel messages in sysctl.conf. And then I got something like, luckily immediately when login prompt appeared, :
rtw_8821ce 0000:01:00.0: failed to dequeue 4088 skb Tx queue 5, .... when laptop stopped responding to keyboard immediately afterwards.
After some research I found solution, plugged USB lan adapter, disabled wifi otherwise it would knocked system down a did these next steps to replace wifi driver and hopefully after reboot 4 of these laptops this driver seems to work better without hangups.
nano /etc/modprobe.d/rtw88_8821ce.conf && update-initramfs -k all -u
ADD NEXT LINES INTO OPENED FILE =>
blacklist rtw88_8821ce
options rtw88_core disable_lps_deep=y
options rtw88_pci disable_msi=y disable_aspm=yNEXT COMMANDS:
sudo apt update && sudo apt install bc module-assistant build-essential dkms git -y
cd /usr/src && git clone https://github.com/tomaspinho/rtl8821ce.git
cd rtl8821ce
sudo m-a prepare
sudo ./dkms-install.sh
sudo nano /etc/modprobe.d/rtw88_8821ce.conf
blacklist rtw88_8821cenote: it should work without "options" lines which I found elsewhere as solution to resolve this problem without driver update
-
Real cpu speeds are for dualcore up to 2.7Ghz and for quadcore about 2086Mhz.
-
I just found they are selling dual core version as-well:
https://www.ebay.co.uk/itm/166222468091?hash=item26b3a193fb:g:wf4AAOSwocdkrWqD
-
One more it consume about 0.8A during load so in theory it could work with different power adapter like 1A. And it is able to handle USB spindle hard drives or USB-C NVME SSD compare to some similar laptops but powered over 5V adapters with obviously have to fail due to high amps demand and long power cable resistance.
-
Hi, I just got 2 of these. Everything is fine but you need to order power adapter 12V 2A with 3.5mm x 1.35mm connector.
Unfortunately due to earlier version of BIOS compare to same looking GeoBook 1E but with dualcore Celeron N4020 it cannot boot from microSD card.
Speakers are rubbish but it could be good for some low powered machine projects.
And one advice. Do not change "Quick boot" option in BIOS setting or it will not boot and you will need to unplug battery to reset BIOS.
It work with both Windows 11 or Linux with no extra drivers mods needed. 5Ghz wifi and bluetooth also included.
-
Just tried latest Armbian 23.5 Jammy on 512MB version of Radxa Zero what about if it will start working (it has not worked on 512MB board yet) and unfortunately results are still same it will never pass u-boot booting process ending up restarting.
Other system images produced by Radxa work fine, both debian or ubuntu versions, even they are using older systems.Boards with 1GB and 2GB RAM which I have run fine with Armbian.
initramfs-tools issue "unsupported architecture" unable to write to uboot
in Pinebook Pro
Posted · Edited by technik007_cz
I just run into this problem again but on different SBC. With new apt apgrade a new version of kernel came, initramfs complainend about "Invalid architecture" and failed to finish.
I tried to fix it differently and it also worked. Removed armbian-bsp-cli-rock-4se-current, with this new attempt to do initramfs started and was completed without error. Then I installed armbian-bsp-cli-rock-4se-current again.
Just bear in mind you need to know which armbian-bsp-cli you had previously installed because it could be also -edge , -vendor , etc.