Author Topic: Agilent DSO6054A boot problem  (Read 1266 times)

0 Members and 1 Guest are viewing this topic.

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Agilent DSO6054A boot problem
« on: March 08, 2020, 12:49:39 pm »
I got a very clean DSO6054A which does not boot. The front panel LEDs blink in order and finally the Single button lights up for a few seconds and then all off, no display (backlight is OK).
I tried the USB recovery as per keysight website and I can see the LED on my USB stick blinks for a while (when Single button is ON) and then
it goes off and nothing...tried multiple times and tried to play with that 4 seconds timing...should the USB stick be formatted in a special way?

Nothing on the VGA monitor either.

I also tried LAN connection and again although the orange LAN LED in the back blinks (and the green one is ON) but it does not show up on my network so I cannot telnet to it...

Checked ALL voltage regulators and supplies on the board and they are all OK. I found the Agilent service bulletin for these scopes that says
they fail to boot and need motherboard replacement however that bulletin applies to DSO6034A and only for S/N <MY44001000. My S/N is MY5007xxxx so I guess that service note does not apply


** Does anybody know a serial console port on this scope so that I can access to the boot prompt  and see what is going on?**

also does the rescue USB need to be formatted in a special way? FAT16 or FAT32 etc...
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #1 on: March 10, 2020, 07:44:19 pm »
a tiny progress...I found the serial console port on the main board and connected my Bus Pirate (UART, 9600 bps, 8-N-1)
Please see the attached picture for pin connections.
here is the boot process when I do not have the bootloader on USB stick (no USB stick in the device)
Code: [Select]
                            VxWorks System Boot


Copyright 1984-2005  Wind River Systems, Inc.





CPU: Agilent KOM PPC405, SA27E rev1
Version: VxWorks 6.4
BSP version: 2.0/0
Creation date: Jan 12 2008, 09:32:29


i

Press any key to stop auto-boot...
 0
auto-booting...


boot device          : tffs;usb
unit number          : 0
processor number     : 0
file name            : sys6000
flags (f)            : 0x8
target name (tn)     : a-d6054a-070138
startup script (s)   : -allLic
other (o)            : emac0

USB2 Host Stack Initialized.
USB Hub Driver Initialized
USBD  Wind River Systems, Inc. 560 Initialized
OHCI Controller found.
Waiting to attach to USBD...0x102d578 (tBoot):
OK, found chip id 0x6123
Done.
Searching for USB device .... Could not find USB device.
Attaching to TFFS... done.
Checking revision of tffs0/bin/sys6000.jzp
Instantiating /ram0 as rawFs,  device = 0x20001
Formatting /ram0 for DOSFS
Instantiating /ram0 as rawFs, device = 0x20001
Formatting...OK.
Uncompressing tffs0/bin/sys6000.jzp to /ram0/sys6000.bin
Entering uncompressFile()
Loading /ram0/sys6000.bin... 10639232
done
Starting at 0x10000...

Instantiating /ram0 as rawFs,  device = 0x1
Host Name: bootHost
User: target
Attaching interface lo0... done
Invalid device "emac0"
USB2 Host Stack Initialized.
USB Hub Driver Initialized
USBD  Wind River Systems, Inc. 560 Initialized
OHCI Controller found.
Waiting to attach to USBD...0x1fffd30 (tRootTask):
OK, found chip id 0x6123
Done.

Adding 28626 symbols for standalone.
wdbCommDevInit: Could not find device tffs;usb, unit 0 !
wdbConfig: error configuring WDB communication interface

->   Cmd line = -allLic
   Formatting /ram0 for DOSFS
Instantiating /ram0 as rawFs, device = 0x1
Formatting...OK.
pFd->pVolDesc->devHdr.name = C:.
pVolDesc->devHdr.name = C:.
C:/  - Volume is OK


-> pwd
pwd
C://
value = 5 = 0x5
-> devs
devs
drv name
  0 /null
  1 /tyCo/0
  1 /tyCo/1
  2 /aioPipe/0x1fffd30
  7 /
  3 C:
  9 /bpf/dhcpc/0
  9 /bpf/dhcpc/1
  9 /bpf/dhcpc/2
  9 /bpf/dhcpc/3
  9 /bpf/dhcpc-arp
 11 /vio
 12 /tgtsvr
  3 /ram0
value = 25 = 0x19
-> ll
ll
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 tmp/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 setups/
drwxrwxrwH  1 0       0                 2048 Feb 17  2000 config/
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 data/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 masks/
drwxrwxrSH  1 0       0                 2048 Feb 17  2000 cal/
drwxrwxrSH  1 0       0                 2048 Dec 24  2003 help/
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 bin/
value = 0 = 0x0
-> cd "bin"
cd "bin"
value = 0 = 0x0
-> ll
ll
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 ./
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 ../
-rwxrwxrwx  1 0       0              1019613 Dec 22  2009 lpk6000.jzp
-rwxrwxrwx  1 0       0               503121 Feb 17  2015 lib6000.jzp
-rwxrwxrwx  1 0       0              4249720 Feb 18  2015 sys6000.jzp
-rwxrwxrwx  1 0       0                  138 Feb 18  2015 license.lic
-rwxrwxrwx  1 0       0                  111 Feb 18  2015 license.bak
value = 0 = 0x0
->

As you can see the device boots and gets to the point that drive C: is OK and then nothing. Sits there and no screen, no error, nothing...
There is an error saying "emac0" device is invalid and I think that is the LAN. The emac0 is defined (on the boot parameters) as the "other" alternative boot device and based on my past experience with VxWorks stuff, this device which I am pretty sure is a LAN interface must be enabled and activated even if it is not used. That's why I get no IP when I connect to my network.

Then there is an error about wdbConfig. I dont know what that is and is it normal to have that error.

Strangely I cannot get into any of the directories except the "bin", "cal", and "tmp" directory. When I try the others I get some weird truncated text in response (to cd command) you can see it down below. I have also included the results of ifShow command and "ti" and "i" command but "moduleShow" again results in a weird truncated text with no output:
Code: [Select]
-> ll
ll
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 tmp/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 setups/
drwxrwxrwH  1 0       0                 2048 Feb 17  2000 config/
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 data/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 masks/
drwxrwxrSH  1 0       0                 2048 Feb 17  2000 cal/
drwxrwxrSH  1 0       0                 2048 Dec 24  2003 help/
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 bin/
value = 0 = 0x0
-> cd "setups"
cd "s"
cd: error = 0x13.
value = -1 = 0xffffffff
-> cd "bin"
cd "bin"
value = 0 = 0x0
-> ll
ll
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 ./
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 ../
-rwxrwxrwx  1 0       0              1019613 Dec 22  2009 lpk6000.jzp
-rwxrwxrwx  1 0       0               503121 Feb 17  2015 lib6000.jzp
-rwxrwxrwx  1 0       0              4249720 Feb 18  2015 sys6000.jzp
-rwxrwxrwx  1 0       0                  138 Feb 18  2015 license.lic
-rwxrwxrwx  1 0       0                  111 Feb 18  2015 license.bak
value = 0 = 0x0
-> cd ".."
cd ".."
value = 0 = 0x0
-> cd "config"
cd "c"
cd: error = 0x13.
value = -1 = 0xffffffff
-> cd "./config"
cd ".ig"
cd: error = 0x13.
value = -1 = 0xffffffff
-> ifShow
ifShow
lo (unit number 0):
     Flags: (0x48049) UP LOOPBACK MULTICAST TRAILERS ARP RUNNING INET_UP
     Type: SOFTWARE_LOOPBACK
     inet: 127.0.0.1
     Netmask 0xff000000 Subnetmask 0xff000000
     Metric is 0
     Maximum Transfer Unit size is 1536
     0 packets received; 0 packets sent
     0 multicast packets received
     0 multicast packets sent
     0 input errors; 0 output errors
     0 collisions; 0 dropped
     0 output queue drops
value = 26 = 0x1a
-> moduleShow
modul
-> i
i

  NAME         ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY
----------  ------------ -------- --- ---------- -------- -------- ------- -----
tJobTask    439a80         b9a540   0 PEND         4d77fc   b9a410       0     0
tExcTask    438b4c         a32b20   0 PEND         4d77fc   a34d60       0     0
tLogTask    logTask        b9d7e8   0 PEND         4d50d8   b9d6c0       0     0
tNbioLog    43b130         ba10a0   0 PEND         4d77fc   ba0f90       0     0
tShell0     shellTask     1475548   1 READY        4df974  1475240      13     0
tBulkClnt   56ce8         1440ab0   5 PEND         4d7fbc  14409d8       0     0
tUfiClnt    58b20         14524d0   5 PEND         4d7fbc  14523d8       0     0
tErfTask    39b8b8         bc2210  10 PEND         4d7fbc   bc2150       0     0
tAioIoTask> aioIoTask      bb6640  50 PEND         4d7fbc   bb6560       0     0
tAioIoTask> aioIoTask      bbea20  50 PEND         4d7fbc   bbe940       0     0
tXbdServic> 430af8        1088e50  50 PEND+T       4d7fbc  1088d90  3d0004     4
tNetTask    netTask       10c5660  50 PEND         4d77fc  10c5590       0     0
tAioWait    aioWaitTask    bae160  51 PEND         4d77fc   bae020       0     0
tPortmapd   portmapd      1204c90  54 PEND         4d77fc  1204a60      16     0
tTelnetd    telnetd       1207e80  55 PEND         4d77fc  1207d20       0     0
tDhcpcStat> 3aad5c        11fec90  56 PEND         4d7fbc  11febb0       0     0
tDhcpcRead> dhcpcRead     12012d0  56 PEND         4d77fc  1201080       0     0
tFtp6d      3b20a8        120c498  56 PEND         4d77fc  120c300       0     0
tTffsPTask  flPollTask    1085dc8 100 DELAY        4ddc24  1085d20       0     5
t1          4b7ca4        1413238 100 PEND         4d50d8  14130f0       0     0
tUsbIsp116> usbIsp1161Hc  141bfb0 100 PEND+T       4d50d8  141bea8  3d0002     1
usbOhciIsr  48084         141f398 100 PEND         4d77fc  141f2d8       0     0
BusM A      4bc8e8        1422800 100 DELAY        4ddc24  1422760       0     1
usbPrinter> 4b7ca4        1428440 100 PEND         4d50d8  1428210       0     0
usbPrinter> 4b7ca4        142df08 100 PEND         4d50d8  142de10       0     0
BULK_CLASS  4b7ca4        1433a58 100 PEND         4d50d8  1433820       0     0
BULK_CLASS> 4b7ca4        1439528 100 PEND         4d50d8  1439430       0     0
CBI_UFI_CL> 4b7ca4        14465f8 100 PEND         4d50d8  14463c0       0     0
CBI_UFI_CL> 4b7ca4        144c0c8 100 PEND         4d50d8  144bfd0       0     0
UNSUP_DEV   4b7ca4        1457f98 100 PEND         4d50d8  1457d60       0     0
UNSUP_DEV_> 4b7ca4        145da68 100 PEND         4d50d8  145d970       0     0
value = 0 = 0x0

-> ti
ti

  NAME         ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY
----------  ------------ -------- --- ---------- -------- -------- ------- -----
tShell0     shellTask     1475548   1 READY        4df974  1475240  ad0007     0

task stack: base 0x1475548   end 0x1465548   size 65536  high 7496   margin 58040
exc. stack: base 0x1476800   end 0x1475810   start 0x1476810
exc. stack: size 4080        high 128        margin 3952

proc id: 0x9f37d0 ((null))
options: 0x9003
VX_SUPERVISOR_MODE  VX_UNBREAKABLE      VX_DEALLOC_TCB      VX_DEALLOC_EXC_STACK

VxWorks Events
--------------
Events Pended on    : 0x0
Received Events     : 0x0
Options             : 0x0       EVENTS_WAIT_ALL
value = 0 = 0x0
-> ll
ll
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 tmp/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 setups/
drwxrwxrwH  1 0       0                 2048 Feb 17  2000 config/
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 data/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 masks/
drwxrwxrSH  1 0       0                 2048 Feb 17  2000 cal/
drwxrwxrSH  1 0       0                 2048 Dec 24  2003 help/
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 bin/
value = 0 = 0x0

-> cd "data"
cd "d

-> pwd
pwd
C:/
value = 4 = 0x4

-> cd "cal"
cd "cal"
value = 0 = 0x0
-> ll
ll
drwxrwxrSH  1 0       0                 2048 Feb 17  2000 ./
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 ../
-rwxrwxrwx  1 0       0                22880 Apr 21  2010 framecal.dat
value = 0 = 0x0

-> cd ".."
cd ".."
value = 0 = 0x0
-> cd "data"
cd "d

-> cd "tmp"
cd "tmp"
value = 0 = 0x0
-> ll
ll
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 ./
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 ../
-rwxrwxrwx  1 0       0                  153 Mar 11 01:16 err.txt
-rwxrwxrwx  1 0       0                  151 Mar 11 01:11 prevErr.txt
-rwxrwxrwx  1 0       0                    0 Feb 17  2000 cal.txt
value = 0 = 0x0
-> cd "../config"
cd ".fig"
cd: error = 0x13.
value = -1 = 0xffffffff


If I put the boot loader on USB stick and start the scope, this is what I get. There is no need for that 4 sec wait and turn on and off crap that is on keysight website. Whenever I put the usb in, it will start the boot loader from USB no matter what. and by the way, ONLY the .jzp file is required
it does not read the .bin (uncompressed) version on the USB
Code: [Select]
                           VxWorks System Boot


Copyright 1984-2005  Wind River Systems, Inc.





CPU: Agilent KOM PPC405, SA27E rev1
Version: VxWorks 6.4
BSP version: 2.0/0
Creation date: Jan 12 2008, 09:32:29




Press any key to stop auto-boot...
 0
auto-booting...


boot device          : tffs;usb
unit number          : 0
processor number     : 0
file name            : sys6000
flags (f)            : 0x8
target name (tn)     : a-d6054a-070138
startup script (s)   : -allLic
other (o)            : emac0

USB2 Host Stack Initialized.
USB Hub Driver Initialized
USBD  Wind River Systems, Inc. 560 Initialized
OHCI Controller found.
Waiting to attach to USBD...0x102d578 (tBoot):
OK, found chip id 0x6123
Done.
Searching for USB device .0x1236e90 (BusM A): <<<port reset:(0)>>>
 found /drive0.
Checking revision of /drive0/sys6000.jzp
Instantiating /ram0 as rawFs,  device = 0x30001
Formatting /ram0 for DOSFS
Instantiating /ram0 as rawFs, device = 0x30001
Formatting...OK.
Uncompressing /drive0/sys6000.jzp to /ram0/sys6000.bin
Entering uncompressFile()
Loading /ram0/sys6000.bin... 10678464
done
Starting at 0x10000...

Instantiating /ram0 as rawFs,  device = 0x1
Host Name: bootHost
User: target
Attaching interface lo0... done
Invalid device "emac0"
USB2 Host Stack Initialized.
USB Hub Driver Initialized
USBD  Wind River Systems, Inc. 560 Initialized
OHCI Controller found.
Waiting to attach to USBD...0x1fffd30 (tRootTask):
OK, found chip id 0x6123
Done.

Adding 28627 symbols for standalone.
wdbCommDevInit: Could not find device tffs;usb, unit 0 !
wdbConfig: error configuring WDB communication interface

->   Cmd line = -allLic
   Formatting /ram0 for DOSFS
Instantiating /ram0 as rawFs, device = 0x1
Formatting...OK.
pFd->pVolDesc->devHdr.name = C:.
pVolDesc->devHdr.name = C:.
C:/  - Volume is OK
Bulk Device Installed as /usb0


-> pwd
pwd
C://
value = 5 = 0x5
-> devs
devs
drv name
  0 /null
  1 /tyCo/0
  1 /tyCo/1
  2 /aioPipe/0x1fffd30
  7 /
  3 C:
  9 /bpf/dhcpc/0
  9 /bpf/dhcpc/1
  9 /bpf/dhcpc/2
  9 /bpf/dhcpc/3
  9 /bpf/dhcpc-arp
 11 /vio
 12 /tgtsvr
  3 /ram0
  3 /usb0
value = 25 = 0x19
-> ll
ll
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 tmp/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 setups/
drwxrwxrwH  1 0       0                 2048 Feb 17  2000 config/
drwxrwxrwH  1 0       0                 2048 Dec 24  2003 data/
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 masks/
drwxrwxrSH  1 0       0                 2048 Feb 17  2000 cal/
drwxrwxrSH  1 0       0                 2048 Dec 24  2003 help/
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 bin/
value = 0 = 0x0
-> cd "bin"
cd "bin"
value = 0 = 0x0
-> ll
ll
drwxrwxrSH  1 0       0                 2048 Feb 17  2015 ./
drwxrwxrwx  1 0       0                 2048 Dec 24  2003 ../
-rwxrwxrwx  1 0       0              1019613 Dec 22  2009 lpk6000.jzp
-rwxrwxrwx  1 0       0               503121 Feb 17  2015 lib6000.jzp
-rwxrwxrwx  1 0       0              4249720 Feb 18  2015 sys6000.jzp
-rwxrwxrwx  1 0       0                  138 Feb 18  2015 license.lic
-rwxrwxrwx  1 0       0                  111 Feb 18  2015 license.bak
value = 0 = 0x0
->

as you can see, the result is exactly the same although I noticed the file sizes are different than what is in the latest firmware.

Anyways, now my question is what do you guys think? Why doesn't it say anything else after "drive C: is OK". Is this because it cannot initialize the LAN interface? what is that "wdbConfig" about? Or maybe it cannot configure/initialize the FPGA? could that be the reason?


It's probably too much to ask, but can anybody open his scope and connect it to a serial to USB and show me the boot process of a normal scope?
Any DSO6000A model would be the same I think (even a two channel one)


The bottom cover easily slides off (no screws) and it's a very easy process to open and close this scope

EDIT: the arrows on the RX and TX pins must be in reverse direction. I mean data is received on pin 2 and is transmitted out from pin 3.
« Last Edit: March 10, 2020, 07:47:01 pm by analogRF »
 

Offline JKKDev

  • Regular Contributor
  • *
  • Posts: 108
  • Country: si
Re: Agilent DSO6054A boot problem
« Reply #2 on: March 10, 2020, 08:21:05 pm »
Could you use other pins on the bus pirate to verify itself if what you're writing to the console is actually being sent out (in the case of truncated text)? Maybe a long shot and probably not the source of your problem but might be worth a look ey?

Btw does the console not like it if you use folder names without ""?
« Last Edit: March 10, 2020, 08:22:58 pm by JKKDev »
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #3 on: March 10, 2020, 08:48:40 pm »
the communication is ok. I can run many commands...it's either something about permission for those directories or they do not actually exist somehow (perhaps they are links to an actual directory that is not accessible?) in any case it's weird and I should be able to change to those directories (someone could verify that? )

no, when I have -> prompt, the directory or file names must be in " ..". when I run cmd command and get VxWorks # prompt, then I can leave out the "" from the names I think but still I could not get into those directories...is it a memory (RAM) problem?...

there are 4 SRAM chips on this, two close to the FPGA and two close to the PPC processor. I dont know which one is hosting /ram0 drive...
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #4 on: March 10, 2020, 08:55:02 pm »
it seems the only task running is tShell. I am pretty sure other task should have been started...they don't because either it's a memory corruption/bad RAM or some device was not initialized (which device?) ....is it possible that those other directories are not accessible under this tShell
and perhaps if it was gone further ahead, they would become accessible under another shell maybe?

boot process of a normal working unit would be a great help.

but even if someone could telnet to the unit and see if they can "cd" to those directories, and also run some commands like "ti" or moduleShow
and ifShow, to see what kind of processes are running, it would still be helpful


 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1387
  • Country: us
  • This is work?
Re: Agilent DSO6054A boot problem
« Reply #5 on: March 11, 2020, 10:41:57 am »
a tiny progress...I found the serial console port on the main board and connected my Bus Pirate (UART, 9600 bps, 8-N-1)

[snip]

It's probably too much to ask, but can anybody open his scope and connect it to a serial to USB and show me the boot process of a normal scope?
Any DSO6000A model would be the same I think (even a two channel one)


The bottom cover easily slides off (no screws) and it's a very easy process to open and close this scope

EDIT: the arrows on the RX and TX pins must be in reverse direction. I mean data is received on pin 2 and is transmitted out from pin 3.

I can do this for you. Are you sure about those serial port settings?
Jay

System error. Strike any user to continue.
 
The following users thanked this post: analogRF

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #6 on: March 11, 2020, 10:58:33 am »
thank you so much for doing this, Jay
I really appreciate it.

yes, I am sure about 9600-8-N-1. I tried them all until I found out it was 9600 bps
make sure you have a good ground connection

in bus pirate, I choose HiZ (open drain), although the other option is probably ok too. Voltage level is 3.3V
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #7 on: March 11, 2020, 11:38:51 am »
Jay,
Maybe there is a problem with the connection between your computer and the serial to USB converter?
for example in BusPirate, that connection is 115200,8-N-1.
 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1387
  • Country: us
  • This is work?
Re: Agilent DSO6054A boot problem
« Reply #8 on: March 11, 2020, 11:53:25 am »
thank you so much for doing this, Jay
I really appreciate it.

yes, I am sure about 9600-8-N-1. I tried them all until I found out it was 9600 bps
make sure you have a good ground connection

in bus pirate, I choose HiZ (open drain), although the other option is probably ok too. Voltage level is 3.3V

Ground connection is fine. I'm using the serial port of a dell docking station which works fine with TDS500, TDS600, TDS700, TDS7000, etc. scopes.
It might be a true serial port with +-12V signaling, not one of those wimpy new-age ones. Looking at the TXD from the laptop, it's +-6V
That may be the problem... I don't have one of those USB serial port adapters  to try.

EDIT: Yeah, and TXD from the scope signaling is only 0 to 3 volts or so...
« Last Edit: March 11, 2020, 11:56:59 am by Jwalling »
Jay

System error. Strike any user to continue.
 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1387
  • Country: us
  • This is work?
Re: Agilent DSO6054A boot problem
« Reply #9 on: March 11, 2020, 02:44:08 pm »
I think I may need a TTL to serial converter, or something like this:
https://www.ebay.com/itm/223171155058?

What do you think?

Jay

System error. Strike any user to continue.
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #10 on: March 11, 2020, 02:58:23 pm »
I think I may need a TTL to serial converter, or something like this:
https://www.ebay.com/itm/223171155058?

What do you think?

yes, I think that should work. Although I have only used BusPirate but this is essentially doing the same thing except
that BusPirate is based on FTDI chip not CH340. it should not make any difference for this simple application. you just download the
drivers for CH340 chip and you will be good to go
« Last Edit: March 11, 2020, 03:00:49 pm by analogRF »
 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1387
  • Country: us
  • This is work?
Re: Agilent DSO6054A boot problem
« Reply #11 on: March 11, 2020, 03:10:04 pm »
I think I may need a TTL to serial converter, or something like this:
https://www.ebay.com/itm/223171155058?

What do you think?

yes, I think that should work. Although I have only used BusPirate but this is essentially doing the same thing except
that BusPirate is based on FTDI chip not CH340. it should not make any difference for this simple application. you just download the
drivers for CH340 chip and you will be good to go

OK, I just bought one - this one was cheaper at $3.99 with free shipping. https://www.ebay.com/itm/382643159433?
I'll update the thread when I get it.
Jay

System error. Strike any user to continue.
 
The following users thanked this post: analogRF

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #12 on: March 11, 2020, 03:59:44 pm »
I think I may need a TTL to serial converter, or something like this:
https://www.ebay.com/itm/223171155058?

What do you think?

yes, I think that should work. Although I have only used BusPirate but this is essentially doing the same thing except
that BusPirate is based on FTDI chip not CH340. it should not make any difference for this simple application. you just download the
drivers for CH340 chip and you will be good to go

OK, I just bought one - this one was cheaper at $3.99 with free shipping. https://www.ebay.com/itm/382643159433?
I'll update the thread when I get it.

Jay, thank you so much :) Looking forward to it

In the meantime, if anyone else has a DSO6000A series and is willing to open the scope and hook up to the serial console and post the boot log
it is highly appreciated.

Also,  if someone could telnet to the scope and see if they can go into those directories (see my earlier post) and post the file names and sizes, and also run some commands like "ti" or moduleShow and ifShow and memShow, to see what tasks are running, it could still be helpful.
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #13 on: March 12, 2020, 10:58:03 pm »
a tiny bit of progress today...
hope somebody can give me suggestions how to proceed from here

I finally managed to move inside all directories and copy their files on to my USB and read them on my laptop. The issue
was a setting in BusPirate . It seems that in buspirate I should have chosen the output type as Normal (H=3.3, L=GND) instead of Open Drain (H=Hi-Z,L=GND). anyways, here is what I found.

on "/ram0" device (see the boot log in my first post) there is a "startup.txt" file and here is the content of that file when the unit boots from its own flash (not from my USB):
Code: [Select]
File system ... ok
  Code rev   Released build, Apr 27 2011, 14:47:24
  Directory:
  Load dynamically linked libraries ... ok
  Turn on hardware communications
    FPGA Rev 02.b4.14.13
  Instrument capability
    instType = 0x3, a Panther, MSO capable, 4 channel
  LED display ... ok
  Real time clock ... ok
  Instrument features
    Licenses = MSO, mem8M, LSS, 232, MST, E00, SND
  Init model number strings
    DSO6054A
  Low level measurement hardware     Attempting Master Ponderosa read ...
 ok
    Attempting Slave Ponderosa read ... ok
    Ponderosa ck100 freq: master=101.87MHz slave=101.87MHz    Ponderosa Rev 2 (sync'd)    acqTableId=500MHz  memoryOption=8Meg

Timeout while trying to stop Talon clocks
Timeout while trying to stop Talon clocks

When I boot from my USB stick I get exactly the same startup.txt file except that the license line only has mem8M,MST,E00 and the code revision becomes Apr 23 2015. Everything else is the same.

The content of the C:/bin/license.lic is:
Code: [Select]
MSO-000000000000-000000000

008-2CE6C61B1F3A-000000000

LSS-000000000000-000000000
232-000000000000-000000000
SND-000000000000-000000000
I think someone has hacked or tried to hack this scope. The license file seems very strange to me with all those zeros but apparently the instrument is recognizing them (see startup.txt content) What are options SND and 232? I cannot find them anywhere...

anyways, it is now clear to me that the last sentence is where the instrument is stuck at. "cannot stop Talon clocks".
If I understand correctly, Talons are the 4 ADS chips and Ponderosa is the ASIC that is in between the 4 ADC chips? or is Panderosa the Xilinx FPGA
near the PPC CPU?  Why is it trying to stop the Talon clocks? There is a 500MHz oscillator near the ASIC chip (in the middle of 4 ADCs) and it is working fine.

any ideas??
« Last Edit: March 12, 2020, 11:02:27 pm by analogRF »
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #14 on: March 13, 2020, 12:41:20 am »
apparently this guy had a similar problem but in the opposite sense  :-// his scope could not start the Talon clocks after it was booted to the scope screen
https://community.keysight.com/thread/6591
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #15 on: March 13, 2020, 03:02:45 am »
can anybody tell me which chips are called Ponderosa and which one is Talon on the DSO6000A main board?

There are 5 ASICs with heatsinks (two behind each pair of channels and one single in between them)
and there is a Xilinx FPGA near the CPU with no heatsink.
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #16 on: March 13, 2020, 01:37:39 pm »
here are pictures of the ASICs and FPGA.
Which one is Ponderosa, which is Talon? How can I find the Talon clocks? My research tells me Talon are the ADC blocks inside those ASICs
(there are 32 of them working at 125MHz?) but I could be wrong...and i dont know which chip is named Ponderosa...
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #17 on: March 13, 2020, 02:21:51 pm »
can someone at least use telnet to connect to the unit and post the content of the /ram0/startup.txt file?
 

Offline Jwalling

  • Supporter
  • ****
  • Posts: 1387
  • Country: us
  • This is work?
Re: Agilent DSO6054A boot problem
« Reply #18 on: March 18, 2020, 12:23:57 pm »
This is from an MSO6012A. I can do an MSO6054A if you think it might be useful...

Code: [Select]






                            VxWorks System Boot


Copyright 1984-2002  Wind River Systems, Inc.





CPU: Agilent KOM PPC405, SA27E rev1
Version: VxWorks5.5.1
BSP version: 1.2/0
Creation date: Jun 10 2005, 18:58:06




Press any key to stop auto-boot...
 1 0
auto-booting...


boot device          : tffs;usb
unit number          : 0
processor number     : 0
host name            : boot
file name            : sys6000
inet on ethernet (e) : 0.0.0.0
host inet (h)        : 0.0.0.0
user (u)             : target
ftp password (pw)    : target
flags (f)            : 0x8
target name (tn)     : target
other (o)            : emac0

Attaching to TFFS... done.
Loading /tffs0/bin/sys6000.bin... 10678464
Starting at 0x10000...

Instantiating /ram0 as rawFs,  device = 0x1
Attaching interface lo0... done
USB2 Host Stack Initialized.
USB Hub Driver Initialized
USBD  Wind River Systems, Inc. 560 Initialized
OHCI Controller found.
Waiting to attach to USBD...0x1fffd30 (tRootTask):
OK, found chip id 0x6123
Done.

Adding 28627 symbols for standalone.
wdbCommDevInit: Could not find device tffs;usb, unit 0 !

-> Formatting /ram0 for DOSFS
Instantiating /ram0 as rawFs, device = 0x1
Formatting...OK.
pFd->pVolDesc->devHdr.name = C:.
pVolDesc->devHdr.name = C:.
                                                                            C:/  - Volume is OK
nColorMapIndex 123
    valid probe detected on ext
Jay

System error. Strike any user to continue.
 
The following users thanked this post: analogRF

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #19 on: March 19, 2020, 11:16:43 am »
Thank you so much, Jay. I appreciate it.

Well, unfortunately it does not help much. Yours has an older VxWorks version so the messages are a little bit different
but it's pretty much what I get on my system too. yours does not complain about that "emacs0" device not being valid though
but it might be because your hardware config is different. In any case, I am not sure that is a clue to the boot problem that I have.
Other than that, it's exactly what I get until the C: drive message and then there is not much afterwards except that mine remains stuck at that point.

I have found the circuitry that distributes the 500MHz Talon clocks and how it is supposed to enable/disable the clock and indeed I am not
getting the signal that needs to disable the Talon clocks but I could not trace that signal to anywhere on the board and I strongly suspect
it is in the middle layers going to one of the ASICs. It is probably (most likely) a solder joint problem I think somewhere...

Do you guys think it is possible to reflow those ASICs somehow? The one in the middle is a QFP package but the two big ones  are BGA (about 28x28 mm) and from the side they look like old CPUs (they have a (PCB and then there is heat spreader plate on top....)
Should I take the heatsink off? how? They dont budge even after heating them to around 90C
 

Offline analogRF

  • Frequent Contributor
  • **
  • Posts: 609
  • Country: ca
Re: Agilent DSO6054A boot problem
« Reply #20 on: March 19, 2020, 01:53:40 pm »
any advice on how to reflow the big BGA ASICs? how to take their heatsink off?
 

Offline lwtlwt

  • Newbie
  • Posts: 3
  • Country: cn
Re: Agilent DSO6054A boot problem
« Reply #21 on: April 28, 2020, 04:27:58 pm »
Hi,
Coincidentally, my friend gave me two oscilloscopes: DSO6014 and DSO6012, 6014 have been repaired, 6012 encountered a problem similar to yours, before I saw your post, I also got almost the same research as your results, but my fault message is:
"Timeout while trying to start Talon clocks"
This information is in the C: \ tmp \ err.txt file.
I noticed the clock distribution chip: 100LVxx14, and its ENA pin is used to enable or disable the "talon clocks". I think we can follow this clue to continue research.  we can share the results.
 

Offline lwtlwt

  • Newbie
  • Posts: 3
  • Country: cn
Re: Agilent DSO6054A boot problem
« Reply #22 on: April 28, 2020, 04:39:24 pm »
Please check the 100LVxx14 chip's pin_19, it will have a narrow pulse when starting(when the startup is about to complete), used to start / stop the clock, maybe it still in "enable" status(low level).
 

Offline lwtlwt

  • Newbie
  • Posts: 3
  • Country: cn
Re: Agilent DSO6054A boot problem
« Reply #23 on: May 02, 2020, 11:08:39 am »
Sorry, I checked the PLL circuit, it is normal and can be locked, Talon clocks has nothing to do with it, I am looking for this talon clocks now, if you have any update, please let me know, thanks!
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf