• State
  • Locked Locked
  • Replies 11 replies
  • Subscribers 99 subscribers
  • Views 483 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM335X: Kernel 6.1.y bring up on am335-evm custom board

Vidya Hegde N
Prodigy 30 points
Part Number: PROCESSOR-SDK-AM335X
Other Parts Discussed in Thread: DS90CF383

Tool/software:

I have a am335-evm custom board on which I need to bring up the kernel - peripherals and file system prompt.

I have compiled the kernel from https://git.ti.com/cgit/ti-linux-kernel/ti-linux-kernel/?h=linux-6.1.y link and also made modifications on the device tree as per the schematics.

Below are the logs when "rootwait" argument is not passed.

Requesting support on how to proceed further. Let me know if further information is required. 

[ 0.369956] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 38, base_baud = 3000000) is a OMAP UART0
[ 2.231286] printk: console [ttyO0] enabled
[ 2.237953] clk: Disabling unused clocks
[ 2.243952] /dev/root: Can't open blockdev
[ 2.248285] VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error -6
[ 2.256419] Please append a correct "root=" boot option; here are the available partitions:
[ 2.265148] 0100 16384 ram0
[ 2.265158] (driver?)
[ 2.271520] 0101 16384 ram1
[ 2.271526] (driver?)
[ 2.277901] 0102 16384 ram2
[ 2.277908] (driver?)
[ 2.284269] 0103 16384 ram3
[ 2.284276] (driver?)
[ 2.290626] 0104 16384 ram4
[ 2.290632] (driver?)
[ 2.297003] 0105 16384 ram5
[ 2.297010] (driver?)
[ 2.303364] 0106 16384 ram6
[ 2.303370] (driver?)
[ 2.309728] 0107 16384 ram7
[ 2.309734] (driver?)
[ 2.316099] 0108 16384 ram8
[ 2.316105] (driver?)
[ 2.322457] 0109 16384 ram9
[ 2.322463] (driver?)
[ 2.328820] 010a 16384 ram10
[ 2.328826] (driver?)
[ 2.335281] 010b 16384 ram11
[ 2.335287] (driver?)
[ 2.341763] 010c 16384 ram12
[ 2.341769] (driver?)
[ 2.348255] 010d 16384 ram13
[ 2.348262] (driver?)
[ 2.354746] 010e 16384 ram14
[ 2.354753] (driver?)
[ 2.361229] 010f 16384 ram15
[ 2.361235] (driver?)
[ 2.367732] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[ 2.376396] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

  • 0 in reply to Vidya Hegde N
    TI__Guru 69010 points

    The subject owner is currently out of office, please expect a response in the second half of this week.

  • 0 in reply to Vidya Hegde N
    TI__Guru**** 168721 points

    Hi Vidya,

    Which U-Boot do you use?

    Please attach the entire console boot log.

  • 0 in reply to Bin Liu
    Prodigy 30 points

    I am using u-boot-2013.10-ti2013.12.01. Note: I am working on an existing product where I have not upgraded the uboot.

    Fullscreen 0358.bootlogs.txt Download 
    
U-Boot 2013.10-00189-g78d8ebd-dirty (Aug 24 2020 - 11:09:05)

I2C:   ready
DRAM:  1 GiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Card did not respond to voltage select!
MMC init failed
Using default environment

Net:   <ethaddr> not set. Validating first E-fuse MAC
cpsw
SF: Detected MX25L12805 with page size 256 Bytes, erase size 64 KiB, total 16 MiB

fm->bootpartition :1
fm->processFlag :0
fm->tryflag :0
fm->u16CRC :99dc
 Calculated CRC: 99dc:
 Image-1 is booting....by default

Hit any key to stop autoboot:  0
custom-U-Boot#
custom-U-Boot# load mmc 0:2 0x80200000 boot/zImage_custom
5403504 bytes read in 321 ms (16.1 MiB/s)
custom-U-Boot# load mmc 0:2 0x80F80000 boot/dtb/ti/omap/am335x-custom.dtb
67152 bytes read in 49 ms (1.3 MiB/s)
custom-U-Boot# setenv bootargs 'console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 earlyprintk loglevel=7 debug'
custom-U-Boot# bootz 0x80200000 - 0x80F80000
Kernel image @ 0x80200000 [ 0x000000 - 0x527370 ]
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   Loading Device Tree to 9ffec000, end 9ffff64f ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 6.1.105-dirty (user@ubuntu) (arm-none-linux-gnueabihf-gcc (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 9.2.1 20191025, GNU ld (GNU Toolchain for the A-profile Architecture 9.2-2019.12 (arm-9.10)) 2.33.1.20191209) #31 Fri Oct 11 18:15:07 IST 2024
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] OF: fdt: Machine model: TI AM335x EVM
[    0.000000] Memory policy: Data cache writeback
[    0.000000] cma: Reserved 24 MiB at 0xbe800000
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000080000000-0x00000000afdfffff]
[    0.000000]   HighMem  [mem 0x00000000afe00000-0x00000000bfffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000080000000-0x00000000afdfffff]
[    0.000000]   node   0: [mem 0x00000000b0000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000] On node 0, zone HighMem: 512 pages in unavailable ranges
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM335X ES2.1 (sgx neon)
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 260100
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 earlyprintk loglevel=7 debug
[    0.000000] Unknown kernel command line parameters "earlyprintk", will be passed to user space.
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] Memory: 999628K/1046528K available (8192K kernel code, 488K rwdata, 2092K rodata, 1024K init, 260K bss, 22324K reserved, 24576K cma-reserved, 237568K highmem)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000] IRQ: Found an INTC at 0x(ptrval) (revision 5.0) with 128 interrupts
[    0.000000] TI gptimer clocksource: always-on /ocp/interconnect@44c00000/segment@200000/target-module@31000
[    0.000002] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 89478484971ns
[    0.000031] clocksource: dmtimer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 79635851949 ns
[    0.000465] TI gptimer clockevent: 24000000 Hz at /ocp/interconnect@48000000/segment@0/target-module@40000
[    0.001844] Console: colour dummy device 80x30
[    0.001944] Calibrating delay loop... 996.14 BogoMIPS (lpj=4980736)
[    0.090568] CPU: Testing write buffer coherency: ok
[    0.090663] CPU0: Spectre v2: using BPIALL workaround
[    0.090675] pid_max: default: 32768 minimum: 301
[    0.090776] LSM: Security Framework initializing
[    0.090937] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.090965] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[    0.092714] Setting up static identity map for 0x80100000 - 0x80100078
[    0.093775] devtmpfs: initialized
[    0.105935] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
[    0.106241] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.106275] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.108411] pinctrl core: initialized pinctrl subsystem
[    0.110276] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[    0.111955] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.113122] thermal_sys: Registered thermal governor 'step_wise'
[    0.113163] cpuidle: using governor ladder
[    0.113172] cpuidle: using governor menu
[    0.125913] platform panel: Fixed dependency cycle(s) with /ocp/interconnect@48000000/segment@300000/target-module@e000/lcdc@0
[    0.126178] No ATAGs?
[    0.126189] hw-breakpoint: debug architecture 0x4 unsupported.
[    0.133908] kprobes: kprobe jump-optimization is enabled. All kprobes are optimized if possible.
[    0.137436] reg-fixed-voltage fixedregulator0: GPIO lookup for consumer (null)
[    0.137465] reg-fixed-voltage fixedregulator0: using device tree for GPIO lookup
[    0.137490] of_get_named_gpiod_flags: can't parse 'gpios' property of node '/fixedregulator0[0]'
[    0.137527] of_get_named_gpiod_flags: can't parse 'gpio' property of node '/fixedregulator0[0]'
[    0.137547] reg-fixed-voltage fixedregulator0: using lookup tables for GPIO lookup
[    0.137557] reg-fixed-voltage fixedregulator0: No GPIO consumer (null) found
[    0.139241] SCSI subsystem initialized
[    0.139674] libata version 3.00 loaded.
[    0.139869] usbcore: registered new interface driver usbfs
[    0.139920] usbcore: registered new interface driver hub
[    0.139975] usbcore: registered new device driver usb
[    0.140196] mc: Linux media interface: v0.10
[    0.140264] videodev: Linux video capture interface: v2.00
[    0.140331] pps_core: LinuxPPS API ver. 1 registered
[    0.140337] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.140360] PTP clock support registered
[    0.142527] clocksource: Switched to clocksource dmtimer
[    0.142924] VFS: Disk quotas dquot_6.6.0
[    0.142983] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.151686] NET: Registered PF_INET protocol family
[    0.152169] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.154028] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.154076] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.154111] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[    0.154191] TCP bind hash table entries: 8192 (order: 4, 65536 bytes, linear)
[    0.154359] TCP: Hash tables configured (established 8192 bind 8192)
[    0.154564] UDP hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.154597] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes, linear)
[    0.154761] NET: Registered PF_UNIX/PF_LOCAL protocol family
[    0.155503] RPC: Registered named UNIX socket transport module.
[    0.155519] RPC: Registered udp transport module.
[    0.155525] RPC: Registered tcp transport module.
[    0.155528] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.155707] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.158130] Initialise system trusted keyrings
[    0.158757] workingset: timestamp_bits=30 max_order=18 bucket_order=0
[    0.165489] NFS: Registering the id_resolver key type
[    0.165579] Key type id_resolver registered
[    0.165586] Key type id_legacy registered
[    0.165640] jffs2: version 2.2. (NAND) (SUMMARY)  © 2001-2006 Red Hat, Inc.
[    0.166470] NET: Registered PF_ALG protocol family
[    0.166496] Key type asymmetric registered
[    0.166503] Asymmetric key parser 'x509' registered
[    0.166677] bounce: pool size: 64 pages
[    0.166769] io scheduler mq-deadline registered
[    0.166782] io scheduler kyber registered
[    0.166966] io scheduler bfq registered
[    0.170639] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.184120] brd: module loaded
[    0.190676] loop: module loaded
[    0.191499] mtdoops: mtd device (mtddev=name/number) must be supplied
[    0.191665] usbcore: registered new interface driver usblp
[    0.191735] usbcore: registered new interface driver usb-storage
[    0.191858] usbcore: registered new interface driver usbserial_generic
[    0.191894] usbserial: USB Serial support registered for generic
[    0.192330] mousedev: PS/2 mouse device common for all mice
[    0.193358] i2c_dev: i2c /dev entries driver
[    0.193478] Driver for 1-wire Dallas network protocol.
[    0.194540] sdhci: Secure Digital Host Controller Interface driver
[    0.194552] sdhci: Copyright(c) Pierre Ossman
[    0.194770] ledtrig-cpu: registered to indicate activity on CPUs
[    0.195079] usbcore: registered new interface driver usbhid
[    0.195087] usbhid: USB HID core driver
[    0.195543] Initializing XFRM netlink socket
[    0.195599] NET: Registered PF_PACKET protocol family
[    0.195619] NET: Registered PF_KEY protocol family
[    0.195686] 8021q: 802.1Q VLAN Support v1.8
[    0.195782] Key type dns_resolver registered
[    0.195978] ThumbEE CPU extension supported.
[    0.195989] omap_voltage_late_init: Voltage driver support not added
[    0.196727] Loading compiled-in X.509 certificates
[    0.227075] input: ti-tsc as /devices/platform/ocp/44c00000.interconnect/44c00000.interconnect:segment@200000/44e0d000.target-module/44e0d000.tscadc/TI-am335x-tsc.0.auto/input/input0
[    0.230473] pinctrl-single 44e10800.pinmux: 142 pins, size 568
[    0.233680] ti-sysc: probe of 44e31000.target-module failed with error -16
[    0.236408] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    0.239476] omap_rtc 44e3e000.rtc: registered as rtc0
[    0.239552] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01T00:00:00 UTC (946684800)
[    0.239588] omap_rtc 44e3e000.rtc: GPIO lookup for consumer wp
[    0.239598] omap_rtc 44e3e000.rtc: using device tree for GPIO lookup
[    0.239623] of_get_named_gpiod_flags: can't parse 'wp-gpios' property of node '/ocp/interconnect@44c00000/segment@200000/target-module@3e000/rtc@0[0]'
[    0.239658] of_get_named_gpiod_flags: can't parse 'wp-gpio' property of node '/ocp/interconnect@44c00000/segment@200000/target-module@3e000/rtc@0[0]'
[    0.239686] omap_rtc 44e3e000.rtc: using lookup tables for GPIO lookup
[    0.239696] omap_rtc 44e3e000.rtc: No GPIO consumer wp found
[    0.244185] omap_uart 48022000.serial: no wakeirq for uart1
[    0.244234] omap_uart 48022000.serial: GPIO lookup for consumer rs485-term
[    0.244242] omap_uart 48022000.serial: using device tree for GPIO lookup
[    0.244268] of_get_named_gpiod_flags: can't parse 'rs485-term-gpios' property of node '/ocp/interconnect@48000000/segment@0/target-module@22000/serial@0[0]'
[    0.244304] of_get_named_gpiod_flags: can't parse 'rs485-term-gpio' property of node '/ocp/interconnect@48000000/segment@0/target-module@22000/serial@0[0]'
[    0.244331] omap_uart 48022000.serial: using lookup tables for GPIO lookup
[    0.244338] omap_uart 48022000.serial: No GPIO consumer rs485-term found
[    0.244350] omap_uart 48022000.serial: GPIO lookup for consumer rts
[    0.244356] omap_uart 48022000.serial: using device tree for GPIO lookup
[    0.244368] of_get_named_gpiod_flags: can't parse 'rts-gpios' property of node '/ocp/interconnect@48000000/segment@0/target-module@22000/serial@0[0]'
[    0.244393] of_get_named_gpiod_flags: can't parse 'rts-gpio' property of node '/ocp/interconnect@48000000/segment@0/target-module@22000/serial@0[0]'
[    0.244414] omap_uart 48022000.serial: using lookup tables for GPIO lookup
[    0.244421] omap_uart 48022000.serial: No GPIO consumer rts found
[    0.244724] 48022000.serial: ttyO1 at MMIO 0x48022000 (irq = 21, base_baud = 3000000) is a OMAP UART1
[    0.247037] omap_uart 48024000.serial: no wakeirq for uart2
[    0.247077] omap_uart 48024000.serial: GPIO lookup for consumer rs485-term
[    0.247087] omap_uart 48024000.serial: using device tree for GPIO lookup
[    0.247108] of_get_named_gpiod_flags: can't parse 'rs485-term-gpios' property of node '/ocp/interconnect@48000000/segment@0/target-module@24000/serial@0[0]'
[    0.247139] of_get_named_gpiod_flags: can't parse 'rs485-term-gpio' property of node '/ocp/interconnect@48000000/segment@0/target-module@24000/serial@0[0]'
[    0.247164] omap_uart 48024000.serial: using lookup tables for GPIO lookup
[    0.247172] omap_uart 48024000.serial: No GPIO consumer rs485-term found
[    0.247181] omap_uart 48024000.serial: GPIO lookup for consumer rts
[    0.247188] omap_uart 48024000.serial: using device tree for GPIO lookup
[    0.247201] of_get_named_gpiod_flags: can't parse 'rts-gpios' property of node '/ocp/interconnect@48000000/segment@0/target-module@24000/serial@0[0]'
[    0.247224] of_get_named_gpiod_flags: can't parse 'rts-gpio' property of node '/ocp/interconnect@48000000/segment@0/target-module@24000/serial@0[0]'
[    0.247245] omap_uart 48024000.serial: using lookup tables for GPIO lookup
[    0.247251] omap_uart 48024000.serial: No GPIO consumer rts found
[    0.247522] 48024000.serial: ttyO2 at MMIO 0x48024000 (irq = 22, base_baud = 3000000) is a OMAP UART2
[    0.250834] i2c i2c-1: GPIO lookup for consumer scl
[    0.250863] i2c i2c-1: using device tree for GPIO lookup
[    0.250889] of_get_named_gpiod_flags: can't parse 'scl-gpios' property of node '/ocp/interconnect@48000000/segment@0/target-module@2a000/i2c@0[0]'
[    0.250918] of_get_named_gpiod_flags: can't parse 'scl-gpio' property of node '/ocp/interconnect@48000000/segment@0/target-module@2a000/i2c@0[0]'
[    0.250945] i2c i2c-1: using lookup tables for GPIO lookup
[    0.250954] i2c i2c-1: No GPIO consumer scl found
[    0.250975] i2c i2c-1: GPIO lookup for consumer sda
[    0.250981] i2c i2c-1: using device tree for GPIO lookup
[    0.250992] of_get_named_gpiod_flags: can't parse 'sda-gpios' property of node '/ocp/interconnect@48000000/segment@0/target-module@2a000/i2c@0[0]'
[    0.251016] of_get_named_gpiod_flags: can't parse 'sda-gpio' property of node '/ocp/interconnect@48000000/segment@0/target-module@2a000/i2c@0[0]'
[    0.251035] i2c i2c-1: using lookup tables for GPIO lookup
[    0.251041] i2c i2c-1: No GPIO consumer sda found
[    0.272920] tps65910 1-002d: No interrupt support, no core IRQ
[    0.294820] omap_i2c 4802a000.i2c: bus 1 rev0.11 at 400 kHz
[    0.297922] ti-sysc: probe of 48040000.target-module failed with error -16
[    0.306712] gpio gpiochip0: (gpio-0-31): created GPIO range 0->7 ==> 44e10800.pinmux PIN 0->7
[    0.306752] gpio gpiochip0: (gpio-0-31): created GPIO range 8->11 ==> 44e10800.pinmux PIN 90->93
[    0.306766] gpio gpiochip0: (gpio-0-31): created GPIO range 12->27 ==> 44e10800.pinmux PIN 12->27
[    0.306778] gpio gpiochip0: (gpio-0-31): created GPIO range 28->31 ==> 44e10800.pinmux PIN 30->33
[    0.306834] gpio gpiochip0: (gpio-0-31): not an immutable chip, please consider fixing it!
[    0.307249] gpio gpiochip0: (gpio-0-31): added GPIO chardev (254:0)
[    0.307371] gpio gpiochip0: registered GPIOs 0 to 31 on gpio-0-31
[    0.307438] OMAP GPIO hardware version 0.1
[    0.308336] ti-sysc 480602fc.target-module: really a child ti,hwmods property?
[    0.308659] platform 48060000.mmc: Cannot lookup hwmod 'mmc1'
[    0.311992] omap-mailbox 480c8000.mailbox: omap mailbox rev 0x400
[    0.318448] gpio gpiochip1: (gpio-32-63): created GPIO range 0->17 ==> 44e10800.pinmux PIN 34->51
[    0.318482] gpio gpiochip1: (gpio-32-63): created GPIO range 18->21 ==> 44e10800.pinmux PIN 77->80
[    0.318496] gpio gpiochip1: (gpio-32-63): created GPIO range 22->31 ==> 44e10800.pinmux PIN 56->65
[    0.318553] gpio gpiochip1: (gpio-32-63): not an immutable chip, please consider fixing it!
[    0.318932] gpio gpiochip1: (gpio-32-63): added GPIO chardev (254:1)
[    0.319035] gpio gpiochip1: registered GPIOs 32 to 63 on gpio-32-63
[    0.320832] gpio gpiochip2: (gpio-64-95): created GPIO range 0->4 ==> 44e10800.pinmux PIN 66->70
[    0.320858] gpio gpiochip2: (gpio-64-95): created GPIO range 5->6 ==> 44e10800.pinmux PIN 98->99
[    0.320871] gpio gpiochip2: (gpio-64-95): created GPIO range 7->8 ==> 44e10800.pinmux PIN 75->76
[    0.320883] gpio gpiochip2: (gpio-64-95): created GPIO range 13->13 ==> 44e10800.pinmux PIN 141->141
[    0.320896] gpio gpiochip2: (gpio-64-95): created GPIO range 14->21 ==> 44e10800.pinmux PIN 100->107
[    0.320947] gpio gpiochip2: (gpio-64-95): not an immutable chip, please consider fixing it!
[    0.321248] gpio gpiochip2: (gpio-64-95): added GPIO chardev (254:2)
[    0.321346] gpio gpiochip2: registered GPIOs 64 to 95 on gpio-64-95
[    0.330377] platform panel: Fixed dependency cycle(s) with /ocp/interconnect@48000000/segment@300000/target-module@e000/lcdc@0
[    0.330511] platform 4830e000.lcdc: Fixed dependency cycle(s) with /panel
[    0.332684] omap_rng 48310000.rng: Random Number Generator ver. 20
[    0.337054] random: crng init done
[    0.343608] debugfs: Directory '49000000.dma' with parent 'dmaengine' already present!
[    0.343648] edma 49000000.dma: TI EDMA DMA engine driver
[    0.361657] hw perfevents: enabled with armv7_cortex_a8 PMU driver, 5 counters available
[    0.366835] l3-aon-clkctrl:0000:0: failed to disable
[    0.367408] pwm-backlight backlight: GPIO lookup for consumer enable
[    0.367426] pwm-backlight backlight: using device tree for GPIO lookup
[    0.367448] of_get_named_gpiod_flags: can't parse 'enable-gpios' property of node '/backlight[0]'
[    0.367472] of_get_named_gpiod_flags: can't parse 'enable-gpio' property of node '/backlight[0]'
[    0.367492] pwm-backlight backlight: using lookup tables for GPIO lookup
[    0.367501] pwm-backlight backlight: No GPIO consumer enable found
[    0.367552] pwm-backlight backlight: supply power not found, using dummy regulator
[    0.368243] gpio gpiochip3: (gpio-96-127): created GPIO range 0->7 ==> 44e10800.pinmux PIN 82->89
[    0.368266] gpio gpiochip3: (gpio-96-127): created GPIO range 8->11 ==> 44e10800.pinmux PIN 52->55
[    0.368280] gpio gpiochip3: (gpio-96-127): created GPIO range 12->15 ==> 44e10800.pinmux PIN 94->97
[    0.368292] gpio gpiochip3: (gpio-96-127): created GPIO range 16->17 ==> 44e10800.pinmux PIN 71->72
[    0.368304] gpio gpiochip3: (gpio-96-127): created GPIO range 18->18 ==> 44e10800.pinmux PIN 135->135
[    0.368318] gpio gpiochip3: (gpio-96-127): created GPIO range 19->20 ==> 44e10800.pinmux PIN 108->109
[    0.368330] gpio gpiochip3: (gpio-96-127): created GPIO range 21->21 ==> 44e10800.pinmux PIN 73->73
[    0.368342] gpio gpiochip3: (gpio-96-127): created GPIO range 22->23 ==> 44e10800.pinmux PIN 8->9
[    0.368356] gpio gpiochip3: (gpio-96-127): created GPIO range 26->27 ==> 44e10800.pinmux PIN 10->11
[    0.368368] gpio gpiochip3: (gpio-96-127): created GPIO range 28->28 ==> 44e10800.pinmux PIN 74->74
[    0.368381] gpio gpiochip3: (gpio-96-127): created GPIO range 29->29 ==> 44e10800.pinmux PIN 81->81
[    0.368394] gpio gpiochip3: (gpio-96-127): created GPIO range 30->31 ==> 44e10800.pinmux PIN 28->29
[    0.368450] gpio gpiochip3: (gpio-96-127): not an immutable chip, please consider fixing it!
[    0.368766] gpio gpiochip3: (gpio-96-127): added GPIO chardev (254:3)
[    0.368870] gpio gpiochip3: registered GPIOs 96 to 127 on gpio-96-127
[    0.369535] omap_uart 44e09000.serial: no wakeirq for uart0
[    0.369566] omap_uart 44e09000.serial: GPIO lookup for consumer rs485-term
[    0.369574] omap_uart 44e09000.serial: using device tree for GPIO lookup
[    0.369592] of_get_named_gpiod_flags: can't parse 'rs485-term-gpios' property of node '/ocp/interconnect@44c00000/segment@200000/target-module@9000/serial@0[0]'
[    0.369621] of_get_named_gpiod_flags: can't parse 'rs485-term-gpio' property of node '/ocp/interconnect@44c00000/segment@200000/target-module@9000/serial@0[0]'
[    0.369645] omap_uart 44e09000.serial: using lookup tables for GPIO lookup
[    0.369653] omap_uart 44e09000.serial: No GPIO consumer rs485-term found
[    0.369663] omap_uart 44e09000.serial: GPIO lookup for consumer rts
[    0.369671] omap_uart 44e09000.serial: using device tree for GPIO lookup
[    0.369682] of_get_named_gpiod_flags: can't parse 'rts-gpios' property of node '/ocp/interconnect@44c00000/segment@200000/target-module@9000/serial@0[0]'
[    0.369705] of_get_named_gpiod_flags: can't parse 'rts-gpio' property of node '/ocp/interconnect@44c00000/segment@200000/target-module@9000/serial@0[0]'
[    0.369725] omap_uart 44e09000.serial: using lookup tables for GPIO lookup
[    0.369732] omap_uart 44e09000.serial: No GPIO consumer rts found
[    0.369956] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 38, base_baud = 3000000) is a OMAP UART0
[    2.231286] printk: console [ttyO0] enabled
[    2.237953] clk: Disabling unused clocks
[    2.243952] /dev/root: Can't open blockdev
[    2.248285] VFS: Cannot open root device "mmcblk0p2" or unknown-block(0,0): error -6
[    2.256419] Please append a correct "root=" boot option; here are the available partitions:
[    2.265148] 0100           16384 ram0
[    2.265158]  (driver?)
[    2.271520] 0101           16384 ram1
[    2.271526]  (driver?)
[    2.277901] 0102           16384 ram2
[    2.277908]  (driver?)
[    2.284269] 0103           16384 ram3
[    2.284276]  (driver?)
[    2.290626] 0104           16384 ram4
[    2.290632]  (driver?)
[    2.297003] 0105           16384 ram5
[    2.297010]  (driver?)
[    2.303364] 0106           16384 ram6
[    2.303370]  (driver?)
[    2.309728] 0107           16384 ram7
[    2.309734]  (driver?)
[    2.316099] 0108           16384 ram8
[    2.316105]  (driver?)
[    2.322457] 0109           16384 ram9
[    2.322463]  (driver?)
[    2.328820] 010a           16384 ram10
[    2.328826]  (driver?)
[    2.335281] 010b           16384 ram11
[    2.335287]  (driver?)
[    2.341763] 010c           16384 ram12
[    2.341769]  (driver?)
[    2.348255] 010d           16384 ram13
[    2.348262]  (driver?)
[    2.354746] 010e           16384 ram14
[    2.354753]  (driver?)
[    2.361229] 010f           16384 ram15
[    2.361235]  (driver?)
[    2.367732] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[    2.376396] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

  • 0 in reply to Vidya Hegde N
    TI__Guru**** 168721 points

    Hi Vidya,

    The boot log doesn't show the MMC interface is enabled, so Linux fails to mount /dev/mmcblk0p2 for the rootfs.

    I also see the following message in the kernel log:

    [    0.308336] ti-sysc 480602fc.target-module: really a child ti,hwmods property?                   
    [    0.308659] platform 48060000.mmc: Cannot lookup hwmod 'mmc1'

    which I have never seen it before, not sure what happened, but I guess this causes the MMC interface failed.

  • 0 in reply to Bin Liu
    Prodigy 30 points

    Thank you. I enabled the MMC. However, I have another question if PMIC and DS90CF383 based LCD support is available in kernel 6.1.

  • 0 in reply to Vidya Hegde N
    TI__Guru**** 168721 points

    Not sure if I understand your message. Do you mean the Linux can boot into Linux login prompt now after enabled MMC?

  • 0 in reply to Bin Liu
    Prodigy 30 points

    I am enable to get the Linux login prompt now with few more changes on the configuration and DTS. However, the display is not up. Please let me know if PMIC and DS90CF383 based LCD support is available in kernel 6.1.

  • 0 in reply to Vidya Hegde N
    TI__Guru**** 168721 points
    Vidya Hegde N said:
    I am enable to get the Linux login prompt now with few more changes on the configuration and DTS.

    Can you please provide the patch of the DTS change which makes the Linux boot working? It seems your company has a different project but with a similar boot MMC enabling issue. Please see the details in the following e2e thread.

    https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1425320/am3358-not-able-to-boot-linux-kernel-5-10-on-custom-am335x-board

    Vidya Hegde N said:
    Please let me know if PMIC and DS90CF383 based LCD support is available in kernel 6.1.

    What PMIC part number do you use?

    Please create a separate e2e thread for your LCD question, it will go to a our LCD support expert.

  • 0 in reply to Bin Liu
    Prodigy 30 points

    Sure. PMIC part number is TPS65910A31A1RSLR. Separate thread created -> e2e.ti.com/.../am3358-pmic-tps65910a31a1rslr-and-ds90cf383-based-lcd-support-in-kernel-6-1

  • 0 in reply to Vidya Hegde N
    TI__Guru**** 168721 points

    Can you please provide the patch of the DTS change which makes the Linux boot working? It seems your company has a different project but with a similar boot MMC enabling issue.