[ptxdist] PTXdist build help on TQma53 please

[ptxdist] PTXdist build help on TQma53 please

[Xizhou Wang]

[-- Attachment #1.1: Type: text/plain, Size: 2562 bytes --]

Hello

 

Plan to transfer a project from i.MX53-QSB kit and LTIB build system to
TQma53 module using the PTXdist tool.  I managed to create the image for
the SD card based on the BSP supplied with the board (the BSP is not
officially released yet). The original hd.image work fine can boot the
TQ kit. But the image I created directly boot from Linux kernel and
stop on the USB device. The Barebox is not show up on the console log.

 

I did not change the kernel and barebox setting and simple select the
platform and ptx config from the exist one and build. The toolchain is
precompiled. The attached is the log output. Any help please.

 

I just start to use PTXdist.  Try to transfer the LTIB based project to
the new TQma53 module. There could be two ways:  porting the customer
device support (LVDS touch panel, GUI, I2C communication protocol) and
apps to PTXdist again or patch the already working LTIB build with the
TQma53 board level code (u-boot, kernel 2.6.35) and build the project
for the TQ board in LTIB. Which one is more logical and easier to
achieve? Any suggestions?

 

Thanks

 

X Wang

 


Xizhou Wang 
Electronics Engineer

Direct: +44 (0) 1296 634024
Direct Fax: +44 (0)1296 634030
De Soutter Medical Limited Halton Brook Business Park, Weston Road, Aston Clinton, Aylesbury. Bucks HP22 5WF
Tel: +44 (0)1296 634000 Fax: +44 (0)1296 634033 Web: http://www.de-soutter.com/
--------------------------------------------------------------------------
This electronic message contains information from De Soutter Medical Ltd, which may be privileged or confidential and protected by copyright. The information is intended to be for the use of the individual(s) or entity named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this email is prohibited and may be unlawful. If you have received this electronic message in error, please notify us by telephone or email immediately.
De Soutter Medical does not authorise any contract to be made using email without our express permission being granted in writing. E-mail communications cannot be guaranteed to be secure or error free, as information could be intercepted corrupted, amended, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept liability for any such matters or their consequences. Anyone who communicates with us by e-mail is taken to accept the risks in doing so.
De Soutter Medical Ltd. Registered in England No. 3164365.

[-- Attachment #1.2: Type: text/html, Size: 5329 bytes --]

[-- Attachment #2: log1.txt --]
[-- Type: text/plain, Size: 4450 bytes --]

Linux version 3.0.21 (lucid@ubuntu) (gcc version 4.6.2 (OSELAS.Toolchain-2011.11.1 linaro-4.6-2011.11) ) #4 Tue Jun 26 17:06:48 BST 2012
CPU: ARMv7 Processor [412fc085] revision 5 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: TQ tqma53 Board
Memory policy: ECC disabled, Data cache writeback
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 130048
Kernel command line: console=ttymxc1,115200 otg_mode=host imx-ipu-ovl.usealpha=1 ro video=chimei-1280x800 ip=none root=/dev/mmcblk0p2 rootfstype=ext3 noinitrd rootwait
tqma53_display
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 514936k/514936k available, 9352k reserved, 0K highmem
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
    DMA     : 0xfbe00000 - 0xffe00000   (  64 MB)
    vmalloc : 0xa0800000 - 0xf4000000   (1336 MB)
    lowmem  : 0x80000000 - 0xa0000000   ( 512 MB)
    modules : 0x7f000000 - 0x80000000   (  16 MB)
      .init : 0x80008000 - 0x8002b000   ( 140 kB)
      .text : 0x8002b000 - 0x80433000   (4128 kB)
      .data : 0x80434000 - 0x80461b20   ( 183 kB)
       .bss : 0x80461b44 - 0x804b4ef0   ( 333 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:528
TrustZone Interrupt Controller (TZIC) initialized
MXC GPIO hardware
sched_clock: 32 bits at 66MHz, resolution 14ns, wraps every 64424ms
Console: colour dummy device 80x30
Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
print_constraints: dummy:
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Switching to clocksource mxc_timer1
Switched to NOHz mode on CPU #0
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
msgmni has been set to 1005
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x53fbc000 (irq = 31) is a IMX
imx-uart.1: ttymxc1 at MMIO 0x53fc0000 (irq = 32) is a IMX
console [ttymxc1] enabled
imx-uart.2: ttymxc2 at MMIO 0x5000c000 (irq = 33) is a IMX
[drm] Initialized drm 1.1.0 20060810
brd: module loaded
loop: module loaded
at24 1-0050: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
CAN device driver interface
FEC Ethernet Driver
fec_enet_mii_bus: probed
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver smsc95xx
usbcore: registered new interface driver cdc_subset
cdc_ncm: 04-Aug-2011
usbcore: registered new interface driver cdc_ncm
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
mxc-ehci mxc-ehci.0: initializing i.MX USB Controller
mxc-ehci mxc-ehci.0: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.0: new USB bus registered, assigned bus number 1
mxc-ehci mxc-ehci.0: irq 18, io mem 0x53f80000
mxc-ehci mxc-ehci.0: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
mxc-ehci mxc-ehci.1: initializing i.MX USB Controller
mxc-ehci mxc-ehci.1: Freescale On-Chip EHCI Host Controller
mxc-ehci mxc-ehci.1: new USB bus registered, assigned bus number 2
mxc-ehci mxc-ehci.1: irq 14, io mem 0x53f80200
mxc-ehci mxc-ehci.1: USB 2.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
mxc-ehci mxc-ehci.3: initializing i.MX USB Controller

[-- Attachment #3: Type: text/plain, Size: 48 bytes --]

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] PTXdist build help on TQma53 please

[Robert Schwebel]

Hi,

On Fri, Jun 29, 2012 at 10:30:35AM +0100, Xizhou Wang wrote:
> Plan to transfer a project from i.MX53-QSB kit and LTIB build system to TQma53
> module using the PTXdist tool. I managed to create the image for the SD card
> based on the BSP supplied with the board (the BSP is not officially released
> yet). The original hd.image work fine can boot the TQ kit. But the image I
> created directly boot from Linux kernel and stop on the USB device. The
> Barebox is not show up on the console log.
>
> I did not change the kernel and barebox setting and simple select the platform
> and ptx config from the exist one and build. The toolchain is precompiled. The
> attached is the log output. Any help please.
>
> I just start to use PTXdist. Try to transfer the LTIB based project to the new
> TQma53 module. There could be two ways: porting the customer device support
> (LVDS touch panel, GUI, I2C communication protocol) and apps to PTXdist again
> or patch the already working LTIB build with the TQma53 board level code
> (u-boot, kernel 2.6.35) and build the project for the TQ board in LTIB. Which
> one is more logical and easier to achieve? Any suggestions?

Porting to ptxdist is usually pretty easy, and much more powerful than
working with LTIB.

This list will help with community questions; if you need commercial
help, please drop me a note off-list.

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de