a problem about mfgtool in imx6q (32bit 1GB DDR)

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

a problem about mfgtool in imx6q (32bit 1GB DDR)

Jump to solution
5,841 Views
wangzhigang
Contributor III

hi,everyone

     I have a problem about mfgtool,our evn is :

     linux 3.10.53 ,imx6q sabresd mfgtool is imx-3.10.53_1.1.0_ga-mfg-tools

(1)  we use 2GB DDR (64bit) for our system,and mfgtool can success to run.

(2)  we take down 2 DDR chip (for 32 bit 1GB DDR),and we change the DDR parameter,and ddr stress test is OK,but we fail to run mfgtool,the mfgtool stop run after starting UTP,the log is as follow:

wm8962-supply: disabling

regulator-dummy: disabling

imx mcc test is registered.

g_mass_storage gadget: Mass Storage Function, version: 2009/09/11

g_mass_storage gadget: Number of LUNs=1

lun0: LUN: removable file: (no medium)

g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11

g_mass_storage gadget: g_mass_storage ready

input: gpio-keys.26 as /devices/soc0/gpio-keys.26/input/input1

snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:06:17 UTC (377)

ALSA device list:

  #0: imx-hdmi-soc

Freeing unused kernel memory: 324K (80bf6000 - 80c47000)

Starting UTP

uuc 0.5 [built Jan  5 2015 14:47:13]

UTP: Waiting for device to appear

UTP: file/device node /dev/utp already exists

cpu_id is 0

(stop here)

(3)  we use the same uboot,kernel,dtb,fs (for mfgtool) in 2GB DDR,and the mfgtool is OK,so I think the filesystem for mfgtool (fsl-image-mfgtool-initramfs-imx6qdlsolo.cpio.gz.u-boot) must match 2GB DDR.

how can I use the mfgtool in 32bit 1GB DDR (in imx6q sabresd)?

or how can I compile the yocto for 32bit 1GB ddr for mfgtool?

can you give me a filesystem for mfgtool in 32 bit DDR (in imx6q sabresd)?

Is everyone can help me?

Best wishes!

0 Kudos
Reply
1 Solution
3,139 Views
wangzhigang
Contributor III

hi,igor

     I have solve the problem, It is a hardware problem,the pin of id in otg was pull down  by a resistance.so that the otg cannot be a slave device.and th UTP cannot receive the windows's command.

     thanks for your help!

   Best regards

View solution in original post

0 Kudos
Reply
9 Replies
3,139 Views
igorpadykov
NXP Employee
NXP Employee

Hi wang

you are right: for using mfgtool with 32bit 1GB DDR it is necessary to rebuild

mfgtools with modified uboot/.. mx6q_xxx.cfg file. For rebuilding

please refer to attached Yocto Guide sect.6.2 The Manufacturing Tool, MFGTool.

Regarding 32-bit ddr configuration one can also look at sect.5 Enabling Solo Emulation

attached i.MX_Linux_User's_Guide.pdf.

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply
3,138 Views
wangzhigang
Contributor III

hi igorpadykov,

thanks for your replay.

(1) you are right: for using mfgtool with 32bit 1GB DDR it is necessary to rebuild

mfgtools with modified uboot/.. mx6q_xxx.cfg file. For rebuilding

please refer to attached Yocto Guide sect.6.2 The Manufacturing Tool, MFGTool.

     According to your suggestion,I modify the source code in "fsl-arm-yocto-bsp/build-mfg/tmp/work/imx6qsabresd-poky-linux-gnueabi/u-boot-imx-mfgtool/2014.04-r0/git/board/freescale/imx/ddr/mx6q_4x_mt41j128.cfg" for 32bit ddr,  and then compile the mfgtools :

  bitbake -c compile -f fsl-image-mfgtool-initramfs

  bitbake fsl-image-mfgtool-initramfs

  compile the uboot (mx6qsabresd):

  bitbake -c compile -f u-boot-mfgtool

  bitbake u-boot-mfgtool

but I still can not run mfgtool successfully.always stop at:

UTP: Waiting for device to appear

UTP: file/device node /dev/utp already exists

cpu_id is 0

(2)Regarding 32-bit ddr configuration one can also look at sect.5 Enabling Solo Emulation

attached i.MX_Linux_User's_Guide.pdf.

   compile the uboot for 32bit ddr: (mx6solosabreauto)

MACHINE=imx6solosabreauto bitbake u-boot-imx-mfgtool

and then  I found this ubootXX.imx can not be load,I get nothing in console.

Could you tell me in detail ?

Best wishes!

0 Kudos
Reply
3,139 Views
igorpadykov
NXP Employee
NXP Employee

Hi wang

had you changed uboot/..configs/board_file.h parameters

for custom board, like:

define PHYS_SDRAM_SIZE

~igor

0 Kudos
Reply
3,139 Views
wangzhigang
Contributor III

hi,igorpadykov

(1) this is my log:

---------------------------

U-Boot 2014.04 (Aug 12 2015 - 14:13:01)

CPU:   Freescale i.MX6Q rev1.2 at 792 MHz

CPU:   Temperature 27 C, calibration data: 0x5814ee69

Reset cause: POR

Board: MX6-SabreSD

I2C:   ready

DRAM:  1 GiB

MMC:   FSL_SDHC: 0, FSL_SDHC: 1, FSL_SDHC: 2

MMC: no card present

MMC init failed

Using default environment

No panel detected: default to Hannstar-XGA

Display: Hannstar-XGA (1024x768)

In:    serial

Out:   serial

Err:   serial

Found PFUZE100 deviceid=10,revid=11

MMC: no card present

mmc1(part 0) is current device

Net:   Phy not found

PHY reset timed out

FEC [PRIME]

Warning: failed to set MAC address

Boot from USB for mfgtools

Use default environment for mfgtools

Run bootcmd_mfg: run mfgtool_args;bootz ${loadaddr} ${initrd_addr} ${fdt_addr};

Hit any key to stop autoboot:  0

Kernel image @ 0x12000000 [ 0x000000 - 0x5105d0 ]

## Loading init Ramdisk from Legacy Image at 12c00000 ...

   Image Name:   fsl-image-mfgtool-initramfs-imx6

   Image Type:   ARM Linux RAMDisk Image (gzip compressed)

   Data Size:    7304221 Bytes = 7 MiB

   Load Address: 00000000

   Entry Point:  00000000

   Verifying Checksum ... OK

## Flattened Device Tree blob at 18000000

   Booting using the fdt blob at 0x18000000

   Using Device Tree in place at 18000000, end 1800f69c

switch to ldo_bypass mode!

Starting kernel ...

Booting Linux on physical CPU 0x0

Linux version 3.10.53 (wangzg@localhost.localdomain) (gcc version 4.6.3 (crosstool-NG linaro-1.13.1-2012.03-20120326 - Linaro GCC 2012.03) ) #3 SMP Thu Jul 30 19:02:35 CST 2015

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

CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache

Machine: Freescale i.MX6 Quad/DualLite (Device Tree), model: Freescale i.MX6 Quad SABRE Smart Device Board

cma: CMA: reserved 320 MiB at 3c000000

Memory policy: ECC disabled, Data cache writealloc

PERCPU: Embedded 8 pages/cpu @81513000 s8768 r8192 d15808 u32768

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

Kernel command line: console=ttymxc0,115200 rdinit=/linuxrc g_mass_storage.stall=0 g_mass_storage.removable=1 g_mass_storage.idVendor=0x066F g_mass_storage.idProduct=0x37FF g_mass_storage.iSerialNumber= 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: 1024MB = 1024MB total

Memory: 690552k/690552k available, 358024k reserved, 0K highmem

Virtual kernel memory layout:

    vector  : 0xffff0000 - 0xffff1000   (   4 kB)

    fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)

    vmalloc : 0xc0800000 - 0xff000000   (1000 MB)

    lowmem  : 0x80000000 - 0xc0000000   (1024 MB)

    modules : 0x7f000000 - 0x80000000   (  16 MB)

      .text : 0x80008000 - 0x80bf5554   (12214 kB)

      .init : 0x80bf6000 - 0x80c47240   ( 325 kB)

      .data : 0x80c48000 - 0x80c98940   ( 323 kB)

       .bss : 0x80c98940 - 0x80cfaf5c   ( 394 kB)

SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1

Hierarchical RCU implementation.

NR_IRQS:16 nr_irqs:16 16

L310 cache controller enabled

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

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

CPU identified as i.MX6Q, silicon rev 1.2

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

CPU0: thread -1, cpu 0, socket 0, mpidr 80000000

Setting up static identity map for 0x80623fb0 - 0x80624008

CPU1: Booted secondary processor

CPU1: thread -1, cpu 1, socket 0, mpidr 80000001

CPU2: Booted secondary processor

CPU2: thread -1, cpu 2, socket 0, mpidr 80000002

CPU3: Booted secondary processor

CPU3: thread -1, cpu 3, socket 0, mpidr 80000003

Brought up 4 CPUs

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

CPU: All CPU(s) started in SVC mode.

devtmpfs: initialized

pinctrl core: initialized pinctrl subsystem

regulator-dummy: no parameters

NET: Registered protocol family 16

DMA: preallocated 256 KiB pool for atomic coherent allocations

Use WDOG2 as reset source

syscon 20c8000.anatop: regmap [mem 0x020c8000-0x020c8fff] registered

vdd1p1: 800 <--> 1375 mV at 1100 mV

vdd3p0: 2800 <--> 3150 mV at 3000 mV

vdd2p5: 2000 <--> 2750 mV at 2400 mV

cpu: 725 <--> 1450 mV

vddpu: 725 <--> 1450 mV

vddsoc: 725 <--> 1450 mV

syscon 20e0000.iomuxc-gpr: regmap [mem 0x020e0000-0x020e0037] registered

syscon 21bc000.ocotp-ctrl: regmap [mem 0x021bc000-0x021bffff] registered

hw-breakpoint: found 5 (+1 reserved) breakpoint and 1 watchpoint registers.

hw-breakpoint: maximum watchpoint size is 4 bytes.

imx6q-pinctrl 20e0000.iomuxc: initialized IMX pinctrl driver

bio: create slab <bio-0> at 0

mxs-dma 110000.dma-apbh: initialized

usb_otg_vbus: 5000 mV

usb_h1_vbus: 5000 mV

wm8962-supply: no parameters

mipi_dsi_pwr_on: no parameters

sensor-supply: 3300 mV

i2c-core: driver [max17135] using legacy suspend method

i2c-core: driver [max17135] using legacy resume method

SCSI subsystem initialized

usbcore: registered new interface driver usbfs

usbcore: registered new interface driver hub

usbcore: registered new device driver usb

i2c i2c-0: IMX I2C adapter registered

i2c i2c-1: IMX I2C adapter registered

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_GPIO_3 already requested by 20e0000.iomuxc; cannot claim for 21a8000.i2c

imx6q-pinctrl 20e0000.iomuxc: pin-139 (21a8000.i2c) status -22

imx6q-pinctrl 20e0000.iomuxc: could not request pin 139 on device 20e0000.iomuxc

imx-i2c 21a8000.i2c: Error applying setting, reverse things back

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_GPIO_3 already requested by 20e0000.iomuxc; cannot claim for 21a8000.i2c

imx6q-pinctrl 20e0000.iomuxc: pin-139 (21a8000.i2c) status -22

imx6q-pinctrl 20e0000.iomuxc: could not request pin 139 on device 20e0000.iomuxc

imx-i2c 21a8000.i2c: Error applying setting, reverse things back

imx-i2c 21a8000.i2c: can't get/select pinctrl

imx-i2c: probe of 21a8000.i2c failed with error -22

Linux video capture interface: v2.00

pps_core: LinuxPPS API ver. 1 registered

pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>

PTP clock support registered

imx-ipuv3 2400000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

imx-ipuv3 2800000.ipu: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)

mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 driver probed

mxc_mipi_csi2 21dc000.mipi_csi: i.MX MIPI CSI2 dphy version is 0x3130302a

MIPI CSI2 driver module loaded

Advanced Linux Sound Architecture Driver Initialized.

cfg80211: Calling CRDA to update world regulatory domain

pureg-dummy: no parameters

Switching to clocksource mxc_timer1

NET: Registered protocol family 2

TCP established hash table entries: 8192 (order: 4, 65536 bytes)

TCP bind hash table entries: 8192 (order: 4, 65536 bytes)

TCP: Hash tables configured (established 8192 bind 8192)

TCP: reno registered

UDP hash table entries: 512 (order: 2, 16384 bytes)

UDP-Lite hash table entries: 512 (order: 2, 16384 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.

Trying to unpack rootfs image as initramfs...

Freeing initrd memory: 7128K (82c01000 - 832f7000)

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

imx6_busfreq busfreq.16: DDR medium rate not supported.

Bus freq driver module loaded

futex hash table entries: 1024 (order: 4, 65536 bytes)

VFS: Disk quotas dquot_6.5.2

Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)

NFS: Registering the id_resolver key type

Key type id_resolver registered

Key type id_legacy registered

jffs2: version 2.2. (NAND) 漏 2001-2006 Red Hat, Inc.

fuse init (API version 7.22)

msgmni has been set to 2002

io scheduler noop registered

io scheduler deadline registered

io scheduler cfq registered (default)

imx-weim 21b8000.weim: WEIM driver registered.

ldb ldb.14: dual mode

ldb ldb.14: split mode or dual mode, ignoring second output

mxc_mipi_dsi 21e0000.mipi: i.MX MIPI DSI driver probed

MIPI DSI driver module loaded

mxc_sdc_fb fb.29: registered mxc display driver ldb

imx-ipuv3 2800000.ipu: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)

Console: switching to colour frame buffer device 128x48

mxc_hdmi 20e0000.hdmi_video: Detected HDMI controller 0x13:0xa:0xa0:0xc1

fbcvt: 1920x1080@60: CVT Name - 2.073M9

mxc_sdc_fb fb.30: registered mxc display driver hdmi

mxc_sdc_fb fb.31: registered mxc display driver lcd

mxc_sdc_fb fb.31: ipu0-di0 already in use

mxc_sdc_fb: probe of fb.31 failed with error -16

ldb ldb.14: LVDS channel1 is not online

mxc_sdc_fb fb.32: NO mxc display driver found!

imx-sdma 20ec000.sdma: no iram assigned, using external mem

imx-sdma 20ec000.sdma: loaded firmware 1.1

imx-sdma 20ec000.sdma: initialized

pfuze100-regulator 1-0008: Full lay: 1, Metal lay: 1

pfuze100-regulator 1-0008: FAB: 0, FIN: 0

pfuze100-regulator 1-0008: pfuze100 found.

SW1AB: 300 <--> 1875 mV at 1150 mV

SW1C: 300 <--> 1875 mV at 1175 mV

SW2: 800 <--> 3300 mV at 3300 mV

SW3A: 400 <--> 1975 mV at 1500 mV

SW3B: 400 <--> 1975 mV at 1500 mV

SW4: 800 <--> 3300 mV at 3150 mV

SWBST: 5000 <--> 5150 mV at 5000 mV

VSNVS: 1000 <--> 3000 mV at 3000 mV

VREFDDR: 750 mV

VGEN1: 800 <--> 1550 mV at 1500 mV

VGEN2: 800 <--> 1550 mV at 1500 mV

VGEN3: 1800 <--> 3300 mV at 2800 mV

VGEN4: 1800 <--> 3300 mV at 1800 mV

VGEN5: 1800 <--> 3300 mV at 3000 mV

VGEN6: 1800 <--> 3300 mV at 3300 mV

Serial: IMX driver

2020000.serial: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX

console [ttymxc0] enabled

21ec000.serial: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX

21f4000.serial: ttymxc4 at MMIO 0x21f4000 (irq = 62) is a IMX

serial: Freescale lpuart driver

imx sema4 driver is registered.

[drm] Initialized drm 1.1.0 20060810

[drm] Initialized vivante 1.0.0 20120216 on minor 0

brd: module loaded

loop: module loaded

imx6q-pinctrl 20e0000.iomuxc: pin MX6Q_PAD_KEY_COL1 already requested by 21f4000.serial; cannot claim for 2008000.ecspi

imx6q-pinctrl 20e0000.iomuxc: pin-128 (2008000.ecspi) status -22

imn6d mr25h256, expected m25p32

K25p80 spi32766.0: mr25h256 (32

usbcore: registered new interface driver usb-storage

ci_hdrc ci_hdrc.0: EHCI Host Controller

ci_hdrc ci_hdrc.0: new USB bus registered, assigned bus number 1

ci_hdrc ci_hdrc.0: USB 2.0 started, EHCI 1.00

hub 1-0:1.0: USB hub found

hub 1-0:1.0: 1 port detected

ci_hdrc ci_hdrc.1: doesn't support gadget

ci_hdrc ci_hdrc.1: EHCI Host Controller

ci_hdrc ci_hdrc.1: new USB bus registered, assigned bus number 2

ci_hdrc ci_hdrc.1: USB 2.0 started, EHCI 1.00

hub 2-0:1.0: USB hub found

hub 2-0:1.0: 1 port detected

mousedev: PS/2 mouse device common for all mice

egalax_ts 1-0004: Failed to read firmware version

egalax_ts: probe of 1-0004 failed with error -5

input: max11801_ts as /devices/soc0/soc.1/2100000.aips-bus/21a4000.i2c/i2c-1/1-0048/input/input0

i2c-core: driver [isl29023] using legacy suspend method

i2c-core: driver [isl29023] using legacy

                                        rmxc_v4l2_output v4l2_out.37: V4L2 device registered as video17

mxc_v4l2_output v4l2_out.37: V4L2 device registered as video18

mxc_v4l2_output v4l2_out.37: V4L2 device registered as video19

i2c-core: driver [mag3110] using legacy suspend method

i2c-core: driver [mag3110] using legacy resume method

mma8451 0-001c: read chip ID 0x1 is not equal to 0x1a or 0x2a!

mma8451: probe of 0-001c failed with error -22

imx2-wdt 20c0000.wdog: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=0)

watchdog: Software Watchdog: cannot register miscdev on minor=130 (err=-16).

watchdog: Software Watchdog: a legacy watchdog module is probably present.

softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)

cpuidle: using governor ladder

cpuidle: using governor menu

sdhci: Secure Digital Host Controller Interface driver

sdhci: Copyright(c) Pierre Ossman

sdhci-pltfm: SDHCI platform and OF driver helper

mmc1: no vqmmc regulator found

mmc1: no vmmc regulator found

mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA

mmc2: no vqmmc regulator found

mmc2: no vmmc regulator found

mmc2: SDHCI controller on 2198000.usdhc [2198000.usdhc] using ADMA

mmc3: no vqmmc regulator found

mmc3: no vmmc regulator found

mmc3: SDHCI controller on 219c000.usdhc [219c000.usdhc] using ADMA

Galcore version 5.0.11.25762

mxc_vdoa 21e4000.vdoa: i.MX Video Data Order Adapter(VDOA) driver probed

mxc_asrc 2034000.asrc: mxc_asrc registered

mxc_vpu 2040000.vpu: VPU initialized

usbcore: registered new interface driver usbhid

usbhid: USB HID core driver

wm8962 0-001a: Failed to read ID register

wm8962: probe of 0-001a failed with error -5

imx-wm8962 sound.27: failed to find codec platform device

imx-wm8962: probe of sound.27 failed with error -22

imx-audio-hdmi sound-hdmi.28:  hdmi-hifi <-> hdmi_audio.17 mapping ok

TCP: cubic registered

NET: Registered protocol family 10

sit: IPv6 over IPv4 tunneling driver

NET: Registered protocol family 17

8021q: 802.1Q VLAN Support v1.8

Key type dns_resolver registered

VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4

VGEN3: disabling

VGEN2: disabling

VGEN1: disabling

SWBST: disabling

SW4: disabling

wm8962-supply: disabling

regulator-dummy: disabling

imx mcc test is registered.

g_mass_storage gadget: Mass Storage Function, version: 2009/09/11

g_mass_storage gadget: Number of LUNs=1

lun0: LUN: removable file: (no medium)

g_mass_storage gadget: Mass Storage Gadget, version: 2009/09/11

g_mass_storage gadget: g_mass_storage ready

input: gpio-keys.26 as /devices/soc0/gpio-keys.26/input/input1

snvs_rtc 20cc034.snvs-rtc-lp: setting system clock to 1970-01-01 00:00:00 UTC (0)

ALSA device list:

  #0: imx-hdmi-soc

Freeing unused kernel memory: 324K (80bf6000 - 80c47000)

Starting UTP

uuc 0.5 [built Aug 11 2015 18:01:57]

UTP: Waiting for device to appear

UTP: file/device node /dev/utp already exists

cpu_id is 0

----------------------------------

(2) and I think I don't need to modify  "define PHYS_SDRAM_SIZE" in mx6qsabresd board,

$ grep -r "PHYS_SDRAM_SIZE" ./

./drivers/video/mb86r0xgdc.c:   pGD->frameAdrs = PHYS_SDRAM + PHYS_SDRAM_SIZE - VIDEO_MEM_SIZE;

./include/configs/mx6sxsabreauto.h:#define PHYS_SDRAM_SIZE                      SZ_2G

./include/configs/pm9261.h:#define PHYS_SDRAM_SIZE                              0x04000000      /* 64 megs */

./include/configs/vf610twr.h:#define PHYS_SDRAM_SIZE                    (128 * 1024 * 1024)

./include/configs/mx53loco.h:#define PHYS_SDRAM_SIZE                    (gd->ram_size)

./include/configs/mx6sxsabresd.h:#define PHYS_SDRAM_SIZE                        SZ_1G

./include/configs/pm9263.h:#define PHYS_SDRAM_SIZE              0x04000000      /* 64 megs */

./include/configs/titanium.h:#define PHYS_SDRAM_SIZE                    (512 << 20)

./include/configs/zmx25.h:#define PHYS_SDRAM_SIZE               0x04000000      /* 64 megs */

./include/configs/zmx25.h:#define CONFIG_SYS_MEMTEST_END                (PHYS_SDRAM + PHYS_SDRAM_SIZE)

./include/configs/m53evk.h:#define PHYS_SDRAM_SIZE                      (gd->ram_size)

./include/configs/kzm9g.h:#define PHYS_SDRAM_SIZE               (512 * 1024 * 1024)

./include/configs/kzm9g.h:#define CONFIG_SYS_SDRAM_SIZE (PHYS_SDRAM_SIZE - CONFIG_SDRAM_OFFSET_FOR_RT)

./include/configs/jadecpu.h:#define PHYS_SDRAM_SIZE     0x08000000      /* 128 megs */

./include/configs/jadecpu.h:#define CONFIG_SYS_MEMTEST_END              (PHYS_SDRAM + PHYS_SDRAM_SIZE)

./include/configs/mx6sx_arm2.h:#define PHYS_SDRAM_SIZE                  SZ_1G

./include/configs/u8500_href.h:#define PHYS_SDRAM_SIZE_1                0x20000000      /* 512 MB */

./include/configs/mx53smd.h:#define PHYS_SDRAM_SIZE         (PHYS_SDRAM_1_SIZE + PHYS_SDRAM_2_SIZE)

./include/configs/mx6slevk.h:#define PHYS_SDRAM_SIZE                    SZ_1G

./include/configs/cgtqmx6eval.h:#define PHYS_SDRAM_SIZE                        (1u * 1024 * 1024 * 1024)

./include/configs/pm9g45.h:#define PHYS_SDRAM_SIZE                      0x08000000      /* 128 megs */

./include/configs/mx53ard.h:#define PHYS_SDRAM_SIZE         (PHYS_SDRAM_1_SIZE + PHYS_SDRAM_2_SIZE)

0 Kudos
Reply
3,138 Views
igorpadykov
NXP Employee
NXP Employee

I think similar problem is discussed below and

problem was in host computer administrator rights

MFGTool not working for i.MX6 DualLite CPU Card

please try with WinXP 32 bit computer.

Also you wrote one time about "mx6qsabresd", another time

about "MACHINE=imx6solosabreauto"

what exactly your board is based on :

solosabreauto or sabresd ? One should not mix these

settings since these are different boards and configurations.

So if your board is based on mx6qsabresd, then you

should use only configurations for mx6qsabresd.

One can look at imx6solosabreauto configurations just for

reference and modify mx6qsabresd files, if necessary.

Best regards

igor

0 Kudos
Reply
3,140 Views
wangzhigang
Contributor III

hi,igor

     I have solve the problem, It is a hardware problem,the pin of id in otg was pull down  by a resistance.so that the otg cannot be a slave device.and th UTP cannot receive the windows's command.

     thanks for your help!

   Best regards

0 Kudos
Reply
3,138 Views
zhangzhencai
Contributor II

Thanks,I meet the same  problem and solve it with your method。

0 Kudos
Reply
3,138 Views
jiejia
Contributor III

王工,你好。

    为了布线的方便,我这边也打算拿掉2片DDR3(for 32 bit 1GB DDR)。想问下你,板上的这两个DDR3(片选信号)都接到DRAM_CS0上, 还是两片DDR3(片选信号)分别接到DRAM_CS0和DRAM_CS1上呢?

0 Kudos
Reply
3,138 Views
wangzhigang
Contributor III

应该都接到cs0吧

0 Kudos
Reply