Agilent N9320B stuck at boot: accessed boot prompt and need advice  - Page 1
Forum section: electronics / repair

author: analogRF
author_rank: Super Contributor
timestamp: November 17, 2019, 07:41:18 pm
content: recently I got this N9320B in an auction (supposedly came from a university) that does not boot. It gets stuck at the Keysight splash screen (after passing the Agilent splash screen)There was nothing on the USB and LAN connections at the back either (were not detected).So I opened it up and first all voltages on the base motherboard are fine (clearly marked test points). So I got the main cpu board out, which also contains the entire IF and RBW filters and DSP sections of the SA, took it out of its shield (after unscrewing a zillion screws) and installed it back so I can do some limited measurements on the board. Still access is a bit limited due to the PSU being close to it.Attached pictures show the CPU board that Agilent call it DIF board, by the way.There are quite a number of DC-DC converters and voltage regulators on this board which I identified and measured all of them. ALL are OKThe battery ONLY connects to a DS1390 RTC (presumably for keeping the time/date) It does not power any memory as far as I can tellI found a MAX232 chip and observed some activities on the pin 11 (T1 input) and on the corresponding pin 14 (T1 out). So I connected my Bus Pirate to pins 11 and 12 (on the TTL side) of the MAX232 and set up UART connection with 115200 baud and bingoI got the boot prompt.Here is what happens:Code:VxWorks System BootCopyright 1984-2004 Wind River Systems, Inc.CPU: Sharp lh7a404Version: VxWorks5.5.1BSP version: 1.0/0Creation date: Oct 1 2008, 10:51:53Press any key to stop auto-boot...0auto-booting...boot device : tffs=0,0unit number : 0processor number : 0host name : hostfile name : /tffs0/VxWorksinet on ethernet (e) : 192.168.0.111host inet (h) : 192.168.0.100user (u) : targetftp password (pw) : targetflags (f) : 0x8other (o) : csnetAttaching to TFFS... done.Loading /tffs0/VxWorks...3414320Starting at 0xc0001000...Attaching interface lo0... doneAttached IPv4 interface to csnet unit 0USB2 Host Stack Initialized.USB Hub Driver InitializedUSBD Wind River Systems, Inc. 560 Initialized1 OHCI Controller found.Waiting to attach to USBD...Done.Adding 6135 symbols for standalone.0xc1effe68 (tRootTask): usbBulkDevInit() returned OKVxWorksCopyright 1984-2002 Wind River Systems, Inc.CPU: Sharp lh7a404Runtime Name: VxWorksRuntime Version: 5.5.1BSP version: 1.0/0Created: Feb 1 2013, 13:54:17WDB Comm Type: WDB_COMM_ENDWDB: Ready.The flash is: S29GL512PusbTMCDevInit() returned OK.-> initkey semtake semabcINT failedtaskSpawn keyTask succsesstaskSpawn powerTask succsesstaskSpawn GpibSendData succsesstaskSpawn GpibSendData succsessuglEpson13506_16BitDevCreate...uglEpson13506_16BitDevCreate...OKuglEpsonModeSet...uglEpsonSetRegs...mode=0i=0,reg[1,0]i=1,reg[508,0]i=2,reg[4,0]i=3,reg[8,0]i=4,reg[16,1]i=5,reg[20,18]i=6,reg[24,0]i=7,reg[28,2]i=8,reg[30,1]i=9,reg[32,1]i=10,reg[33,0]i=11,reg[42,1]i=12,reg[43,1]i=13,reg[48,37]i=14,reg[49,0]i=15,reg[50,79]i=16,reg[52,3]i=17,reg[53,1]i=18,reg[54,11]i=19,reg[56,223]i=20,reg[57,1]i=21,reg[58,44]i=22,reg[59,10]i=23,reg[60,1]i=24,reg[64,5]i=25,reg[65,0]i=26,reg[66,0]i=27,reg[67,0]i=28,reg[68,0]i=29,reg[70,128]i=30,reg[71,2]i=31,reg[72,0]i=32,reg[74,25]i=33,reg[75,60]i=34,reg[80,79]i=35,reg[82,19]i=36,reg[83,1]i=37,reg[84,11]i=38,reg[86,223]i=39,reg[87,1]i=40,reg[88,43]i=41,reg[89,9]i=42,reg[90,1]i=43,reg[91,24]i=44,reg[96,5]i=45,reg[98,0]i=46,reg[99,0]i=47,reg[100,0]i=48,reg[102,128]i=49,reg[103,2]i=50,reg[104,0]i=51,reg[106,59]i=52,reg[107,60]i=53,reg[112,0]i=54,reg[113,1]i=55,reg[114,0]i=56,reg[115,0]i=57,reg[116,0]i=58,reg[117,0]i=59,reg[118,0]i=60,reg[119,0]i=61,reg[120,0]i=62,reg[122,31]i=63,reg[123,63]i=64,reg[124,31]i=65,reg[126,0]i=66,reg[128,0]i=67,reg[129,1]i=68,reg[130,0]i=69,reg[131,0]i=70,reg[132,0]i=71,reg[133,0]i=72,reg[134,0]i=73,reg[135,0]i=74,reg[136,0]i=75,reg[138,31]i=76,reg[139,63]i=77,reg[140,31]i=78,reg[142,0]i=79,reg[256,0]i=80,reg[257,0]i=81,reg[258,0]i=82,reg[259,0]i=83,reg[260,0]i=84,reg[261,0]i=85,reg[262,0]i=86,reg[264,0]i=87,reg[265,0]i=88,reg[266,0]i=89,reg[268,0]i=90,reg[269,0]i=91,reg[272,0]i=92,reg[273,0]i=93,reg[274,0]i=94,reg[275,0]i=95,reg[276,0]i=96,reg[277,0]i=97,reg[280,0]i=98,reg[281,0]i=99,reg[480,0]i=100,reg[482,0]i=101,reg[496,0]i=102,reg[497,0]i=103,reg[500,0]i=104,reg[508,1]uglEpsonModeSet...OK0xc1effe68 (tRootTask): memPartFree: invalid block 0x2c6c6c75 in partition 0xc023a3f8.0xc1effe68 (tRootTask): memPartFree: invalid block 0xc14b8d1c in partition 0xc023a3f8.0xc1effe68 (tRootTask): memPartFree: invalid block 0x8000011c in partition 0xc023a3f8.0xc1effe68 (tRootTask): memPartFree: invalid block 0xc14b8934 in partition 0xc023a3f8.Undefined instructionException address: 0xc1791854Current Processor Status Register: 0x00000010Task: 0xc1effe68 "tRootTask"I cannot quite figure out what my problem could beI am an absolute idiot when it comes to these embedded system stuff. Maybe some experts out there can interpret the results and tell me how to proceed...My guess is that either the memory (SRAM) is bad which would be a very good news or the FLASH ROM is corrupted which for me is perhaps the end of this adventureSome further information: the main processor has 80KB of on chip SRAM and a boot ROM in it too.after the boot stopped I pressed enter and got this -> prompt and ran some information gathering commands which you can see here:Code:.....Undefined instructionException address: 0xc1791854Current Processor Status Register: 0x00000010Task: 0xc1effe68 "tRootTask"-> moduleShowMODULE NAME MODULE ID GROUP # TEXT START DATA START BSS START--------------- ---------- ---------- ---------- ---------- ----------usb488.out 0xc18d74e8 1 0xc179b350 0xc18b4814 0xc18c5480SA.out 0xc14b8f6c 2 0 0 0value = 0 = 0x0-> ls0xc18f1940 (tShell): memPartAlloc: block too big - 99 in partition 0xc023a3f8.value = -1 = 0xffffffff-> versionVxWorks (for Sharp lh7a404) version 5.5.1.Kernel: WIND version 2.6.Made on Feb 1 2013, 13:54:17.Boot line:tffs=0,0(0,0)host:/tffs0/VxWorks h=192.168.0.100 e=192.168.0.111 f=0x8 u=target pw=target o=csnetvalue = 109 = 0x6d = 'm'->->-> devsdrv name0 /null1 /tyCo/01 /tyCo/13 /tffs05 host:6 /bpf/dhcpc/06 /bpf/dhcpc/16 /bpf/dhcpc/26 /bpf/dhcpc/36 /bpf/dhcpc-arp9 /viovalue = 25 = 0x19->->-> lkupNumber of Symbols : 8464Symbol Mutex Id : 0xc18f4bb4Symbol Hash Id : 0xc18f438cSymbol memPartId : 0xc023a3f8Name Clash Policy : Allowedvalue = 0 = 0x0->->-> taskShowNAME ENTRY TID PRI STATUS PC SP ERRNO DELAY---------- ------------ -------- --- ---------- -------- -------- ------- -----tRootTask usrRoot c1effe68 0 SUSPEND c1791854 0 110003 0value = 0 = 0x0->It seems the firmware is made in 2013 but agilent has had firmware updates in 2014, 2015, and the last one was 2017. So my guess is that it was not corrupted during a firmware update (I know this device was decommissioned not too long ago definitely not 5-6 years ago)also when I press a key and stop the auto boot, I get these after typing ? help command:Code:Version: VxWorks5.5.1BSP version: 1.0/0Creation date: Oct 1 2008, 10:51:53Press any key to stop auto-boot...1[VxWorks Boot]: ?? - print this list@ - boot (load and go)p - print boot paramsc - change boot paramsl - load boot fileg adrs - go to adrsd adrs[,n] - display memorym adrs - modify memoryf adrs, nbytes, value - fill memoryt adrs, adrs, nbytes - copy memorye - print fatal exceptionv - print boot logo with versionn netif - print network interface device address$dev(0,procnum)host:/file h=# e=# b=# g=# u=usr [pw=passwd] f=#tn=targetname s=script o=otherboot device: tffs=drive,removable file name: /tffs0/vxWorksBoot flags:0x02 - load local system symbols0x04 - don't autoboot0x08 - quick autoboot (no countdown)0x20 - disable login security0x40 - use bootp to get boot parameters0x80 - use tftp to get boot image0x100 - use proxy arpavailable boot devices:Enhanced Network Devicescsnet0 tffs[VxWorks Boot]:any advice is highly appreciatedEDIT: funny, someone spelled success wrong

author: analogRF
author_rank: Super Contributor
timestamp: November 19, 2019, 04:18:10 pm
content: any hint or suggestion?I am planning to replace the SRAM chips first just out of desperation and see what happens. ordered the chip from China...but if it is the flash EPROM being corrupted, is there any way to fix it?is there any way to program the firmware into it? I think the boot loader is inside the CPU....any help would be wonderful...

author: analogRF
author_rank: Super Contributor
timestamp: November 20, 2019, 03:01:37 pm
content: almost 100 reads and no suggestionit seems I have the option of changing boot parameters and perhaps force it to boot from tftpdoes anybody know if and how this is possible? do I need a boot image (like a .bin file) of the whole flash eprom on a local tftp server?can I do anything with the firmeware downloaded from keysight?

author: TheSteve
author_rank: Unknown
timestamp: November 20, 2019, 06:16:08 pm
content: Having no experience with a N9320B or VxWorks to any real extent it is hard to offer advice. It would be nice to know what the boot messages look like on a functioning unit. It does seem quite possible there is a ram issue or it is flash corruption.If it was mine I would certainly be experimenting with the tftp option to recovery it.

author: analogRF
author_rank: Super Contributor
timestamp: November 20, 2019, 06:23:50 pm
content: Quote from: TheSteve on November 20, 2019, 06:16:08 pmyes that's what I am thinking about but how? I have seen people reviving modem's with tftp booting but they have a single .bin file for the firmwarefor now i am waiting for the SRAM to arrive and try to replace them...but flash corruption seems more likely

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 20, 2019, 07:57:04 pm
content: Don't give up yet, that is nor flash and your system boots, so you can get a new chip and program it with the current contents, and then do a firmware upgrade.What firmware versions from keysight do you have? Do you have the same that is installed? i only found the latest 2017-04-13 B.03.61I would do a copy of the entire memory using the commands you found, and compare it to a keysight upgrade file.I would remove the chip and back it up anyway.If i were confident that the copy i made is the same as in the physical chip, i would try a firmware update (DON'T try this before making a backup of the contents of the actual chip, even if you have to remove it)Since it boots and the usb subsystem is listed as working in your logs, it might recognize a usb flash drive prepared for the firmware update.Try keeping a key pressed while booting, for example preset.Ask keysight if there is a full reset key while booting, or a bad firmware recovery procedure?

author: analogRF
author_rank: Super Contributor
timestamp: November 20, 2019, 08:30:08 pm
content: Quote from: YetAnotherTechie on November 20, 2019, 07:57:04 pmi am not giving up at all. i didn't get what you meant hereQuoteif the current content is corrupted somehow, then the new chip will have the same issue, no? maybe I misunderstood...I only have the latest firmware from keysight website. If you unzip it it has a bunch of .out modules and .txt files which are config files and a single VxWorks file with no extension. plus a couple of directories including all the texts that the SA shows on screen and some .jpg imagestrying to reflash it from usb is a good point. I didn't try because it is not the normal way of firmware update (it is done through the system menus when it is working) but I also suspect that there might be a back door that let me reflash it at power on. The problem is that even though the boot sequence showed LAN and USB were enabled, when I connected them to my computer (back USB host connector) or to my LAN I got no activityby that I mean Agilent IO and connection expert could not find the instrument. So maybe my way of testing was wrong. But I got no new IP listed on my network so I could not even ping it.I have asked help from Keysight support but no answer yet. Although i didn't ask specifically about a trick to firmware update at boot. That would be wonderful...I will ask them when they answer my request and conversation gets going

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 20, 2019, 09:35:00 pm
content: I tought you would give up because of this:Quote from: analogRF on November 20, 2019, 06:23:50 pmYour flash is a NOR chip, it has a one-to-one relation between contents inside and what it outputs, NAND flash has contents + error correction and even if you had the firmware it would be much harder to figure out how to program a new chip.The analyser has an embedded file system, is not a linear program like small micros, it's like your hard disk, and your logs say that there is an error in one of the partitions (a logical division of that disk)Since your system boots, a firmware upgrade might do something similar to formatting the disk and writing it entirely again, which might work, if there is no longer a hardware fault in the chip.It might fail even if there is no fault, only corruption. Some embedded systems rewrite the partition scheme, some don't. In that case you need to make an image of the file system, and load it on linux, analyse the partition scheme, etc, etc, a lot of work, (think data-recovery) and i'm a beginner at that.What i suggested was to create a dump of the chip you have and compare it to some of the files in the keysight upgrade, more specifically the VxWorks file, of course they won't match unless you have the same version, but should be similar.Your SA.out file seems corrupted, but is it the file, or the partition? who knows...Try pinging 192.168.0.100 or 192.168.0.111, for this to work you need to set up your pc to have a fixed IP in the range 192.168.0.1xx and connect directly to the SA.if it doesn't ping you should still try a tftp server program to connect. Don't write anything until you hava a backup of your flash.Until you have a copy of the flash, there's not much anyone can do to help you. And if you loose the working copy you have then no one can help you, because you probably loose instrument specific data. Good luck, and patience!

author: analogRF
author_rank: Super Contributor
timestamp: November 20, 2019, 09:41:33 pm
content: the only programmer that I have is TL866 II which seems unable to read or write TSOP56 flash chips :-(any suggestion for a programmer that is not too expensive?

author: analogRF
author_rank: Super Contributor
timestamp: November 20, 2019, 09:43:12 pm
content: isnt there any online command that can be used to dump the whole firmware from the system?

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 21, 2019, 12:28:57 am
content: I also only have the tl866. My solution would be to use an adapter board and read the chip 4 or 8 times, as needed, by setting the unconnected high address lines manually.Try the d adrs[,n] commandd 0x00000000, 0x3FFFFFF post resultsd 0xc0000000, 0x3FFFFFF post resultswith SA off, plug an USB drive, empty except for one file named test.txt, drive should be one of keysight recommended list, or at most 1gb,boot and post the result of the same steps you showed on your first post.Are there any other flash chips inside?

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 21, 2019, 12:53:49 pm
content: try:memShow - Display allocated/free memorymemPartS0how - Show memory partitionsemShow - Show info about semaphori - Display synopsis of all taskstaskshow - List info about the tasks from TCBpwd - Present working directoryls - list the directory

author: analogRF
author_rank: Super Contributor
timestamp: November 21, 2019, 12:54:14 pm
content: I was looking inside that VxWorks file that comes with the downloaded firmware, and I noticed that these texts are in there:"WIND version 2.6", "VxWorks version 5.5.1", "Feb 1 2013, 13:54:17"These are exactly what I get when I run the "version" command when I am connected to the instrument (see my first post) so at least the OS part of the firmware seems to be the same as the latest version on keysight website but this might have also been used in older versions of the firmware, too. I don't know the version of SA software modules...another thing I noticed is that N9320B is mentioned inside the vxworks file! does it mean the OS is customized for this instrument? I thought the vxworks is a general OS.i don;t know why I cannot run the "ls" command to see the content of current directory. See the error that I got in my first post...you can see that there are two boot devices, one is the tffs which I assume is the file system residing on the flash and the other one is csnet0I wonder how I can change my boot parameters to use csnet0 for booting and how I can use that to boot from a location on network? is that used for booting through tftp? I would like to try this route and maybe bypass the flash chip and boot the system. but i dont know how to set it all upI am thinking just putting the raw unpacked firmware somewhere and point the instrument to boot from that directory on, for example, on my laptop. Can somebody help me to set it up?

author: analogRF
author_rank: Super Contributor
timestamp: November 21, 2019, 12:55:57 pm
content: Quote from: YetAnotherTechie on November 21, 2019, 12:53:49 pmplease see my first post. I did all these commands and reported the results. some of them did not work and were "unknown" so I didnt report thembut i did try all these commands that you just mentioned except the "i" command

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 21, 2019, 01:05:09 pm
content: I'm new to vxworks, but from what i read, if it could recognize pendrive, then loading a file would be much easier. It would show up on the ""available boot devices:" line.Try "ls" on other devices/directories to see if it's the command or the folders fault.

author: analogRF
author_rank: Super Contributor
timestamp: November 21, 2019, 02:19:54 pm
content: I also notice that in my boot log I have this line : "Loading /tffs0/VxWorks...3414320"but the size of the vxworks file that is in the firmware package is 3142892since I am now pretty sure the same vxworks file is used in the current system (see post #12) then, does it mean it is de-compressed when loadedor does it mean it is corrupted and the size is wrong?!

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 21, 2019, 08:20:28 pm
content: Quote from: analogRF on November 21, 2019, 02:19:54 pmFrom what i read if it was compressed it would have a name with an extension, so i've no idea if it's good or bad.TrytffsShowtffsShowAllusrFdiskPartShow "/tffs0"dosFsShow "/tffs0"alternatives /tffs0/ /tffs /tffs/Lll

author: analogRF
author_rank: Super Contributor
timestamp: November 24, 2019, 09:04:46 pm
content: some update and more disappointmentI put a FAT32 formatted USB drive into the front USB port and as you can see here, the instrument recognized it and i believe it is mounted as /db0 device.Code:VxWorks System BootCopyright 1984-2004 Wind River Systems, Inc.CPU: Sharp lh7a404Version: VxWorks5.5.1BSP version: 1.0/0Creation date: Oct 1 2008, 10:51:53Press any key to stop auto-boot...0auto-booting...boot device : tffs=0,0unit number : 0processor number : 0host name : hostfile name : /tffs0/VxWorksinet on ethernet (e) : 192.168.0.111host inet (h) : 192.168.0.100user (u) : targetftp password (pw) : targetflags (f) : 0x8other (o) : csnetAttaching to TFFS... done.Loading /tffs0/VxWorks...3414320Starting at 0xc0001000...Attaching interface lo0... doneAttached IPv4 interface to csnet unit 0USB2 Host Stack Initialized.USB Hub Driver InitializedUSBD Wind River Systems, Inc. 560 Initialized1 OHCI Controller found.Waiting to attach to USBD...Done.Adding 6135 symbols for standalone.0xc1effe68 (tRootTask): usbBulkDevInit() returned OKVxWorksCopyright 1984-2002 Wind River Systems, Inc.CPU: Sharp lh7a404Runtime Name: VxWorksRuntime Version: 5.5.1BSP version: 1.0/0Created: Feb 1 2013, 13:54:17WDB Comm Type: WDB_COMM_ENDWDB: Ready.The flash is: S29GL512PusbTMCDevInit() returned OK.-> Found Bulk Device with 1 Logical Units at node 2initkey semtake semabcINT failedtaskSpawn keyTask succsesstaskSpawn powerTask succsesstaskSpawn GpibSendData succsesstaskSpawn GpibSendData succsessuglEpson13506_16BitDevCreate...uglEpson13506_16BitDevCreate...OKuglEpsonModeSet...uglEpsonSetRegs...mode=0i=0,reg[1,0]i=1,reg[508,0]i=2,reg[4,0]i=3,reg[8,0]i=4,reg[16,1]i=5,reg[20,18]i=6,reg[24,0]i=7,reg[28,2]i=8,reg[30,1]i=9,reg[32,1]i=10,reg[33,0]i=11,reg[42,1]i=12,reg[43,1]i=13,reg[48,37]i=14,reg[49,0]i=15,reg[50,79]i=16,reg[52,3]i=17,reg[53,1]i=18,reg[54,11]i=19,reg[56,223]i=20,reg[57,1]i=21,reg[58,44]i=22,reg[59,10]i=23,reg[60,1]i=24,reg[64,5]i=25,reg[65,0]i=26,reg[66,0]i=27,reg[67,0]i=28,reg[68,0]i=29 ,reg[70,128]i=30,reg[71,2]i=31,reg[72,0] /bd0 Bulk device is createdi=32,reg[74,25]i=33,reg[75,60]i=34,reg[80,79]i=35,reg[82,19]i=36,reg[83,1]i=37,reg[84,11]i=38,reg[86,223]i=39,reg[87,1]i=40,reg[88,43]i=41,reg[89,9]i=42,reg[90,1]i=43,reg[91,24]i=44,reg[96,5]i=45,reg[98,0]i=46,reg[99,0]i=47,reg[100,0]i=48,reg[102,128]i=49,reg[103,2]i=50,reg[104,0]i=51,reg[106,59]i=52,reg[107,60]i=53,reg[112,0]i=54,reg[113,1]i=55,reg[114,0]i=56,reg[115,0]i=57,reg[116,0]i=58,reg[117,0]i=59,reg[118,0]i=60,reg[119,0]i=61,reg[120,0]i=62,reg[122,31]i=63,reg[123,63]i=64,reg[124,31]i=65,reg[126,0]i=66,reg[128,0]i=67,reg[129,1]i=68,reg[130,0]i=69,reg[131,0]i=70,reg[132,0]i=71,reg[133,0]i=72,reg[134,0]i=73,reg[135,0]i=74,reg[136,0]i=75,reg[138,31]i=76,reg[139,63]i=77,reg[140,31]i=78,reg[142,0]i=79,reg[256,0]i=80,reg[257,0]i=81,reg[258,0]i=82,reg[259,0]i=83,reg[260,0]i=84,reg[261,0]i=85,reg[262,0]i=86,reg[264,0]i=87,reg[265,0]i=88,reg[266,0]i=89,reg[268,0]i=90,reg[269,0]i=91,reg[272,0]i=92,reg[273,0]i=93,reg[274,0]i=94,reg[275,0]i=95,reg[276,0]i=96,reg[277,0]i=97,reg[280,0]i=98,reg[281,0]i=99,reg[480,0]i=100,reg[482,0]i=101,reg[496,0]i=102,reg[497,0]i=103,reg[500,0]i=104,reg[508,1]uglEpsonModeSet...OK0xc1effe68 (tRootTask): memPartFree: invalid block 0xc1487240 in partition 0xc023a3f8.0xc1effe68 (tRootTask): memPartFree: invalid block 0x8000011c in partition 0xc023a3f8.0xc1effe68 (tRootTask): memPartFree: invalid block 0xc1486de8 in partition 0xc023a3f8.Undefined instructionException address: 0xc1486e04Current Processor Status Register: 0x00000010Task: 0xc1effe68 "tRootTask"after it stops, I executed these commands at the prompt and here are the results:Code:-> devsdrv name0 /null1 /tyCo/01 /tyCo/13 /tffs05 host:6 /bpf/dhcpc/06 /bpf/dhcpc/16 /bpf/dhcpc/26 /bpf/dhcpc/36 /bpf/dhcpc-arp9 /vio3 /bd0value = 25 = 0x19-> moduleShowMODULE NAME MODULE ID GROUP # TEXT START DATA START BSS START--------------- ---------- ---------- ---------- ---------- ----------usb488.out 0xc18d7398 1 0xc179b200 0xc18b46c4 0xc18c5330SA.out 0xc1487490 2 0 0 0value = 0 = 0x0-> iNAME ENTRY TID PRI STATUS PC SP ERRNO DELAY---------- ------------ -------- --- ---------- -------- -------- ------- -----tRootTask usrRoot c1effe68 0 SUSPEND c1486dec 0 110003 0tExcTask excTask c1bf25b4 0 PEND c01ce7fc c1bf24bc 0 0tLogTask logTask c1befc38 0 PEND c01ce7fc c1befb50 0 0tNbioLog c012443c c1bed5a8 0 PEND c0063ea0 c1bed4f8 0 0tShell shell c18f1940 1 READY c0188b68 c18f15d4 110001 0tWdbTask wdbTask c18f3b50 3 PEND c0063ea0 c18f3a84 0 0tUSBVbusMonc1892474 c179b058 5 DELAY c0187a90 c179af8c 0 2tUSBEP0Intrc1892474 c14ddcb0 5 PEND c0063ea0 c14ddbfc 0 0tUSBTargIntc1892474 c14e5e58 10 PEND c0063ea0 c14e5da4 0 0tNetTask netTask c1bc56b8 50 PEND c0063ea0 c1bc5654 0 0tPortmapd portmapd c1b17664 54 PEND c0063ea0 c1b17490 3d0002 0tTelnetd telnetd c1b14ba0 55 PEND c0063ea0 c1b14abc 0 0tFtpdTask c0080a00 c1b126bc 55 PEND c0063ea0 c1b1257c 0 0tDhcpcStatec0079274 c1b1a174 56 PEND c0063ea0 c1b1a0ec 0 0tDhcpcReadTdhcpcRead c1b18bec 56 PEND c0063ea0 c1b18a08 3d0002 0tUglInput uglInputTask c148c980 60 PEND+T c0063ea0 c148c65c 3d0002 60GPIBINT GpibIntHande c14c6a88 90 PEND c0063ea0 c14c6a24 0 0PowerMonitopowerTask c14d5b08 99 PEND c0063ea0 c14d5aac 0 0tTffsPTask flPollTask c1bebce8 100 DELAY c0187a90 c1bebc70 0 5t1 c013fa34 c190f8b4 100 PEND c01ce7fc c190f788 0 0usbOhciIsr c0167dd8 c1906e20 100 PEND c0063ea0 c1906dbc 0 0BusM A c014abc0 c1904bf0 100 DELAY c0187a90 c1904b6c 0 1BULK_CLASS c013fa34 c19024a4 100 PEND c01ce7fc c1902278 0 0BULK_CLASS_c013fa34 c18fdd88 100 PEND c01ce7fc c18fdcc8 0 0tBulkClnt c0018e38 c18f9af8 100 PEND c0063ea0 c18f9a70 0 0usbTMCLib c013fa34 c18e1134 100 PEND c01ce7fc c18e0f08 0 0usbTMCLib_Ic013fa34 c18dca18 100 PEND c01ce7fc c18dc958 0 0keytask keypadRead c18ce964 100 PEND c0063ea0 c18ce8f4 0 0GPIBOUTPUT GpibSendData c14ce160 106 PEND c0063ea0 c14ce0fc 0 0tDcacheUpd dcacheUpd c1bc914c 250 DELAY c0187a90 c1bc90b4 0 9value = 0 = 0x0->->->-> pwdhost:value = 6 = 0x6->->-> ls0xc18f1940 (tShell): memPartAlloc: block too big - 99 in partition 0xc023a3f8.value = -1 = 0xffffffff->-> cd "/db0"0xc18f1940 (tShell): memPartAlloc: block too big - 5 in partition 0xc023a3f8.not enough memory for new string.->->-> cd "/tffs0"0xc18f1940 (tShell): memPartAlloc: block too big - 7 in partition 0xc023a3f8.not enough memory for new string.->->-> cd /db0syntax error->-> ll0xc18f1940 (tShell): memPartAlloc: block too big - 99 in partition 0xc023a3f8.value = -1 = 0xffffffff->-> fdiskundefined symbol: fdisk-> taskShowNAME ENTRY TID PRI STATUS PC SP ERRNO DELAY---------- ------------ -------- --- ---------- -------- -------- ------- -----tShell shell c18f1940 1 READY c0188b68 c18f15d4 110001 0value = 0 = 0x0->->-> ti tRootTaskNAME ENTRY TID PRI STATUS PC SP ERRNO DELAY---------- ------------ -------- --- ---------- -------- -------- ------- -----tRootTask usrRoot c1effe68 0 SUSPEND c1486dec 0 110003 0stack: base 0xc1effe68 end 0xc1efc018 size 15940 high 14400 margin 1540options: 0x6VX_UNBREAKABLE VX_DEALLOC_STACKVxWorks Events--------------Events Pended on : Not PendedReceived Events : 0x0Options : N/Ar0 = 4 r1 = c04feea0 r2 = 807c3d3a r3 = c1efb008r4 = 0 r5 = c1effb6c r6 = c1487490 r7 = 0r8 = c023a3f8 r9 = 0 r10 = 74732df8 r11/fp = 74732df8r12/ip = 0 r13/sp = 0 r14/lr = ffffffff pc = c1486deccpsr = 10Undefined instructionvalue =0Exception address: 0x = 0xc1486decCurrent Processor Status Register: 0x000000010->checkStackNAME ENTRY TID SIZE CUR HIGH MARGIN------------ ------------ -------- ----- ----- ----- ------tRootTask usrRoot c1effe68 15940 1168 14400 1540tExcTask excTask c1bf25b4 7988 248 1008 6980tLogTask logTask c1befc38 4988 232 908 4080tNbioLog 0x00c012443c c1bed5a8 4988 176 236 4752tShell shell c18f1940 64860 876 3924 60936tWdbTask wdbTask c18f3b50 8180 204 264 7916tUSBVbusMon 0x00c1892474 c179b058 32756 204 260 32496tUSBEP0Intr 0x00c1892474 c14ddcb0 32756 180 240 32516tUSBTargIntr 0x00c1892474 c14e5e58 32752 180 240 32512tNetTask netTask c1bc56b8 9988 100 416 9572tPortmapd portmapd c1b17664 9988 468 652 9336tTelnetd telnetd c1b14ba0 7988 228 288 7700tFtpdTask 0x00c0080a00 c1b126bc 6132 320 380 5752tDhcpcStateT 0x00c0079274 c1b1a174 4984 136 196 4788tDhcpcReadTa dhcpcRead c1b18bec 4984 484 668 4316tUglInput uglInputTask c148c980 4084 804 864 3220GPIBINT GpibIntHande c14c6a88 29992 100 160 29832PowerMonitor powerTask c14d5b08 30704 92 152 30552tTffsPTask flPollTask c1bebce8 2036 120 296 1740t1 0x00c013fa34 c190f8b4 16380 300 732 15648usbOhciIsr 0x00c0167dd8 c1906e20 8180 100 400 7780BusM A 0x00c014abc0 c1904bf0 8184 132 728 7456BULK_CLASS 0x00c013fa34 c19024a4 16372 556 1772 14600BULK_CLASS_I 0x00c013fa34 c18fdd88 16368 192 252 16116tBulkClnt 0x00c0018e38 c18f9af8 19988 136 948 19040usbTMCLib 0x00c013fa34 c18e1134 16372 556 616 15756usbTMCLib_IR 0x00c013fa34 c18dca18 16368 192 14332 2036keytask keypadRead c18ce964 30712 112 200 30512GPIBOUTPUT GpibSendData c14ce160 29988 100 200 29788tDcacheUpd dcacheUpd c1bc914c 4988 152 328 4660INTERRUPT 1792 0 304 1488 - SVC -256 0 24 232 - IRQ -value = 43 = 0x2b = '+'-> memShowundefined symbol: memShow-> memPartShowundefined symbol: memPartShow->-> chkdsk "/tffs0"0xc18f1940 (tShell): memPartAlloc: block too big - 7 in partition 0xc023a3f8.not enough memory for new string.-> ioHelpcd "path" Set current working pathpwd Print working pathls ["wpat"[,long]] List contents of directoryll ["wpat"] List contents of directory - long formatlsr ["wpat"[,long]] Recursive list of directory contentsllr ["wpat"] Recursive detailed list of directoryrename "old","new" Change name of filecopy ["in"][,"out"] Copy in file to out file (0 = std in/out)cp "wpat","dst" Copy many files to another dirxcopy "wpat","dst" Recursively copy filesmv "wpat","dst" Move files into another directoryxdelete "wpat" Delete a file, wildcard list or treeattrib "path","attr" Modify file attributesxattrib "wpat","attr" Recursively modify file attributeschkdsk "device", L, V Consistency check of file systemdiskInit "device" Initialize file system on diskdiskFormat "device" Low level and file system disk format"attr" contains one or more of: " + - A H S R" characters"wpat" may be name of a file, directory or wildcard patternin which case "dst" must be a directory namechkdsk() params: L=0, check only, L=2, check and fix, V=0x200 verbosevalue = 1 = 0x1-> chkdsk "/tffs0"0xc18f1940 (tShell): memPartAlloc: block too big - 7 in partition 0xc023a3f8.not enough memory for new string.-> chkdsk "/db0"0xc18f1940 (tShell): memPartAlloc: block too big - 5 in partition 0xc023a3f8.not enough memory for new string.if you compare with what I had before in the first post, you see the difference which is not much except the USB stick is now a new drivethe problem is there is no way I can access or point to not only the USB device (/db0) but to any part of the file system, when I try commandslike "ll", "ls", "cd" or "chkdsk" etc...for /db0 or /tffs0 I get a memory allocation error. (see above)but about the disappointment, unfortunately I am no longer able to halt the boot loader and stop the boot process in order to change boot parameters anymore. In the beginning there was a message (after VxWorks title) that "press any key to stop auto-boot..." but that is now disappeared and no matter how fast I pound on the keyboard I am not able to stop auto-bootingI played with boot parameters and tried (with my limited knowledge) to force it to load the boot file from USB but I was very careful not to play with anything else other than the boot device and boot file name (I did not change the boot flag and it is the same as before) and I reversed everything back but somehow I found out that I am not getting that "press any key to stop auto boot" message and I am not able to stop auto boot...so setting up tftp is now out of the window...although i dont think it would have helped anyway...you see, the system loads the VxWorks into memory and runs quite a bit of stuff but my guess is that when it tries to free memory or partition memory in a certain section of memory it gets stuck because it receives garbage perhaps...I think one of the RAM chips might be bad and when it tries to use its address space it gets stuck...i don't know...

author: analogRF
author_rank: Super Contributor
timestamp: November 24, 2019, 09:12:39 pm
content: anybody know how I can get that stop auto-booting option back?can anybody show me a forum that vxworks people hang around and might know this?I tried google for hours but didnt find anythingstill I dont know how that could have happened. The boot loader as I understand resides inside the cpuand then it loads the main vxworks file for this system from the flash chip...

author: analogRF
author_rank: Super Contributor
timestamp: November 24, 2019, 09:20:45 pm
content: Quote from: YetAnotherTechie on November 21, 2019, 01:05:09 pmI noticed that it does not show up in the boot devices. In fact I found out that at that time during initial boot up (I assume from the boot loader inside the CPU perhaps) actually the USB device is not known at all (only ethernet is known as csnet0 device)Later on after loading the VxWorks into memory from the flash chip and running it, the system initializes USB and finds the drive...EDIT: I was thinking the same and that got me in trouble because i tried to play with those damn parameters and even though I cannot think of doing anything that might have resulted "fast boot only" but apparently it is what has occurred...boot parameters on scree still show up exactly as before though...

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: November 25, 2019, 01:01:25 am
content: I noticed that the bad memory locations decreased from 4 to 3 right?So, crazy idea, plug as many devices as you can in usb ports, use a hub if you have to, if it's ram, maybe it will shift the bad memory to a different task and you can do something.

author: analogRF
author_rank: Super Contributor
timestamp: November 25, 2019, 12:35:30 pm
content: yes for some reason there are three lines giving allocation error instead of 4 but that doesnt mean anything. These are the same error I get when I try to execute any file/directory command like "cd", "ls" ...now that I am no longer able to stop the autobooting, reading the boot file from tftp is not possible but, like I said, I dont really think the firmware is corrupted. It is indeed loading the kernel into memory, the problem however is that it gets corrupted IN the memory I think.for now I am waiting for the memory chips to show up and try to replace them and see what happens...I am pretty much out of options after that...I ran the serial number on keysight website and i found out that the instrument had a 3 month replacement guarantee between Oct 2, 2017 to Jan 2, 2018! I know the instrument is older than that (judging by the date codes on the chips, it's probably made around 2011) so perhaps it was refurbished or repaired by Keysight at that time, if that is the case I think they must have upgraded the firmware at that time, too and the last firmware came out 5-6 month before Oct 2017. So my theory is that this thing died one day in the lab (university as the seller told me) not because students tried to upgrade the firmware which they will never do but because one of the SRAM chips gave out...

author: analogRF
author_rank: Super Contributor
timestamp: November 26, 2019, 02:20:45 pm
content: for the first time even Keysight tech support didn't bother to get back to me on this at all after 7-8 days now

author: Renate
author_rank: Super Contributor
timestamp: November 27, 2019, 04:57:43 pm
content: Mmm, let me tell you about a recent unrelated experience of mine.Same sort of setup, different device, different processor.There's an on-chip ROM bootloader and in flash a secondary bootloader and a system.The ROM bootloader can boot off the flash or using the iMX SDP protocol over USB, but only if the flash fails.I accidentally borked the secondary bootloader, but not enough for the ROM bootloader to know that it was bad.It would start up, load the broken secondary bootloader and fail.Since it already passed the decision point in the ROM bootloader, I didn't have any access to the SDP over USB.So, I grounded one of the data/control pins (dunno what it was) on the flash and reset the processor.The ROM bootloader came up, noticed the inaccessible flash and started running the SDP over USB.(At that point I removed the ground.)I loaded in the secondary bootloader over USB, booted the system from flash and used that to rewrite the secondary bootloader in flash.Everything was back to working.I couldn't make out exactly what processor that is. I don't know what boot options/protocols the ROM bootloader uses.

author: analogRF
author_rank: Super Contributor
timestamp: November 27, 2019, 06:52:53 pm
content: Thanks, Renate for suggestionbased on what I have experienced with this thing, I am pretty sure the boot loader (which I believe is sitting on CPU chip) can only boot from csnet device (internet) or tffs which i think refers to the flash chip. I am pretty sure during the original boot no usb device was initialized and recognized (my usb stick had a led on it,I could see when there was activity) it was only recognized after vxworks was loaded into memory (from flash)however, now I have lost the ability to stop autobooting which means I must have done something that is written in the config of the on-chip boot loader! seems a bit odd to me that such a thing would be possible or allowed...besides the boot flag still shows 0x8 which is the original one and has not changed. so I cannot figure out why I have lost that optionanyways, I was hoping I can get it to stop autoboot so I can change the boot settings and perhaps setup a tftp and boot it from tftp.now your suggestion might do the trick, if it cannot boot from tffs, perhaps it will stop and give me the boot prompt and then I can change the boot settings.one question also remains and that is even if I set it up to boot from tftp, the only thing I have available is the firmware files downloaded from keysight. is that enough for the system to boot?for now I am planning first to replace the SRAM because as I explained, I am still hopeful that this instrument didnt die due to bad firmware update.if that doesn't work, I will do your trick and try tftp boot

author: Renate
author_rank: Super Contributor
timestamp: November 27, 2019, 07:37:54 pm
content: Quote from: analogRF on November 27, 2019, 06:52:53 pmWell, what is the chip?ROM bootloaders are all different and they also have boot options.Some always pause and check if there is some USB thing out there (like OMAP 36xx).Others only appear if they have reason to believe that things have failed (like iMX6).If things were working well enough you might never have seen a lower-level boot attempt.It could be on a serial port, on USB, on SPI, on I2C ROM, maybe network (I don't think so, but who knows).Also, it would be more usual to expect a USB peripheral port, rather than a host port.There's also JTAG. (You've got a lot of test points there.)Or it could be SD card. (You've got a lot of test points there. I've added SD cards to things on test points.)How does manufacturing load an image, huh?Still, SRAM is worth a shot.

author: cgz2001
author_rank: Contributor
timestamp: November 28, 2019, 12:27:50 pm
content: One comment - I have an Agilent DSOX2002A scope, first put into production in 2011 which has a failure mode in that the boot-up sequence does not finish, and that it endlessly loops on the Agilent splash screen. See the forum below for details:https://www.eevblog.com/forum/testgear/agilent-dsox2024-won_t-boot/?allKeysight Daniel has indicated this repair is free to resolve, and I have PM him to see if this offer still stands. Anyways, the community seems to believe this is a bootloader memory corruption issue, and I am starting to wonder from this post if it's widespread with equipment first into production during that time frame.Keysight seems to have recognized the problem and implemented a feature which allows the ability to reflash the bootloader. I wonder if the later firmware revisions offer the same for you on your instrument. There are forum posts from the community that indicate a hardware fix has occured (new boards appear to be installed once repaired by keysight) as well as firmware updates to address the problem.I am also intrigued by the information from another user indicating bootloader code resides in two locations, and disabling one location allows the other to get the machine up and running. Can anybody provide detailed instructions on this procedure?

author: analogRF
author_rank: Super Contributor
timestamp: November 28, 2019, 01:07:02 pm
content: Quote from: Renate on November 27, 2019, 07:37:54 pmthe cpu and the flash names were shown in my first post (in the boot log)network booting is always there, and shows up along with tffs booting. I cannot attempt it anymore because the instrumenthas stopped giving me the option of stopping the auto bootlet me receive the SRAM and see what happens but if that fails, and I can use your trick to getmy network boot option back, my question is what file(s) can I feed into it for booting? I mean the only thing I have isthe firmware files downloaded from keysight. I don't have the .bin image of the flash for example...there is a VxWorks (no extension)file in that firmware which I am hoping will be the boot file....

author: analogRF
author_rank: Super Contributor
timestamp: November 28, 2019, 01:15:33 pm
content: Quote from: cgz2001 on November 28, 2019, 12:27:50 pmmy N9320B is not in a boot loop, it stops because of some kind of memory failure (either flash corrupted or the SRAM is bad)I dont think this is a wide spread issue for these instruments. These units were designed by a totally separate group in AgilentI mean their oscilloscope group in Colorado is separate as I understand and also these units use a completely different architecture, different cpu and flash etc....than DSOXI have asked Keysight tech support for help (as Daniel also told me to do so in a private message) and they never answered me back, not even saying "sorry you should only send the unit to us to fix it for $5000"

author: TheSteve
author_rank: Unknown
timestamp: November 28, 2019, 05:26:03 pm
content: The scope issue isn't caused by a bootloader issue, it is NAND memory corruption in the main OS memory. The fix was to make two copies of firmware and to check it extensively at boot and correct any errors.I believe it has already been stated the N9320B uses linear (NOR) flash so any failure would be different.The N9320B would likely be a lot easier to troubleshoot with the boot log from a good unit. I have no experience with them and don't own one or I'd get a log.

author: Dacke
author_rank: Regular Contributor
timestamp: November 28, 2019, 06:04:18 pm
content: With regards to stopping the autoboot... Just by chance, have you tried something like this -http://support.motioneng.com/Hardware/eXMP/VxWorks/exmp_qs_vx_05.htm- Apologies if I missed it and you already tried.Maybe it would work for the version of VxWorks on the SA. I noticed there is an enter key on the front of the analyzer, I would just try pushing it repeatedly the second you power it up.

author: analogRF
author_rank: Super Contributor
timestamp: November 28, 2019, 06:22:02 pm
content: Quote from: Dacke on November 28, 2019, 06:04:18 pmyes I have seen that site...I did have the option "Press any key to stop auto booting..." and I could stop itbut the problem is later on it disappeared and now it goes to auto boot right away, tried anything to stop it .... what Renate saidby intentionally making the flash not responding (correctly) i might be able to stop the bootloader and get a boot prompt .still I am puzzled by why this happened. The only thing related is the boot flag which I never changed it...Steve is right, only if I had a boot log of a working unit

author: Renate
author_rank: Super Contributor
timestamp: November 29, 2019, 12:21:30 am
content: Quote from: analogRF on November 28, 2019, 01:07:02 pmWell, okay.It's a Sharp LH7A404, now taken over by NXP.This is the manual:http://www.keil.com/dd/docs/datashts/philips/lh7a404_um.pdfI think your best bet is to look for boot jumpers and see if you can get XMODEM on UART2.Still, it's going to be an uphill battle.

author: analogRF
author_rank: Super Contributor
timestamp: December 13, 2019, 05:19:04 am
content: finally the memory chips arrived. I replaced them carefully and nothing...no change whatsoever...same symptoms and same boot log...I also tried to reflow the ASIC that is near the CPU... not 100% sure if it actually reflowed but i think it did. anyways, no change...still stuck at the same memory allocation errors...now I need to force it to boot from something else and i have lost the option of stopping autoboot...

author: analogRF
author_rank: Super Contributor
timestamp: December 13, 2019, 04:03:02 pm
content: the flash eeprom has a hardware reset pin:https://www.cypress.com/file/219926/downloadsee page 15 and 35 for examplecan I try to pull it LOW and then reset the processor and see if it gives me the boot options back again?or maybe it comes up with USB boot option, too as Renate had experienced in another instrument

author: analogRF
author_rank: Super Contributor
timestamp: December 14, 2019, 06:30:46 pm
content: well, after spending more than an hour trying to find a spot that is connected to the RESET pin of the flash and soldering a wire to it (a tiny <0.5mm via pad) it turns out that pin is also connected to the reset pin of the CPU and when I pull it to ground the whole system goes to reset and does not start at all....so that was a waste of time....I don't want to pull any of the CE or OE pins of the flash to Vcc because it might damage thechip that is controlling them...so i don't know how to prevent the system from booting? pulling an address line to ground maybe?!

author: YetAnotherTechie
author_rank: Regular Contributor
timestamp: December 15, 2019, 11:47:59 pm
content: Could you post the new boot log that doesn't let you stop it?What's stopping you from cutting that trace or lifting the pin?There is a risk of breaking the pin, so i recommend you desolder the chip and make a backup.Don't pull address or data lines to ground, there might be writes going on anyway and you'll corrupt the flash even more.

author: kada
author_rank: Contributor
timestamp: May 22, 2020, 02:04:32 pm
content: This is a booting log from my device in case this is still relevant for you:Code:VxWorks System BootCopyright 1984-2004 Wind River Systems, Inc.CPU: Sharp lh7a404Version: VxWorks5.5.1BSP version: 1.0/0Creation date: Oct 1 2008, 10:51:53Press any key to stop auto-boot...10auto-booting...boot device : tffs=0,0unit number : 0processor number : 0host name : hostfile name : /tffs0/VxWorksinet on ethernet (e) : 192.168.0.111host inet (h) : 192.168.0.100user (u) : targetftp password (pw) : targetflags (f) : 0x8other (o) : csnetAttaching to TFFS... done.Loading /tffs0/VxWorks...3414320Starting at 0xc0001000...Attaching interface lo0... doneAttached IPv4 interface to csnet unit 0USB2 Host Stack Initialized.USB Hub Driver InitializedUSBD Wind River Systems, Inc. 560 Initialized1 OHCI Controller found.Waiting to attach to USBD...Done.Adding 6135 symbols for standalone.0xc1effe68 (tRootTask): usbBulkDevInit() returned OKVxWorksCopyright 1984-2002 Wind River Systems, Inc.CPU: Sharp lh7a404Runtime Name: VxWorksRuntime Version: 5.5.1BSP version: 1.0/0Created: Feb 1 2013, 13:54:17WDB Comm Type: WDB_COMM_ENDWDB: Ready.The flash is: S29GL512PusbTMCDevInit() returned OK.-> initkey semtake semabcINT failedtaskSpawn keyTask succsesstaskSpawn powerTask succsesstaskSpawn GpibSendData succsesstaskSpawn GpibSendData succsessuglEpson13506_16BitDevCreate...uglEpson13506_16BitDevCreate...OKuglEpsonModeSet...uglEpsonSetRegs...mode=0i=0,reg[1,0]i=1,reg[508,0]i=2,reg[4,0]i=3,reg[8,0]i=4,reg[16,1]i=5,reg[20,18]i=6,reg[24,0]i=7,reg[28,2]i=8,reg[30,1]i=9,reg[32,1]i=10,reg[33,0]i=11,reg[42,1]i=12,reg[43,1]i=13,reg[48,37]i=14,reg[49,0]i=15,reg[50,79]i=16,reg[52,3]i=17,reg[53,1]i=18,reg[54,11]i=19,reg[56,223]i=20,reg[57,1]i=21,reg[58,44]i=22,reg[59,10]i=23,reg[60,1]i=24,reg[64,5]i=25,reg[65,0]i=26,reg[66,0]i=27,reg[67,0]i=28,reg[68,0]i=29,reg[70,128]i=30,reg[71,2]i=31,reg[72,0]i=32,reg[74,25]i=33,reg[75,60]i=34,reg[80,79]i=35,reg[82,19]i=36,reg[83,1]i=37,reg[84,11]i=38,reg[86,223]i=39,reg[87,1]i=40,reg[88,43]i=41,reg[89,9]i=42,reg[90,1]i=43,reg[91,24]i=44,reg[96,5]i=45,reg[98,0]i=46,reg[99,0]i=47,reg[100,0]i=48,reg[102,128]i=49,reg[103,2]i=50,reg[104,0]i=51,reg[106,59]i=52,reg[107,60]i=53,reg[112,0]i=54,reg[113,1]i=55,reg[114,0]i=56,reg[115,0]i=57,reg[116,0]i=58,reg[117,0]i=59,reg[118,0]i=60,reg[119,0]i=61,reg[120,0]i=62,reg[122,31]i=63,reg[123,63]i=64,reg[124,31]i=65,reg[126,0]i=66,reg[128,0]i=67,reg[129,1]i=68,reg[130,0]i=69,reg[131,0]i=70,reg[132,0]i=71,reg[133,0]i=72,reg[134,0]i=73,reg[135,0]i=74,reg[136,0]i=75,reg[138,31]i=76,reg[139,63]i=77,reg[140,31]i=78,reg[142,0]i=79,reg[256,0]i=80,reg[257,0]i=81,reg[258,0]i=82,reg[259,0]i=83,reg[260,0]i=84,reg[261,0]i=85,reg[262,0]i=86,reg[264,0]i=87,reg[265,0]i=88,reg[266,0]i=89,reg[268,0]i=90,reg[269,0]i=91,reg[272,0]i=92,reg[273,0]i=93,reg[274,0]i=94,reg[275,0]i=95,reg[276,0]i=96,reg[277,0]i=97,reg[280,0]i=98,reg[281,0]i=99,reg[480,0]i=100,reg[482,0]i=101,reg[496,0]i=102,reg[497,0]i=103,reg[500,0]i=104,reg[508,1]uglEpsonModeSet...OKcreate /tffs0/dcqmode directory successnew align data formatreload default align data from eprom becasue version 1 !=2 not the samerf align version is A.01.01.1.CIDKMNEWwait DSP be readycurrent dsp status is 1426063360USBTMC already initilaized.