On 05/08/2014 03:10 PM, Ross Morrison wrote:
Hi all,
This is a low level Linux question.
at 0.034103 in the boot process I'm seeing this message (see below
snippet).
============
[ 0.011765] Security Framework initialized
[ 0.011843] Mount-cache hash table entries: 512
[ 0.020224] Initializing cgroup subsys cpuacct
[ 0.020252] Initializing cgroup subsys memory
[ 0.020303] Initializing cgroup subsys blkio
[ 0.020416] CPU: Testing write buffer coherency: ok
[ 0.020880] CPU0: thread -1, cpu 0, socket -1, mpidr 0
[ 0.020942] Setting up static identity map for 0x8045fa10 - 0x8045fa5c
[ 0.022251] Brought up 1 CPUs
[ 0.022271] SMP: Total of 1 processors activated (715.96 BogoMIPS).
[ 0.023216] devtmpfs: initialized
[ 0.034103] omap_hwmod: wd_timer2: _wait_target_disable failed
[ 0.088079] pinctrl core: initialized pinctrl subsystem
[ 0.088251] rstctl core: initialized rstctl subsystem
[ 0.088639] regulator-dummy: no parameters
[ 0.089062] NET: Registered protocol family 16
[ 0.089869] DMA: preallocated 256 KiB pool for atomic coherent
allocations
[ 0.097669] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800
size 568
[ 0.098469] platform 49000000.edma: alias fck already exists
[ 0.098493] platform 49000000.edma: alias fck already exists
[ 0.098513] platform 49000000.edma: alias fck already exists
============
Booting this very same uSD card on my BBB A6A this message does not
appear. On our custom hardware board,
it does appear. It is the first difference in the boot process. I'm
skipping the EEPROM ID check by hard coding the
board ID into board.c and rebuilding u-boot. I'm also setting the
dpll_mpu_opp100.m to MPUPLL_M_720 since we are using the 720MHz
version of the AM3359 processor.
Our board is identical to the BBB reference design except no ID
EEPROM, no ethernet and no EMMC.
We are booting Robert C Nelson's 3.8.13-bone49 kernel.
Thanks for any ideas..
Ross
One additional note, before I changed the dpll_mpu_opp100.m to
MPUPLL_M_1000 to dpll_mpu_opp100.m to MPUPLL_M_720 I was running the
720MHz AM3359 at 1Gig. Don't know, but possibly broke something in the
processor? Gerald, you might know the answer to that one.
Thanks,
Ross
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
