-
Hantek MSO5074FG Firmware Upgrade Problem - *** Warning - bad CRC or NAND, using
Posted by dtomazini on 31 Jan, 2015 05:03 -
Hi Guys,
I'm a eletronic hobbyst, familiarized with PIC, ARM, and another microcontrollers. These days, finaly i bought this Hantek MSO5074FG osciloscipe.
After some time usage, tests, and reading the user manual, the same behavior that described by other collegues: Some freezing, dificult with the trigger, etc.. So i decided to apply the firmware upgrade provided by the Equipment Seller from aliexpress. The seller told-me that this firmware was provided by Hantek, and the upgrade is very easy to do.
After reading the user manual:
"Update Firmware
I insert a USB disk with upgrade program and the disk icon at the top left corner is highlighted. Press the Firmware Update button and the Software Upgrade dialog pops up. Push F5 to confim upgrade or push F2 to cancel. "
I follow the instructions, save the attached file "dst1kb_func_hantek_mso5074fg_20141110.0.up" on a USB drive, and start the firmware upgrade process.
This is the file: https://drive.google.com/file/d/0B3cM-n_wYzNmVHN2ZXRGcXNUbDg/view?usp=sharing
The upgrade process occurs normally, take around 5 minutes and a dialog pops up on screen confirming the sucess of upgrade, and asking to restart the equipment.
After the restart, the screen still black (with a low bright), and nothing occurs. The oscope didn't start.
Reading this big topic, i found some help to try undertand why is wrong: https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg472938/#msg472938
KL27x kindly send me the hantek rescue tool (that uses de USB port) and a stock version of the firmware. However unfortunately the computer doesn't recognize the oscilloscope using the USB port.
Using the internal serial port of the osciloscope, a Serial <-> USB adapter connected, and the Putty terminal for windows, i could retrieve this log from the equipment:Code: [Select]*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...
NAND read: device 0 offset 0x300000, size 0x400000
4194304 bytes read: OK
Boot with zImage
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (root@cjh-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 200 9q1-176) ) #62 PREEMPT Mon Aug 19 13:58:30 CST 2013
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: noinitrd ubi.mtd=3 root=ubi0:rootfs rootfstype=ubifs init=/ linuxrc console=ttySAC0 mem=64M
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59772k/59772k available, 5764k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xc4800000 - 0xf6000000 ( 792 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc03e9000 (3972 kB)
.init : 0xc03e9000 - 0xc0409000 ( 128 kB)
.data : 0xc040a000 - 0xc04e6ea0 ( 884 kB)
.bss : 0xc04e6ec4 - 0xc050419c ( 117 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:99
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
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
s3c24xx_i2c_probe
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 65 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
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.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 116
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bi t)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 421 at 0x0000034a0000
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
UBI: attaching mtd3 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 2
UBI: attached mtd3 to ubi0
UBI: MTD device name: "ROOTFS"
UBI: MTD device size: 121 MiB
UBI: number of good PEBs: 967
UBI: number of bad PEBs: 1
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 0
UBI: available PEBs: 954
UBI: total number of reserved PEBs: 13
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 2/1
UBI: image sequence number: -737010380
UBI: background thread "ubi_bgt0d" started, PID 304
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
#0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-02 01:49:30 UTC (946777770)
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(0,0)
Please append a correct "root=" boot option; here are the available partitions:
1f00 1024 mtdblock0 (driver?)
1f01 2048 mtdblock1 (driver?)
1f02 4096 mtdblock2 (driver?)
1f03 123904 mtdblock3 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
So, i believe now that i need to flash the stock firmware using a JTAG (or something), that's wright ?.
Any help will be apreciated.
Cheers
Daniel
-
KL27x kindly send me the hantek rescue tool (that uses de USB port) and a stock version of the firmware. However unfortunately the computer doesn't recognize the oscilloscope using the USB port.
It can't as linux is not running on the device Using the internal serial port of the osciloscope, a Serial <-> USB adapter connected, and the Putty terminal for windows, i could retrieve this log from the equipment:
Code: [Select]*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mode.!
SD:File System init failed!
Start Linux ...
That's the good news: the bootloader is still OK so you can try flashing rootfs via USB. That depends on the size and the type of your stock firmware. If it's a nand dump (about 128Mb) you can't as this feature is limited by the size of the RAM (64Mb on your scope). You would then need to flash it via JTAG.
If your firmware file is about 60MB that will be OK. You will need another PC connected via USB, the transfer tool program (DNW) plus the drivers for your system (special ones).
What OS do you have on your PC?
To enter download mode you need to switch on and stop the boot process by pressing space key (you may have to try several times to find the right timing).
-
Hi fremen67,
Here is the files size:
"dst1kb_func_hantek_mso5074fg_20141110.0.up" - 4.288.512 bytes (4,08 MB) - This one i receive from the Seller (and brick the oscope after uptade)
"dst1kb_mso5074fg_fact140616.0.up" - 1.503.232 bytes (1,43 MB) - This one i receive from KL27x
Booth files are in my google drive: https://drive.google.com/folderview?id=0B3cM-n_wYzNmfk81RmxqandGOHBkWldKYU0tbDhqZTFQWDZUS0V2U2VFSlRsTmFONXJsRE0&usp=sharing
I have one J-Link from Segger that i use with ARM micro-controller boards, but i have no idea how to use in this oscilloscope. I can use 2 PCs with Windows 7.
Please, this is the DNW tool that you said: http://www.friendlyarm.net/downloads ?.
Follow attached some pictures from inside the MSO5074FG.
Regards
Daniel
-
Booting the osciloscope, ans pressing the "space key", i got this menu:Code: [Select]*** Warning - bad CRC or NAND, using default environment
##### EmbedSky BIOS for SKY2416/TQ2416 #####
This Board: SDRAM is 64MB; LCD display size is: 800 X 480
Press Space key to Download Mod 0!
SD and FAT initialize success!
sizeof(LineC)=160
Without this file
return -1
c=255
Without EmbedSky.ini !
##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection:
Hoewever don't know how to transform the "dst1kb_mso5074fg_fact140616.0.up" file in a linux image.
Att;
Daniel -
Hi fremen67,
Hi Daniel,
Here is the files size:
"dst1kb_func_hantek_mso5074fg_20141110.0.up" - 4.288.512 bytes (4,08 MB) - This one i receive from the Seller (and brick the oscope after uptade)
"dst1kb_mso5074fg_fact140616.0.up" - 1.503.232 bytes (1,43 MB) - This one i receive from KL27x
Booth files are in my google drive: https://drive.google.com/folderview?id=0B3cM-n_wYzNmfk81RmxqandGOHBkWldKYU0tbDhqZTFQWDZUS0V2U2VFSlRsTmFONXJsRE0&usp=sharing
I have one J-Link from Segger that i use with ARM micro-controller boards, but i have no idea how to use in this oscilloscope. I can use 2 PCs with Windows 7.
Please, this is the DNW tool that you said: http://www.friendlyarm.net/downloads ?.
The 2 files are not firmware files but only firmware update files. They just include some updated files for your MSO. They are useless for your problem as it does not come from a faulty file but from a faulty file system.
The file you need is the UBIFS image for your system (root.ubi). I doubt Hantek will provide it to you. So the best solution would be to find someone with the same model and hardware than yours who would be able to provide you with a nand dump of his rootfs file system (root.bin, 121MB). Than you will have to convert it to a UBIFS file , which you should be able to flash with the bootloader (using DNW and the USB connection). I can help you later on with the root.bin to root.ubi file conversion and for the flashing part but at the moment you need a full backup of a similar MSO.
Maybe KL27x or Lauris (https://www.eevblog.com/forum/testgear/hantek-mso5074fg/msg593315/#msg593315 ) would be able to provide you with a dump of their rootfs partition... All they have to do is to insert an USB stick and type "nanddump -l 0x7900000 -f /mnt/udisk/root.bin /dev/mtd3" (be careful that some version of nandump are not working so they may have to use another version of it)
The JTAG port is J901 but you don't need it at the moment.
-
Now i clearly understood, thank you. Perhaps that i have a serious trouble here
. How Hantek can made this crap upgrade routine ??. This is oscilloscope is my first and my last Hantek.
I will send a message for KL27x or Lauris asking if they could get the dump.
After install the USB drivers for DNW and test it, i believe that everything is ok to made the download. Please look these logs:
DWN:Code: [Select]===== USB DEVICE STATUS =====
USB_CONFIGURATION_DESCRIPTOR
bLength = 0x9, decimal 9
bDescriptorType = 0x2 ( USB_CONFIGURATION_DESCRIPTOR_TYPE )
wTotalLength = 0x20, decimal 32
bNumInterfaces = 0x1, decimal 1
bConfigurationValue = 0x1, decimal 1
iConfiguration = 0x0, decimal 0
bmAttributes = 0x80 ( USB_CONFIG_BUS_POWERED )
MaxPower = 0x19, decimal 25
-----------------------------
USB_INTERFACE_DESCRIPTOR #0
bLength = 0x9
bDescriptorType = 0x4 ( USB_INTERFACE_DESCRIPTOR_TYPE )
bInterfaceNumber = 0x0
bAlternateSetting = 0x0
bNumEndpoints = 0x2
bInterfaceClass = 0xff
bInterfaceSubClass = 0x0
bInterfaceProtocol = 0x0
bInterface = 0x0
-----------------------------
USB_ENDPOINT_DESCRIPTOR for Pipe00
bLength = 0x7
bDescriptorType = 0x5 ( USB_ENDPOINT_DESCRIPTOR_TYPE )
bEndpointAddress= 0x81 ( INPUT )
bmAttributes= 0x2 ( USB_ENDPOINT_TYPE_BULK )
wMaxPacketSize= 0x200, decimal 512
bInterval = 0x0, decimal 0
-----------------------------
USB_ENDPOINT_DESCRIPTOR for Pipe01
bLength = 0x7
bDescriptorType = 0x5 ( USB_ENDPOINT_DESCRIPTOR_TYPE )
bEndpointAddress= 0x3 ( OUTPUT )
bmAttributes= 0x2 ( USB_ENDPOINT_TYPE_BULK )
wMaxPacketSize= 0x200, decimal 512
bInterval = 0x0, decimal 0
-----------------------------
Putty Terminal:Code: [Select]##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: a
Now, Please connect to USB cable and USB interface!
USB cable Connected!
Thks;
Daniel -
As I wrote to dtomazini, taking root dump would be possible in my case, just need more info on entering dump command. Is it done only over inside UART port or there are more ways?
Lauris -
After install the USB drivers for DNW and test it, i believe that everything is ok to made the download. Please look these logs:
Putty Terminal:Code: [Select]##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: a
Now, Please connect to USB cable and USB interface!
USB cable Connected!
It seems to be OK. If you want to go a step further and really want to try to send a file from DNW , use the "t" option (Test Linux Image) on the hdg side. Don't go on with the "a" option as you did as if the tranfer succeeds than the next step would be a nand format. The "a" option writes a test program on the nand, which you don't want !
For the "t" option, it doesn't matter the file you send for the test. You will see the tranfer and of course your HDG won't recognize this file as a valid one but it won't erase nor write on the flash. You will get an error like:
"Wrong Image Format for bootm command
ERROR: can't get kernel image!"
You will be sure that the file tranfer is working. -
Thanks for the advise, now i will use the "t" option before anything.
About the Lauris doubt, is there a way to get the roots image using the USB connection ?, or another way without disassemble the equipment ?.
I read this article http://embdev.net/articles/Tekway_MSO#MSO_firmware_backup , here the authors make a back-up using the MSO Back-up Tools.
Tks;
Daniel -
Thanks for the advise, now i will use the "t" option before anything.
Yes this was written by Tinhead who started "Hantek - Tekway - DSO hack - get 200MHz bw for free" but it will not work on your scope. You need a special tool for MSO5074FG.
About the Lauris doubt, is there a way to get the roots image using the USB connection ?, or another way without disassemble the equipment ?.
I read this article http://embdev.net/articles/Tekway_MSO#MSO_firmware_backup , here the authors make a back-up using the MSO Back-up Tools.
Tks;
Daniel
I had a look in the 2 upgrade files you posted and I doubt there were made for your model.
The partition layout of your scope is the standard one for Hantek/Tekway DSO/MSO as you can see in your logs, that is 4 partitions:
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
Rootfs is usually mounted using /dev/mtd3
In your upgrade packages, the usual special "update" script calls 2 scripts:
- do_update.sh
- do_update_general.sh
The surprising thing is the content of do_update_general.sh:Code: [Select]#!/bin/bash
flash_eraseall /dev/mtd4
nandwrite -p dev/mtd4 /tmp/tekwayup_client/zImage
cp -rf /tmp/tekwayup_client/dso/ /
cp -rf /tmp/tekwayup_client/etc/ /
cp -rf /tmp/tekwayup_client/icon/ /
cp -rf /tmp/tekwayup_client/lib/ /
mv /tmp/tekwayup_client/tdc/* /
tar xvf /tmp/tekwayup_client/lib.tar.gz -C /
#tar xvf /mnt/udisk/arm.tar.bz2 -C /usr/
sync
sync
It starts erasing the /dev/mtd4 partition that you do not have, so I would guess destroying instead your /dev/mtd3 partition. That would explain why your scope doesn't boot anymore.
So I suppose Hantek changed the partition layout on the last MSO5074FG, as they did on the HDG2000 AWG series. They added new partitions to ease the update and recovery process.
We could try rebuilding your scope using dumps from another MSO5074FG but the hardware has to match too.
I will package and post a backup tool compatible with your MSO5074fg that dumps up to 9 partitions, that should be enough.
-
As I wrote to dtomazini, taking root dump would be possible in my case, just need more info on entering dump command. Is it done only over inside UART port or there are more ways?
Lauris
You can backup your MSO5074FG via the backup tool attached so you don't have to open it.
- Unzip the file and copy dst1kb_backup_tool_mso5074fg.up to the root directory of a USB stick
- Check that you don't have other files beginning with "dst1kb" on the root directory of your USB stick
- Connect the USB stick to your scope
- Go to Utility Menu
- Select Update Firmware
- Confirm
This will last some minutes and your scope will reboot at the end.
You will find the backup files in the /dump directory of the USB stick. Just zip this directory and post it somewhere we can download it.
Thanks!
-
Hello,
Here are dump from my scope: Google_drive_dir hope it will help.
My scope info:
Model: MSO5074FG
SW version: 3.2.35(141110.0)
HW version: 10020x5402820510002 -
Thanks a lot Lauris !!
-
Hello,
Thanks a lot! That was quick
Here are dump from my scope: Google_drive_dir hope it will help.
My scope info:
Model: MSO5074FG
SW version: 3.2.35(141110.0)
HW version: 10020x5402820510002
This is indeed a new partition layout with a recovery partition like the HDG2000.
One partition is missing and this is the most important, the "recover" one. I had a quick look in the uboot dump (mtd0.bin) and the layout is as follows:
mtdparts=nandflash0:1024k@0(uboot),512k(params),2048K(logo),512k(misc),4m(kernel),70m(rootfs),4m(kernel_bk),46m(recover)
The missing file is mtd7.bin which should have a size of 46Mb (All files together should be 128Mo)
In order to have a clean recovery of the system, we need mtd0.bin (uboot), mtd6.bin (kernel_bk) and mtd7.bin (recover)
Maybe I made a tipo in the backup script...
I will check this evening when back home.
Edit: or maybe the MSO rebooted before the write on the USB sticks was completely finished.. I could also add some syncs at the end of the script... -
Nice job, i'm impressed with all this knowledge !!.
Let me ask, looking on the first error log:Code: [Select]...
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bi t)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 421 at 0x0000034a0000
Creating 4 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "Bootloader"
0x000000100000-0x000000300000 : "LOGO"
0x000000300000-0x000000700000 : "Kernel"
0x000000700000-0x000008000000 : "ROOTFS"
...
Perhaps the error is in the Kernal partition ( 0x000000300000-0x000000700000 : "Kernel" ) on "Bad eraseblock 421 at 0x0000034a0000".
So if i try to flhash the kernel again, using the mtd4.bin file (4mb), can i leave the situation worst than it is now ? , is better i wait for the a new dump, including the mtd7.bin ?.
[]'s
Daniel -
Perhaps the error is in the Kernal partition ( 0x000000300000-0x000000700000 : "Kernel" ) on "Bad eraseblock 421 at 0x0000034a0000".
I don't think so. Uboot is the only partition where you are not supposed to find bad blocks (at least where it could cause a problem). Having bad blocks elsewhere on a nand flash is normal. it's annoying as you can't simply clone a nand to another one. Is does not always work. That's why you need things like a .ubi file. It does not only contain the data but also a file system in it and uboot deals with bad blocks when writing such files to the nand.So if i try to flhash the kernel again, using the mtd4.bin file (4mb), can i leave the situation worst than it is now ? , is better i wait for the a new dump, including the mtd7.bin ?.
It won't do any good as the partition layout has changed and anyway the kernel partition will be recreated during the recovery process. But on the other hand, it will allow you to test the DNW transfer process without taking to many risks (you can also check dnw with the test kernel option). If the flash fails when updating uboot you will have to use the JTAG solution.
At the moment 2 of the 3 partitions could be flashed:
- You can update uboot with mtd0.bin (using DNW) by choosing option [1], and then reboot and stop again with space bar
- You will have new options in the menu, choose this one: "[6] Download Kernel_bk (kernel_bk.bin)" and send mtd6.bin with DNW
The next step would be to choose "[7] Download UBIFS image (recover.ubi) to Nand Flash" and send the recover.ubi file that I will create with mtd7.bin ... when I have it.
And the last step would be to choose "[9] recover start!" that will recreate all the other partitions from scratch.
I will post a modified script so that we can get the missing file. -
Hello,
Hello Lauris
Here are dump from my scope: Google_drive_dir hope it will help.
My scope info:
Model: MSO5074FG
SW version: 3.2.35(141110.0)
HW version: 10020x5402820510002
Could you run another backup with the attached modified script? I swaped the partition backup order so that it starts now with mtd7.bin and added a 10 sec sleep at the end of the script to allow some time for the usb stick to finish ongoing writes. Let's hope it will be OK now...
Thank you !
-
Hi Guys,
I'm validating the DNW test mode, with the "mtd4.bin", and the result LOG is this:Code: [Select]##### Boot for SKY2416/TQ2416 Main Menu #####
##### EmbedSky USB download mode #####
[1] Download u-boot or STEPLDR.nb1 or other bootloader to Nand Flash
[2] Download Eboot (eboot.nb0) to Nand Flash
[3] Download Linux Kernel (zImage.bin) to Nand Flash
[4] Download LOGO Picture (logo.bin) to Nand Flash
[5] Download UBIFS image (root.ubi) to Nand Flash
[6] Download YAFFS image (root.bin) to Nand Flash
[7] Download Program to SDRAM and Run it
[8] Boot the system
[9] Format the Nand Flash
[0] Set the boot parameters
[a] Download User Program
[n] Enter TFTP download mode menu
[r] Reboot u-boot
[t] Test Linux Image (zImage)
Enter your selection: t
Now, Please connect to USB cable and USB interface!
USB cable Connected!
Now, Waiting for DNW to transmit data.
Now, Downloading [ADDRESS:0xc0008000,TOTAL:0x400000]
Please waiting ................................................................Download Done!!
Download Address: 0xc0008000, Download Filesize:0x400000
Now, Checksum calculation....
Checksum O.K !!!
Boot with zImage
Is this Checksum O.K a indication that booth MSO5074FG are the same model and hardware ?. I can get a bit less worried ?
Quote- You can update uboot with mtd0.bin (using DNW) by choosing option [1], and then reboot and stop again with space bar
- You will have new options in the menu, choose this one: "[6] Download Kernel_bk (kernel_bk.bin)" and send mtd6.bin with DNW
Ok, all updates with Checksum O.K . The new option "6" cames after the uboot update.
-
Is this Checksum O.K a indication that booth MSO5074FG are the same model and hardware ?. I can get a bit less worried ?
No it just says that you did not get the data corrupted during the tranfer from DNW to the MSOOk, all updates with Checksum O.K . The new option "6" cames after the uboot update.
Good news! One step left to go ...
BTW do you know the Firmware and Hardware versions you had?
-
No i didn't remenber the firmware and hardware version. I wrote it on a piece of paper to compare with the firmware upgrade file, but i lost this paper... .Is there a way to retrieve this information from the oscilloscope ?.
On the XILINX board there is a number: "DDS V1.00.2"
PS.: Using the "GNU Privacy Assistant" for Windows, now i understood (just a litle bit
) and could retrieve the content of .up files !!!. Thanks again EEV forum.
-
Hello,
New dump, same folder dump_2015_02_03.rar archive. Hope this will work better, if not - will be possible to take new dump next week.
Lauris -
Hello,
New dump, same folder dump_2015_02_03.rar archive. Hope this will work better, if not - will be possible to take new dump next week.
Lauris
Thanks again Lauris !!!
Tonight i will test it.
Att;
Daniel -
Hello,
New dump, same folder dump_2015_02_03.rar archive. Hope this will work better, if not - will be possible to take new dump next week.
Lauris
Thank you, it is a full dump now
-
At the moment 2 of the 3 partitions could be flashed:
- You can update uboot with mtd0.bin (using DNW) by choosing option [1], and then reboot and stop again with space bar
- You will have new options in the menu, choose this one: "[6] Download Kernel_bk (kernel_bk.bin)" and send mtd6.bin with DNW
The next step would be to choose "[7] Download UBIFS image (recover.ubi) to Nand Flash" and send the recover.ubi file that I will create with mtd7.bin ... when I have it.
And the last step would be to choose "[9] recover start!" that will recreate all the other partitions from scratch.
I will post a modified script so that we can get the missing file.
@dtomazini: OK Daniel, we have to move from plan A to plan B.
The recover partition has not been updated with roofs+kernel backup by Hantek so it is useless at the moment and we can't launch the recovery process.
Plan B:
mtd0: uboot: you already restored it -> OK
mtd1: params: when unavailable, uboot will take default parameters (backup already empty anyway) -> Nothing to do
mtd2: logo: empty but you can restore it -> Restore with option [2] and mtd2.bin
mtd3: misc: to be erased -> Erase with option [3]
mtd4: kernel: need to be restored -> Restore with option [4] and mtd4.bin
mtd5: rootfs: need to be restored -> Restore with option [5] and rootfs.ubi you will get from me
mtd6: kernel_bk: need to be restored -> Restore with option [6] and mtd6.bin
mtd7: restore: need to be restored -> Restore with option [7] and recover.ubi you will get from me
After that just do a normal start with option [8] and cross your fingers.
I your hardware is the same as Lauris, then you are good
I PM you the link to download rootfs.ubi and recover.ubi.
Good luck! -
Everything done !!, the oscilloscope is now working !!!.
Awsome job fremen67 !!. Thanks a lot to You, Lauris and KL27x !!.
Here is the log, after de reboot:Code: [Select]NAND read: device 0 offset 0x400000, size 0x400000
4194304 bytes read: OK
Boot with zImage
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Linux version 3.2.35 (liuqian@ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-176) ) #115 PREEMPT Mon Nov 10 10:24:50 CST 2014
CPU: ARM926EJ-S [41069265] revision 5 (ARMv5TEJ), cr=00053177
CPU: VIVT data cache, VIVT instruction cache
Machine: SMDK2416
Ignoring unrecognised tag 0x54410008
Memory policy: ECC disabled, Data cache writeback
CPU S3C2416/S3C2450 (id 0x32450003)
S3C24XX Clocks, Copyright 2004 Simtec Electronics
CPU: MPLL on 800.000 MHz, cpu 400.000 MHz, mem 133.333 MHz, pclk 66.666 MHz
CPU: EPLL on 96.000 MHz, usb-bus 48.000 MHz
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 16256
Kernel command line: noinitrd ubi.mtd=5 root=ubi0:rootfs rootfstype=ubifs init=/linuxrc console=ttySAC0 lcd=X480Y272
PID hash table entries: 256 (order: -2, 1024 bytes)
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 64MB = 64MB total
Memory: 59288k/59288k available, 6248k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
vmalloc : 0xc4800000 - 0xf6000000 ( 792 MB)
lowmem : 0xc0000000 - 0xc4000000 ( 64 MB)
modules : 0xbf000000 - 0xc0000000 ( 16 MB)
.text : 0xc0008000 - 0xc03f1000 (4004 kB)
.init : 0xc03f1000 - 0xc0412000 ( 132 kB)
.data : 0xc0412000 - 0xc0560020 (1337 kB)
.bss : 0xc0560044 - 0xc057dd7c ( 120 kB)
SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:107
irq: clearing subpending status 00000003
irq: clearing subpending status 00000002
Calibrating delay loop... 198.45 BogoMIPS (lpj=496128)
pid_max: default: 4096 minimum: 301
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
S3C2416: Initializing architecture
S3C2416: IRQ Support
S3C24XX DMA Driver, Copyright 2003-2006 Simtec Electronics
DMA channel 0 at c4804000, irq 88
DMA channel 1 at c4804100, irq 89
DMA channel 2 at c4804200, irq 90
DMA channel 3 at c4804300, irq 91
DMA channel 4 at c4804400, irq 92
DMA channel 5 at c4804500, irq 93
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
s3c-i2c s3c2410-i2c: slave address 0x10
s3c-i2c s3c2410-i2c: bus frequency set to 9 KHz
s3c-i2c s3c2410-i2c: i2c-0: S3C I2C adapter
Advanced Linux Sound Architecture Driver Version 1.0.24.
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
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.
s3c-adc s3c24xx-adc: attached adc driver
msgmni has been set to 115
io scheduler noop registered (default)
io scheduler cfq registered
s3c-fb s3c-fb: window 0: fb
s3c-fb s3c-fb: LCD type is TN83 800*480, default_bpp=16, pixclock=5
s3c2440-uart.0: ttySAC0 at MMIO 0x50000000 (irq = 70) is a S3C2440
console [ttySAC0] enabled
s3c2440-uart.1: ttySAC1 at MMIO 0x50004000 (irq = 73) is a S3C2440
s3c2440-uart.2: ttySAC2 at MMIO 0x50008000 (irq = 76) is a S3C2440
s3c2440-uart.3: ttySAC3 at MMIO 0x5000c000 (irq = 94) is a S3C2440
loop: module loaded
S3C24XX NAND Driver, (c) 2004 Simtec Electronics
info->cpu_type=3, tacls_max=8
s3c24xx-nand s3c2416-nand: Tacls=3, 22ns Twrph0=7 52ns, Twrph1=3 22ns
s3c24xx-nand s3c2416-nand: System booted from NAND
s3c24xx-nand s3c2416-nand: NAND ECC disabled
NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-bit)
NAND_ECC_NONE selected by board driver. This is not recommended!
Scanning device for bad blocks
Bad eraseblock 421 at 0x0000034a0000
Creating 8 MTD partitions on "NAND":
0x000000000000-0x000000100000 : "uboot"
0x000000100000-0x000000180000 : "params"
0x000000180000-0x000000380000 : "logo"
0x000000380000-0x000000400000 : "misc"
0x000000400000-0x000000800000 : "kernel"
0x000000800000-0x000004e00000 : "rootfs"
0x000004e00000-0x000005200000 : "kernel_bk"
0x000005200000-0x000008000000 : "recover"
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
UBI: max. sequence number: 268
UBI: attached mtd5 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 70 MiB
UBI: number of good PEBs: 559
UBI: number of bad PEBs: 1
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 0
UBI: total number of reserved PEBs: 559
UBI: number of PEBs reserved for bad PEB handling: 5
UBI: max/mean erase counter: 2/1
UBI: image sequence number: 0
UBI: background thread "ubi_bgt0d" started, PID 330
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
s3c2410-ohci s3c2410-ohci: S3C24XX OHCI
s3c2410-ohci s3c2410-ohci: new USB bus registered, assigned bus number 1
s3c2410-ohci s3c2410-ohci: irq 42, io mem 0x49000000
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
usbcore: registered new interface driver usblp
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
s3c-hsudc s3c-hsudc: bound driver g_serial
samsung-ts s3c2416-ts: driver attached, registering input device
input: S3C24XX TouchScreen as /devices/virtual/input/input0
S3C24XX RTC, (c) 2004,2006 Simtec Electronics
s3c-rtc s3c2410-rtc: rtc disabled, re-enabling
s3c-rtc s3c2410-rtc: rtc core: registered s3c as rtc0
i2c /dev entries driver
S3C2410 Watchdog Timer, (c) 2004 Simtec Electronics
s3c2410-wdt s3c2410-wdt: watchdog inactive, reset disabled, irq disabled
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
s3c-sdhci s3c-sdhci.1: clock source 0: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 1: hsmmc (133333333 Hz)
s3c-sdhci s3c-sdhci.1: clock source 2: hsmmc-if (24000000 Hz)
mmc0: SDHCI controller on samsung-hsmmc [s3c-sdhci.1] using ADMA
S3C24XX_UDA134X SoC Audio driver
UDA134X SoC Audio Codec
asoc: uda134x-hifi <-> s3c24xx-iis mapping ok
ALSA device list:
#0: S3C24XX_UDA134X
TCP cubic registered
NET: Registered protocol family 17
Registering the dns_resolver key type
s3c-rtc s3c2410-rtc: setting system clock to 2000-01-05 22:09:32 UTC (947110172)
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 68440064 bytes (66836 KiB, 65 MiB, 539 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
Freeing init memory: 132K
g_serial gadget: high-speed config #1: Generic Serial config
dso-iobank: install ok
0x505
gpio_major_n = 5, io_minor_n = 5, output 0
0x603
gpio_major_n = 6, io_minor_n = 3, output 0
0x309
gpio_major_n = 3, io_minor_n = 9, output 0
0x70a
gpio_major_n = 7, io_minor_n = 10, output 0
dso5000b fpga configure init
FPGA0_nCONFIG set config = -15
FPGA0_nSTATUS set config = -16
FPGA0_CONF_DONE set config = -16
FPGA0_nCONFIG set pull = 2
FPGA0_nSTATUS set pull = 2
FPGA1_nCONFIG set config = -15
FPGA1_nSTATUS set config = -16
FPGA1_CONF_DONE set config = -14
FPGA1_nCONFIG set pull = 2
FPGA1_nSTATUS set pull = 2
fpga0:status: 0x0
FPGA0 CONFIGURE DATA DOWN finish.
FPGA0 CONFIGURE Ok.
fpga1:status: 0x1
FPGA1 CONFIGURE DATA DOWN finish.
FPGA1 CONFIGURE Ok.
0x8090
0x1
fpga bank 11811dso-fpga: install ok
0x8090
0x1
fpga bank 11811dso-fpga-la: install ok
dm9000 Ethernet Driver, V1.31
dm9000 dm9000: eth%d: Invalid ethernet MAC address. Please set using ifconfig
eth0: dm9000b at c4988300,c498a308 IRQ 48 MAC: ba:b2:87:0d:4c:7e (random)
bkl tq2416-backlight initialized done...
dso-buzzer s3c2416-beep initialized done...
make snd node.
dm9000 dm9000: eth0: link down
--------------------------------------------------------------------------------
start
--------------------------------------------------------------------------------
filename=/lib/firmware/pll_125M.mif, filenamelen=26
pllset[0].data=0xc000
pllset[1].data=0xc001
pllset[2].data=0xc002
pllset[3].data=0xc003
pllset[4].data=0xc104
pllset[5].data=0xc105
pllset[6].data=0xc006
pllset[7].data=0xc107
pllset[8].data=0xc108
pllset[9].data=0xc009
pllset[10].data=0xc00a
pllset[11].data=0xc00b
pllset[12].data=0xc00c
pllset[13].data=0xc00d
pllset[14].data=0xc00e
pllset[15].data=0xc00f
pllset[16].data=0xc010
pllset[17].data=0xc111
pllset[18].data=0xc112
pllset[19].data=0xc013
pllset[20].data=0xc014
pllset[21].data=0xc015
pllset[22].data=0xc016
pllset[23].data=0xc017
pllset[24].data=0xc018
pllset[25].data=0xc019
pllset[26].data=0xc01a
pllset[27].data=0xc01b
pllset[28].data=0xc01c
pllset[29].data=0xc01d
pllset[30].data=0xc01e
pllset[31].data=0xc01f
pllset[32].data=0xc020
pllset[33].data=0xc021
pllset[34].data=0xc022
pllset[35].data=0xc023
pllset[36].data=0xc024
pllset[37].data=0xc025
pllset[38].data=0xc026
pllset[39].data=0xc027
pllset[40].data=0xc028
pllset[41].data=0xc029
pllset[42].data=0xc02a
pllset[43].data=0xc12b
pllset[44].data=0xc12c
pllset[45].data=0xc02d
pllset[46].data=0xc02e
pllset[47].data=0xc02f
pllset[48].data=0xc030
pllset[49].data=0xc031
pllset[50].data=0xc032
pllset[51].data=0xc033
pllset[52].data=0xc134
pllset[53].data=0xc135
pllset[54].data=0xc036
pllset[55].data=0xc037
pllset[56].data=0xc038
pllset[57].data=0xc039
pllset[58].data=0xc03a
pllset[59].data=0xc03b
pllset[60].data=0xc03c
pllset[61].data=0xc13d
pllset[62].data=0xc13e
pllset[63].data=0xc03f
pllset[64].data=0xc040
pllset[65].data=0xc041
pllset[66].data=0xc042
pllset[67].data=0xc043
pllset[68].data=0xc044
pllset[69].data=0xc045
pllset[70].data=0xc146
pllset[71].data=0xc147
pllset[72].data=0xc048
pllset[73].data=0xc049
pllset[74].data=0xc04a
pllset[75].data=0xc04b
pllset[76].data=0xc04c
pllset[77].data=0xc04d
pllset[78].data=0xc04e
pllset[79].data=0xc14f
pllset[80].data=0xc150
pllset[81].data=0xc051
pllset[82].data=0xc052
pllset[83].data=0xc053
pllset[84].data=0xc054
pllset[85].data=0xc055
pllset[86].data=0xc056
pllset[87].data=0xc057
pllset[88].data=0xc158
pllset[89].data=0xc159
pllset[90].data=0xc05a
pllset[91].data=0xc05b
pllset[92].data=0xc05c
pllset[93].data=0xc05d
pllset[94].data=0xc05e
pllset[95].data=0xc05f
pllset[96].data=0xc060
pllset[97].data=0xc161
pllset[98].data=0xc162
pllset[99].data=0xc063
pllset[100].data=0xc064
pllset[101].data=0xc065
pllset[102].data=0xc066
pllset[103].data=0xc067
pllset[104].data=0xc068
pllset[105].data=0xc069
pllset[106].data=0xc16a
pllset[107].data=0xc16b
pllset[108].data=0xc06c
pllset[109].data=0xc06d
pllset[110].data=0xc06e
pllset[111].data=0xc06f
pllset[112].data=0xc070
pllset[113].data=0xc071
pllset[114].data=0xc072
pllset[115].data=0xc173
pllset[116].data=0xc174
pllset[117].data=0xc075
pllset[118].data=0xc076
pllset[119].data=0xc077
pllset[120].data=0xc078
pllset[121].data=0xc079
pllset[122].data=0xc07a
pllset[123].data=0xc07b
pllset[124].data=0xc17c
pllset[125].data=0xc17d
pllset[126].data=0xc17e
pllset[127].data=0xc07f
pllset[128].data=0xc080
pllset[129].data=0xc081
pllset[130].data=0xc082
pllset[131].data=0xc083
pllset[132].data=0xc084
pllset[133].data=0xc085
pllset[134].data=0xc086
pllset[135].data=0xc087
pllset[136].data=0xc088
pllset[137].data=0xc089
pllset[138].data=0xc08a
pllset[139].data=0xc08b
pllset[140].data=0xc08c
pllset[141].data=0xc08d
pllset[142].data=0xc08e
pllset[143].data=0xc08f
filename=/lib/firmware/pll_100M.mif, filenamelen=26
pllset[0].data=0xa000
pllset[1].data=0xa001
pllset[2].data=0xa002
pllset[3].data=0xa003
pllset[4].data=0xa104
pllset[5].data=0xa105
pllset[6].data=0xa006
pllset[7].data=0xa107
pllset[8].data=0xa108
pllset[9].data=0xa009
pllset[10].data=0xa00a
pllset[11].data=0xa00b
pllset[12].data=0xa00c
pllset[13].data=0xa00d
pllset[14].data=0xa00e
pllset[15].data=0xa00f
pllset[16].data=0xa010
pllset[17].data=0xa111
pllset[18].data=0xa112
pllset[19].data=0xa013
pllset[20].data=0xa014
pllset[21].data=0xa015
pllset[22].data=0xa016
pllset[23].data=0xa017
pllset[24].data=0xa018
pllset[25].data=0xa019
pllset[26].data=0xa01a
pllset[27].data=0xa01b
pllset[28].data=0xa01c
pllset[29].data=0xa01d
pllset[30].data=0xa01e
pllset[31].data=0xa01f
pllset[32].data=0xa020
pllset[33].data=0xa021
pllset[34].data=0xa022
pllset[35].data=0xa023
pllset[36].data=0xa024
pllset[37].data=0xa025
pllset[38].data=0xa026
pllset[39].data=0xa027
pllset[40].data=0xa028
pllset[41].data=0xa029
pllset[42].data=0xa02a
pllset[43].data=0xa12b
pllset[44].data=0xa12c
pllset[45].data=0xa02d
pllset[46].data=0xa02e
pllset[47].data=0xa02f
pllset[48].data=0xa030
pllset[49].data=0xa031
pllset[50].data=0xa032
pllset[51].data=0xa033
pllset[52].data=0xa134
pllset[53].data=0xa135
pllset[54].data=0xa036
pllset[55].data=0xa037
pllset[56].data=0xa038
pllset[57].data=0xa039
pllset[58].data=0xa03a
pllset[59].data=0xa03b
pllset[60].data=0xa03c
pllset[61].data=0xa13d
pllset[62].data=0xa13e
pllset[63].data=0xa03f
pllset[64].data=0xa040
pllset[65].data=0xa041
pllset[66].data=0xa042
pllset[67].data=0xa043
pllset[68].data=0xa044
pllset[69].data=0xa045
pllset[70].data=0xa146
pllset[71].data=0xa147
pllset[72].data=0xa048
pllset[73].data=0xa049
pllset[74].data=0xa04a
pllset[75].data=0xa04b
pllset[76].data=0xa04c
pllset[77].data=0xa04d
pllset[78].data=0xa04e
pllset[79].data=0xa14f
pllset[80].data=0xa150
pllset[81].data=0xa051
pllset[82].data=0xa052
pllset[83].data=0xa053
pllset[84].data=0xa054
pllset[85].data=0xa055
pllset[86].data=0xa056
pllset[87].data=0xa057
pllset[88].data=0xa158
pllset[89].data=0xa159
pllset[90].data=0xa05a
pllset[91].data=0xa05b
pllset[92].data=0xa05c
pllset[93].data=0xa05d
pllset[94].data=0xa05e
pllset[95].data=0xa05f
pllset[96].data=0xa060
pllset[97].data=0xa161
pllset[98].data=0xa162
pllset[99].data=0xa063
pllset[100].data=0xa064
pllset[101].data=0xa065
pllset[102].data=0xa066
pllset[103].data=0xa067
pllset[104].data=0xa068
pllset[105].data=0xa069
pllset[106].data=0xa16a
pllset[107].data=0xa16b
pllset[108].data=0xa06c
pllset[109].data=0xa06d
pllset[110].data=0xa06e
pllset[111].data=0xa06f
pllset[112].data=0xa070
pllset[113].data=0xa071
pllset[114].data=0xa072
pllset[115].data=0xa173
pllset[116].data=0xa174
pllset[117].data=0xa075
pllset[118].data=0xa076
pllset[119].data=0xa077
pllset[120].data=0xa078
pllset[121].data=0xa079
pllset[122].data=0xa07a
pllset[123].data=0xa07b
pllset[124].data=0xa17c
pllset[125].data=0xa17d
pllset[126].data=0xa17e
pllset[127].data=0xa07f
pllset[128].data=0xa080
pllset[129].data=0xa081
pllset[130].data=0xa082
pllset[131].data=0xa083
pllset[132].data=0xa084
pllset[133].data=0xa085
pllset[134].data=0xa086
pllset[135].data=0xa087
pllset[136].data=0xa088
pllset[137].data=0xa089
pllset[138].data=0xa08a
pllset[139].data=0xa08b
pllset[140].data=0xa08c
pllset[141].data=0xa08d
pllset[142].data=0xa08e
pllset[143].data=0xa08f
Erasing 128 Kibyte @ 80000 - 100% complete..
mkdir: can't create directory '/param': File exists
mkdir: can't create directory '/param/sav': File exists
mkdir: can't create directory '/param': File exists
mkdir: can't create directory '/param/sav': File exists
Thu Jan 1 00:00:00 UTC 2009
p_pth->pthid[PTH_ID_SCAN_KEYBOARD]=1189733520
p_pth->pthid[PTH_ID_DISP_WAVE]=1180914832
p_pth->pthid[PTH_ID_ACQ]=1198122128
p_pth->pthid[PTH_ID_PC_UART]=1207301264
mount: mounting 192.168.1.22:/home/nfsroot on /mnt/nfs failed: No route to host
Att;
Daniel