SONY/Tektronix AWG520 2ch 1Gs/s with no output - repair attempt and teardown

[tchiwam]

Cpu back side

[tchiwam]

OK, hmmmmm



Kingspec PA25-64 seems to refuse to be a slave

I tried all the jumper config

I've made myself Cable select, 44 pin with pin 28 open and put the Kingspec in the middle and at the end,

Always there as Master not matter what ... Unless someone has a trick to force that drive as Slave it is a no go for the AWG520 as a 2nd drive.

It is recognised as Master, so a partition could be done to replace the 32MB one....

[DC1MC]

OK, hmmmmm

Kingspec PA25-64 seems to refuse to be a slave

I tried all the jumper config

I've made myself Cable select, 44 pin with pin 28 open and put the Kingspec in the middle and at the end,

Always there as Master not matter what ... Unless someone has a trick to force that drive as Slave it is a no go for the AWG520 as a 2nd drive.

It is recognised as Master, so a partition could be done to replace the 32MB one....

What about the original cable ? It should already be suitable, I didn't fiddle with jumpers or cables on my device  .

Cheers,
DC1MC

[tchiwam]

Did you use a Kingspec PA25-XX
Mine is a Black box

And yes I did use the original cable.

Did you leave the jumper on or off ?

What model of Kingspec ?

[lugaw]

I have figured out how to use any drive for booting the  system.

I wrote the steps here https://github.com/nukem/Tektronix-AWG420-Support-Files

I had an AWG420 with a broken flash drive. In my search to make it work I found this code https://github.com/tpunix/vxworks-project/tree/master/vxsys that can place a bootloader on a new drive and using FAT16 or FAT32 formats the AWGs uses FAT12 for the boot drive.

The bootloader will load the bootrom.sys on a FAT16 or FAT32 file system.  The hard part was compiling it on a DOS environment and I have uploaded the compiled vxsys.exe on github.  You need a DOS environment to do all the format and  bootloader install.

I hope this  can help someone.

[DC1MC]

Did you use a Kingspec PA25-XX
Mine is a Black box

And yes I did use the original cable.

Did you leave the jumper on or off ?

What model of Kingspec ?

I've actually used two Compact Flash (CF) cards, one of 32Mb and one of 2GB, because I wasn't able to find any SSD so small. And at least in my situation, for the boot disk, everything bigger than 64MB would not boot.

DC1MC

[DC1MC]

I have figured out how to use any drive for booting the  system.

I wrote the steps here https://github.com/nukem/Tektronix-AWG420-Support-Files

I had an AWG420 with a broken flash drive. In my search to make it work I found this code https://github.com/tpunix/vxworks-project/tree/master/vxsys that can place a bootloader on a new drive and using FAT16 or FAT32 formats the AWGs uses FAT12 for the boot drive.

The bootloader will load the bootrom.sys on a FAT16 or FAT32 file system.  The hard part was compiling it on a DOS environment and I have uploaded the compiled vxsys.exe on github.  You need a DOS environment to do all the format and  bootloader install.

I hope this  can help someone.

Hi, thanks for your good work, I wish I've had this when I was fighting with boot cards of few MiB !! because of this bloody WindRiver stuff,

Cheers,
DC1MC

[lugaw]

DC1MC thanks for the images you sent it really helped.

Next thing I will try is to use just one flash drive to boot the AWG420 by partitioning it for  boot drive and data drive.  It originally came with just one 128mb flash drive option.

[DC1MC]

DC1MC thanks for the images you sent it really helped.

Next thing I will try is to use just one flash drive to boot the AWG420 by partitioning it for  boot drive and data drive.  It originally came with just one 128mb flash drive option.

I've heard of 520 that were delivered with 1 drive as well, but most likely after they start die, when people were hammering the anemic drive, Tek smarted out and out added a rotating rust as well for data.
Unfortunately due the incorrect belief propagated in the Tek forums that "once the drive is is dead, the device is gone" there are practically no drive images. I'm wondering who had the interest to have these rumors spread      ?

 Cheers,
 DC1MC

[TERRA Operative]

Hi,

I just picked up an AWG510 and I'm interested in doing the CF card mod.
Is there some step by step instructions on how to create the disk images and copy them to the CF cards?

I found the beeper capacitor in my unit is a little leaky too, so I'll have to clean that up as well..

[DC1MC]

Hi,

I just picked up an AWG510 and I'm interested in doing the CF card mod.
Is there some step by step instructions on how to create the disk images and copy them to the CF cards?

I found the beeper capacitor in my unit is a little leaky too, so I'll have to clean that up as well..

Haaii, haaiii, there is, post #43  !!!

OK, so the situation is like this, my unit has the 10MB SSD and the 2GiB HDD, the 2GiB guy was copied 1:1 on an SD card of suitable capacity, there has been no problem as it was recognized immediately by one of the cheap IDE to USB adapter.

The 10MiB one, well, that was a pain, while it was recognized by all my IDE adapters, it was not able to read on any of them  , including an old laptop with dual IDE interfaces.

In desperation, I have booted a linux floppy (VERY rare animal) and did some hackery explained in detail in #43.

The images is attached to a message, so you could still try to use it, it will at least test your SD card as not many are recognized by the BIOS if the capacity is too big.
Any specific issues, please ask here.

Cheers,
DC1MC

[TERRA Operative]

Ok, parts are ordered and on the way.

Now, currently trying to update to version 4.... I got the FTP transfer working and have the two files on the machine, but I can't find the menu option to actually run the update as per the manual..
Is there a trick to it?

I'm currently on Program Version: 1.6b and OS Version: 1.1

[DC1MC]

Ok, parts are ordered and on the way.

Now, currently trying to update to version 4.... I got the FTP transfer working and have the two files on the machine, but I can't find the menu option to actually run the update as per the manual..
Is there a trick to it?

I'm currently on Program Version: 1.6b and OS Version: 1.1

Not so fast nii-san  , you need to do it in two steps, first the OS (1.6b is too old) and then the next OS  and then the User Mode program.
Or at least this is how it went on my 520.

Here the excerpt from Readme.txt that was coming with update archive:


4.Update the System Software (OS and User program)
  In this case, you must update both OS and User Program
  simultaneously.

4.1 Update the OS according to the dialog of
  the system software update menu of the AWGs.

 4.1-1.Select Update Program menu(UTILITY->System->Update System
     Software... ->Update OS...).
 
    Advance to the displayed disclaimer pushing OK when approving.
    Discontinue Cancel pushing when not approving.

 4.1-2.In the side menu of Drive.., select the drive which is transferred
    or copied by 3-1 or 3-2 and push OK.

 4.1-3.Select the module(aw50s30) from the file list and then push OK.

    The dialog of the confirmation is displayed before the
    updating is done.
    After accepting it and pushing OK, the AWGs begins updating.
           
   Warning:Never turn off the power supply while executing
          the update.

 4.1-4.When the message of the update completion appears, push OK.
   Then you should proceed to update the User Program (Step 4.2)

4.2 Update the User Program according to the dialog of
  the system software update menu of the AWGs.

 4.2-1.Select Update Program menu(UTILITY->System->Update System
     Software... ->Update Program...).
 
    Advance to the displayed disclaimer pushing OK when approving.
    Discontinue Cancel pushing when not approving.

 4.2-2.In the side menu of Drive.., select the drive which is transferred
    or copied by 3-1 or 3-2 and push OK.

 4.2-3.Select the module(aw50p40) from the file list and then push OK.

    The dialog of the confirmation is displayed before the
    updating is done.


Where did it failed ?

[TERRA Operative]

I don't have any option to select the 'Update System Software' that I can see, all I get is what's shown in the screenshot of my previous post, unless it's somewhere else in the menu system?

I have both versions of the firmware as you used downloaded from the Tektronix website, so doing the update in steps is fine, I just can't work out how to actually start the update process.... Either my unit is different somehow, or I'm being dumb and can't see it.

Help me obi-wan, you're my only hope!

[DC1MC]

I don't have any option to select the 'Update System Software' that I can see, all I get is what's shown in the screenshot of my previous post, unless it's somewhere else in the menu system?

I have both versions of the firmware as you used downloaded from the Tektronix website, so doing the update in steps is fine, I just can't work out how to actually start the update process.... Either my unit is different somehow, or I'm being dumb and can't see it.

Help me obi-wan, you're my only hope!

I did seem to remember that I had do do something on the secure menu, deleted and enabled some shite, I don't remember for sure, now I have the menu.

[DC1MC]

Ok, I got the Pocket Linux booted and working, but I am sooo lost with Linux stuff... Any chance the ftp of the disk image will work with FileZilla?
How do I run the ftp commands in pocket Linux? I am the n00biest n00b with this stuff...

First of all, the Pocket Linux command running on the device is a FTP client, it will not work with Filezilla, that, AFAIK, is also a FTP client, you need a FTP server, if you can't be bothered to boot on some spare machine an Ubuntu Live CD of USB stick and do the post #43 stuff, you'll have to install a FTP server on the windozian machine:

https://www.windowscentral.com/how-set-ftp-server-windows-10

On the device running Pocket Linux you have to say:
(ping it first to make sure is accessible, also check in the windozian firewall that the ftp incomming connections are allowed)

then enter:

ftp <your ftp server address>

then you will be asked for the user name  (case sensitive !!!)
and the password, that you've selected when you've set up the FTP server.

finally run the command:

put "| cat /dev/hda" ssd_10mb.img

and that's it !!!


As a plan B, I can give you my image (PM if you want it), the software seem to be compatible in between 520/510  and as a bonus, you'll have the update stuff installed.

 Cheers,
 DC1MC

[TERRA Operative]

Ok, I managed to find an old laptop. installed Linux Mint, and I got the 10Mb disk image.
My setup.inf looks identical you yours earlier in the thread.

Did you take an image of the other disk too? What command did you use to mount the drive?
I tried mount /dev/hdb1 -o -ro /mnt but it said it couldn't find a valid MSDOS filesystem or root block and to specify the filesystem type.

[TERRA Operative]

Alrighty, I have this mostly figured out.

- Taking an image of the 10Mb SSD via Pocket Linux and FTP is all ok, and I am able to transfer that image reliably to a 32Mb CF card.
- I have the Dual CF card to IDE adapter working perfectly in the AWG510 after swapping the voltage jumper to 3.3V as mentioned previously by DC1MC.
- I am able to copy an image of the 2Gb disk provided by DC1MC to a 4Gb CF card (BIOS sees 4Gb, but the OS only sees the 2Gb partition as expected, no problems) and it works fine too.


Now, my next problem...

If I use my 10Mb SSD image, my machine boots perfectly BUT it is on OS version 1.x, so I can't upgrade to the latest OS as the option to upgrade is missing in the menu system (Instructions say to 'contact your Tektronix representative'... yay...)
So I used a 10Mb SSD image from DC1MC that was taken from an AWG520 with the latest OS version, and while it boots and seems to work, I get a System error code of 2402 which is 'clock delay data checksum'.
Running any combination of the factory reset/secure wipe/setting the RTC/etc does not seem to fix it. Also, the 2Gb disk used doesn't seem to have any effect on it too, so it's definitely something to do with the SSD image.
I also tried reapplying the latest OS update over the top of the existing installation to no effect as well.

So, at this point I can either have a machine with V1.x OS and no errors, or a machine running V4 and error 2402....

I also need to image my 2Gb HDD, just for posterity, my curiosity, and so I can add the info to the step-by-step instructions I'm writing up that I'll post here when I have it all documented (mostly for my future reference but for others to benefit from too).
I'm not sure if I need to install DC1MC's vxext_fs drivers in Linux Mint to image the HDD? (I am not very good with Linux at all.... )

Also, is it possible to expand the 10Mb partition to use the full size of the 32Mb CF card? Or does this not have any benefit or real reason to do anyway?

[DC1MC]

Alrighty, I have this mostly figured out.

- Taking an image of the 10Mb SSD via Pocket Linux and FTP is all ok, and I am able to transfer that image reliably to a 32Mb CF card.
- I have the Dual CF card to IDE adapter working perfectly in the AWG510 after swapping the voltage jumper to 3.3V as mentioned previously by DC1MC.
- I am able to copy an image of the 2Gb disk provided by DC1MC to a 4Gb CF card (BIOS sees 4Gb, but the OS only sees the 2Gb partition as expected, no problems) and it works fine too.


Now, my next problem...

If I use my 10Mb SSD image, my machine boots perfectly BUT it is on OS version 1.x, so I can't upgrade to the latest OS as the option to upgrade is missing in the menu system (Instructions say to 'contact your Tektronix representative'... yay...)
So I used a 10Mb SSD image from DC1MC that was taken from an AWG520 with the latest OS version, and while it boots and seems to work, I get a System error code of 2402 which is 'clock delay data checksum'.
Running any combination of the factory reset/secure wipe/setting the RTC/etc does not seem to fix it. Also, the 2Gb disk used doesn't seem to have any effect on it too, so it's definitely something to do with the SSD image.
I also tried reapplying the latest OS update over the top of the existing installation to no effect as well.

So, at this point I can either have a machine with V1.x OS and no errors, or a machine running V4 and error 2402....

I also need to image my 2Gb HDD, just for posterity, my curiosity, and so I can add the info to the step-by-step instructions I'm writing up that I'll post here when I have it all documented (mostly for my future reference but for others to benefit from too).
I'm not sure if I need to install DC1MC's vxext_fs drivers in Linux Mint to image the HDD? (I am not very good with Linux at all.... )

Also, is it possible to expand the 10Mb partition to use the full size of the 32Mb CF card? Or does this not have any benefit or real reason to do anyway?

Hi, let's put this in order, from the simplest, to the most complex:

- HDD: you don't need any special Linux driver to imagine the HDD, as log as is recognized by whatever adapter/interface you have, the imaging process is a one-to-one copy of the disk sectors, with total disregard of whatever partition or higher level organization is there.
WORD OF CAUTION: Do NOT attempt to mount that disk, especially on windozian machine, that will recognize the "almost FAT" filesystem and offer to "repair" it, in the process destroying it fully.
If you want to ACCESS the partition and rear/write/modify files there, you can either use the Linux vxWorks driver posted here, or use the NFS mount on the AWG, to my knowledge there is nothing important for the functioning of the device there, the calibration files that are recreated everytime you run the internal calibration process are actually stored on the SSD.

Did you run the calibration already already ?

- OS, that's the tough one, assuming that the issue is not some HW incompatibility that needs a trip to Tex laboratories to move a jumper or switch some bits in the configuration of the AWG boards, that probably means that there are some specific "markers" used by the OS application to recognize the HW, OR is there something on the SSD that is specific to the 510, so I suggest to  look into the original SSD and list all the files there.

There are two files of interest that may screw your device and have to be recreated:

cal.dat

delays.dly

These are device specific and will ABSOLUTELY not work on your device, so mount your SSD card (this one should be mountable) and delete them, or alternatively run the calibration process, or even better, first delete them and then run the calibration process, of course after you've rebooted with the calibration files deleted.

 Now the ball is in your court, let us know how did the calibration process went.

 Cheers,
 DC1MC

EDIT See if the above mentioned files are on your ORIGINAL SSD and copy them on the new OS SSD, it may even work, but I will still run the calibration.

[TERRA Operative]

Cool, I assumed but wasn't sure about the drivers/imaging of the HDD.
I'll give the imaging of it a go tonight to get a copy for my archives
I did read about the Windows thing so have kept both these disks well away from my Windows laptop.

For the SSD, I did run the self-calibration after booting with your disk image and still had the checksum error.
I'll check out the files and compare, and mix and match as you suggest, I suspect it might be something to do with the fact my unit is single channel compared to two channels on your unit..
I'll attach the files here too later so you can take a look yourself too if you like.

[TERRA Operative]

I GOT IT WORKING!!!  

So, the trick was the delays.dly file

I re-imaged the SSD CF card with the AWG520 image so it was clean and fresh.
As is, I was getting the System error 2402 - 'clock delay data checksum'

So I went and deleted the cal.dat and delays.dly files and booted the AWG again and got two more errors:
System: 2701 - 'Calibration data not found' (well yeah, I deleted it)
Output: 7151 - 'CH1 10MHz filter' (as above)

After running self calibration and diagnostic then a reboot the previous errors were gone, but I instead had a System error 2401 - 'Clock delay data not found'

Hmm, so maybe the delays.dly file isn't re-generated with a self calibration...
So I took the delays.dly file from my original SSD disk image and stuck it onto the CF card (and yep, it was missing since I deleted it, but the cal.dat file had been re-generated during the self calibration).

I booted the machine and IT WORKS!!!! No errors!   

It looks like the calibration procedure in the service manual makes adjustments to the clock, so a missing file (i.e. faulty disks) could be re-generated, but a 'Performance Check/Adjustment Disk' (part number 063-2983-00) that was originally supplied with the AWG is needed, so now I'm on the hunt for one of those disks for future calibration/adjustment.....
If we can find that disk, it would then be possible to revive a unit with completely trashed disk drives. All you should need is an SSD and HDD disk image, a couple CF cards, then perform the self calibration and full adjustment to re-generate the missing cal.dat and delays.dly files.


Next step, run through the whole procedure from scratch and document it step by step to post here for future reference. And find that adjustment floppy....

[DC1MC]

I GOT IT WORKING!!!  

So, the trick was the delays.dly file

I re-imaged the SSD CF card with the AWG520 image so it was clean and fresh.
As is, I was getting the System error 2402 - 'clock delay data checksum'

So I went and deleted the cal.dat and delays.dly files and booted the AWG again and got two more errors:
System: 2701 - 'Calibration data not found' (well yeah, I deleted it)
Output: 7151 - 'CH1 10MHz filter' (as above)

After running self calibration and diagnostic then a reboot the previous errors were gone, but I instead had a System error 2401 - 'Clock delay data not found'

Hmm, so maybe the delays.dly file isn't re-generated with a self calibration...
So I took the delays.dly file from my original SSD disk image and stuck it onto the CF card (and yep, it was missing since I deleted it, but the cal.dat file had been re-generated during the self calibration).

I booted the machine and IT WORKS!!!! No errors!   

It looks like the calibration procedure in the service manual makes adjustments to the clock, so a missing file (i.e. faulty disks) could be re-generated, but a 'Performance Check/Adjustment Disk' (part number 063-2983-00) that was originally supplied with the AWG is needed, so now I'm on the hunt for one of those disks for future calibration/adjustment.....
If we can find that disk, it would then be possible to revive a unit with completely trashed disk drives. All you should need is an SSD and HDD disk image, a couple CF cards, then perform the self calibration and full adjustment to re-generate the missing cal.dat and delays.dly files.

Next step, run through the whole procedure from scratch and document it step by step to post here for future reference. And find that adjustment floppy....

Bazaiii  !!!

Congratulations for a job well done, persistence paid off !!!

Now I'm really curious what is in the calibration disk, some bootable stuff to do the adjustments or what ?

Cheers,
DC1MC

[TERRA Operative]

Ok, here are my instructions. it should be mostly correct....
Big thanks to DC1MC and others for the info and help in this process!  

I have made these instructions a verbose step-by-step to make it easier for others following along as well as for me in the future because I forget everything...   

To perform the Compact Flash disk upgrade you will need the following items:

- A PC running Linux (I used Linux Mint on an old laptop) connected to your local network and with internet access.
- 1x 16, 32 or 64Mb CF card (No larger than this or it won't work!)
- 1x 2 or 4Gb CF card (The machine will only see 2Gb maximum)
- 1x CF to USB adapter
- 1x 2.5" IDE to USB adapter
- 1x Dual CF to IDE adapter (Looks like a 2.5" SSD/HDD sized box, holds 2 CF cards and converts them to a 2.5" IDE form factor)
- 3.5" Floppy disk drive (I used a USB floppy drive)
- 3.5" Floppy disk
- PS/2 Keyboard
- A long thin pokey thing to poke into the holes in the side of the Function Generator (I used a straw from a can of aerosol contact cleaner)
- LAN cable connected to your local network
- Soldering iron
- Pocket Linux disk image (attached below)
- Optional - 'ssd_10mb_500_v4.img' SSD image (if upgrading AWG510/520 software to v4, this file works for both model numbers) (attached below)

I am assuming that all files described are in the 'home' directory on the Linux PC and unzipped if required.

Also, do NOT plug these disks into a windows machine. They are VX Works partitions and while they are similar to FAT partitions, there are some incompatibilities that cause Windows to freak out a little and you risk corruption when windows tries to do windows things to the disks... You have been warned!

1) Copy the Pocket Linux image to the floppy disk:
With all extra disks and card readers disconnected from the Linux PC, type 'ls /dev/sd*' into the command line, this will list the currently connected disks.
Plug the floppy drive in to the PC with the floppy disk inserted and run the command again, you will see an additional disk ID present.
If it is the second disk connected to the machine, you will see '/dev/sdb' for example (ignore any trailing numbers, this indicates existing partitions which we don't care about).
Now run the following command, where 'sd*' is the ID found in the previous step. 'sudo dd if=PocketLinux2.51-fix-4.bin of=/dev/sd* status=progress'

2) Install the FTP server:
In the command line, type 'sudo apt install vsftpd'
Once installed, type 'sudo vi /etc/vsftpd.conf' and enable writing of files (delete the # in front of write_enable=YES line), save and exit (Press the <ESC> key, then hold the <Shift> key then press <Z> twice.)
Now type 'sudo systemctl restart vsftpd'

3) Boot Function Generator to Pocket Linux:
Attach the PS/2 keyboard and LAN cable to the Function Generator and insert the Pocket Linux disk into the disk drive.
Poke the thin rod into the hole on the left side of the machine and gently find the button inside, keep depressed while you turn the machine on until text appears on the screen then press F2 to enter BIOS.
Use the down arrow key to select the 'Boot Sequence' option and set it to '[A: then C:]' using the minus key or space bar.
Use the right arrow key to select the 'Exit' menu and select 'Save Changes & Exit'.
Pocket Linux should automatically boot from the floppy disk now.

4) Set Function Generator Network settings:
Select 'Manual Configuration' from the menu.
Set the network settings as needed:
- This Machine's IP: As needed (Choose your IP address)
- Network Mask: As needed to match your network (Typically 255.255.255.0 etc)
- Broadcast Address: Leave blank
- Default Gateway: As needed to match your network (Typically 192.168.1.1 etc)
- Name Server IP(s): Same as Default Gateway
- Default Domain(s): Leave blank

Select 'OK' then 'Exit - Do not configure the network' to get back to the command prompt (we have made the settings so they will stick until reboot, regardless of what it says)

You should see a message saying "This machine's IP is xxx.xxx.xxx.xxx" and a command prompt.
Check connectivity by typing 'ping yyy.yyy.yyy.yyy' (Where yyy.yyy.yyy.yyy is your Linux PC's IP address)
Press 'Q' to exit ping back to command line.

5) Copy SSD Disk Image:
Mount the SSD by typing the following command 'mount /dev/hda1 -o ro /mnt'
Connect to FTP server using the command 'ftp yyy.yyy.yyy.yyy' (Where yyy.yyy.yyy.yyy is your Linux PC's IP address)
Enter the username and password (Typically the login username and password for your PC)
Copy the SSD disk image across to the PC using the following command 'put "| cat /dev/hda" ssd_10mb.img'
Once the transfer is complete, exit the FTP server with the command 'bye'
Turn off the Function Generator using the rear panel switch and remove the Pocket Linux disk.

6) Copy HDD Disk Image:
To image the HDD, I found it's quicker to connect it directly to the PC due to it's size. (slow 10mbit/s LAN is ssslloooooww...)
Remove the existing SSD and HDD from the Function Generator and attach the HDD to the PC with the IDE-USB adapter.
Copy the disk image to the PC using 'dd if=/dev/sd* of=~/hdd_2gb.img' where sd* is the disk ID, using the 'ls /dev/sd*' command as before to determine the correct disk ID.

7) Copy Disk Images to CF Cards:
If not performing step (7a) below, simply run the following command with the smaller CF card connected to the PC with the CF to USB adapter. 'sudo dd if=ssd_10mb.img of=/dev/sd* status=progress' to copy the SSD image (Substitute 'sd*' with the disk ID using 'ls /dev/sd*' as before).

7a) **OPTIONAL IF UPGRADING SOFTWARE TO v4**
With the smaller CF card connected to the PC using the CF to USB adapter, type 'sudo dd if=ssd_10mb_500_v4.img of=/dev/sd* status=progress' to copy the v4 SSD image (Substitute 'sd*' with the disk ID from the previous step, ignore the number).
When finished mount your old SSD disk image by double clicking on it in the in the file explorer and copy the 'delay.dly' file over to the SD card, overwriting the existing file.
This file has a checksum applied, so it is specific to each machine. Using a delay.dly file from another machine will throw errors.
If you are following this guide to replace dead disks and are unable to retrieve your original delay.dly file, you will need to perform a full calibration as described in the service manual to re-generate this file after completing all these steps.
I have uploaded the required 'Performance Verification Disk' disk images needed to perform the calibration and adjustment to the relevant pages on Tekwiki:
https://w140.com/tekwiki/wiki/AWG510
https://w140.com/tekwiki/wiki/AWG610
etc

Once the SSD CF card is imaged, remove it from the CF-USB adapter.

Insert the 2/4Gb CF card into the CF to USB adapter and copy the hdd_2gb.img image file using 'sudo dd if=hdd_2gb.img of=/dev/sd* status=progress' (Substitute 'sd*' with the disk ID using 'ls /dev/sd*' as before).

8 ) Modify and install IDE-Dual CF Adapter:
Open the case of the IDE-Dual CF adapter and remove the PCB.
Move/re-solder the voltage jumper to the 3.3V position (the jumper should short pins 3 and 4 on the voltage selector jumpers, but double check just in case yours is different).
Reassemble the adapter casing and plug the CF cards into the IDE-Dual CF adapter (SSD imaged CF card in Master position, HDD imaged CF card in the Slave position).
Remove the existing SSD and HDD from the Function Generator and install the CF adapter assembly into the machine. Use the first connector on the cable, the second connector can be tucked away neatly.
The red stripe on the cable should be towards the 3.3v/5v jumper end of the connector in the CF adapter.

9) Set Disk Parameters in BIOS:
Reassemble the machine, reconnect the PS/2 keyboard and boot to BIOS, again poking a thin rod into the hole on the left side as before.
Select each disk in turn ('IDE Adapter 0 Master/Slave') and press <Enter> on 'Autotype Fixed Disk' to auto set the parameters.
You can also set the boot order back to '[C: only]' too using the space bar.

Exit saving changes and allow the machine to boot. You may see errors on boot. This is expected and if all went well, they should go away after step (10).

10) Perform Calibration/Diag Routines:
Let the machine warm up and perform a diagnostic test and calibration ('Utility' panel button > 'Diag' bottom button on screen > 'Execute Calibration' then 'Execute Diagnostic') to check it is all ok.

11) Finished!:
Reboot once more for good measure and it's all done!

[TERRA Operative]

Bazaiii  !!!

Congratulations for a job well done, persistence paid off !!!

Now I'm really curious what is in the calibration disk, some bootable stuff to do the adjustments or what ?

Cheers,
DC1MC

I am a happy panda tonight!

I wonder too, I guess it's as you say. Some sort of application that can write that delay.dly file as you run through the full calibration process.

[strick]

Hi,
I recently bought a working AWG610 on Greedbay for a good price as it throwing a waveform memory error (5301) and found this message thread on the Tekwiki site.

I've been trying save an image of the operating system using the bootable Linux floppy method and have been totally unsuccessful.  I simply cannot get the network card to mount in either linux or any of the network floppy methods folks have used on this site.

My network card is a Buffalo LGY-ISA-TR with a chip being a Davicam DM9008F.  My searches for drivers has not been rewarding at all.  I finally ordered a ISA network card (SMC Ultra) that is supposed to be compatible with the floppy Linux to be able to get the image.  I loaded a 32-bit version of Linux Mint on a laptop and an old Pentium 4 desktop (with Pata capability)

However, I fix TEK TDS500-700 and TDS5000 series scopes as a hobby and have all kinds of parts, including a conventional PATA to Travelstar disk (just like the one in the AWGs) adapter.  Has anyone attempted to simply copy the image on the 64 Meg SSD just using an adapter or is the AWG bios required to be in the middle somehow?

thanks,
Strick