I understand the importance now. No, I got to the same result with your dts as with the evk one, crash after the usbcore modules were registered, and then binary garbage on the console.
I do understand that you are not familiar with the Wink Hub, and am especially appreciative of the time you are offering. Is this still relevant to u-boot, or should this conversation move elsewhere, since this is more about the kernel now it seems? Although I guess modern u-boot also cares about device trees? Regards, Rogan On Fri, 23 Jun 2023 at 16:05, Fabio Estevam <feste...@gmail.com> wrote: > Hi Rogan, > > On Fri, Jun 23, 2023 at 10:53 AM Rogan Dawes <ro...@dawes.za.net> wrote: > > > > Hi Fabio, > > > > Thanks so much for the effort put in. I just wanted to confirm that I am > able to get console output when using the imx28-evk.dts file, although it > crashes after a few lines of output. That seems to suggest that the > additional pins that you have added in your patch are not necessary, and > possibly even incorrect? > > It could be that the kernel console log is appearing only because > U-Boot did the correct pinmux of the duart pins. > > If the arch/arm/mach-mx28/mx28evk_pins.c corresponds to the correct > pinmux for the wink hub board, then the > duart pins need to be as: > > MX28_PAD_I2C0_SCL__DUART_RX > MX28_PAD_I2C0_SDA__DUART_TX > > like it is done on my patch. > > Just so you know, I have no knowledge about the wink hub board. > > My comment on the duart pin was merely due to code inspection. > > > NAND read: device 0 offset 0x2b00000, size 0x600000 > > 6291456 bytes read: OK > > ## Booting kernel from Legacy Image at 42000000 ... > > Image Name: > > Created: 2023-06-23 6:36:22 UTC > > Image Type: ARM Linux Kernel Image (uncompressed) > > Data Size: 6279441 Bytes = 6 MiB > > Load Address: 40008000 > > Entry Point: 40008000 > > Verifying Checksum ... OK > > Loading Kernel Image ... OK > > > > Starting kernel ... > > > > [ 0.000000] Booting Linux on physical CPU 0x0 > > [ 0.000000] Linux version 6.4.0-rc6-00242-g1639fae5132b (rogan@vermin) > (arm-linux-gnueabi-gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU > Binutils for Debian) 2.35.2) #5 Fri Jun 23 08:35:38 SAST 2023 > > [ 0.000000] CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), > cr=0005317f > > [ 0.000000] CPU: VIVT data cache, VIVT instruction cache > > [ 0.000000] OF: fdt: Machine model: Freescale i.MX28 Evaluation Kit > > [ 0.000000] Memory policy: Data cache writeback > > [ 0.000000] Zone ranges: > > [ 0.000000] Normal [mem 0x0000000040000000-0x0000000043ffffff] > > [ 0.000000] Movable zone start for each node > > [ 0.000000] Early memory node ranges > > Here is an updated dts with the GPMI node added. > > Hopefully, with this one, the NAND flash device can be detected. > > Does this dts boot for you without hanging in the USB part? >