frauhottelmann
-
Posts
31 -
Joined
-
Last visited
Content Type
Forums
Store
Crowdfunding
Applications
Events
Raffles
Community Map
Posts posted by frauhottelmann
-
-
vor einer Stunde schrieb denni_isl:
How can one clock roc-rk3399-pc to 2016000 Armbian 21.02.1 kern 5.10.12 Bullseye - already done armbian-config, Hardware, rk3399-opp-2ghz,
After applying the overlay you also have to go to armbian-config -> system -> governor and frequency (or whatever it's called). Then select the lowest and highest frequency and the governor and reboot.
-
Am 8.2.2021 um 10:29 schrieb frauhottelmann:
I have also tried it with my big 5V power supply. Same problem.
U-Boot looks good:
U-Boot TPL 2020.10-armbian (Feb 05 2021 - 15:50:41) Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.10-armbian (Feb 05 2021 - 15:50:41 +0000) Loading Environment from SPIFlash... *** Warning - bad CRC, using default environment Trying to boot from MMC1 NOTICE: BL31: v2.2(release):a04808c-dirty NOTICE: BL31: Built : 15:50:35, Feb 5 2021 U-Boot 2020.10-armbian (Feb 05 2021 - 15:50:41 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: Firefly ROC-RK3399-PC Mezzanine Board DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPIFlash... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Firefly ROC-RK3399-PC Mezzanine Board Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 230 bytes read in 5 ms (44.9 KiB/s) 15339012 bytes read in 652 ms (22.4 MiB/s) 28582400 bytes read in 1213 ms (22.5 MiB/s) 77058 bytes read in 12 ms (6.1 MiB/s) 267 bytes read in 8 ms (32.2 KiB/s) Applying kernel provided DT overlay rockchip-pcie-gen2.dtbo 2698 bytes read in 8 ms (329.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Moving Image from 0x2080000 to 0x2200000, end=3de0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15338948 Bytes = 14.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f1078000, end f1f18dc4 ... OK Loading Device Tree to 00000000f0ffc000, end 00000000f1077fff ... OK Starting kernel ...
Armbianmonitor: http://ix.io/2OIx
@piter75
any ideas why it wouldn't work? You also have one right? -
vor 5 Minuten schrieb Panzerknacker:
U-Boot v2021.01 + SPI-Patch
Linux roc-pc 5.11.0-rc6-next-20210205 #166 SMP PREEMPT Fri Feb 5 12:05:45 CET 2021 aarch64 GNU/Linux
But did also work with December kernels.
pci was broken on linux-next/arm64 from 8. Jan. until end of Jan or beginning of Feb.
Then that might be the problem. I am building 20.11 right now. Let's see if that helps. Otherwise I'll try master+dev kernel
-
Which kernel and u-boot are you on?
-
I have also tried it with my big 5V power supply. Same problem.
U-Boot looks good:
SpoilerU-Boot TPL 2020.10-armbian (Feb 05 2021 - 15:50:41) Trying to boot from BOOTROM Returning to boot ROM... U-Boot SPL 2020.10-armbian (Feb 05 2021 - 15:50:41 +0000) Loading Environment from SPIFlash... *** Warning - bad CRC, using default environment Trying to boot from MMC1 NOTICE: BL31: v2.2(release):a04808c-dirty NOTICE: BL31: Built : 15:50:35, Feb 5 2021 U-Boot 2020.10-armbian (Feb 05 2021 - 15:50:41 +0000) SoC: Rockchip rk3399 Reset cause: POR Model: Firefly ROC-RK3399-PC Mezzanine Board DRAM: 3.9 GiB PMIC: RK808 MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0 Loading Environment from SPIFlash... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB *** Warning - bad CRC, using default environment In: serial Out: serial Err: serial Model: Firefly ROC-RK3399-PC Mezzanine Board Net: eth0: ethernet@fe300000 Hit any key to stop autoboot: 0 switch to partitions #0, OK mmc1 is current device Scanning mmc 1:1... Found U-Boot script /boot/boot.scr 3185 bytes read in 5 ms (622.1 KiB/s) ## Executing script at 00500000 Boot script loaded from mmc 1 230 bytes read in 5 ms (44.9 KiB/s) 15339012 bytes read in 652 ms (22.4 MiB/s) 28582400 bytes read in 1213 ms (22.5 MiB/s) 77058 bytes read in 12 ms (6.1 MiB/s) 267 bytes read in 8 ms (32.2 KiB/s) Applying kernel provided DT overlay rockchip-pcie-gen2.dtbo 2698 bytes read in 8 ms (329.1 KiB/s) Applying kernel provided DT fixup script (rockchip-fixup.scr) ## Executing script at 09000000 Moving Image from 0x2080000 to 0x2200000, end=3de0000 ## Loading init Ramdisk from Legacy Image at 06000000 ... Image Name: uInitrd Image Type: AArch64 Linux RAMDisk Image (gzip compressed) Data Size: 15338948 Bytes = 14.6 MiB Load Address: 00000000 Entry Point: 00000000 Verifying Checksum ... OK ## Flattened Device Tree blob at 01f00000 Booting using the fdt blob at 0x1f00000 Loading Ramdisk to f1078000, end f1f18dc4 ... OK Loading Device Tree to 00000000f0ffc000, end 00000000f1077fff ... OK Starting kernel ...
Armbianmonitor: http://ix.io/2OIx
-
What is everyone with a NVMe using to power it? Anyone using it with a PD power supply?
-
No, unfortunately it's the only one I have. But I did just try a known good wireless card - same result 😒
-
Am 25.2.2020 um 19:30 schrieb Panzerknacker:
Probably not.
The 0.9V regulator will come with 5.6 :-) but missing it causes no failure.
Link training can time out when no NVME device is connected or a connected one is not powered.
I am getting the same error:
[ 1.253914] vcc3v3_pcie: supplied by sys_12v [ 2.630978] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 2.631008] OF: /pcie@f8000000: Missing device_type [ 2.631041] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 2.631062] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 2.631950] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 2.723678] ehci-pci: EHCI PCI platform driver [ 2.763643] ohci-pci: OHCI PCI platform driver [ 3.092350] rockchip-pcie f8000000.pcie: host bridge /pcie@f8000000 ranges: [ 3.092401] rockchip-pcie f8000000.pcie: MEM 0x00fa000000..0x00fbdfffff -> 0x00fa000000 [ 3.092423] rockchip-pcie f8000000.pcie: IO 0x00fbe00000..0x00fbefffff -> 0x00fbe00000 [ 3.093327] rockchip-pcie f8000000.pcie: no vpcie12v regulator found [ 3.645989] rockchip-pcie f8000000.pcie: PCIe link training gen1 timeout! [ 3.646968] rockchip-pcie: probe of f8000000.pcie failed with error -110 [ 33.762142] vcc3v3_pcie: disabling
Any ideas? I have the mezzanine without PoE and I have enabled PCIe in armbian-config. The build is from today
The m.2 is a Corsair Force MP510 NVMe drive. Power supply is a 60W PD unit, -
Am 26.1.2021 um 04:02 schrieb Fred St-Pierre:
So further trying to get the board to boot, I tried to compile Linux-next, copied all files to the /boot folder, flashed spi.img as recommended and the board is dead in the water again. The u-boot from the amarula release seems to have initramfs built in to the image... So... More attempts required to get the board to boot with self-compiled u-boot and initramfs, I guess.
Maybe check this commit: https://github.com/armbian/build/pull/2572
-
If anyone is interested: I designed a new cover instead of the acrylic plate. I broke it because I tried to drill a hole into it to get access to the power pins:
Spoiler
I made a new one in Fusion 360 to be 3D-printed or laser cut: https://www.thingiverse.com/thing:4501621
With it you get access to all pins (power, PCIe, GPIO, serial and SPI) and the reset button. The picture is of version 1. The newer version on thingiverse has larger cutouts and holes.
Spoiler
-
2 minutes ago, piter75 said:
This shouldn't be the u-boot's HDMI issue - this got disabled in master some time ago.
I am suspecting dev's transition to 5.7
I will look into that over the next few days.
Thanks! Higher boot verbosity doesn't give any more details:
QuoteU-Boot TPL 2020.01-armbian (Mar 30 2020 - 09:10:54)
Channel 0: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 50MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
256B stride
lpddr4_set_rate: change freq to 400000000 mhz 0, 1
lpddr4_set_rate: change freq to 800000000 mhz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...U-Boot SPL 2020.01-armbian (Mar 30 2020 - 09:10:54 -0400)
Trying to boot from MMC1
NOTICE: BL31: v2.2(release):a04808c-dirty
NOTICE: BL31: Built : 09:10:50, Mar 30 2020
U-Boot 2020.01-armbian (Mar 30 2020 - 09:10:54 -0400)Model: Firefly ROC-RK3399-PC Board
DRAM: 3.9 GiB
PMIC: RK808
MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from MMC... Card did not respond to voltage select!
*** Warning - No block device, using default environmentIn: serial@ff1a0000
Out: serial@ff1a0000
Err: serial@ff1a0000
Model: Firefly ROC-RK3399-PC Board
rockchip_dnl_key_pressed: adc_channel_single_shot fail!
Net: eth0: ethernet@fe300000
Hit any key to stop autoboot: 0
Card did not respond to voltage select!
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
2940 bytes read in 7 ms (410.2 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
151 bytes read in 6 ms (24.4 KiB/s)
11772741 bytes read in 504 ms (22.3 MiB/s)
20505088 bytes read in 873 ms (22.4 MiB/s)
74780 bytes read in 13 ms (5.5 MiB/s)
2698 bytes read in 10 ms (262.7 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 39000000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 11772677 Bytes = 11.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f53e5000, end f5f1f305 ... OK
Loading Device Tree to 00000000f536a000, end 00000000f53e4fff ... OKStarting kernel ...
-
Has anybody tried to build an image recently? I get a working image out of 20.05 with focal and dev kernel. It stops booting after an upgrade. It hangs on "starting kernel" (console).
And if I try to build one on master with dev it doesn't boot at all. Over HDMI it shows the following. First I thought it was the HDMI-boot problem of rk3399 ( @piter75 ), but it doesn't change without HDMI cable. The green LED just keeps flashing and nothing happens.
EDIT: Oh and with master and current it boots, but ethernet doesn't come up and open ssh server keeps crashing
And it's not a power supply problem since I power via 12V-headers.
-
Since I also had this problem:
Your time is probably off. I installed an image from a while ago and the time on the board didn't update. Then the certificates are invalid, because they're only valid for 30 days. I did set the time roughly correct to get it going:
sudo date --set="2020-06-26 09:05:59.990"
After that everything starts working again.
-
1 hour ago, a16bitsysop said:
I got an NVME one now, and it is recognized! Did a dd speed test and got 370mb/s on the nvme drive and 13.8mb/s on the SD card.
I created an ext4 filesystem on the already existing single partition it had as if I do:
sudo fdisk /dev/nvme0
I get the error Illegal seek and it exits.
If I try:
sudo parted /dev/nvme0
I get
Error: The device /dev/nvme0 is so small it cannot possibly store a filesystem or partition table. Perhaps you are using the wrong device.
But I can create a filesystem on /dev/nvmen1 mount it and dd a1gb file without errors.
Sent from my moto g(7) power using Tapatalk
What does lspci and lsblk say?
-
I've built the current branch which is 5.4.20. You could go dev which I believe is 5.5.x.
-
I've build 20.02. It's working fine (still powering via 12V).
-
I would test the roc-rk3399-pc for you as I have it here and it works now with power via headers. It appears in your testing list, but it's not being build right now. I can build it myself, but that might defeat the purpose 😀
-
I finally got everything together to power this thing via the 12V header and it works
I did a minimal Ubuntu build like two weeks ago and it booted fine. I ran sbc-bench: http://ix.io/2aVd
Now it might be something more than a paper weight
-
Do you know which pin is what? Edit: Found an image of the add-on board, where it's labeled.
-
On 1/14/2020 at 3:48 PM, Panzerknacker said:
If we could solve this:
https://lore.kernel.org/linux-usb/0ac6bbe7-6395-526d-213c-ac58a19d8673@fivetechno.de/
we probably had everything working in mainline.
Does anyone know if I can power this thing via the 12V header? The documentation on this is lacking. It should work since the mezzanine board can provide power either via battery or PoE. I do have a beefy 5V power supply, but it's in use and I do have a spare 12V power supply. I also have a USB-C PD power supply, but apparently that doesn't switch to higher voltages yet...
-
6 hours ago, cowbe0x004 said:
Did you figure it out?
Can armbian boot from SSD also?
It works out of the box. After the first boot just choose to move everything to the connected SSD in armbian-config. I am booting from an SSD and have two more HDDs connected.
-
Interesting. I don't recall it being picky with the power supply when I tried the images from Firefly. They are horrible by the way, somebody called it "dependency hell". It took me about an hour to just get it to apt upgrade
-
You should probably set your locales manualy. At least it's what I had to so, because dpkg-reconfigure keyboard-configuration is buggy
Check the output of locale and set everything to de_DE.UTF-8:
https://www.thomas-krenn.com/de/wiki/Locales_unter_Ubuntu_konfigurieren
It should then work without
# set convert-meta off -
On 6/7/2019 at 3:50 PM, pavelectric said:
The long-awaited fee on the M4, in the form of a plate.
NVME SSD Adapter for M4 No price yet, write to WiKiIt's already available: https://www.friendlyarm.com/index.php?route=product/product&path=70&product_id=262
5$ is pretty nice!
ROC-RK3399-PC (Renegade Elite)
in Libre Renegade
Posted
Thanks
Unfortunately I don't have another device right now to test the ssd or update the firmware. But that'll change soon.