Date: Mon, 14 Dec 2020 15:24:28 -0400 From: Mitchell Horne <mhorne@freebsd.org> To: Klaus Cucinauomo <maciphone2@googlemail.com> Cc: freebsd-riscv <freebsd-riscv@freebsd.org> Subject: Re: any prebuilt-sd card-image image available for HiFive Unleashed ? Message-ID: <CADeAsy38W%2BZcmYo4%2Bz0SDyCC5M5T9YXFiDE4O-gtA2Ei=dmu2Q@mail.gmail.com> In-Reply-To: <E0FEBDDE-64F5-4E7F-B082-B7ED20A14B2C@googlemail.com> References: <C2DE05FF-6415-4648-88A3-37B03A0BD26B@googlemail.com> <CADeAsy3Hm8ifqeqQtPsU0Yx8BmRYr8G-nrC77WY3XnRTmZQhiQ@mail.gmail.com> <E0FEBDDE-64F5-4E7F-B082-B7ED20A14B2C@googlemail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Klaus, Thanks for your detailed response. More below. On Fri, Dec 11, 2020 at 10:35 PM Klaus Cucinauomo <maciphone2@googlemail.com> wrote: > > Hi Mitchell, > > thanks, after I had rebased my chaotic ports-tree ;-) , your port has bui= lt fine. > Well, for now the best I can get out of uSD-boot with your port is : > > =E2=80=94 your port:------ > U-Boot SPL 2020.10 (Dec 11 2020 - 22:20:01 +0000) > Trying to boot from MMC1 > Unhandled UUnhanldd excleled excepti:on:n > 0EPrucnisntr Euct0i0o0n IPllegc0aln > RE 0P0C: 00000000:800200000 0R00A:# 000000000008 > 000 7500#aP TV0AeL: 00= 00t0#00E0E000P00000r > ### ERhROR ### Please RESET the board ### > =E2=80=94------------ Hmm. Looks like things go wrong in u-boot SPL, before entering u-boot proper, but it's not entirely clear. You could try to isolate the issue by first flashing the freedom-u-sdk image, and replacing the u-boots one at a time with the versions from my port. So: 1. dd entire freedom-u-sdk image to SD 2. delete linux and msdos partition 3. Verify that board boots to u-boot 2020.07 (non SPL) 4. dd u-boot.itb from my port to !2e54b353-1271-4842-806f-e436d6af6985 partition 5. Check whether it boot to u-boot 2020.10 (non SPL) 6. If it does, dd u-boot-spl.bin from my port to !5b193300-fc78-40cd-8002-e86c45580b47 7. See if you receive the above unhandled exception Before we try booting to freebsd this should help us narrow down where u-boot is going wrong. Please give this a try when you have a chance and let me know the result. > with boot jumper MSEL2 switched up(required to boot from u-boot) . > Well, no FreeBSD-Kernel installed=E2=80=A6.only u-boot. > > -- > Compared to: > =E2=80=94 https://github.com/sifive/freedom-u-sdk ---- > U-Boot SPL 2020.07 (Nov 20 2020 - 12:10:09 +0000) > Trying to boot from MMC1 > > U-Boot 2020.07 (Nov 20 2020 - 12:10:09 +0000) > > CPU: rv64imafdc > Model: SiFive HiFive Unleashed A00 > DRAM: 8 GiB > MMC: spi@10050000:mmc@0: 0 > In: serial@10010000 > Out: serial@10010000 > Err: serial@10010000 > Net: eth0: ethernet@10090000 > Hit any key to stop autoboot: 0 > switch to partitions #0, OK > mmc0 is current device > Scanning mmc 0:3=E2=80=A6 > =E2=80=94=E2=80=94=E2=80=A6.Boots into Linux=E2=80=A6 > =E2=80=94---------- > well ,freedom-u-sdk has a visible (msdos)- Partition which contains a dt= b: > / hifive-unleashed-a00.dtb / > And a configuration file extlinux.conf: > default OpenEmbedded > label OpenEmbedded-SiFive-HiFive-Unleashed > kernel /bbla.gz > fdt /hifive-unleashed-a00.dtb > append root=3D/dev/mmcblk0p4 rootfstype=3Dext4 rootwait console=3DttySIF0= ,115200 earlycon=3Dsbi > =E2=80=94 > > This is the freedom-u-sdk partition table: > =E2=80=94=E2=80=94=E2=80=94 boots fine: --- > root@freebsd:/usr/local/share/u-boot/u-boot-sifive-fu540 # gpart show da2 > =3D> 34 13918175 da2 GPT (30G) [CORRUPT] > 34 2048 1 !5b193300-fc78-40cd-8002-e86c45580b47 (1.0M) > 2082 8192 2 !2e54b353-1271-4842-806f-e436d6af6985 (4.0M) > 10274 6110 - free - (3.0M) > 16384 266240 3 ms-basic-data (130M) > 282624 4096 - free - (2.0M) > 286720 13631488 4 linux-data (6.5G) > 13918208 1 - free - (512B) > > =E2=80=94=E2=80=94 > > dd' =C3=ACng > https://download.freebsd.org/ftp/snapshots/riscv/riscv64/ISO-IMAGES/13.0/= FreeBSD-13.0-CURRENT-riscv-riscv64-GENERICSD-20201210-7578a4862f0.img.xz > directly to uSD also shows / [CORRUPT] / from # gpart show da2 > Usually this indicates that the backup GPT header can't be found, and is harmless. However, I did find a small issue with the config that generates the GENERICSD image, and I will have to generate a new one. > well, at the moment I haven`t any further idea where to start hacking it = but trying to dd > /fw_dynamic.bin/ to the !2e54b353-1271-4842-806f-e436d6af6985 - partitio= n in your port > also didn`t succeed and no idea how I had to apply your port to the GENER= ICSD-20201210. > > Do you have any further idea/instruction ? > Thanks > > Best Regards > > Klaus
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADeAsy38W%2BZcmYo4%2Bz0SDyCC5M5T9YXFiDE4O-gtA2Ei=dmu2Q>