> As of right now I'm stuck here... if there's anything obvious that I should be > focusing on please point it out and possibly recommend a tool to avenue I should start > down in searching for a solution. > > DDR version 1.13 20180428 > ID:0x805 N > In > LPDDR3 > 786MHz > Bus Width=32 Col=11 Bank=8 Row=15/15 CS=2 Die Bus-Width=32 Size=4096MB > ddrconfig:7 > OUT > Boot1 Release Time: Feb 2 2018 15:41:39, version: 2.46 > ChipType = 0x11, 144 > SdmmcInit=2 0 > BootCapSize=0 > UserCapSize=0MB > FwPartOffset=2000 , 0 > SdmmcInit=0 0 > BootCapSize=0 > UserCapSize=30436MB > FwPartOffset=2000 , 0 > StorageInit ok = 35976 > Raw SecureMode = 0 > SecureInit read PBA: 0x4 > SecureInit read PBA: 0x404 > SecureInit read PBA: 0x804 > SecureInit read PBA: 0xc04 > SecureInit read PBA: 0x1004 > SecureInit ret = 0, SecureMode = 0 > LoadTrustBL > No find bl30.bin > No find bl32.bin > Load uboot, ReadLba = 2000 > Load OK, addr=0x200000, size=0x92bd4 > RunBL31 0x10000 > NOTICE: BL31: v1.3(debug):9d3f591 > NOTICE: BL31: Built : 14:39:02, Jan 17 2018 > NOTICE: BL31:Rockchip release version: v1.3 > INFO: ARM GICv2 driver initialized > INFO: Using opteed sec cpu_context! > INFO: boot cpu mask: 1 > INFO: plat_rockchip_pmu_init: pd status 0xe > INFO: BL31: Initializing runtime services > WARNING: No OPTEE provided by BL2 boot loader, Booting device without OPTEE initiK > ERROR: Error initializing runtime service opteed_fast > INFO: BL31: Preparing for EL3 exit to normal world > INFO: Entry point address = 0x200000 > INFO: SPSR = 0x3c9 > > > U-Boot 2019.01-rc1 (Dec 04 2018 - 16:09:21 +0000) > > Model: Rockchip RK3328 EVB > DRAM: 4 GiB > MMC: rksdmmc@ff500000: 1, rksdmmc@ff520000: 0 > Loading Environment from MMC... *** Warning - bad CRC, using default environment > > In: serial@ff130000 > Out: serial@ff130000 > Err: serial@ff130000 > Model: Rockchip RK3328 EVB > Net: > Warning: ethernet@ff540000 (eth0) using random MAC address - 72:af:2b:fe:8b:98 > eth0: ethernet@ff540000 > 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 EFI removable media binary efi/fedora/grubaa64.efi > Found DTB mmc 1:2 /dtb/rockchip/rk3328-evb.dtb > 32498 bytes read in 3 ms (10.3 MiB/s) > Scanning disk rksdmmc@xxxxxxxxxxxx... > Card did not respond to voltage select! > Scanning disk rksdmmc@xxxxxxxxxxxx... > Disk rksdmmc(a)ff520000.blk not ready > Found 4 disks > 1882872 bytes read in 88 ms (20.4 MiB/s) > ## Starting EFI application at 02080000 ... > Speed: 100, full duplex > "Synchronous Abort" handler, esr 0x96000210 > elr: fffffffffcf419b0 lr : fffffffffcf419a8 (reloc) > elr: 00000000fbc799b0 lr : 00000000fbc799a8 > x0 : 0000000000000000 x1 : 00000000fbb6ae56 > x2 : 00000000ffffffff x3 : 00000000fbd718cc > x4 : 00000000fbb6f080 x5 : 0000000000000020 > x6 : 00000000fcf26538 x7 : 00000000fbb6be20 > x8 : 0000000000000001 x9 : 0000000000000008 > x10: 00000000fcf56070 x11: 00000000fcf56070 > x12: 000000000000a3c0 x13: 0000000000000001 > x14: 00000000fcf2686c x15: 00000000ffffffff > x16: 0000000000001550 x17: 0000000000000000 > x18: 00000000fcf2fdf8 x19: 0000000000000000 > x20: 00000000fcf56130 x21: 00000000fef385c8 > x22: 0000000000000000 x23: 0000000002080000 > x24: 0000000000000003 x25: 0000000000000000 > x26: 0000000000000000 x27: 0000000000000000 > x28: 00000000fcf56010 x29: 00000000fcf26920 > > Resetting CPU ... Quick update.... Issue seems to be the grub efi app (grubaa64.efi) I've created a bootloader that works and the grub efi app loads although I get a kernel hang (using fedora 4.20.x kernel). I couldn't get the Fedora 29 grub efi app to work so I borrowed opensuses and grub loaded although with no config. I head to 'configfile 'disk location of config'' to get fedoras grub.cfg to load. The kernel and initramfs were pulled from the disk although it hung when attempting boot without any obvious visual debug logs of what might be wrong. I've used the DRAM config binaries, fist stage loader configs and arm trust stuff from from ayufan repos with the fedora u-boot binary for evb-rk3288 It's a 4.20 version of the fedora kernel. Possibly Fedoras grub may require a few patches or need a slightly different configuration. I'll be looking into how Suse does things for the for the time being so I can add that support to Fedoras grub. I am going to try to get the 4.20 version of the kernel to boot after I've resolved that issue. If boots are unsuccessful I'll move on to ayufans mainline kernel to see if I can bring over what he's done to his kernels to get Fedora to make this board boot. If anyone has any wise words I'll love to here them? Around: * the possible differences between opensuses grub and fedoras grub (grubaa64.efi); where to focus? just point and I'll look. * the opensuse grubaa64.efi app not wanting to boot a kernel (where to look what tools could help me debug something like this?) And thanks to everyone who's done work to get me up to this point (ayufans stuff and friends) It's time to make a wee bit more progress and move forward. Regards, _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
