Release SuperZaxxon Final released!

Asmo · Jul 26, 2012

Just another WiFi LED observation -

Activated WiFi, LED came on. Found file I wanted on archive.org, set Pandora downloading it and left it in place.

20 minutes later, screen has turned off (as normal) but WiFi LED is also now off - although WiFi very much active and downloading still in progress.

Edit: last two activations of WiFi in the last 24hrs, no WiFi LED at all.

FaeMinx · Jul 26, 2012

I've just tried to flash (twice) and I get this:

u-boot.bin already flashed, skipped.

uImage already flashed, skipped.

uImage-2.6.27.57-omap1 already flashed, skipped.

uImage-3 already flashed, skipped.

Calculating checksum, this might take a few minutes..

INCORRECT

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

Update FAILED

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

update.log saved to SD

press Enter to power off

EDIT:

[ 0.000000] Linux version 3.2.16-00257-g22711aa (notaz@pixelinis) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #604 Sun Apr 29 20:37:25 EEST 2012

[ 0.000000] CPU: ARMv7 Processor [411fc082] revision 2 (ARMv7), cr=10c5387d

[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache

[ 0.000000] Machine: Pandora Handheld Console

[ 0.000000] Reserving 8388608 bytes SDRAM for VRAM

[ 0.000000] Memory policy: ECC disabled, Data cache writeback

[ 0.000000] On node 0 totalpages: 61952

[ 0.000000] free_area_init_node: node 0, pgdat c04ae9e0, node_mem_map c04d4000

[ 0.000000] Normal zone: 512 pages used for memmap

[ 0.000000] Normal zone: 0 pages reserved

[ 0.000000] Normal zone: 61440 pages, LIFO batch:15

[ 0.000000] OMAP3430/3530 ES2.1 (l2cache iva sgx neon isp )

[ 0.000000] Clocking rate (Crystal/Core/MPU): 26.0/332/500 MHz

[ 0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768

[ 0.000000] pcpu-alloc: [0] 0

[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 61440

[ 0.000000] Kernel command line: console=tty1 ramdisk_size=8192 root=/dev/ram0 rw rootfstype=ext2 initrd=0x82321000,8M vram=6272K omapfb.vram=0:3000K

[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)

[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)

[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)

[ 0.000000] Memory: 242MB = 242MB total

[ 0.000000] Memory: 232388k/232388k available, 29756k reserved, 0K highmem

[ 0.000000] Virtual kernel memory layout:

[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)

[ 0.000000] fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)

[ 0.000000] vmalloc : 0xd0800000 - 0xf8000000 ( 632 MB)

[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)

[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)

[ 0.000000] .text : 0xc0008000 - 0xc0442c18 (4332 kB)

[ 0.000000] .init : 0xc0443000 - 0xc0473000 ( 192 kB)

[ 0.000000] .data : 0xc0474000 - 0xc04af080 ( 237 kB)

[ 0.000000] .bss : 0xc04af0a4 - 0xc04d3ea4 ( 148 kB)

[ 0.000000] SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1

[ 0.000000] NR_IRQS:410

[ 0.000000] IRQ: Found an INTC at 0xfa200000 (revision 4.0) with 96 interrupts

[ 0.000000] Total of 96 interrupts on 1 active controller

[ 0.000000] OMAP clockevent source: GPTIMER1 at 32768 Hz

[ 0.000000] sched_clock: 32 bits at 32kHz, resolution 30517ns, wraps every 131071999ms

[ 0.000000] Console: colour dummy device 80x30

[ 0.000000] console [tty1] enabled

[ 0.000701] Calibrating delay loop... 497.82 BogoMIPS (lpj=1941504)

[ 0.039123] pid_max: default: 32768 minimum: 301

[ 0.039489] Mount-cache hash table entries: 512

[ 0.040069] Initializing cgroup subsys devices

[ 0.040161] CPU: Testing write buffer coherency: ok

[ 0.040435] hw perfevents: enabled with ARMv7 Cortex-A8 PMU driver, 5 counters available

[ 0.041381] devtmpfs: initialized

[ 0.055877] print_constraints: dummy:

[ 0.056457] NET: Registered protocol family 16

[ 0.056945] GPMC revision 5.0

[ 0.061279] OMAP GPIO hardware version 2.5

[ 0.066162] omap_mux_init: Add partition: #1: core, flags: 0

[ 0.074829] Reprogramming SDRC clock to 332000000 Hz

[ 0.077911] hw-breakpoint: debug architecture 0x4 unsupported.

[ 0.087860] omap-mcbsp.2: alias fck already exists

[ 0.088317] omap-mcbsp.3: alias fck already exists

[ 0.090362] OMAP DMA hardware revision 4.0

[ 0.112823] bio: create slab <bio-0> at 0

[ 0.114501] print_constraints: vwlan: 1800 mV

[ 0.116760] SCSI subsystem initialized

[ 0.120239] usbcore: registered new interface driver usbfs

[ 0.120605] usbcore: registered new interface driver hub

[ 0.121002] usbcore: registered new device driver usb

[ 0.122924] omap_i2c omap_i2c.1: bus 1 rev1.3.12 at 2600 kHz

[ 0.142547] twl4030: PIH (irq 7) chaining IRQs 368..375

[ 0.142700] twl4030: power (irq 373) chaining IRQs 376..383

[ 0.143463] twl4030: gpio (irq 368) chaining IRQs 384..401

[ 0.144073] _omap_mux_init_gpio: Could not set gpio192

[ 0.145507] _omap_mux_init_gpio: Could not set gpio193

[ 0.149047] print_constraints: VUSB1V5: 1500 mV normal standby

[ 0.149993] print_constraints: VUSB1V8: 1800 mV normal standby

[ 0.150909] print_constraints: VUSB3V1: 3100 mV normal standby

[ 0.152954] twl4030_usb twl4030_usb: Initialized TWL4030 USB module

[ 0.154815] print_constraints: vdd_mpu_iva: 600 <--> 1450 mV normal

[ 0.155731] print_constraints: vdd_core: 600 <--> 1450 mV normal

[ 0.156768] print_constraints: VMMC1: 1850 <--> 3150 mV at 3150 mV normal standby

[ 0.157775] print_constraints: VDAC: 1800 mV normal standby

[ 0.158721] print_constraints: VAUX2: 1800 mV normal standby

[ 0.159698] print_constraints: VPLL2: 1800 mV normal standby

[ 0.160705] print_constraints: VMMC2: 1850 <--> 3150 mV at 2600 mV normal standby

[ 0.161712] print_constraints: VSIM: 2800 mV normal standby

[ 0.162658] print_constraints: VAUX1: 3000 mV normal standby

[ 0.163574] print_constraints: VAUX4: 2800 mV normal standby

[ 0.164337] omap_i2c omap_i2c.3: bus 3 rev1.3.12 at 100 kHz

[ 0.167846] Advanced Linux Sound Architecture Driver Version 1.0.24.

[ 0.169006] Switching to clocksource 32k_counter

[ 0.201416] musb-hdrc: version 6.0, ?dma?, otg (peripheral+host)

[ 0.206848] musb-hdrc: ConfigData=0xde (UTMI-8, dyn FIFOs, bulk combine, bulk split, HB-ISO Rx, HB-ISO Tx, SoftConn)

[ 0.206878] musb-hdrc: MHDRC RTL version 1.400

[ 0.206909] musb-hdrc: setup fifo_mode 4

[ 0.206939] musb-hdrc: 28/31 max ep, 16384/16384 memory

[ 0.207641] musb-hdrc musb-hdrc: USB OTG mode controller at fa0ab000 using DMA, IRQ 92

[ 0.208709] NET: Registered protocol family 2

[ 0.208953] IP route cache hash table entries: 2048 (order: 1, 8192 bytes)

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

[ 0.209686] TCP bind hash table entries: 8192 (order: 3, 32768 bytes)

[ 0.209899] TCP: Hash tables configured (established 8192 bind 8192)

[ 0.209930] TCP reno registered

[ 0.209960] UDP hash table entries: 256 (order: 0, 4096 bytes)

[ 0.210021] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)

[ 0.210449] NET: Registered protocol family 1

[ 0.210784] Trying to unpack rootfs image as initramfs...

[ 0.212341] rootfs image is not initramfs (no cpio magic); looks like an initrd

[ 0.280212] Freeing initrd memory: 8192K

[ 0.280273] NetWinder Floating Point Emulator V0.97 (double precision)

[ 0.282623] omap_dsp_init: 600000 bytes @ 8f200000

[ 0.315399] VFS: Disk quotas dquot_6.5.2

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

[ 0.319580] msgmni has been set to 469

[ 0.322296] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253)

[ 0.322357] io scheduler noop registered

[ 0.322387] io scheduler deadline registered

[ 0.322448] io scheduler cfq registered (default)

[ 0.336456] OMAP DSS rev 2.0

[ 0.341156] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled

[ 0.344085] omap_uart.0: ttyO0 at MMIO 0x4806a000 (irq = 72) is a OMAP UART0

[ 0.344726] omap_uart.1: ttyO1 at MMIO 0x4806c000 (irq = 73) is a OMAP UART1

[ 0.345306] omap_uart.2: ttyO2 at MMIO 0x49020000 (irq = 74) is a OMAP UART2

[ 0.362121] brd: module loaded

[ 0.370880] loop: module loaded

[ 0.370971] OMAP overclocker loaded.

[ 0.374084] omap2-nand driver initializing

[ 0.374328] NAND device: Manufacturer ID: 0x2c, Chip ID: 0xbc (Micron NAND 512MiB 1,8V 16-bit)

[ 0.375000] Creating 5 MTD partitions on "omap2-nand.0":

[ 0.375030] 0x000000000000-0x000000080000 : "xloader"

[ 0.376098] 0x000000080000-0x000000260000 : "uboot"

[ 0.377319] 0x000000260000-0x000000280000 : "uboot-env"

[ 0.378173] 0x000000280000-0x000000c80000 : "boot"

[ 0.381072] 0x000000c80000-0x000020000000 : "rootfs"

[ 0.482391] usbcore: registered new interface driver libusual

[ 0.483337] mousedev: PS/2 mouse device common for all mice

[ 0.484069] input: keypad as /devices/platform/omap/omap_i2c.1/i2c-1/1-004a/twl4030_keypad/input/input0

[ 0.487030] input: power-button as /devices/platform/omap/omap_i2c.1/i2c-1/1-0049/twl4030_pwrbutton/input/input1

[ 0.488555] input: nub0 as /devices/platform/omap/omap_i2c.3/i2c-3/3-0066/input/input2

[ 0.490356] input: nub1 as /devices/platform/omap/omap_i2c.3/i2c-3/3-0067/input/input3

[ 0.494354] twl_rtc twl_rtc: rtc core: registered twl_rtc as rtc0

[ 0.495117] i2c /dev entries driver

[ 0.505767] OMAP Watchdog Timer Rev 0x31: initial timeout 60 sec

[ 0.506347] twl4030_wdt twl4030_wdt: Failed to register misc device

[ 0.506408] twl4030_wdt: probe of twl4030_wdt failed with error -16

[ 0.507110] voltdm_scale: No voltage scale API registered for vdd_mpu_iva

[ 0.507171] platform mpu.0: omap_target: unable to scale voltage up.

[ 0.507629] cpuidle: using governor ladder

[ 0.507659] cpuidle: using governor menu

[ 0.508331] omap_hsmmc omap_hsmmc.0: multiblock reads disabled due to 35xx erratum 2.1.1.128; MMC read performance may suffer

[ 0.732910] Registered led device: pandora::sd1

[ 0.733245] Registered led device: pandora::sd2

[ 0.733551] Registered led device: pandora::bluetooth

[ 0.733825] Registered led device: pandora::wifi

[ 0.735168] Registered led device: pandora::keypad_bl

[ 0.736083] Registered led device: pandora:

ower

[ 0.738922] Registered led device: pandora::charger

[ 0.740325] usbcore: registered new interface driver usbhid

[ 0.740356] usbhid: USB HID core driver

[ 0.743011] OMAP3 Pandora SoC init

[ 0.827758] asoc: twl4030-hifi <-> omap-mcbsp-dai.1 mapping ok

[ 0.829345] asoc: twl4030-hifi <-> omap-mcbsp-dai.3 mapping ok

[ 0.832275] ALSA device list:

[ 0.832336] #0: omap3pandora

[ 0.832550] TCP cubic registered

[ 0.832580] NET: Registered protocol family 17

[ 0.832641] NET: Registered protocol family 15

[ 0.832672] Registering the dns_resolver key type

[ 0.832794] VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 1

[ 0.832855] ThumbEE CPU extension supported.

[ 0.832885] Registering SWP/SWPB emulation handler

[ 0.836761] PM: no software I/O chain control; some wakeups may be lost

[ 0.840881] clock: disabling unused clocks to save power

[ 0.872955] Console: switching to colour frame buffer device 100x30

[ 1.066986] input: gpio-keys as /devices/platform/gpio-keys/input/input4

[ 1.072814] twl_rtc twl_rtc: setting system clock to 2012-07-25 02:21:17 UTC (1343182877)

[ 1.077148] RAMDISK: gzip image found at block 0

[ 1.184906] mmc0: host does not support reading read-only switch. assuming write-enable.

[ 1.192718] mmc0: new high speed SD card at address 0002

[ 1.208374] mmcblk0: mmc0:0002 N/A 961 MiB

[ 1.214569] mmcblk0: p1

[ 1.370880] mmc2: card claims to support voltages below the defined range. These will be ignored.

[ 1.384460] mmc2: new SDIO card at address 0001

[ 1.520965] VFS: Mounted root (ext2 filesystem) on device 1:0.

[ 1.525268] devtmpfs: mounted

[ 1.529876] Freeing init memory: 192K

[ 6.049957] UBI: attaching mtd3 to ubi0

[ 6.049987] UBI: physical eraseblock size: 131072 bytes (128 KiB)

[ 6.050018] UBI: logical eraseblock size: 129024 bytes

[ 6.050048] UBI: smallest flash I/O unit: 2048

[ 6.050079] UBI: sub-page size: 512

[ 6.050109] UBI: VID header offset: 512 (aligned 512)

[ 6.050140] UBI: data offset: 2048

[ 6.092071] UBI: max. sequence number: 965

[ 6.113433] UBI: attached mtd3 to ubi0

[ 6.113494] UBI: MTD device name: "boot"

[ 6.113525] UBI: MTD device size: 10 MiB

[ 6.113555] UBI: number of good PEBs: 80

[ 6.113586] UBI: number of bad PEBs: 0

[ 6.113586] UBI: number of corrupted PEBs: 0

[ 6.113616] UBI: max. allowed volumes: 128

[ 6.113647] UBI: wear-leveling threshold: 4096

[ 6.113677] UBI: number of internal volumes: 1

[ 6.113677] UBI: number of user volumes: 1

[ 6.113708] UBI: available PEBs: 0

[ 6.113739] UBI: total number of reserved PEBs: 80

[ 6.113769] UBI: number of PEBs reserved for bad PEB handling: 2

[ 6.113800] UBI: max/mean erase counter: 111/62

[ 6.113830] UBI: image sequence number: 228449004

[ 6.117401] UBI: background thread "ubi_bgt0d" started, PID 733

[ 6.164978] UBIFS: recovery needed

[ 6.262573] UBIFS: recovery completed

[ 6.262634] UBIFS: mounted UBI device 0, volume 0, name "boot"

[ 6.262664] UBIFS: file system size: 8386560 bytes (8190 KiB, 7 MiB, 65 LEBs)

[ 6.262695] UBIFS: journal size: 1032193 bytes (1008 KiB, 0 MiB, 6 LEBs)

[ 6.262725] UBIFS: media format: w4/r0 (latest is w4/r0)

[ 6.262786] UBIFS: default compressor: lzo

[ 6.262786] UBIFS: reserved for root: 396117 bytes (386 KiB)

[ 14.120025] UBIFS: un-mount UBI device 0, volume 0

[ 14.142791] UBI: mtd3 is detached from ubi0

----------

+ . /etc/updater_funcs.sh

+ LOG_TTY=3

+ LOG_DEVICE=/dev/tty3

+ status_uboot=missing

+ status_uboot_env=already empty

+ status_uimage=missing

+ status_rootfs=missing

+ mkdir /mnt/ubifs

+ [ ! -e /dev/mmcblk0p1 ]

+ mdevs=/dev/mmcblk0p1 /dev/mmcblk0p2

+ bootfiles=bootf.tgz bootfiles.tar.gz uimage.tar.gz

+ cd /tmp

+ basename /dev/mmcblk0p1

+ mpoint=/mnt/mmcblk0p1

+ keep_mpoint=no

+ mkdir /mnt/mmcblk0p1

+ mount /dev/mmcblk0p1 /mnt/mmcblk0p1

+ [ -x /mnt/mmcblk0p1/initialize.sh ]

+ [ -e /mnt/mmcblk0p1/bootf.tgz ]

+ tar xzvf /mnt/mmcblk0p1/bootf.tgz

autoboot.txt

bootmenu.txt

u-boot.bin

uImage

uImage-2.6.27.57-omap1

uImage-3

+ [ -e /mnt/mmcblk0p1/bootfiles.tar.gz ]

+ [ -e /mnt/mmcblk0p1/uimage.tar.gz ]

+ [ -x /mnt/mmcblk0p1/finalize.sh ]

+ [ -e /mnt/mmcblk0p1/rootfs.img -a -e /mnt/mmcblk0p1/rootfs.md5 -a -z ]

+ rootfs_file=/mnt/mmcblk0p1/rootfs.img

+ + cut -chead 1-32 -n

1 /mnt/mmcblk0p1/rootfs.md5

+ rootfs_md5=db16fe789fd21ec4360d2becffbd8800

+ rootfs_mpoint=/mnt/mmcblk0p1

+ keep_mpoint=yes

+ [ yes != yes ]

+ basename /dev/mmcblk0p2

+ mpoint=/mnt/mmcblk0p2

+ keep_mpoint=no

+ mkdir /mnt/mmcblk0p2

+ mount /dev/mmcblk0p2 /mnt/mmcblk0p2

mount: mounting /dev/mmcblk0p2 on /mnt/mmcblk0p2 failed: No such file or directory

+ continue

+ [ -e u-boot.bin ]

+ stat -c %s u-boot.bin

+ size=524288

+ nanddump --omitoob --omitbad -q -l 524288 -f u-boot.bin.flashed /dev/mtd1ro

+ cmp u-boot.bin u-boot.bin.flashed

+ log u-boot.bin already flashed, skipped.

+ echo u-boot.bin already flashed, skipped.

u-boot.bin already flashed, skipped.

+ echo u-boot.bin already flashed, skipped.

+ status_uboot=already there

+ nanddump --omitoob --omitbad -q -f mtd2dump /dev/mtd2ro

+ cmp mtd2dump /usr/local/erasednandblk

+ ubiattach /dev/ubi_ctrl -m 3

UBI device number 0, total 80 LEBs (10321920 bytes, 9.8 MiB), available 0 LEBs (0 bytes), LEB size 129024 bytes (126.0 KiB)

+ mount -t ubifs ubi0:boot /mnt/ubifs

+ handle_kernels

+ ls uImage uImage-2.6.27.57-omap1 uImage-3

+ kernels=uImage

uImage-2.6.27.57-omap1

uImage-3

+ [ -z uImage

uImage-2.6.27.57-omap1

uImage-3 ]

+ cmp uImage /mnt/ubifs/uImage

+ log uImage already flashed, skipped.

+ echo uImage already flashed, skipped.

uImage already flashed, skipped.

+ echo uImage already flashed, skipped.

+ status_uimage=already there

+ cmp uImage-2.6.27.57-omap1 /mnt/ubifs/uImage-2.6.27.57-omap1

+ log uImage-2.6.27.57-omap1 already flashed, skipped.

+ echo uImage-2.6.27.57-omap1 already flashed, skipped.

uImage-2.6.27.57-omap1 already flashed, skipped.

+ echo uImage-2.6.27.57-omap1 already flashed, skipped.

+ status_uimage=already there

+ cmp uImage-3 /mnt/ubifs/uImage-3

+ log uImage-3 already flashed, skipped.

+ echo uImage-3 already flashed, skipped.

uImage-3 already flashed, skipped.

+ echo uImage-3 already flashed, skipped.

+ status_uimage=already there

+ [ -e bootmenu.txt ]

+ cmp bootmenu.txt /mnt/ubifs/bootmenu.txt

+ [ -e autoboot.txt ]

+ cmp autoboot.txt /mnt/ubifs/autoboot.txt

+ umount /mnt/ubifs

+ ubidetach /dev/ubi_ctrl -d 0

+ [ -n /mnt/mmcblk0p1/rootfs.img ]

+ log Calculating checksum, this might take a few minutes..

+ echo Calculating checksum, this might take a few minutes..

Calculating checksum, this might take a few minutes..

+ echo Calculating checksum, this might take a few minutes..

+ + cut -c 1-32

md5sum /mnt/mmcblk0p1/rootfs.img

+ real_md5=b10ffa0458ffc5eeb779b39f8ba0b935

+ [ b10ffa0458ffc5eeb779b39f8ba0b935 = db16fe789fd21ec4360d2becffbd8800 ]

+ log INCORRECT

+ echo INCORRECT

INCORRECT

+ echo INCORRECT

+ cleanup

+ cd /tmp

+ [ -n ]

+ [ -n /mnt/mmcblk0p1 ]

+ umount /mnt/mmcblk0p1

+ false

Sent from my HTC Sensation Z710e using Tapatalk 2

A2000 · Jul 26, 2012

^^^^It seems that ED has rushed updating to the latest version and thereby mixing the checksums before leaving for his holidays. See previous posts.

FaeMinx · Jul 26, 2012

*sigh*

Ok, so what do I have to do to fix this.

Redownloading the file is not an option at this point, and won't be for about a month. I have a very slow temperamental internet connection and I held off downloading any os updates untill this 'final' one was released.

Someone else mentioned changing a file to get the checksums to match. How do I do this?

Please keep in mind I'm no techy so I need everything spelled out in dumb-speak.

Edit: ok, nevermind.... Extracted to a different slightly newer SD card and the checksum error has disappeared.

Sent from my HTC Sensation Z710e using Tapatalk 2

panik · Jul 27, 2012

I had the md5 problem also on a slightly newer version (20120720) than the one talked about on the previous page. I changed the rootfs.md5 file in a text-editor, and now it works.

After unzipping, my rootfs.md5 file reads:

Code:

cb6039cdcdf89738f76b6be1a2536b76 Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20120720-omap3-pandora.ubifs.img

While it should be:

Code:

2180aa90d82992ff52339fe9d9711205 Angstrom-pandora-xfce-image-glibc-ipk-2010.4-test-20120720-omap3-pandora.ubifs.img

If you run into the same problem, the correct md5sum can be spotted in the last part of the update.log. Look for the 'real_md5' part, and copy that to the rootfs.md5 file, replacing the incorrect number. This obviously only works if the download is undamaged. I took my chances. Your mileage may vary.

Gdax · Jul 27, 2012

Thank you Panik for highlighting the rootfs.md5 checksum error.

You just saved my bacon.

Ys

Gdax

NearTao · Jul 27, 2012

Panik's suggestion works, I can confirm. I wouldn't suggest doing this normally though as it is possible to install garbage onto your system.

Looks like ED forgot to update the rootfs.md5 file before leaving. Apparently they don't have a build/package script to do this part of the process, or somebody tried to take a shortcut.

RevBlackie · Jul 28, 2012

Thank you, Panik! I've been pulling my hair out for the past two hours trying to get this thing to flash until I found your solution. Works great!

Linux-SWAT · Jul 29, 2012

About the final-final-final, may i ask which changes were made apart the new kernel ?

EvilDragon · Jul 29, 2012

Linux-SWAT said:
About the final-final-final, may i ask which changes were made apart the new kernel ?

Only one, that's why it's not a new release but still a final:

TI changed the CPU Revision on the new 1GHz units, so the 3D Driver didn't know the CPU and didn't start.

That's the only change here, it doesn't affect any of the old units, it only makes 3D work on the new 1GHz ones.

BTW: You can always check OS changes at git.openpandora.org

Linux-SWAT · Jul 29, 2012

That's what i did... after having posted here.

Also it's not a bad thing to inform everyone ^^.

Zero3K · Jul 30, 2012

How do I upgrade if my Right Shoulder button is broken?

notaz · Jul 30, 2012

Adding autoboot.txt with this content might work:

Code:

fatload mmc1 0:1 ${loadaddr} boot.scr;source ${loadaddr}

But you'll need to remove SD card after flashing, or else it will reflash on every boot.

CapcomSuicide · Jul 30, 2012

notaz said:
Adding autoboot.txt with this content might work:

Code:

fatload mmc1 0:1 ${loadaddr} boot.scr;source ${loadaddr}

But you'll need to remove SD card after flashing, or else it will reflash on every boot.

Cool! That might be useful if a production line was wanting to automate the flash procedure. A few seconds saved at least.

I love the way this community (and Guru's like Notaz) come up with solutions to challenges. (Not to mention in such a quick fashion)

Hopefully Zero3K will let us know how it goes.

Zero3K · Jul 30, 2012

notaz said:
Adding autoboot.txt with this content might work:

Code:

fatload mmc1 0:1 ${loadaddr} boot.scr;source ${loadaddr}

But you'll need to remove SD card after flashing, or else it will reflash on every boot.

It worked. I renamed the autoboot.txt to autoboot.bak so I can rename it back when another firmware upgrade is available.

CapcomSuicide · Jul 31, 2012

Zero3K said:
notaz said:

Adding autoboot.txt with this content might work:

Code:

fatload mmc1 0:1 ${loadaddr} boot.scr;source ${loadaddr}

But you'll need to remove SD card after flashing, or else it will reflash on every boot.

Click to expand...

It worked. I renamed the autoboot.txt to autoboot.bak so I can rename it back when another firmware upgrade is available.

Cool

Nice work Notaz! Maybe that workaround should be added to the wiki?

EvilDragon · Jul 31, 2012

CapcomSuicide said:
notaz said:

Adding autoboot.txt with this content might work:

Code:

fatload mmc1 0:1 ${loadaddr} boot.scr;source ${loadaddr}

But you'll need to remove SD card after flashing, or else it will reflash on every boot.

Cool! That might be useful if a production line was wanting to automate the flash procedure. A few seconds saved at least.

As the Pandoras directly from the production don't have any bootloader on, that wouldn't work

But the special testing / booting SD-Card does exactly that, it boots automatically, does tests, reports failures and flashes the OS automatically

[/CODE]

Click to expand...

captain_coconut · Jul 31, 2012

I had a question about the change in SuperZaxxon with regards to requiring users to explicitly enable the USB host feature. What is the reason for this? I don't believe it makes any difference with power consumption because the USB port seems to be providing power regardless of if you enable USB host in the menu. Is this intended behavior, or is the idea to have the USB port completely turned off?

I noticed this because yesterday I was driving a long distance listening to a Sansa Clip music player when the battery ran out. Since I had my Pandora with me, I turned it on and plugged the Clip into the Pandora USB host and it started charging without me having to enable the USB host feature.

EvilDragon · Aug 1, 2012

USB Host driver is not compatible with suspend-to-RAM, therefore, low-power mode will be used instead of suspend-to-RAM in that case.

Zero3K · Aug 1, 2012

I have been noticing that the console output has been showing during startup and shutdown. It would be nice if it wasn't shown.

Release SuperZaxxon Final released!

Advanced Member

Rainbow Liberation Instigation

Member

Rainbow Liberation Instigation

Member

Still Fresh

Member

Still Fresh

Forum Addict!

Administrator

Forum Addict!

Active Member

Certified Guru

Member

Active Member

Member

Administrator

Member

Administrator

Active Member

Similar threads