Re: Pandaboard ES
Rui-Xiang Guo <[email protected]>
| Newsgroups | gmane.os.netbsd.ports.arm |
|---|---|
| Message-ID | <Z9QY6tA5uNs-3eMa@picohive> |
On Mon, Jun 17, 2024 at 08:42:12PM +0800, Rui-Xiang Guo wrote: > On Mon, May 01, 2023 at 07:31:07AM -0300, Jared McNeill wrote: > > The PANDABOARD kernel relies on firmware to program the base address of the > > GIC and local timers correctly in the CBAR cp15 register. Likely the reason > > that the GIC driver did not discover any valid sources: > > I find the singularity in the early boot log: > [ 1.0000000] NetBSD 9.4 (PANDABOARD) #0: Sat Apr 20 13:32:22 UTC 2024 > [ 1.0000000] [email protected]:/usr/src/sys/arch/evbarm/compile/PANDABOARD > [ 1.0000000] total memory = 1024 MB > [ 1.0000000] avail memory = 1006 MB > [ 1.0000000] mainbus0 (root) > [ 1.0000000] cpu0 at mainbus0 core 0: 699 MHz Cortex-A9 r2p10 (Cortex V7A core) > [ 1.0000000] cpu0: DC enabled IC enabled WB enabled LABT branch prediction enabled > [ 1.0000000] cpu0: 32KB/32B 4-way L1 VIPT Instruction cache > [ 1.0000000] cpu0: 32KB/32B 4-way write-back-locking-C L1 PIPT Data cache > [ 1.0000000] cpu0: 64KB/32B 8-way write-through L2 PIPT Unified cache > [ 1.0000000] vfp0 at cpu0: NEON MPE (VFP 3.0+), rounding, NaN propagation, denormals > [ 1.0000000] armperiph0 at mainbus0 > [ 1.0000000] arml2cc0 at armperiph0: ARM PL310 r0p0 L2 Cache Controller (disabled) > > It means the L2 cache id returns 0 through bus_space_read_4(). > > By comparing against OpenBSD 7.5: > OpenBSD 7.5 (RAMDISK) #157: Sat Mar 23 20:49:21 MDT 2024 > [email protected]:/usr/src/sys/arch/armv7/compile/RAMDISK > real mem = 895275008 (853MB) > avail mem = 860352512 (820MB) > random: boothowto does not indicate good seed > mainbus0 at root: TI OMAP4 PandaBoard-ES > cpu0 at mainbus0 mpidr 0: ARM Cortex-A9 r2p10 > cpu0: 32KB 32b/line 4-way L1 VIPT I-cache, 32KB 32b/line 4-way L1 D-cache > cortex0 at mainbus0 > amptimer0 at cortex0: 396000 kHz > armliicc0 at cortex0: rtl 7 waymask: 0x0000000f > > It returns 7. I test them with the same u-boot. > So, what went wrong? I am trying to bring the board to 10.0, and it looks better now: https://github.com/picohive/netbsd-pandaboard/blob/main/boot.log The current problem - is there any proper method to pass a clock from omap4prcm to a9ptmr? -rxg