topic Re: How to get Nitrogen6W working with android in i.MX Processors

How to get Nitrogen6W working with android

seanwalton — Fri, 20 Apr 2018 01:49:02 GMT

I inherited a couple Nitrogen 6W boards from my work. They have a 3-22-12 release date and u-boot "U-Boot 2009.08 (Jul 05 2012 - 15:37:27)" I am trying to get the stock Android distro on them.

this is what I get with Android 601:

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

U-Boot 2009.08 (Jul 05 2012 - 15:37:27)

CPU: Freescale i.MX 6 family 0.0V at 792 MHz
Temperature: can't get valid data!
mx6q pll1: 792MHz
mx6q pll2: 528MHz
mx6q pll3: 480MHz
mx6q pll8: 50MHz
ipg clock : 66000000Hz
ipg per clock : 66000000Hz
uart clock : 80000000Hz
cspi clock : 60000000Hz
ahb clock : 132000000Hz
axi clock : 264000000Hz
emi_slow clock: 29333333Hz
ddr clock : 528000000Hz
usdhc1 clock : 200000000Hz
usdhc2 clock : 200000000Hz
usdhc3 clock : 200000000Hz
usdhc4 clock : 200000000Hz
nfc clock : 24000000Hz
Board: MX6Q-SABRELITE:[ POR]
Boot Device: I2C
I2C: ready
DRAM: 1 GB
MMC: FSL_USDHC: 0,FSL_USDHC: 1
JEDEC ID: 0xbf:0x25:0x41
Reading SPI NOR flash 0xc0000 [0x2000 bytes] -> ram 0x276009b8
SUCCESS

In: serial
Out: serial
Err: serial
Net: got MAC address from IIM: 00:19:b8:00:f7:33
FEC0 [PRIME]
Warning: FEC0 MAC addresses don't match:
Address in SROM is 00:19:b8:00:f7:33
Address in environment is 00:08:72:00:00:ff

Hit any key to stop autoboot: 0
mmc0 is current device
reading /6q_bootscript

** Unable to read "/6q_bootscript" from mmc 0:1 **
Loading file "/6q_bootscript" from mmc device 0:1 (xxa1)
Failed to mount ext2 filesystem...
** Bad ext2 partition or disk - mmc 0:1 **
Card did not respond to voltage select!
mmc1(part 0) is current device
MMC: block number 0x1 exceeds max(0x0)
** Can't read from device 1 **

** Unable to use mmc 1:1 for fatload **
** Bad partition 1 **
MX6Q SABRELITE U-Boot >

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

This is what I get with 711:

## Booting kernel from Legacy Image at 10800000 ...
Image Name: Linux-3.0.15-ts-armv7l
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4038272 Bytes = 3.9 MB
Load Address: 10008000
Entry Point: 10008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 3.0.15-ts-armv7l (andrew@gumshoe) (gcc version 4.6.3 (Timesys 20120611) ) #11 SMP PREEMPT Wed Aug 15 15:54:17 EDT 2012
CPU: ARMv7 Processor [412fc09a] revision 10 (ARMv7), cr=10c53c7d
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: Freescale i.MX 6Quad Sabre-Lite Board
Memory policy: ECC disabled, Data cache writealloc
PERCPU: Embedded 7 pages/cpu @8c008000 s5664 r8192 d14816 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 227328
Kernel command line: console=ttymxc1,115200 video=mxcfb0:dev=ldb,1024x768M@60,if=RGB666 vmalloc=400M consoleblank=0 calibration tsdev=tsc2004 fbmem=10M,28M ethaddr=00:08:72:00:00:FF console=ttymxc1,115200 vmalloc=400M root=/dev/mmcblk0p1 rootwait consoleblank=0
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: 896268k/896268k available, 152308k 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 - 0x8004e000 ( 280 kB)
.text : 0x8004e000 - 0x80b32efc (11156 kB)
.data : 0x80b34000 - 0x80b80130 ( 305 kB)
.bss : 0x80b80154 - 0x80bcf564 ( 318 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
Preemptible hierarchical RCU implementation.
NR_IRQS:496
MXC GPIO hardware
sched_clock: 32 bits at 6MHz, resolution 166ns, wraps every 715827ms
MXC_Early serial console at MMIO 0x21e8000 (options '115200')
bootconsole [ttymxc1] 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
ftrace: allocating 19294 entries in 57 pages
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 1100 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: 2800 <--> 3150 mV at 3000 mV fast normal
------------ Board type Nitrogen6X/W
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
IMX usb wakeup probe
IMX usb wakeup probe
bio: create slab <bio-0> at 0
print_constraints: VDDA: 2500 mV
print_constraints: VDDIO: 3300 mV
machine_constraints_voltage: VDDD: unsupportable voltage constraints
reg-fixed-voltage reg-fixed-voltage.2: Failed to register regulator: -22
reg-fixed-voltage: probe of reg-fixed-voltage.2 failed with error -22
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
Freescale USB OTG Driver loaded, $Revision: 1.55 $
add wake up source irq 75
imx-ipuv3 imx-ipuv3.0: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
imx-ipuv3 imx-ipuv3.1: IPU DMFC NORMAL mode: 1(0~1), 5B(4,5), 5F(6,7)
mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 driver probed
mxc_mipi_csi2 mxc_mipi_csi2: i.MX MIPI CSI2 dphy version is 0x3130302a
MIPI CSI2 driver module loaded
Advanced Linux Sound Architecture Driver Version 1.0.24.
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
i2c-core: driver [max17135] using legacy suspend method
i2c-core: driver [max17135] using legacy resume method
Switching to clocksource mxc_timer1
Switched to NOHz mode on CPU #0
Switched to NOHz mode on CPU #1
Switched to NOHz mode on CPU #2
Switched to NOHz mode on CPU #3
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 5, 131072 bytes)
TCP established hash table entries: 131072 (order: 8, 1048576 bytes)
TCP bind hash table entries: 65536 (order: 7, 786432 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
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.
Static Power Management for Freescale i.MX6
cpaddr = c0884000 suspend_iram_base=c0932000
PM driver module loaded
i.MXC CPU frequency driver
JFFS2 version 2.2. (NAND) © 2001-2006 Red Hat, Inc.
msgmni has been set to 1750
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
MIPI DSI driver module loaded
mxc_sdc_fb mxc_sdc_fb.0: register mxc display driver ldb
_regulator_get: get() with no identifier
fbcvt: 1024x768@60: CVT Name - .786M3
imx-ipuv3 imx-ipuv3.1: IPU DMFC DP HIGH RESOLUTION: 1(0,1), 5B(2~5), 5F(6,7)
Console: switching to colour frame buffer device 128x48
mxc_sdc_fb mxc_sdc_fb.1: register mxc display driver lcd
mxc_sdc_fb mxc_sdc_fb.2: register mxc display driver ldb
mxc_sdc_fb mxc_sdc_fb.3: register mxc display driver ldb
mxc_sdc_fb mxc_sdc_fb.3: ipu1-di1 already in use
mxc_sdc_fb: probe of mxc_sdc_fb.3 failed with error -16
imx-sdma imx-sdma: loaded firmware 1.1
imx-sdma imx-sdma: initialized
Serial: IMX driver
imx-uart.0: ttymxc0 at MMIO 0x2020000 (irq = 58) is a IMX
imx-uart.1: ttymxc1 at MMIO 0x21e8000 (irq = 59) is a IMX
old_ufcr=a81 new_ufcr=b01, old_ucr2=4027 new_ucr2=4027, old_ubir=f num=1f7, old_ubmr=15b denom=c34
clk=80000000 div=7 num=504 denom=3125 baud=115200
console [ttymxc1] enabled, bootconsole disabled
console [ttymxc1] enabled, bootconsole disabled
imx-uart.2: ttymxc2 at MMIO 0x21ec000 (irq = 60) is a IMX
loop: module loaded
Can't recover from RESET HBA!
No sata disk.
m25p80 spi0.0: sst25vf016b (2048 Kbytes)
Creating 2 MTD partitions on "m25p80":
0x000000000000-0x000000040000 : "bootloader"
0x000000040000-0x000000200000 : "kernel"
vcan: Virtual CAN interface driver
CAN device driver interface
flexcan netdevice driver
flexcan imx6q-flexcan.0: device registered (reg_base=c09a8000, irq=142)
FEC Ethernet Driver
fec_enet_mii_bus: probed
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
fsl-ehci fsl-ehci.0: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.0: new USB bus registered, assigned bus number 1
fsl-ehci fsl-ehci.0: irq 75, io base 0x02184000
fsl-ehci fsl-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: Freescale On-Chip EHCI Host Controller
usb usb1: Manufacturer: Linux 3.0.15-ts-armv7l ehci_hcd
usb usb1: SerialNumber: fsl-ehci.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
add wake up source irq 72
fsl-ehci fsl-ehci.1: Freescale On-Chip EHCI Host Controller
fsl-ehci fsl-ehci.1: new USB bus registered, assigned bus number 2
fsl-ehci fsl-ehci.1: irq 72, io base 0x02184200
fsl-ehci fsl-ehci.1: USB 2.0 started, EHCI 1.00
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: Freescale On-Chip EHCI Host Controller
usb usb2: Manufacturer: Linux 3.0.15-ts-armv7l ehci_hcd
usb usb2: SerialNumber: fsl-ehci.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
ARC USBOTG Device Controller driver (1 August 2005)
mousedev: PS/2 mouse device common for all mice
input: gpio-keys as /devices/platform/gpio-keys/input/input0
i2c-core: driver [isl29023] using legacy suspend method
i2c-core: driver [isl29023] using legacy resume method
snvs_rtc snvs_rtc.0: rtc core: registered snvs_rtc as rtc0
i2c /dev entries driver
Linux video capture interface: v2.00
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video16
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video17
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video18
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video19
mxc_v4l2_output mxc_v4l2_output.0: V4L2 device registered as video20
i2c-core: driver [mag3110] using legacy suspend method
i2c-core: driver [mag3110] using legacy resume method
imx2-wdt imx2-wdt.0: IMX2+ Watchdog Timer enabled. timeout=60s (nowayout=1)
Bluetooth: Virtual HCI driver ver 1.3
Bluetooth: HCI UART driver ver 2.2
Bluetooth: HCIATH3K protocol initialized
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci sdhci-esdhc-imx.2: no write-protect pin available!
mmc0: Unknown controller version (3). You may experience problems.
mmc0: SDHCI controller on platform [sdhci-esdhc-imx.2] using ADMA
sdhci sdhci-esdhc-imx.3: no write-protect pin available!
mmc1: Unknown controller version (3). You may experience problems.
mmc1: SDHCI controller on platform [sdhci-esdhc-imx.3] using ADMA
mxc_vdoa mxc_vdoa: i.MX Video Data Order Adapter(VDOA) driver probed
VPU initialized
mxc_asrc registered
Anatop Thermal registered as thermal_zone0
anatop_thermal_probe: default cooling device is cpufreq!
usb 2-1: new high speed USB device number 2 using fsl-ehci
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
mxc_hdmi_soc mxc_hdmi_soc.0: MXC HDMI Audio
sgtl5000 0-000a: Failed to get supply 'VDDD': -19
print_constraints: 0-000a: 850 <--> 1600 mV at 1200 mV normal
sgtl5000 0-000a: sgtl5000 revision 17
mmc0: host does not support reading read-only switch. assuming write-enable.
mmc0: new SDHC card at address b368
mmcblk0: mmc0:b368 3.73 GiB
GPT:Primary header thinks Alt. header is not at the end of the disk.
GPT:7372799 != 7829503
GPT:Alternate GPT header not at the end of the disk.
GPT:7372799 != 7829503
GPT: Use GNU Parted to correct GPT errors.
mmcblk0: p1 p2 p3 p4 p5 p6 p7
asoc: sgtl5000 <-> imx-ssi.1 mapping ok
imx-hdmi-soc-dai: probe of imx-hdmi-soc-dai.0 failed with error -12
ALSA device list:
#0: sgtl5000-audio
NET: Registered protocol family 26
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
usb 2-1: New USB device found, idVendor=0424, idProduct=2513
usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM ver 1.11
hub 2-1:1.0: USB hub found
hub 2-1:1.0: 3 ports detected
Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Bluetooth: BNEP filters: protocol multicast
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
VFP support v0.3: implementor 41 architecture 3 part 30 variant 9 rev 4
Bus freq driver module loaded
mxc_dvfs_core_probe
DVFS driver module loaded
snvs_rtc snvs_rtc.0: setting system clock to 1970-01-01 00:00:00 UTC (0)
EXT3-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (240)
mmc1: host does not support reading read-only switch. assuming write-enable.
mmc1: new SDHC card at address b368
mmcblk1: mmc1:b368 3.73 GiB
mmcblk1: p1
EXT2-fs (mmcblk0p1): error: couldn't mount because of unsupported optional features (244)
EXT4-fs (mmcblk0p1): recovery complete
EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null)
VFS: Mounted root (ext4 filesystem) on device 179:1.
Freeing init memory: 280K
Kernel panic - not syncing: No init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
[<8005aedc>] (unwind_backtrace+0x0/0x104) from [<8058f9ac>] (dump_stack+0x20/0x24)
[<8058f9ac>] (dump_stack+0x20/0x24) from [<8058fc74>] (panic+0x74/0x18c)
[<8058fc74>] (panic+0x74/0x18c) from [<8058f8f4>] (init_post+0xb0/0xd4)
[<8058f8f4>] (init_post+0xb0/0xd4) from [<80008a3c>] (kernel_init+0x104/0x130)
[<80008a3c>] (kernel_init+0x104/0x130) from [<80055100>] (kernel_thread_exit+0x0/0x8)
CPU1: stopping
[<8005aedc>] (unwind_backtrace+0x0/0x104) from [<8058f9ac>] (dump_stack+0x20/0x24)
[<8058f9ac>] (dump_stack+0x20/0x24) from [<8004e520>] (do_IPI+0x140/0x168)
[<8004e520>] (do_IPI+0x140/0x168) from [<8005400c>] (__irq_svc+0x4c/0xe8)
Exception stack(0xbff2bf68 to 0xbff2bfb0)
bf60: 00000007 20000013 bff2bfb0 00000000 bff2a000 80b80204
bf80: 80599704 80b4954c 1000406a 412fc09a 00000000 bff2bfbc bff2bfb0 bff2bfb0
bfa0: 8006324c 800551ac 60000013 ffffffff
[<8005400c>] (__irq_svc+0x4c/0xe8) from [<800551ac>] (default_idle+0x34/0x38)
[<800551ac>] (default_idle+0x34/0x38) from [<800553f4>] (cpu_idle+0xc4/0x104)
[<800553f4>] (cpu_idle+0xc4/0x104) from [<8058ca84>] (secondary_start_kernel+0x154/0x174)
[<8058ca84>] (secondary_start_kernel+0x154/0x174) from [<1058c3f4>] (0x1058c3f4)
CPU3: stopping
[<8005aedc>] (unwind_backtrace+0x0/0x104) from [<8058f9ac>] (dump_stack+0x20/0x24)
[<8058f9ac>] (dump_stack+0x20/0x24) from [<8004e520>] (do_IPI+0x140/0x168)
[<8004e520>] (do_IPI+0x140/0x168) from [<8005400c>] (__irq_svc+0x4c/0xe8)
Exception stack(0xbff3bf68 to 0xbff3bfb0)
bf60: 00000001 20000013 bff3bfb0 00000000 bff3a000 80b80204
bf80: 80599704 80b4954c 1000406a 412fc09a 00000000 bff3bfbc bff3bfb0 bff3bfb0
bfa0: 8006324c 800551ac 60000013 ffffffff
[<8005400c>] (__irq_svc+0x4c/0xe8) from [<800551ac>] (default_idle+0x34/0x38)
[<800551ac>] (default_idle+0x34/0x38) from [<800553f4>] (cpu_idle+0xc4/0x104)
[<800553f4>] (cpu_idle+0xc4/0x104) from [<8058ca84>] (secondary_start_kernel+0x154/0x174)
[<8058ca84>] (secondary_start_kernel+0x154/0x174) from [<1058c3f4>] (0x1058c3f4)
CPU0: stopping
[<8005aedc>] (unwind_backtrace+0x0/0x104) from [<8058f9ac>] (dump_stack+0x20/0x24)
[<8058f9ac>] (dump_stack+0x20/0x24) from [<8004e520>] (do_IPI+0x140/0x168)
[<8004e520>] (do_IPI+0x140/0x168) from [<8005400c>] (__irq_svc+0x4c/0xe8)
Exception stack(0x80b35f38 to 0x80b35f80)
5f20: 0000000f 20000013
5f40: 80b35f80 00000000 80b34000 80b80204 80599704 80b4954c 1000406a 412fc09a
5f60: 00000000 80b35f8c 80b35f80 80b35f80 8006324c 800551ac 60000013 ffffffff
[<8005400c>] (__irq_svc+0x4c/0xe8) from [<800551ac>] (default_idle+0x34/0x38)
[<800551ac>] (default_idle+0x34/0x38) from [<800553f4>] (cpu_idle+0xc4/0x104)
[<800553f4>] (cpu_idle+0xc4/0x104) from [<80582728>] (rest_init+0x8c/0xa4)
[<80582728>] (rest_init+0x8c/0xa4) from [<800088f4>] (start_kernel+0x258/0x29c)
[<800088f4>] (start_kernel+0x258/0x29c) from [<10008040>] (0x10008040)

Re: How to get Nitrogen6W working with android

joanxie — Wed, 25 Apr 2018 08:33:52 GMT

how did you program them to the board? by mfgtool? did you use demo image or customized image? I don't have this board to test for you, so pls share with me more detailed information.

Re: How to get Nitrogen6W working with android

seanwalton — Wed, 25 Apr 2018 17:05:45 GMT

I downloaded and used the image under "for the impatient." I could not find a way to create a custom image.

From Linux, I burned the bootable image on a micro-sd and tried to boot from it. UBoot complained that it did not recognize the partition table. So, I assumed that the UBoot version was too old (2009/08) and tried to update UBoot.

At this juncture, I bricked one of the two boards while trying to update UBoot. I will try to get you more info...

Re: How to get Nitrogen6W working with android

gary_bisson — Thu, 26 Apr 2018 17:00:38 GMT

Hi Sean,

Please visit our wiki:

Wiki - Boundary Devices

You'll find:

- How to update your U-Boot to latest 2017.07 (yours is too old)

- How to download and flash latest stable Android (Nougat, yours is too old)

Regards,

Gary

Re: How to get Nitrogen6W working with android

seanwalton — Fri, 27 Apr 2018 20:04:22 GMT

Thank you for your reply. I have been trying to update the uboot (I bricked the device) without success. Perhaps you can help. Here is a photo of the board so that you can see version, etc.

I start up sb_loader.exe:

1) u-boot.nitrogen6sx, *6s, and *max install but cannot start up

2) u-boot.nitrogen6q loads and starts

3) *6q expects 6q_upgrade, but only 6x_upgrade is available and according to the website, 6x_upgrade replaces 6q*

4) resorted to stripping 6x_upgrade down to a few crucial, relevant steps:

erase_size=0xC0000
offset=0x400
a_base=0x10008000

setexpr a_qspi1 ${a_base}
setexpr a_qspi2 ${a_qspi1} + 0x400000
setexpr a_uImage1 ${a_qspi1} + 0x400
setexpr a_uImage2 ${a_qspi2} + 0x400
setexpr a_script ${a_base}

sf probe || sf probe || sf probe 1 27000000 || sf probe 1 27000000
fatload mmc 0:1 ${a_uImage1} u-boot.nitrogen6q

sf erase 0 ${erase_size}
sf write ${a_uImage1} 0 ${filesize} #---Line #6

5) Base memory address (0x12000000 or 0x82000000) failed, so I used the address we use on a custom i.mx6 board: 0x10008000 -- It worked and grabbed the uboot image successfully.

6) I tried with and without ${offset}. Ultimately, I stuck with the base address, because 0x400 appeared to be protecting something, and since my board was bricked, I figured that it couldn't hurt.

7) I tried to burn *6q, but it would not boot; I tried *6SX. It seemed to me that *6q should have worked, because I had USB-booted with the exact same image.

What should I try next?

-Sean

Re: How to get Nitrogen6W working with android

gary_bisson — Mon, 30 Apr 2018 08:08:10 GMT

Hi Sean,

Please read the wiki, it does provide the "manual procedure" to update U-Boot without using 6x_upgrade for very old U-Boot.

Also, the Nitrogen6w needs u-boot.nitrogen6q, do not try any other configuration.

Regards,

Gary