Products > Test Equipment

HP Logic Analyzer Inverse Assemblers

<< < (23/37) > >>

ahakman:
Ok, I got it built. I'm just installing the 5.90 version of the logic analyzer software in my VM to see if I can install the addin.

You really have to follow the directions in the manual very carefully. I was trying to figure out why I kept getting a bunch of path errors during the build, and was manually adding folders to the include path in visual studio, but then it got to a header file that just didn't exist, and I was like "WTF???"

Then I read the manual closer - open VS, create the project using the wizard (being sure to visit ALL 3 pages of the wizard), close VS, delete the project file, swap in the other project file, re-open VS, THEN Build. Just a slightly kludgy workaround they had there... ahhh, windows in the 90's / early 2000's - brings back not fond memories...

gslick:

--- Quote from: ahakman on March 03, 2023, 02:15:52 am ---Ok, I got it built. I'm just installing the 5.90 version of the logic analyzer software in my VM to see if I can install the addin.

You really have to follow the directions in the manual very carefully. I was trying to figure out why I kept getting a bunch of path errors during the build, and was manually adding folders to the include path in visual studio, but then it got to a header file that just didn't exist, and I was like "WTF???"

Then I read the manual closer - open VS, create the project using the wizard (being sure to visit ALL 3 pages of the wizard), close VS, delete the project file, swap in the other project file, re-open VS, THEN Build. Just a slightly kludgy workaround they had there... ahhh, windows in the 90's / early 2000's - brings back not fond memories...

--- End quote ---

Yeah, a couple of other details I didn't mention yet:

First, before you use Visual Studio to create the first IAL wizard project, you need to modify this file:

C:\Program Files\Agilent Technologies\Logic Development\Analysis AddIn Wizard\wizard-files\Templates\1033\AnalysisAddIn_vcproj.txt

There are two lines in that file:

--- Code: ---AdditionalDependencies="agAnalysisAddIn_i.idl;agAnalysisAddIn2_i.idl;"

--- End code ---

Change both of those lines to:

--- Code: ---AdditionalDependencies="agAnalysisAddIn_i.idl;agAnalysisAddIn2_i.idl;agAnalysisAddIn3_i.idl;"

--- End code ---

It appears that there may be errors building an IAL wizard project if those changes are not made before using the wizard to create a new project.

And second, each time you use Visual Studio to create a new IAL wizard project, the newly created project directory should contain a .vcproj file, and a .vcproj.replace file. As the file name suggests, first close the new project, replace the .vcproj file with the .vcproj.replace file, and then reopen the new project. If you forget to do that the project will fail to build with the original .vcproj file.


After you successfully build an IAL wizard project dll, inside the project directory the IA wizard scripts should have created a directory with a create.bat file. That's what you run to create the installation directory. It will copy the IA dll to an installation directory that you specify by defining the shell variable ANALYSIS_DIRECTORY. It will also copy to that directory install.bat and uninstall.bat files, some .reg registry addition files, and RegisterAddIn.exe and UnregisterAddIn.exe utilities used by the install.bat and uninstall.bat files.

To actually install the IA dll you would run the install.bat file from the installation directory created by running the create.bat file.

As-is, the generated .reg registry addition files only work when the logic analyzer application is installed on a 32-bit version of Windows. They can be modified to work when the logic analyzer application is installed on a 64-bit version of Windows.

ahakman:
Yes, when I was mucking around trying to install the LA suite 5.90.whatever, I had tons of issues, and ended up really borking up my VM image - good thing it's a VM image, and it was just a copy of a good image!

I did all of what you mentioned, except adding in the agAnalysisAddIn3_i.idl; dependency to the AnalysisAddIn_vcproj.txt file. The DLL still seemed to build fine.

I also figured out all the stuff about how to make the install directory from reading the batch files themselves. I copied the directory to the 16903A on a usb stick and ran the intall.bat file, and now it actually shows up in the tools menu (and my actual logic analyzer is running version 4.00.[whatever].

Now I have 2 questions:
Is is there a quick way to import the bus / pod assignments? If I try to add the IA analyzer, I get an error message saying (shortened / paraphrased) "The analysis tool has requested signal ADDR as input, but that signal isn't defined". I could define the bus layouts to the pods manually, but isn't there a way to do that automatically from some of the files in the .zip files at the beginning of this thread? It doesn't seem to like to import either the txt version of the config, or the .p binary version of the config. It's not that big of a deal - it took 2 minutes to define the buses by hand using the .txt version of the config from the zip file

The 68020 IA has 5 pods worth of signals defined. ADDR = 2 pods, DATA = 2 PODS, STAT = 1 POD. I have 2 cards that are 4 pods each, so the first card is entirely the address and data buses (as they're 32 bits each), and then the STAT bus needs to be on the first pod of the second card. So currently I have the cards independent of eachother, but with it setup that way, I can't assign signals or buses from more than one card to the IA at the same time. Is there a way to do this? Or is the only way to link the cards together with the linking cables into one larger analyzer? I would expect that I could just clock both cards from the same clock, and use them in state mode as if they're one larger card, even if they're not linked with the joiner cables, and then assign buses from pods on both cards into the signals the IA is looking for. Is this not the case??

MarkL:
Unless you're trying to analyze two independent domains, the cards are supposed to be linked together.  This allows multiple cards to operate as one seemless unit, and it takes care of clocking, skew, pattern matching, and triggering across all the inputs.

I think you said in a previous post you had two 16752A cards.  You would need two flat-flex jumpers to combine the two cards.  If you don't have them, you can buy them as a set 16715-60001, or individually as 16715-61603.  There's a pair on ebay right now for $10 + shipping.

ahakman:
On the 2 cards I repaired, I would have to replace the sockets on the cards for the linking cables as well - they're pretty cruddy looking and corroded.

Anyone know what the connector is on the board side so I could order new ones?

Would you trust these to work? I don't think I would... the only one that is maybe ok is card2 connector 2. The rest look pretty awful

Oddly enough I have 2 more cards here temporarily that are also broken and corroded very badly under the runners, but the linking connectors are perfect on those. Unfortunately those cards will be going back because they were sold as "Used (aka functional)" on ebay, both fail the self tests, and the seller seems to think his broken junk is worth more than I'm willing to pay for the privilege of spending hours under the microscope fixing them.

These things really are a PAIN at every step of the way...

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod