

MOUNT DDR RECOVERY DRIVER
5.3.6 - Copyright 2005-2007 Rodolfo Giometti Īdvanced Linux Sound Architecture Driver Initialized.īluetooth: HCI device and connection manager initializedīluetooth: L2CAP socket layer initialized Usbcore: registered new device driver usb Usbcore: registered new interface driver hub Usbcore: registered new interface driver usbfs MU is ready for cross core communication!Ģrial: ttymxc0 at MMIO 0x2020000 (irq = 58, base_baud = 5000000) is a IMXĢrial: ttymxc2 at MMIO 0x21ec000 (irq = 60, base_baud = 5000000) is a IMXĢrial: ttymxc4 at MMIO 0x21f4000 (irq = 62, base_baud = 5000000) is a IMX Im圆sx-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driverĢ0dc000.gpc supply pu not found, using dummy regulator Hw-breakpoint: maximum watchpoint size is 4 bytes. Hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers. Syscon 21bc000.ocotp-ctrl: regmap registered Syscon 20e4000.iomuxc-gpr: regmap registered Pinctrl core: initialized pinctrl subsystemĭMA: preallocated 256 KiB pool for atomic coherent allocations VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4 SMP: Total of 1 processors activated (6.00 BogoMIPS). Setting up static identity map for 0x8164c7e8 - 0x8164c840 Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)ĬPU0: thread -1, cpu 0, socket 0, mpidr 80000000 Mount-cache hash table entries: 2048 (order: 1, 8192 bytes) Sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655765682nsĬlocksource_of_init: no matching clocksources foundĬalibrating delay loop (skipped), value calculated using timer frequency. RCU: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=1 RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=1. Preemptible hierarchical RCU implementation. SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 Inode-cache hash table entries: 65536 (order: 6, 262144 bytes) PID hash table entries: 4096 (order: 2, 16384 bytes)ĭentry cache hash table entries: 131072 (order: 7, 524288 bytes) Kernel command line: console=ttymxc0,115200 vmalloc=400M consoleblank=0 rootwait fixrtc root=/dev/mmcblk0p2 PERCPU: Embedded 7 pages/cpu s8192 r8192 d12288 u32768īuilt 1 zonelists in Zone order, mobility grouping on. Machine model: Freescale i.MX6 SoloX Nitrogen6sx Board Linux version 3.14.38-prenav+yocto+g4af577c (gcc version 5.3.0 (GCC) ) #4 SMP PREEMPT Wed Jan 20 12:02:ĬPU: ARMv7 Processor revision 10 (ARMv7), cr=10c5387dĬPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache Using Device Tree in place at 83000000, end 8300dfff

Reserving fdt memory region: addr=83000000 size=b000 SF: Detected SST25VF016B with page size 256 Bytes, erase size 4 KiB, total 2 MiB My issue is that at some point during Linux booting, the M4 sometimes hangs, or gives garbled output before hanging.ĬPU: Freescale i.MX6SX rev1.2 996 MHz (running at 792 MHz) The M4 loads without issue and Linux also loads without any problems.

I also had to change the "6x_bootscript" that is used to load Linux from u-boot:

#define PHYS_SDRAM (MMDC0_ARB_BASE_ADDR + SZ_16M) // i.e. I followed the guide "How to Run the MQX™ RTOS on Various RAM Memories for i.MX 6SoloX":Ĭonfiguring u-boot, the kernel, and MQX was fairly straight forward and I completed every step in the process. Unfortunately, OCRAM is restricted to 128kB and so I looked at loading the M4 binary into DDR (address 0x80000000). I'm using the Boundary Devices Nitrogen 6SoloX board, which, out of the box loads the M4 into OCRAM (address 0x09000000).
