> Date: Sat, 12 Oct 2019 08:55:50 +0200 > From: Sylvain <sylvain.sab...@free.fr> > > Le 11 octobre 2019 20:24:20 GMT+02:00, Mark Kettenis > <mark.kette...@xs4all.nl> a écrit : > >> Date: Fri, 11 Oct 2019 19:33:25 +0200 (CEST) > >> From: sylvain.sab...@free.fr > >> > >> Hello. > >> > >> I have been acquiring a Firefly RK-3399 ARM card, > >> with the intention of using it as a support platform > >> for diverse projects. > >> > >> Unfortunately my attempts at running OpenBSD on it > >> have not been as fruitful as expected. > >> (confer my post on the French OpenBSD community forums) > >> https://obsd4a.net/forum/showthread.php?tid=2408&pid=19053 > >> > >> May I know, where is the support at for this platform ? > > > >The platform works really well (I have one). There is no graphics > >support though, so you'll have to use a serial console. The standard > >serial speed is 1500000 baud (which isn't always supported by usb > >serial converters) but the U-Boot firmware in ports has been patched > >to support a more standard 115200. > > > >The main problem is that board comes with firmware already installed > >on eMMC and the board boots from eMMC first. I worked around that by > >zapping the contents of the eMMC from Linux (risky). Then the board > >will boot from uSD. It is also possible to flash the eMMC over one of > >the USB ports, but you'd need a machine with Linux and/or Windows to > >do that. > > > >Cheers, > > > >Mark > > Indeed, I cannot get the console to display anything. Does this mean > that the usb-ttl adapter that is provided with my order is even > unfit, and I have to purchase another one?
The one that I got with my board worked. If you're using OpenBSD you'll need to use: # cu -l cuaU0 -s 15000000 There may be an issue with driver support for those speeds. A dmesg would help in that case. > And, yes again, the only solution is to flash the eMMC. Really? That > sounds unfortunate, as I prefer to keep things in factory settings, > as an option. I guess eventually there might be a workaround with > working on the boot manager? Depending on the firmware in eMMC it may be possible to build your own trust.img and u-boot.img and write them at the appropriate offsets on your uSD card. The miniroot66.fs will have anough space at the start of the image to do that. This needs some binary-only tools that only run on Linux or Windows though. See doc/README.rockchip in the U-Boot source tree. The following URL may be helpful to understand how things work: http://opensource.rock-chips.com/wiki_Boot_option In this setup it would load idbloader.img from eMMC and u-boot.img and trust.img from uSD. > I have the second version of the card/firmware at present, which is > the second one released in 2018 I think. It seems to not be fully > open source although this was promoted... If you want fully open source firmware you'll need to wipe eMMC or replace the firmware on the eMCC. Cheers, Mark
