i.MX ProcessorsのトピックRe: Can't get to u-boot using Android prebuilt for iMX6q

Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Mon, 03 Feb 2014 22:09:22 GMT

Hi All,

i'm using the pre built Android image version:

android_jb4.2.2_1.1.0

With android_jb4.2.2_1.1.0-ga_image_6qsabresd prebuilt image and MFG tool Mfgtools-Rel-13.01.00_ER_MX6Q_UPDATER.

However after MFGTool completes to write the image, I change the SW switches and try to get anything from the debug uart. At least to get into uboot. But nothing is written on the uart, and system does not start at all.

Any suggestions?

Re: Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Mon, 03 Feb 2014 22:11:24 GMT

Just to avoid suggestions on the SW switch, I am trying both:

eMMC 4-bit (MMC3) boot

eMMC 8-bit (MMC3) boot

None works...

Re: Can't get to u-boot using Android prebuilt for iMX6q

briannorman — Mon, 03 Feb 2014 22:21:11 GMT

I had this issue and it ended up being that my DDR was not wired up correctly(hardware). U-boot initializes RAM before any console output so if it fails or hangs, you won't ever see any output. I figured this out by modifying u-boot to initialize the uarts and print something out before initializing DDR.

Re: Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Tue, 04 Feb 2014 11:55:10 GMT

Well I'm using the Freescale Kit and the SD Card pre built image works fine, so I believe the DDR is ok. Thanks for the advice.

Re: Can't get to u-boot using Android prebuilt for iMX6q

SergioSolis — Tue, 04 Feb 2014 16:29:46 GMT

You are using the SABRE SDP QUAD right?... what is the MFGTools profile you are using?

Re: Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Tue, 04 Feb 2014 19:38:15 GMT

Yes, and i'm using this profile:

Android-SabreSD-eMMC

Besides I just downloaded MFGTool version Rel-4.1.0_130816

But still nothing on u-boot :smileysad:

Re: Can't get to u-boot using Android prebuilt for iMX6q

LeonardoSandova — Tue, 04 Feb 2014 20:01:25 GMT

During the flashing phase, do you see some output from the serial port? If no, which app are you using to connect? Do you have the correct serial port settings?

Re: Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Tue, 04 Feb 2014 20:16:40 GMT

I can see this using picocom (from my VM host):

Uncompressing Linux... done, booting the kernel.

Linux version 3.0.35-2666-gbdde708 (r65388@shlinux3) (gcc version 4.6.2 20110630 (prerelease) (Freescale MAD -- Linaro 2011.07 -- Built at 2011/08/10 09:20) ) #1 SMP PREEMPT Fri Aug 16 14:34:30 CST 2013

CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d

CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: Freescale i.MX 6Quad/DualLite/Solo Sabre-SD Board

Memory policy: ECC disabled, Data cache writealloc

CPU identified as i.MX6Q, silicon rev 1.1

PERCPU: Embedded 7 pages/cpu @8c008000 s5184 r8192 d15296 u32768

Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227328

Kernel command line: console=ttymxc0,115200 rdinit=/linuxrc enable_wait_mode=off

PID hash table entries: 4096 (order: 2, 16384 bytes)

Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)

Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)

Memory: 640MB 256MB = 896MB total

Memory: 897620k/897620k available, 150956k reserved, 0K highmem

Virtual kernel memory layout:

vector : 0xffff0000 - 0xffff1000 ( 4 kB)

fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

DMA : 0xf4600000 - 0xffe00000 ( 184 MB)

vmalloc : 0xc0800000 - 0xf2000000 ( 792 MB)

lowmem : 0x80000000 - 0xc0000000 (1024 MB)

pkmap : 0x7fe00000 - 0x80000000 ( 2 MB)

modules : 0x7f000000 - 0x7fe00000 ( 14 MB)

.init : 0x80008000 - 0x8003a000 ( 200 kB)

.text : 0x8003a000 - 0x805ada70 (5583 kB)

.data : 0x805ae000 - 0x805fc880 ( 315 kB)

.bss : 0x805fc8a4 - 0x806277f4 ( 172 kB)

SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

Preemptible hierarchical RCU implementation.

NR_IRQS:624

MXC GPIO hardware

sched_clock: 32 bits at 3000kHz, resolution 333ns, wraps every 1431655ms

arm_max_freq=800MHz

MXC_Early serial console at MMIO 0x2020000 (options '115200')

bootconsole [ttymxc0] enabled

Console: colour dummy device 80x30

Calibrating delay loop... 1581.05 BogoMIPS (lpj=7905280)

pid_max: default: 32768 minimum: 301

Mount-cache hash table entries: 512

CPU: Testing write buffer coherency: ok

hw perfevents: enabled with ARMv7 Cortex-A9 PMU driver, 7 counters available

CPU1: Booted secondary processor

CPU2: Booted secondary processor

CPU3: Booted secondary processor

Brought up 4 CPUs

SMP: Total of 4 processors activated (6324.22 BogoMIPS).

print_constraints: dummy:

NET: Registered protocol family 16

print_constraints: vddpu: 725 <--> 1300 mV at 700 mV fast normal

print_constraints: vddcore: 725 <--> 1300 mV at 1100 mV fast normal

print_constraints: vddsoc: 725 <--> 1300 mV at 1200 mV fast normal

print_constraints: vdd2p5: 2000 <--> 2775 mV at 2400 mV fast normal

print_constraints: vdd1p1: 800 <--> 1400 mV at 1100 mV fast normal

print_constraints: vdd3p0: 2625 <--> 3400 mV at 3000 mV fast normal

No AHCI save PWR: PDDQ enabled

hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.

hw-breakpoint: 1 breakpoint(s) reserved for watchpoint single-step.

hw-breakpoint: maximum watchpoint size is 4 bytes.

L310 cache controller enabled

l2x0: 16 ways, CACHE_ID 0x410000c7, AUX_CTRL 0x02070000, Cache size: 1048576 B

bio: create slab <bio-0> at 0

mxs-dma mxs-dma-apbh: initialized

print_constraints: SPKVDD: 4200 mV

print_constraints: vmmc: 3300 mV

SCSI subsystem initialized

spi_imx imx6q-ecspi.0: probed

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

mc_pfuze 1-0008: ID: 0,Full lay: 1 ,Metal lay: 0

mc_pfuze 1-0008: FAB: 0 ,FIN: 0

PF100 1.0 chip found!

print_constraints: PFUZE100_SW1A: 300 <--> 1875 mV at 1300 mV

print_constraints: PFUZE100_SW1B: 300 <--> 1875 mV at 300 mV

print_constraints: PFUZE100_SW1C: 300 <--> 1875 mV at 1300 mV

print_constraints: PFUZE100_SW2: 800 <-->

It stops here... not sure why...

Will post the MFGTool logs in a bit

Re: Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Tue, 04 Feb 2014 20:17:44 GMT

Now the process is failing during partitioning... however the uboot should have been writter right?

ModuleID[2] LevelID[10]: Device Manager thread is running

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0054#7&25c389c1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_15A2&PID_0054#7&25c389c1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 0

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 0

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_0e0f&pid_0003&mi_00#8&17be0303&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 1

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_0e0f&pid_0003&mi_01#8&2f818f48&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--index: 2

ModuleID[2] LevelID[1]: DeviceClass::FindDeviceByUsbPath() - DeviceListType_New--devPath: \\?\hid#vid_15a2&pid_0054#8&116f1592&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

ModuleID[2] LevelID[10]: new MxHidDevice[017A0C08]

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, devInstPathToFind: USB\VID_15A2&PID_0054\7&25C389C1&0&2, _deviceInstanceID: USB\VID_15A2&PID_0054\7&25C389C1&0&2

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_New, Find the device, Port: 2

ModuleID[2] LevelID[10]: DeviceClass::AddUsbDevice() successful USB#VID_15A2&PID_0054#7&25C389C1&0&2#{A5DCBF10-6530-11D2-901F-00C04FB951ED} add to current list, retrycount: 0

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:2-Port:2

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT, Notify

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive

ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.

ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1

ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 0

ModuleID[2] LevelID[10]: ExecuteCommand--Boot[WndIndex:0], File is \\vmware-host\Shared Folders\freescale\android_jb4.2.2_1.1.0-ga_tool\Mfgtools-Rel-4.1.0_130816_MX6Q_UPDATER\Profiles\MX6Q Linux Update\OS Firmware\u-boot-mx6q-sabresd.bin

ModuleID[2] LevelID[10]: ExecuteCommand--Load[WndIndex:0], File is \\vmware-host\Shared Folders\freescale\android_jb4.2.2_1.1.0-ga_tool\Mfgtools-Rel-4.1.0_130816_MX6Q_UPDATER\Profiles\MX6Q Linux Update\OS Firmware\uImage, address is 0x10800000

ModuleID[2] LevelID[10]: PortMgrDlg(0)--Command Load excute successfully, retry count: 0

ModuleID[2] LevelID[10]: ExecuteCommand--Jump[WndIndex:0]

ModuleID[2] LevelID[10]: *********MxHidDevice[017A0C08] Jump to Ramkernel successfully!**********

ModuleID[2] LevelID[10]: CmdOperation[0], current state command has been finished and the last command is successful, so SetEvent(hDevCanDeleteEvent)

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0054#7&25c389c1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT(\\?\USB#VID_15A2&PID_0054#7&25c389c1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, _devices.size: 1

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, devInstPathToFind: USB\VID_15A2&PID_0054\7&25C389C1&0&2, _deviceInstanceID: USB\VID_15A2&PID_0054\7&25C389C1&0&2

ModuleID[2] LevelID[10]: DeviceClass::FindDeviceByUsbPath--DeviceListType_Current, Find the device

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT,[MxHidDeviceClass] vid_15a2&pid_0054, Hub:2-Port:2

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_REMOVAL_EVT, Notify

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Remove

ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceRemoveEvent.

ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device remove1

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent()-DEVICE_REMOVAL_EVT, hDevCanDeleteEvent has been set

ModuleID[2] LevelID[10]: delete MxHidDevice[017A0C08]

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_066F&PID_37FF#7&25c389c1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT(\\?\USB#VID_066F&PID_37FF#7&25c389c1&0&2#{a5dcbf10-6530-11d2-901f-00c04fb951ed})

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - DEVICE_ARRIVAL_EVT,[Msc,DiskDeviceClass] vid_066f&pid_37ff, not handled

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - VOLUME_ARRIVAL_EVT(E)

ModuleID[2] LevelID[10]: DeviceManager::DevChangeWnd::OnDeviceChange() - end

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT(E)

ModuleID[2] LevelID[10]: VolumeDeviceClass::AddUsbDevice() E

ModuleID[2] LevelID[1]: *** Error: 1, Drive: A:

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 1

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:1, Volume->_diskNumber:1

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 017A29C0

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 2

ModuleID[2] LevelID[10]: VolumeDeviceClass::AddUsbDevice() successful E add to current list, retrycount: 0

ModuleID[2] LevelID[10]: Device::hubIndex::getmsc, return the port index is: 2

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT-Disk(E), Hub:2-Port:2

ModuleID[2] LevelID[10]: DeviceManager::OnMsgDeviceEvent() - VOLUME_ARRIVAL_EVT, Notify

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume Arrive/Remove or Device Arrive/Remove

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, m_p_usb_port is not NULL, so only refresh

ModuleID[2] LevelID[10]: CmdOpreation[0]--OnDeviceChangeNotify, Volume/Device Arrive

ModuleID[2] LevelID[1]: CmdOpreation[0]--set m_hDeviceArriveEvent.

ModuleID[2] LevelID[10]: CmdOpreation[0]--WaitforEvents device arrive1

ModuleID[2] LevelID[10]: CmdOperation[0] device chagned and reset to state 1

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=/dev/zero of=/dev/mmcblk0 bs=512 seek=1536 count=16

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ echo 0 > /sys/block/mmcblk0boot0/force_ro

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ dd if=$FILE of=/dev/mmcblk0boot0 bs=512 seek=2 skip=2

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ echo 1 > /sys/block/mmcblk0boot0/force_ro

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ echo 8 > /sys/devices/platform/sdhci-esdhc-imx.3/mmc_host/mmc0/mmc0:0001/boot_config

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is send

ModuleID[2] LevelID[10]: ExecuteCommand--Push[WndIndex:0], Body is $ tar xf $FILE

ModuleID[2] LevelID[1]: PortMgrDlg(0)--MSCDevice--Command Push(no file) excute failed

ModuleID[2] LevelID[10]: CmdOperation[0], current command executed failed, so SetEvent(hDevCanDeleteEvent)

Re: Can't get to u-boot using Android prebuilt for iMX6q

RafaelThomasGoz — Tue, 04 Feb 2014 20:21:56 GMT

And for some reason, if I stop MFTTool after the partitioning error. Close it, open a new instance and re execute (without powering off the board) it completes successfully. Here is the log:

DLL version: 2.2.3

Tuesday, February 04, 2014 18:17:58 Start new logging

ModuleID[2] LevelID[10]: CMyExceptionHandler thread is running

ModuleID[2] LevelID[1]: new MxHidDeviceClass

ModuleID[2] LevelID[1]: *** Error: 1, Drive: A:

ModuleID[2] LevelID[10]: DeviceTypeDisk--_devices size: 1

ModuleID[2] LevelID[10]: Volume--StorageDisk, Disk->_driveNumber:1, Volume->_diskNumber:1

ModuleID[2] LevelID[10]: DeviceTypeDisk--find Disk device: 016B8FD0