Re: Zynq FDTisation [was Re: Cortex-A9 boot problems with d-cache on Zynq]

[Alexander Nasonov <alnsn%yandex.ru@localhost>]

Nick Hudson wrote:
> To get the ball rolling I've added early Zynq-7000 support to GENERIC
> 
> http://mail-index.netbsd.org/source-changes/2019/06/11/msg106540.html
> 
> 
> A clock driver is the next step.
> 
> Nick

It panics on Zybo Z7-20:

Zynq> fatload mmc 0 100000 netbsd.ub
9380180 bytes read in 599 ms (14.9 MiB/s)
Zynq> fatload mmc 0 ${fdt_addr_r} zynq-zybo-z7.dtb
11694 bytes read in 14 ms (815.4 KiB/s)
Zynq> bootm 0x100000  - ${fdt_addr_r}
## Booting kernel from Legacy Image at 00100000 ...
   Image Name:   NetBSD/earmv7 8.99.44
   Image Type:   ARM Linux Kernel Image (no loading done) (uncompressed)
   Data Size:    9380116 Bytes = 8.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
   Booting using the fdt blob at 0x1f00000
   XIP Kernel Image (no loading done) ... OK
   Loading Device Tree to 1fffa000, end 1ffffdad ... OK

Starting kernel ...

[   1.0000000] NetBSD/evbarm (fdt) booting ...
[   1.0000000] panic: kernel diagnostic assertion "(va & ((L1_S_SIZE * (PAGE_SIZE / L2_T_SIZE)) - 1)) == 0" failed: file "/home/alnsn/netbsd-current/sljit/src/sys/arch/arm/arm32/pmap.c", line 6728
[   1.0000000] cpu0: Begin traceback...
[   1.0000000] 0x808f2604: 802836e4
[   1.0000000] 0x808f261c: 8042c7ac
[   1.0000000] 0x808f2634: 80566c44
[   1.0000000] 0x808f2674: 800857f4
[   1.0000000] 0x808f28cc: 800014d8
[   1.0000000] 0x808f28f4: 8007b7fc
[   1.0000000] 0x808f297c: 80008684
[   1.0000000] cpu0: End traceback...

-- 
Alex