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.

AM437x ID memory read

Hi,

I have one question regarding AM437x.

The below log is for AM437xEVM. This is Linux boot from SD. I would like to know where AM437x reads the data from ID memory on board.

ID Memory is CAT24C256W. But I could not find its device in the below log.

----- boot log -----
U-Boot SPL 2013.10-g78d8ebd (Jun 09 2014 - 09:45:11)
SPL: Please implement spl_start_uboot() for your board
SPL: Direct Linux boot not active!
reading u-boot.img
reading u-boot.img


U-Boot 2013.10-g78d8ebd (Jun 09 2014 - 09:45:11)

I2C:   ready
DRAM:  1 GiB
NAND:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
Net:   cpsw
Hit any key to stop autoboot:  0
4119048 bytes read in 234 ms (16.8 MiB/s)
46472 bytes read in 23 ms (1.9 MiB/s)
Kernel image @ 0x80200000 [ 0x000000 - 0x3eda08 ]
## Flattened Device Tree blob at 80f80000
   Booting using the fdt blob at 0x80f80000
   Loading Device Tree to 9fff1000, end 9ffff587 ... OK

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 3.12.10-ti2013.12.01 (jenkins@sdit-build02) (gcc version 4.7.3 20130226 (prerelease) (crosstool-NG linaro-1.13.1-4.7-2013.03-20130313 - Linaro GCC 2013.03) ) #1 Mon Jun 9 09:55:20 CDT 2014
[    0.000000] CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Generic AM43 (Flattened Device Tree), model: TI AM437x gp EVM
[    0.000000] cma: CMA: reserved 24 MiB at ae000000
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] CPU: All CPU(s) started in SVC mode.
[    0.000000] AM437x ES1.0 (sgx neon )
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 259856
[    0.000000] Kernel command line: console=ttyO0,115200n8 root=/dev/mmcblk0p2 rw rootfstype=ext4 rootwait
[    0.000000] PID hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[    0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[    0.000000] Memory: 1003104K/1045504K available (5559K kernel code, 560K rwdata, 1880K rodata, 345K init, 225K bss, 42400K reserved, 267264K highmem)
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     vmalloc : 0xf0000000 - 0xff000000   ( 240 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xef800000   ( 760 MB)
[    0.000000]     pkmap   : 0xbfe00000 - 0xc0000000   (   2 MB)
[    0.000000]     modules : 0xbf000000 - 0xbfe00000   (  14 MB)
[    0.000000]       .text : 0xc0008000 - 0xc074c04c   (7441 kB)
[    0.000000]       .init : 0xc074d000 - 0xc07a3658   ( 346 kB)
[    0.000000]       .data : 0xc07a4000 - 0xc0830058   ( 561 kB)
[    0.000000]        .bss : 0xc0830058 - 0xc0868680   ( 226 kB)
[    0.000000] NR_IRQS:16 nr_irqs:16 16
[    0.000000] GIC CPU mask not found - kernel will fail to boot.
[    0.000000] GIC CPU mask not found - kernel will fail to boot.
[    0.000000] OMAP clockevent source: timer2 at 24000000 Hz
[    0.000000] sched_clock: 32 bits at 24MHz, resolution 41ns, wraps every 178956ms
[    0.000000] OMAP clocksource: timer1 at 24000000 Hz
[    0.000000] Console: colour dummy device 80x30
[    0.000388] Calibrating delay loop... 597.60 BogoMIPS (lpj=2988032)
[    0.059544] pid_max: default: 32768 minimum: 301
[    0.059696] Security Framework initialized
[    0.059771] Mount-cache hash table entries: 512
[    0.068914] CPU: Testing write buffer coherency: ok
[    0.069378] Setting up static identity map for 0xc0573be8 - 0xc0573c58
[    0.069513] L310 cache controller enabled
[    0.069538] l2x0: 16 ways, CACHE_ID 0x410000c9, AUX_CTRL 0x7e030000, Cache size: 256 kB
[    0.070406] devtmpfs: initialized
[    0.073817] VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
[    0.138699] omap_hwmod: dss_dispc: cannot be enabled for reset (3)
[    0.141990] omap_hwmod: dss_rfbi: cannot be enabled for reset (3)
[    0.142654] pinctrl core: initialized pinctrl subsystem
[    0.143524] regulator-dummy: no parameters
[    0.145732] NET: Registered protocol family 16
[    0.148395] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.151259] cpuidle: using governor ladder
[    0.151273] cpuidle: using governor menu
[    0.164929] platform 49000000.edma: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.166334] platform 44e3e000.rtc: Cannot lookup hwmod 'rtc'
[    0.168022] OMAP GPIO hardware version 0.1
[    0.176126] omap-gpmc 50000000.gpmc: could not find pctldev for node /pinmux@44e10800/nand_flash_x8, deferring probe
[    0.176158] platform 50000000.gpmc: Driver omap-gpmc requests probe deferral
[    0.176594] platform 56000000.sgx: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.178634] platform ocp2scp.0: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.178944] platform ocp2scp.1: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.179301] platform 48380000.omap_dwc3_1: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.179705] platform 483c0000.omap_dwc3_2: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.180054] platform 4832a000.dss: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.180427] platform 4832a400.dispc: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.181030] platform 4832a800.rfbi: FIXME: clock-name 'fck' DOES NOT exist in dt!
[    0.184591] No ATAGs?
[    0.184617] hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.
[    0.184628] hw-breakpoint: maximum watchpoint size is 4 bytes.
[    0.212191] bio: create slab <bio-0> at 0
[    0.229152] edma-dma-engine edma-dma-engine.0: TI EDMA DMA engine driver
[    0.230263] vmmcsd_fixed: 3300 mV
[    0.230674] evm_v3p3: 3300 mV
[    0.234738] vgaarb: loaded
[    0.236079] SCSI subsystem initialized
[    0.237609] usbcore: registered new interface driver usbfs
[    0.237813] usbcore: registered new interface driver hub
[    0.238045] usbcore: registered new device driver usb
[    0.239170] omap_i2c 44e0b000.i2c: could not find pctldev for node /pinmux@44e10800/pinmux_i2c0_pins, deferring probe
[    0.239200] platform 44e0b000.i2c: Driver omap_i2c requests probe deferral
[    0.239232] omap_i2c 4802a000.i2c: could not find pctldev for node /pinmux@44e10800/i2c1_pins, deferring probe
[    0.239250] platform 4802a000.i2c: Driver omap_i2c requests probe deferral
[    0.239547] media: Linux media interface: v0.10
[    0.239809] Linux video capture interface: v2.00
[    0.240137] pps_core: LinuxPPS API ver. 1 registered
[    0.240149] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    0.240312] PTP clock support registered
[    0.243130] Switched to clocksource timer1
[    0.264224] NET: Registered protocol family 2
[    0.264852] TCP established hash table entries: 8192 (order: 4, 65536 bytes)
[    0.265035] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)
[    0.265142] TCP: Hash tables configured (established 8192 bind 8192)
[    0.265285] TCP: reno registered
[    0.265303] UDP hash table entries: 512 (order: 1, 8192 bytes)
[    0.265336] UDP-Lite hash table entries: 512 (order: 1, 8192 bytes)
[    0.265582] NET: Registered protocol family 1
[    0.265959] RPC: Registered named UNIX socket transport module.
[    0.265972] RPC: Registered udp transport module.
[    0.265980] RPC: Registered tcp transport module.
[    0.265987] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.266946] NetWinder Floating Point Emulator V0.97 (double precision)
[    0.267701] PM: Loading am335x-pm-firmware.binbounce pool size: 64 pages
[    0.424644] VFS: Disk quotas dquot_6.5.2
[    0.424709] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    0.425284] NFS: Registering the id_resolver key type
[    0.425404] Key type id_resolver registered
[    0.425414] Key type id_legacy registered
[    0.425464] jffs2: version 2.2. (NAND) (SUMMARY)  c 2001-2006 Red Hat, Inc.
[    0.425644] msgmni has been set to 1485
[    0.427399] NET: Registered protocol family 38
[    0.427444] io scheduler noop registered
[    0.427454] io scheduler deadline registered
[    0.427476] io scheduler cfq registered (default)
[    0.428266] omap-ocp2scp ocp2scp.0: invalid resource
[    0.428301] omap-ocp2scp: probe of ocp2scp.0 failed with error -22
[    0.428802] omap-ocp2scp ocp2scp.1: invalid resource
[    0.428829] omap-ocp2scp: probe of ocp2scp.1 failed with error -22
[    0.432139] pinctrl-single 44e10800.pinmux: 199 pins at pa f9e10800 size 796
[    0.439642] OMAP DSS rev 2.0
[    0.444195] connector-hdmi connector.6: failed to find video source
[    0.444228] platform connector.6: Driver connector-hdmi requests probe deferral
[    0.459599] Console: switching to colour frame buffer device 100x30
[    0.472313] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.475131] omap_uart 44e09000.serial: No clock speed specified: using default:48000000
[    0.475421] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 104, base_baud = 3000000) is a OMAP UART0
[    1.254559] console [ttyO0] enabled
[    1.259898] omap_rng 48310000.rng: OMAP Random Number Generator ver. 20
[    1.278129] brd: module loaded
[    1.287378] loop: module loaded
[    1.295999] mtdoops: mtd device (mtddev=name/number) must be supplied
[    1.307676] usbcore: registered new interface driver asix
[    1.313742] usbcore: registered new interface driver ax88179_178a
[    1.320466] usbcore: registered new interface driver cdc_ether
[    1.326871] usbcore: registered new interface driver r815x
[    1.332939] usbcore: registered new interface driver smsc95xx
[    1.339241] usbcore: registered new interface driver net1080
[    1.345478] usbcore: registered new interface driver cdc_subset
[    1.351985] usbcore: registered new interface driver zaurus
[    1.358150] usbcore: registered new interface driver cdc_ncm
[    1.364794] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    1.371754] ehci-pci: EHCI PCI platform driver
[    1.376760] ehci-omap: OMAP-EHCI Host Controller driver
[    1.383533] usbcore: registered new interface driver cdc_wdm
[    1.389808] usbcore: registered new interface driver usb-storage
[    1.397528] mousedev: PS/2 mouse device common for all mice
[    1.404806] input: matrix_keypad.8 as /devices/matrix_keypad.8/input/input0
[    1.415582] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as rtc0
[    1.424292] i2c /dev entries driver
[    1.429104] vpfe-capture 48326000.vpfe: v4l2 device registered
[    1.435432] vpfe-capture 48326000.vpfe: Asynchronous subdevice registration
[    1.442907] vpfe-capture 48326000.vpfe: AM437x ISIF is registered with vpfe.
[    1.451026] vpfe-capture 48328000.vpfe: v4l2 device registered
[    1.457349] vpfe-capture 48328000.vpfe: Asynchronous subdevice registration
[    1.464838] vpfe-capture 48328000.vpfe: AM437x ISIF is registered with vpfe.
[    1.472592] Driver for 1-wire Dallas network protocol.
[    1.480972] omap_wdt: OMAP Watchdog Timer Rev 0x01: initial timeout 60 sec
[    1.490650] edma-dma-engine edma-dma-engine.0: allocated channel for 0:25
[    1.498055] edma-dma-engine edma-dma-engine.0: allocated channel for 0:24
[    1.544168] ledtrig-cpu: registered to indicate activity on CPUs
[    1.554104] edma-dma-engine edma-dma-engine.0: allocated channel for 0:36
[    1.561428] omap-sham 53100000.sham: hw accel on OMAP rev 0.0
[    1.569600] omap-aes 53501000.aes: OMAP AES hw accel rev: 0.1
[    1.576911] edma-dma-engine edma-dma-engine.0: allocated channel for 0:5
[    1.586117] edma-dma-engine edma-dma-engine.0: allocated channel for 0:6
[    1.594251] omap-des 53701000.des: OMAP DES hw accel rev: 0.33
[    1.600526] edma-dma-engine edma-dma-engine.0: allocated channel for 0:33
[    1.607901] edma-dma-engine edma-dma-engine.0: allocated channel for 0:34
[    1.616501] usbcore: registered new interface driver usbhid
[    1.622446] usbhid: USB HID core driver
[    1.629652] oprofile: no performance counters
[    1.634818] oprofile: using timer interrupt.
[    1.639673] TCP: cubic registered
[    1.643253] Initializing XFRM netlink socket
[    1.647895] NET: Registered protocol family 17
[    1.652697] NET: Registered protocol family 15
[    1.657533] 8021q: 802.1Q VLAN Support v1.8
[    1.662089] Key type dns_resolver registered
[    1.667418] cpu cpu0: cpu0 regulator not ready, retry
[    1.672852] platform cpufreq-cpu0.0: Driver cpufreq-cpu0 requests probe deferral
[    1.681559] ThumbEE CPU extension supported.
[    1.688439] omap-gpmc 50000000.gpmc: GPMC revision 6.0
[    1.694015] gpmc_mem_init: disabling cs 0 mapped at 0x0-0x1000000
[    1.701682] ONFI param page 0 valid
[    1.705490] ONFI flash detected
[    1.708847] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABAEAWP), 512MiB, page size: 4096, OOB size: 224
[    1.721090] omap2-nand: detected x8 NAND flash
[    1.725835] using OMAP_ECC_BCH16_CODE_HW ECC scheme
[    1.731054] omap2-nand: using custom ecc layout
[    1.735910] mmc0: host does not support reading read-only switch. assuming write-enable.
[    1.744687] 10 ofpart partitions found on MTD device omap2-nand.0
[    1.751180] Creating 10 MTD partitions on "omap2-nand.0":
[    1.756963] 0x000000000000-0x000000040000 : "NAND.SPL"
[    1.764207] 0x000000040000-0x000000080000 : "NAND.SPL.backup1"
[    1.771993] 0x000000080000-0x0000000c0000 : "NAND.SPL.backup2"
[    1.779938] 0x0000000c0000-0x000000100000 : "NAND.SPL.backup3"
[    1.786381] mmc0: new high speed SDHC card at address e624
[    1.793170] mmcblk0: mmc0:e624 SS08G 7.40 GiB
[    1.800048] 0x000000100000-0x000000180000 : "NAND.u-boot-spl-os"
[    1.806794]  mmcblk0: p1 p2 p3
[    1.813042] 0x000000180000-0x000000280000 : "NAND.u-boot"
[    1.820566] 0x000000280000-0x0000002c0000 : "NAND.u-boot-env"
[    1.828286] 0x0000002c0000-0x000000300000 : "NAND.u-boot-env.backup1"
[    1.836739] 0x000000300000-0x000000a00000 : "NAND.kernel"
[    1.845497] 0x000000a00000-0x000010000000 : "NAND.file-system"
[    1.911032] vdd_core: 920 <--> 1140 mV at 1100 mV
[    1.919222] vdd_mpu: 920 <--> 1375 mV at 1100 mV
[    1.926120] DCDC3: at 1500 mV
[    1.933449] LDO1: 1800 mV
[    1.937496] ov2659 0-0030: ov2659_probe: debug: 0
[    1.974329] ov2659 0-0030: Sensor detection failed (3030, 0)
[    1.980417] omap_i2c 44e0b000.i2c: bus 0 rev0.12 at 100 kHz
[    1.989159] sii9022 1-003b: sil9022 HDMI Chip version = b0
[    1.996647] ov2659 1-0030: ov2659_probe: debug: 0
[    2.034317] ov2659 1-0030: Found OV2656 sensor
[    2.041746] vpfe-capture 48326000.vpfe: v4l2 sub device ov2659 registered
[    2.049567] vpfe-capture 48326000.vpfe: video device registered as video0
[    2.056852] vpfe-capture 48326000.vpfe: vpfe0 capture driver initialized
[    2.064122] vpfe-capture 48326000.vpfe: sd[0]->entity is ed386e10
[    2.070619] vpfe-capture 48326000.vpfe: video_dev->entity is ed2d0400
[    2.077504] vpfe-capture 48326000.vpfe: source_pad:0 source->num_pads:1
[    2.084567] vpfe-capture 48326000.vpfe: sink_pad:0 sink->num_pads:1
[    2.091558] ov2659 1-0030: ov2659 sensor driver registered !!
[    2.097808] omap_i2c 4802a000.i2c: bus 1 rev0.12 at 100 kHz
[    2.173174] davinci_mdio 4a101000.mdio: davinci mdio revision 1.6
[    2.179658] davinci_mdio 4a101000.mdio: detected phy mask fffffffe
[    2.186791] libphy: 4a101000.mdio: probed
[    2.191056] davinci_mdio 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver unknown
[    2.200213] Detected MACID = 34:b1:f7:30:f0:81
[    2.206537] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:00:00 UTC (946684800)
[    2.394511] EXT4-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recommended
[    2.405852] EXT4-fs (mmcblk0p2): recovery complete
[    2.412741] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    2.421716] VFS: Mounted root (ext4 filesystem) on device 179:2.
[    2.429434] devtmpfs: mounted
[    2.433280] Freeing unused kernel memory: 344K (c074d000 - c07a3000)
INIT: version 2.88 booting
Starting udev
[    3.019496] udevd[895]: starting version 182
[    3.507993] CAN device driver interface
[    3.597529] PM: CM3 Firmware Version = 0x186
[    3.642723] c_can_platform 481cc000.d_can: c_can_platform device registered (regs=fa1cc000, irq=84)
[    3.770684] c_can_platform 481d0000.d_can: can't request region for resource [mem 0x44e10644-0x44e10647]
[    3.780826] c_can_platform 481d0000.d_can: control memory is not used for raminit
[    3.970816] input: pixcir_tangoc as /devices/44000000.ocp/4802a000.i2c/i2c-1/1-005c/input/input1
[    4.090082] c_can_platform 481d0000.d_can: c_can_platform device registered (regs=fa1d0000, irq=81)
[    4.331280] davinci_evm sound.7:  tlv320aic3x-hifi <-> 4803c000.mcasp mapping ok
[    6.428422] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[    6.484237] EXT4-fs (mmcblk0p3): warning: maximal mount count reached, running e2fsck is recommended
[    6.568272] EXT4-fs (mmcblk0p3): recovery complete
[    6.584887] EXT4-fs (mmcblk0p3): mounted filesystem with ordered data mode. Opts: (null)
[    6.955386] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    6.961654] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 1
[    6.970519] xhci-hcd xhci-hcd.0.auto: irq 206, io mem 0x483d0000
[    6.977066] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[    6.984292] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    6.991958] usb usb1: Product: xHCI Host Controller
[    6.997145] usb usb1: Manufacturer: Linux 3.12.10-ti2013.12.01 xhci-hcd
[    7.004173] usb usb1: SerialNumber: xhci-hcd.0.auto
[    7.010328] hub 1-0:1.0: USB hub found
[    7.014391] hub 1-0:1.0: 1 port detected
[    7.018814] xhci-hcd xhci-hcd.0.auto: xHCI Host Controller
[    7.025054] xhci-hcd xhci-hcd.0.auto: new USB bus registered, assigned bus number 2
[    7.033379] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003
[    7.040590] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.048282] usb usb2: Product: xHCI Host Controller
[    7.053471] usb usb2: Manufacturer: Linux 3.12.10-ti2013.12.01 xhci-hcd
[    7.060490] usb usb2: SerialNumber: xhci-hcd.0.auto
[    7.066609] hub 2-0:1.0: USB hub found
[    7.070631] hub 2-0:1.0: 1 port detected
[    7.165592] cryptodev: driver 1.6 loaded.
Starting Bootlog daemon: bootlogd: cannot allocate pseudo tty: No such file or directory
bootlogd.
[    7.254514] EXT4-fs (mmcblk0p2): re-mounted. Opts: data=ordered
ALSA: Restoring mixer settings...
Configuring network interfaces... [    7.807024] net eth0: initializing cpsw version 1.15 (0)
[    7.814144] net eth0: phy found : id is : 0x221622
[    7.824983] 8021q: adding VLAN 0 to HW filter on device eth0
udhcpc (v1.20.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
done.
Mon Jun  9 20:20:00 UTC 2014
INIT: Entering runlevel: 5
Starting system message bus: dbus.
UIM SYSFS Node Not Found
Starting Dropbear SSH server: dropbear.
Starting telnet daemon.
Starting syslogd/klogd: done
Starting thttpd.
Starting PVR
Starting Lighttpd Web Server: lighttpd.
2014-06-09 20:20:01: (log.c.166) server started
/
Starting Matrix GUI application.
***************************************************************
***************************************************************
NOTICE: This file system contains the followin GPLv3 packages:
        binutils-symlinks
        binutils
        gdbserver

If you do not wish to distribute GPLv3 components please remove
the above packages prior to distribution.  This can be done using
the opkg remove command.  i.e.:
    opkg remove <package>
Where <package> is the name printed in the list above

NOTE: If the package is a dependency of another package you
      will be notified of the dependent packages.  You should
      use the --force-removal-of-dependent-packages option to
      also remove the dependent packages as well
***************************************************************
***************************************************************
Stopping Bootlog daemon: bootlogd.

 _____                    _____           _         _
|  _  |___ ___ ___ ___   |  _  |___ ___  |_|___ ___| |_
|     |  _| .'| . | . |  |   __|  _| . | | | -_|  _|  _|
|__|__|_| |__,|_  |___|  |__|  |_| |___|_| |___|___|_|
              |___|                    |___|

Arago Project http://arago-project.org am437x-evm ttyO0

Arago 2013.12 am437x-evm ttyO0

am437x-evm login:

-------------------------------------------------------

Please advise me. 

I appreciate your quick reply.

Best regards,

Michi

  • The software team have been notified. They will respond here.
  • Dear Biser-san,

    Thank you for your support.

    I have one more question.

    I tried to make SD card with latest SDK(03.01.00.06) for booting. Because the above log is strange for me. The above is SD card boot log. But, while booting, NAND access occurred. I think SD card boot does not access to NAND memory while booting.
    So I made other SD card with prebuilt image. The result was same. NAND memory access is occurred.

    So I have question. While SD card booting, why does NAND access occur? And is this situation same on other EVM (AM437x starter kit)?

    My customer made own board based on AM437x starter kit. But there is no NAND memory on their board. So I would like to know whether NAND meomory is needed or not. At present, their board can't boot up linux.

    Please advise me .

    I appreciate your quick reply.

    Best regards,
    Michi
  • Hello Michi,

    The EEPROM data is read by read_eeprom function in <SDK>/board-support/u-boot-<version>/board/ti/am43xx/board.c but there is no reflected prints to the bootlog on sucess. You can use the i2c commands to check its content from the U-Boot console.

    Michi Yama said:

    I tried to make SD card with latest SDK(03.01.00.06) for booting. Because the above log is strange for me. The above is SD card boot log. But, while booting, NAND access occurred. I think SD card boot does not access to NAND memory while booting.
    So I made other SD card with prebuilt image. The result was same. NAND memory access is occurred.

    If they have attached and properly configured NAND on their board, it will be detected and NAND memory access will occur while Linux boots up. It shouldn't depend of that if they are booting from MMC or NAND device.

    Best regards,
    Kemal

  • Dear Kemal-san, 

    Thank you for your quick reply. It is very helpful.

    I would like to reconfirm your advice.

    > It shouldn't depend of that if they are booting from MMC or NAND device.

    Do you mean that NAND device access is never happened while booting if NAND device is not on the board?

    I appreciate your quick reply again.

    Best regards,

    Michi

  • You mean these messages in the bootlog, right?

    [ 1.701682] ONFI param page 0 valid
    [ 1.705490] ONFI flash detected
    [ 1.708847] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xdc (Micron MT29F4G08ABAEAWP), 512MiB, page size: 4096, OOB size: 224
    [ 1.721090] omap2-nand: detected x8 NAND flash
    [ 1.725835] using OMAP_ECC_BCH16_CODE_HW ECC scheme
    [ 1.731054] omap2-nand: using custom ecc layout
    [ 1.735910] mmc0: host does not support reading read-only switch. assuming write-enable.
    [ 1.744687] 10 ofpart partitions found on MTD device omap2-nand.0
    [ 1.751180] Creating 10 MTD partitions on "omap2-nand.0":
    [ 1.756963] 0x000000000000-0x000000040000 : "NAND.SPL"
    [ 1.764207] 0x000000040000-0x000000080000 : "NAND.SPL.backup1"
    [ 1.771993] 0x000000080000-0x0000000c0000 : "NAND.SPL.backup2"
    [ 1.779938] 0x0000000c0000-0x000000100000 : "NAND.SPL.backup3"
    [ 1.786381] mmc0: new high speed SDHC card at address e624
    [ 1.793170] mmcblk0: mmc0:e624 SS08G 7.40 GiB
    [ 1.800048] 0x000000100000-0x000000180000 : "NAND.u-boot-spl-os"
    [ 1.806794] mmcblk0: p1 p2 p3
    [ 1.813042] 0x000000180000-0x000000280000 : "NAND.u-boot"
    [ 1.820566] 0x000000280000-0x0000002c0000 : "NAND.u-boot-env"
    [ 1.828286] 0x0000002c0000-0x000000300000 : "NAND.u-boot-env.backup1"
    [ 1.836739] 0x000000300000-0x000000a00000 : "NAND.kernel"
    [ 1.845497] 0x000000a00000-0x000010000000 : "NAND.file-system"
    [ 1.911032] vdd_core: 920 <--> 1140 mV at 1100 mV
    [ 1.919222] vdd_mpu: 920 <--> 1375 mV at 1100 mV
    [ 1.926120] DCDC3: at 1500 mV
    [ 1.933449] LDO1: 1800 mV

    Yes, these messages appear during NAND initialisation, and will not appear if there is no NAND device on the board.

  • Dear Kemal-san,

    Thank you for your quick reply. I appreciate your support.

    I have two more questions.

    1) You said the below.

    > The EEPROM data is read by read_eeprom function in <SDK>/board-support/u-boot-<version>/board/ti/am43xx/board.c but there is no reflected prints to the bootlog on sucess. You can use the i2c commands to check its content from the U-Boot console.

    I checked "read_eeprom" function in board.c. "read_eeprom" is called in three lines (#340, #498, #596). If these read_eeprom funcutions are comment out, does not the access to ID memory occur? My customer does not have ID memory on their board.

    2) Is it possible to change UART port for debug message out? I know the default is UART0. My customer would like to change it to other UART port. If possible, please let me know how to modify it.

    Best regards,

    Michi

  • Michi Yama said:

    I checked "read_eeprom" function in board.c. "read_eeprom" is called in three lines (#340, #498, #596). If these read_eeprom funcutions are comment out, does not the access to ID memory occur? My customer does not have ID memory on their board.


    Instead of removing the EEPROM checks it is better to harcode the ID memory layout as in this post.

    Michi Yama said:

    2) Is it possible to change UART port for debug message out? I know the default is UART0. My customer would like to change it to other UART port. If possible, please let me know how to modify it.

    Yes it is possible, the U-Boot UART port can be changed as per the steps in this post, to change the kernel UART port first they need to pinmux and enable the desired UART port in the dts as in this post, then set the new console=ttyOX,115200n8 in U-Boot environment variables to inform the kernel for the UART change.

  • Dear Kemal-san,

    Thank you for your quick reply. It is very helpful for me.

    I checked the E2E post you informed me. So I have two questions.

    1)From the post "UART debug console u-boot changes from default UART0 to UART5 on AM437x"(E2E-support/arm/sitara-arm/f/791/t/536830)
    The below is Brad-san's comment
    > You also need to update /etc/inittab in the file system. Usually u-boot is updated as well.

    Regarding "initab" file, should I modify this file? There is no information in this post.


    2) After I modified some source code based on E2E(e2e.ti.com/support/arm/sitara_arm/f/791/t/536830), should I modify dts file for AM437x? My customer's board is based on Starter Kit. So Should I modify the pin mux of "arch/arm/dts/am437x-sk-evm.dts" file?

    Please advise me again.

    I appreciate your quick reply.

    Best regards,

    Michi
  • Michi Yama said:

    Regarding "initab" file, should I modify this file? There is no information in this post.


    You will need to modify the S:2345:respawn:/sbin/getty 115200 ttyO0 line in /etc/inittab if you want to change the getty UART port where the login screen gets spawned.

    Michi Yama said:

    So Should I modify the pin mux of "arch/arm/dts/am437x-sk-evm.dts" file?

    It will depend on that which UART you want to change. If you want to change the kernel UART, then you will need to change the corresponding settings in dts.

  • Dear Kemal-san,

    Thank you for your quick reply.

    I can't find "intitab" in etc directory. The below is the screenshot of my etc directory.

    Which directory can I find it in? 

    Please advise me.

    Best regards,

    Michi

  • The relevant files are in systemd directory. You can enable an additional console by systemctl enable serial-getty@ttySX.service command.

  • Dear Kemal-san,

    Thank you for your continuous support.

    Sorry, I have one more question.

    I had asked you regarding NAND flash memory in previous post. And I had an answer that NAND access will not appear if there is no NAND device on the board.
    How about NOR flash? QSPI NOR flash is on Starterkit. If SD boot access does not need NOR flash, my customer
    would like to remove it.

    Please give me your advice again.

    I appreciate your quick reply.

    Best regards,
    Michi
  • The NOR flash will be detected in similar way like NAND flash. It is not mandatory to have a NOR flash while booting from SD card.