Hello,
I am working towards bringing up U-Boot (2014.07) and Linux (3.12) on a custom hardware platform based around the AM3354. Things are mostly going swimmingly other than part way through the kernel boot process the output gets garbled (presumably by the baud rate or its source clock getting changed). The latest output from the kernel is as follows:
[ 0.871885] NFS: Registering the id_resolver key type
[ 0.877273] Key type id_resolver registered
[ 0.881846] Key type id_legacy registered
[ 0.886117] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 0.893866] msgmni has been set to 483
[ 0.900972] NET: Registered protocol family 38
[ 0.905696] io scheduler noop registered
[ 0.909906] io scheduler deadline registered
[ 0.914478] io scheduler cfq registered (default)
[ 0.922542] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568
[ 0.934479] pwm-backlight backlight.5: unable to request PWM, trying legacy API
[ 0.942553] pwm-backlight backlight.5: unable to request legacy PWM
[ 0.949408] platform backlight.5: Driver pwm-backlight requests probe deferral
[ 0.995194] Console: switching to colour frame buffer device 60x34
[ 1.010594] 44e09000.serial: ttyO0 at MMIO 0x44e09000 (irq = 88, base_baud = 3000000) is a OMAP UART0
; .2F´Ö µ!?æ'4³00.æ'¯…0².z-®k¢’ *®’!{2¶’.2-Õ; .4Ã±Ö $$‘5• ½!*¤©í; .63ƒ=¬½0‘5• ½!*¤©í;
I guess this is something misconfigured in the kernel boot arguments or device tree but I am struggling to see what.
Thanks,
Andy.
