Products > Test Equipment
Agilent E7495 linux root account
kirill_ka:
--- Quote from: kirill_ka on March 30, 2021, 08:10:07 pm ---tty sure there should be a JTAG connector on the DSP board which can be used to access the flash.
Here's the picture of the board:
https://www.ebay.com/itm/Agilent-E7495-63015-E7495-20015-990075-101602-REV-103-Board-Assembly/284074186099
--- End quote ---
Ah, right. The link above should be the "Complex source board". I was fooled because it also contains a similar ADSP processor. Note the similarities between the boards.
If you are not fluent with reverse engineering linux/arm code, I think that your best bet is to identify the JTAG connector. Once you can extract the flash image, I might be able to help with recovery.
kirill_ka:
Eric,
Why ever you think that the logic analyser's giving you wrong numbers and 2403 should be read as 230400? :-//
I'd say it's pointless to assume that replaceTrashedRunCode /which is designed to run on different hardware of N1996A/ will magically recover your E7495.
kirill_ka:
--- Quote from: Ericmax on April 01, 2021, 09:53:04 pm ---I would like to believe that it is only a problem of configuration before I part with this object in parts. ;D
--- End quote ---
In Russian this is called "searching at well lit place but not the place where you've lost the thing" ;) I don't know an English equivalent for the phrase.
kirill_ka:
--- Quote from: Ericmax on April 02, 2021, 03:06:28 am ---we could say that with the differences that i don't know what i lost, nor where i lost it. :-BROKE ;D
At first I thought I had flashed the DSP card, but with these last measurements on J102, I am not sure of anything.
why would the A4A1 ADS / CPU Board drop to 4800bd / s and why a
setserial / dev / ttyS3 Baud_base 230400 does not change anything.
I admit being a little confused about the impact of replacing the Dragonfly / Firmware / *. bin files with those from the N1996A as well as the comPort4 file.
--- End quote ---
As you restored the ARM board firmware, there's no reason to think that something's wrong with the configuration of the "CPU board".
The serial port speed is normally set by an application to whatever it wants. So I assume that replaceTrashedRunCode does what it's supposed to do. It may be just incompatible.
kirill_ka:
--- Code: ---USAGE: replaceTrashedRunCode [-r <rev>]
where: -r <rev> = revision to be replaced
--- End code ---
If the help text doesn't lie, you need to specify the revision to be replaced, but not the revision you are going to replace with.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version