Date: Wed, 13 Nov 2019 15:19:17 -0700 (MST) From: =?UTF-8?Q?Klaus_K=C3=BCchemann?= <maciphone2@googlemail.com> To: freebsd-arm@freebsd.org Subject: Re: Choose between Raspberry Pi 4B 4GB and ROCKPro64 Message-ID: <1573683557830-0.post@n6.nabble.com> In-Reply-To: <20191113220928.GZ43404@cicely7.cicely.de> References: <7b75e2ed23e334878fbb3c1d585ffc51.squirrel@10.1.1.11> <20191015220433.GS96402@funkthat.com> <20191112124539.GM43404@cicely7.cicely.de> <1573571378957-0.post@n6.nabble.com> <20191112221610.GN43404@cicely7.cicely.de> <20191112225251.GB4552@funkthat.com> <20191113075343.GP43404@cicely7.cicely.de> <20191113220928.GZ43404@cicely7.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Bernd Walter-4 wrote > On Wed, Nov 13, 2019 at 08:53:43AM +0100, Bernd Walter wrote: >> On Tue, Nov 12, 2019 at 02:52:51PM -0800, John-Mark Gurney wrote: >> > Bernd Walter wrote this message on Tue, Nov 12, 2019 at 23:16 +0100: >> > > On Tue, Nov 12, 2019 at 08:09:38AM -0700, Klaus K=C3=BCchemann via >> freebsd-arm wrote: >> > > > <<The u-boot has to go into the SPI-Flash or on the card? >> >> > > >=20 >> > > > onto the uSD : >> > > > https://www.freshports.org/sysutils/u-boot-rockpro64/ >> > > > Regards=20 >> > > > Klaus >> > >=20 >> > > Thank you. >> > >=20 >> > > Do you know the bps rate used by u-boot and later components? >> > > I do see some output at the usual 115200 bps, but it is messed up. >> > > Also tried other typical bps rates, including 1.5Mbps as mentioned >> > > on the RockPro Wiki, but none worked. >> > > I wouldn't rule out that it is the USB uart failing at 1.5M though, >> > > but I've tried a PL2303, CP2102 (which refused 1.5Mbps) and >> > > a CH340. >> > > Unfortunately I don't have an FTDI based TTL one at hands. >> > > It also fails with reading the uartt output when booting an Armbian >> > > image, which as such is booting fine according to the HDMI output. >> >=20 >> > It's 1.5Mbps, aka 1500000. I'm using the CH340G that they sell: >> > https://store.pine64.org/?product=3Dpadi-serial-console >> >=20 >> > And it works, but it will occasionally drop characters. >>=20 >> Sigh - IMO 1.5M is an insane idea for that and so needless. >>=20 >> > None of my other serial adapters could do the speed necessary. >>=20 >> I just retried with the CH340 - again no success, but noticed that the >> chip on my adapter is unlabeled. >> So probably it isn't a genuine. >> I should have some others, but not at home, and I also have some >> loose CH340G chips. >=20 >=20 > Grr - I was off by one pin. > Ground on TX and signal on RX. > On the analyzer it was obvious that it's is not propper uart signaling. > With the wrong wiring it was inverted. >=20 > Now I get FreeBSD output: > U-Boot TPL 2019.10 (Oct 25 2019 - 06:55:42) > Trying to boot from BOOTROM > Returning to boot ROM... >=20 > U-Boot SPL 2019.10 (Oct 25 2019 - 06:55:42 +0000) > Trying to boot from MMC1 > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@= ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ > ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^= @^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@= ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ >=20 > U-Boot 2019.10 (Oct 25 2019 - 06:55:42 +0000) >=20 > Model: Pine64 RockPro64 > DRAM: 2 GiB > MMC: dwmmc@fe320000: 1, sdhci@fe330000: 0 > Loading Environment from MMC... Card did not respond to voltage select! > *** Warning - No block device, using default environment >=20 > In: serial@ff1a0000 > Out: serial@ff1a0000 > Err: serial@ff1a0000 > Model: Pine64 RockPro64 > rockchip_dnl_key_pressed: adc_channel_single_shot fail! > Net: eth0: ethernet@fe300000 > Hit any key to stop autoboot: 0=20 > Card did not respond to voltage select! > switch to partitions #0, OK > mmc1 is current device > Scanning mmc 1:1... > 73463 bytes read in 9 ms (7.8 MiB/s) > Found EFI removable media binary efi/boot/bootaa64.efi > ESC7ESC[rESC[999;999HESC[6nESC8Scanning disk=20 > dwmmc@ > ... > Card did not respond to voltage select! > Scanning disk=20 > sdhci@ > ... > Disk=20 > sdhci@ > not ready > Found 3 disks > BootOrder not defined > EFI boot manager: Cannot load any image > 676216 bytes read in 34 ms (19 MiB/s) > ESC[?25hESC[1;1HESC[0;37;40mCESC[0;37;40mESC[1;2HE > ... > I hate when console output includes that crap... > Seriously, the typescript file is 792405 Bytes long. > WTF is wrong with plain line output while booting? > Somewhere hidden in between is the whole loader output. > I can cat the file and see something of that, but the screen gets > redrawn in between. > ... > ;37;40m ^[[0;37;40m^[[25;72H^[[0;37;40m ^[[0;37;40m^[[25;73H^[[0;37;40m > ^[[0;37;40m^[[25;74H^[[0;37;40m ^[[0;37;40m^[[25;75H^[[0;37;40m > ^[[0;37;40m^[[25;76H^[[0;37;40m ^[[0;37;40m^[[25;77H^[[0;37;40m > ^[[0;37;40m^[[25;78H^[[0;37;40m ^[[0;37;40m^[[25;79H^[[0;37;40m > ^[[0;37;40m^[[25;80H^ > [[?25h^[[25;1H---< > <BOOT> >>---^M > KDB: debugger backends: ddb^M > KDB: current backend: ddb^M > Copyright (c) 1992-2019 The FreeBSD Project.^M > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994^= M > The Regents of the University of California. All rights > reserved.^M > FreeBSD is a registered trademark of The FreeBSD Foundation.^M > FreeBSD 13.0-CURRENT #0 r354423: Thu Nov 7 12:03:03 UTC 2019^M > =20 > root@.freebsd > :/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64^M > FreeBSD clang version 9.0.0 (tags/RELEASE_900/final 372316) (based on LLV= M > 9.0.0)^M > WARNING: WITNESS option enabled, expect reduced performance.^M > VT: init without driver.^M > module firmware already present!^M > KLD file umodem.ko is missing dependencies^M > Starting CPU 1 (1)^M > Starting CPU 2 (2)^M > Starting CPU 3 (3)^M > Starting CPU 4 (100)^M > Starting CPU 5 (101)^M > FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs^M > arc4random: WARNING: initial seeding bypassed the cryptographic random > device because it was not yet seeded and the knob 'bypass_before_seeding' > was enabled.^M > random: entropy device external interface^M > MAP 7cf1a000 mode 2 pages 1^M > MAP 7cf25000 mode 2 pages 1^M > MAP 7ff40000 mode 2 pages 16^M > kbd0 at kbdmux0^M > ofwbus0:=20 > <Open Firmware Device Tree> > ^M > clk_fixed0:=20 > <Fixed clock> > on ofwbus0^M > simplebus0:=20 > <Flattened device tree simple bus> > on ofwbus0^M > rk_grf0:=20 > <RockChip General Register Files> > mem 0xff320000-0xff320fff on ofwbus0^M > rk3399_pmucru0:=20 > <Rockchip RK3399 PMU Clock and Reset Unit> > mem 0xff750000-0xff750fff on ofwbus0^M > rk3399_cru0:=20 > <Rockchip RK3399 Clock and Reset Unit> > mem 0xff760000-0xff760fff on ofwbus0^M >=20 > And it hangs at this point. > Ok - I created the image in an oportunistic way and downloaded: > FreeBSD-13.0-CURRENT-arm64-aarch64-PINE64-LTS-20191107-r354423.img > Then wrote the rockpro64 u-boot onto the card. >=20 > This is what I have on my screen after a cat: > Loading /boot/device.hints n ( = = = =20 > e > Loading /boot/loader.conf ; 0 = =20 > 7;40m1 > Loading /boot/loader.conf.local 0 = =20 > Loading kbrnel... 4 = =20 > /boot/kernel/kernel text=3D0x96c524 data=3D0x1898b0 data=3D0x +0x79a5e0 > syms=3D[0x8+0x14 > 16a8+0x8+0x12c6e9] 5 = =20 > Loading conf4gured modules... = =20 > /boot/kernel/umodem.kd text=3D0x2100 text=3D0x13a0 data=3D0x6e0+0x1=20 > syms=3D[0x8+0xf48+0 > x8+0xb6e] k 1 = =20 > can't find '/boot/e[tropy'0mn t = 0 =20 > b > e s = =20 > Hit [Enter] to boot immediately, or any other key or command prompt. = =20 > Booting [/boot/kern l/kernel]... = =20 > Using DTB provided by EFI at 0x.0eb000. = =20 > Loading DTB tverlays: 'sun50i-a64-sid,sun50i-a64-ths,sun50i-a64-tim > r,sun50i-a64 > -opp' 0 4 = =20 > 78Hx > /boot/dtb/overlays sun50i-a64-sid.dtbo size=3D0x1fd = =20 > /boot/dtb/overlays/sun50i-a643ths.dtbo size=3D0x3e80;37;40mi = =20 > /boot/dtb/ov7rlays/sun50i-a64-thmer.dtbo size=3D0x175 ; = =20 > /boot/dtb/overla[s/sun50i-a64-opp.dtbo size=3D0m74f s = =20 > DTB overlay '/boot/dtb/overlayspsun50i-a64-sid.dtbo' not compatible = =20 > DTB o/erlay '/boot/dtb/overlays/sun50i-a64-thmsdtbo' not compatible = =20 > DTB overlay '/boot/dtb/overlays/sun50i-a64-timer.dtbo' not compatible = =20 > DTB overlay '/boot/dtb/overlays/sun50i-a64-opp.dtbo' 'ot compatible = =20 > ---< > <BOOT> >>--- 0 ; 40m > KDB: debugger backends: ddb > KDB: current backend: ddb > Copyright (c) 1992-2019 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 > The Regents of the University of California. All rights reserved. > FreeBSD is a registered trademark of The FreeBSD Foundation. > FreeBSD 13.0-CURRENT #0 r354423: Thu Nov 7 12:03:03 UTC 2019 > =20 > root@.freebsd > :/usr/obj/usr/src/arm64.aarch64/sys/GENERIC arm64 > FreeBSD clang version 9.0.0 (tags/RELEASE_900/final 372316) (based on LLV= M > 9.0.0) > WARNING: WITNESS option enabled, expect reduced performance. > VT: init without driver. > module firmware already present! > KLD file umodem.ko is missing dependencies > Starting CPU 1 (1) > Starting CPU 2 (2) > Starting CPU 3 (3) > Starting CPU 4 (100) > Starting CPU 5 (101) > FreeBSD/SMP: Multiprocessor System Detected: 6 CPUs > arc4random: WARNING: initial seeding bypassed the cryptographic random > device because it was not yet seeded and the knob 'bypass_before_seeding' > was enabled. > random: entropy device external interface > MAP 7cf1a000 mode 2 pages 1 > MAP 7cf25000 mode 2 pages 1 > MAP 7ff40000 mode 2 pages 16 > kbd0 at kbdmux0 > ofwbus0:=20 > <Open Firmware Device Tree> > clk_fixed0:=20 > <Fixed clock> > on ofwbus0 > simplebus0:=20 > <Flattened device tree simple bus> > on ofwbus0 > rk_grf0:=20 > <RockChip General Register Files> > mem 0xff320000-0xff320fff on ofwbus0 > rk3399_pmucru0:=20 > <Rockchip RK3399 PMU Clock and Reset Unit> > mem 0xff750000-0xff750fff on ofwbus0 > rk3399_cru0:=20 > <Rockchip RK3399 Clock and Reset Unit> > mem 0xff760000-0xff760fff on ofwbus0 >=20 > Looks like it didn't load the rk3399-rockpro64.dtb, which is on the > filesystem > and just tried A64 ones. > The GENERIC kernel on the image seems to know the RK3399 at least. >=20 > --=20 > B.Walter < > bernd@ > > http://www.bwct.de > Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm. > _______________________________________________ > freebsd-arm@ > mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to " > freebsd-arm-unsubscribe@ > " Bernd, did you notice ? : -- U-Boot 2019.10 (Oct 25 2019 - 06:55:42 +0000) Model: Pine64 RockPro64 DRAM: 2 GiB -- wasn't it the 4GB-model you bought ? -- <<Ok - I created the image in an oportunistic way and downloaded: FreeBSD-13.0-CURRENT-arm64-aarch64-PINE64-LTS-20191107-r354423.img Then wrote the rockpro64 u-boot onto the card.>> O.K., when it boots it's O.K., but I'm surprised why you use **Pine64**.im= g (which is NOT RockPro64) -- Regards,Klaus=20 -- Sent from: http://freebsd.1045724.x6.nabble.com/freebsd-arm-f4199244.html
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1573683557830-0.post>