Load to: 0x43c00000 Load Size: 655872 Launch Addr :0x43c00000 bl1, image loaded, launching to 0x43c00000 U-Boot 2016.01 (Sep 24 2018 - 14:49:36 -0700) Model: NanoPi Fire3 board based on Samsung/Nexell s5p6818 Board: NanoPi Fire3 DRAM: 1 GiB HW Revision: 7 MMC: NEXELL DWMMC: 0, NEXELL DWMMC: 1 In: serial Out: serial Err: serial LCD#1:0x0, LCD#2:0x0, CAM#1:0x0, CAM#2:0x0 ADD-ON-BOARD : 0x0 Net: eth0: ethernet@c0060000 Hit any key to stop autoboot: 0 Booting Kyu via dhcp ethernet@c0060000 Waiting for PHY auto negotiation to complete...... done Speed: 1000, full duplex BOOTP broadcast 1 BOOTP broadcast 2 DHCP client bound to address 192.168.0.67 (251 ms) Using ethernet@c0060000 device TFTP from server 192.168.0.5; our IP address is 192.168.0.67 Filename 'fire3.bin'. Load address: 0x40000000 Loading: ############ 6.9 MiB/s done Bytes transferred = 166616 (28ad8 hex) ## Starting application at 0x40000000 ... Probing for amount of ram Found 1024 M of ram XXX mmu_initialize still pending for ARM v8 ARM cache line size: 64 RAM 1024M total starting at 40000000 Kyu image size: 1287856 bytes kernel end: 4013a6b0 Ram alloc start: 4013c000 ram_alloc: 4194304 (4194304) bytes -- 4013c000 Kyu version 0.8.0 for fire3, Compiled by tom: Tue 04 Aug 2020 08:50:44 AM MST starting ram_alloc: 524288 (524288) bytes -- 4053c000 Enabling interrupts 0 symbols RAM 1018M+ available starting at 405bc000 Kyu version 0.8.0 for fire3, Compiled by tom: Tue 04 Aug 2020 08:50:44 AM MST running Kyu, ready>The standard kyu test sequence works fine, so apparently the timer is running and I am getting interrupts. This is of particular interest because I am having trouble with the Allwinner H5 chip in this regard, and it is my only other ARM64 chip.
Looking at the source code I see:
Tom's electronics pages / tom@mmto.org