Need full firmware (full dump flash) oscilloscope Atten ADS 1062CML

[alexitaly]

Or test with the CML .CFG file, to see if the CML flag makes any difference.

I've tried, but no... the roll mode is completely wrong: the writing of the dots on the screen is too fast (it seems that they are time-random written). I need to try the (very) old atten firmware. And hope well 

[tv84]

OK, so we have to regroup and rethink our current situation:

- You confirm that you can flash any Siglent CNL/CML FW, right?
- You can't flash any Atten FW, right?
- The .CFG that provides the best results is the "stock" Siglent_CNL.cfg, right?

[alexitaly]

OK, so we have to regroup and rethink our current situation:

- You confirm that you can flash any Siglent CNL/CML FW, right?
- You can't flash any Atten FW, right?
- The .CFG that provides the best results is the "stock" Siglent_CNL.cfg, right?

Yes to all 

[alexitaly]

Try this one.

Big hopes...

ok wait please

EDIT

YAHUUUUUUUU 

THANKS A LOT!!!!!!!!!

The signals with slow time bases seems to be correct, i've to do some test 

[tv84]

ALLELUIA!   

[alexitaly]

ALLELUIA!   

Do you want to buy an oscilloscope? ADS1102CAL   

[tv84]

Do you want to buy an oscilloscope? ADS1102CAL   

Now it is somewhat recovered, we could try investigate the BW upgrade.

Could you send the 3 SCPI commands and *IDN?  to see their response?

[alexitaly]

Ok, please wait

EDIT

Hi tv84,
i've tried, but the old Atten fw does not implement SCPI commands. Today, i will try the old Easyscope 3 (not Easyscope X), wich uses a proprietary protocol.
If you want, i've also the SDS1102CML on my bench. I've tried the SCPI commands also with it, and only SRLN seems to work.

[routerfan]

Routerfan,

Can you make dumps through JTAG?

It would help a lot if we could see the difference in the dumps of the changes we make.

So, now, we've been successful in changing the Product ID of the FW and the Product Type that appears in the scope's screen.

Both changes are useless but, at least, we know they work...

We need to discover what needs to be changed. I'll try to have another look.

From both of you it would help if you were able to dump via JTAG!

I finally exported the firmware of the device through Altera USB Blaster, and I will try to compare other BIN files I can find. But I am not familiar with this.
Warning: The uploaded files are only for research and comparison. Please do not use it for flashing, otherwise it will cause your device to become brick.

[alexitaly]

Do you want to buy an oscilloscope? ADS1102CAL   

Now it is somewhat recovered, we could try investigate the BW upgrade.

Could you send the 3 SCPI commands and *IDN?  to see their response?

Hi tv84, sorry for delay.
Yesterday and today i've tried in many ways to send commands to oscilloscope.
I've tried with two PCs: one very old desktop (AthlonXP, 256Mb RAM, WinXP), another recent laptop (i3 8th, SSD, Win10 64bit).
I'e installed Easyscope 3 on the old machine, and NI-MAX on the new machine.

The ATTEN ADS1102CAL does not respond to SCPI commands: it communicates only with EASYSCOPE software, rel 3R001B03D01P11 (the previous version that i have on the supplied CD made me crazy: test connection ok but link failed... one day of test, reinstalling software, controlling pc). In the Atten oscilloscope i've installed, in the end, the fw version with product_id=80 (after your version with product_id=79 that allowed me to downgrade from Siglent fw). I've tried this fw because i've thinked that the connection problems with Easyscope could be caused from the modified version of fw, instead it was Easyscope's faults.

The SIGLENT SDS1102CML respond to SCPI commands: it communicates with NI-MAX. It respond only to the SRLN? command.

How can i help you?

[tv84]

Guys, I'll try to answer as soon as I have more time. Thanks

[routerfan]

Hi, alexitaly
 Since we have a consistent hardware platform, if you are convenient, can you share with me your full dump flash file.
 I have built a JTAG chain to easily flash any firmware.  I think the ultimate solution to all problems is to find the appropriate dump flash files

[routerfan]

Guys, I'll try to answer as soon as I have more time. Thanks

Thanks TV84！

[alexitaly]

Hi, alexitaly
 Since we have a consistent hardware platform, if you are convenient, can you share with me your full dump flash file.
 I have built a JTAG chain to easily flash any firmware.  I think the ultimate solution to all problems is to find the appropriate dump flash files

Hi routerfan.
I'm convenient, but the problem is that i haven't a JTAG programmer (you have a very well Segger). I have only a ST-LINK V2, but i don't know if it can be useful.
I'm thinking to buy a JTAG programmer, but what?
Have you tried the firmware that tv84 has linked? I've tried, and my oscilloscope is as new, with pros and cons.
The bad news is that the keyboard response is not very good, the SCPI commands are not implemented, the USB-memory over 1GB (the old 4GB gold usb key that you can see in some my photo) are not correctly recognised. All these problems are original characteristics of the dso.
If the tv84's last fw doesn't works properly, i think that you could have hw problems: in fact you have soldered and removed a memory chip, but are you sure that the memory chip that you have installed was compatible with our hw revision?

If, after covid epidemic, i won't have any work problems, i'm thinking to change dso with a SDS1202X-E if it hasn't particular problems.

[tautech]

the USB-memory over 1GB are not correctly recognised. All these problems are original characteristics of the dso.

Some are, some are not, there is no hard and fast rule ..... but cheap USB sticks can give issues.
It is also important the USB stick is formatted as FAT32.

[alexitaly]

the USB-memory over 1GB are not correctly recognised. All these problems are original characteristics of the dso.

Some are, some are not, there is no hard and fast rule ..... but cheap USB sticks can give issues.
It is also important the USB stick is formatted as FAT32.

Hi tautech, thanks for your reply.
The memory stick is the same Verbatim 4GB that you can see in my photos. The Siglent's fw recognise correctly the key, the Atten's fw no. But it's normal, it's a feature that i remember... it's the Atten fw that is very old.

[alexitaly]

Or test with the CML .CFG file, to see if the CML flag makes any difference.

Hi tv84, this .CFG file is compatible with SDS1102CML, hw rev 11-62-3.5?

[tv84]

Yes, the CML .CFG should be compatible with all Siglent CML. From what I see in regards to a CNL .CFG the difference is only one byte that the scope tests. I think it's the flag that tells it to use the extra memory.

BTW, we have to do a more detailed analysis of the SCPI commands thing. The Atten has SCPI commands, I can see that in the FW. Of course, not all the ones that we are trying to test. I'll try to get a list.

[alexitaly]

Yes, the CML .CFG should be compatible with all Siglent CML. From what I see in regards to a CNL .CFG the difference is only one byte that the scope tests. I think it's the flag that tells it to use the extra memory.

Ok thanks

BTW, we have to do a more detailed analysis of the SCPI commands thing. The Atten has SCPI commands, I can see that in the FW. Of course, not all the ones that we are trying to test. I'll try to get a list.

I haven't the source code, then i can't say anything, but... are you sure?
I think that, maybe, the commands are similar, but no control software (NI or KEYSIGHT) can see the oscilloscope.
I've tried and re-tried: there isn't VISA driver, and with the old Atten driver (only that works correctly with Atten old fw) neither NI-MAX nor Keysight IO libraries can see the oscilloscope.
Could Easyscope 3 be a primitive attempt of software to dialogue through an embryonic SCPI protocol?

[tv84]

Alex,

As I've said in the past, I think the flag bits in the .CFG of the Atten disable the SCPI commands. So we should flash a .CFG that is similar to the Siglent, to see if we can get answers from the commands.

Need time to craft one.

[alexitaly]

Alex,

As I've said in the past, I think the flag bits in the .CFG of the Atten disable the SCPI commands. So we should flash a .CFG that is similar to the Siglent, to see if we can get answers from the commands.

Need time to craft one.

I will gladly wait for the new file. I hope that i can help you 
The only doubt I have is about the drivers and the fact that it is not correctly recognized by NI and Keysight, but... i wait 

[routerfan]

Hi, alexitaly
 Since we have a consistent hardware platform, if you are convenient, can you share with me your full dump flash file.
 I have built a JTAG chain to easily flash any firmware.  I think the ultimate solution to all problems is to find the appropriate dump flash files

Hi routerfan.
I'm convenient, but the problem is that i haven't a JTAG programmer (you have a very well Segger). I have only a ST-LINK V2, but i don't know if it can be useful.
I'm thinking to buy a JTAG programmer, but what?
Have you tried the firmware that tv84 has linked? I've tried, and my oscilloscope is as new, with pros and cons.
The bad news is that the keyboard response is not very good, the SCPI commands are not implemented, the USB-memory over 1GB (the old 4GB gold usb key that you can see in some my photo) are not correctly recognised. All these problems are original characteristics of the dso.
If the tv84's last fw doesn't works properly, i think that you could have hw problems: in fact you have soldered and removed a memory chip, but are you sure that the memory chip that you have installed was compatible with our hw revision?

If, after covid epidemic, i won't have any work problems, i'm thinking to change dso with a SDS1202X-E if it hasn't particular problems.

Yes, ADS_1102CAL_ok.zip has been used by programmers before, and it has been refreshed by JTAG now. Proved to be invalid on my device. The keyboard responded very slowly. I used another file, which was sold by a friend. On the surface, there are no problems with all functions. The keyboard responds quickly, but the waveform is still as bad. I suspect that the loss of verification data caused my problem. In addition, I did not find the ST-LINK option in the TopJTAG Flash Programmer settings, it is estimated that it cannot be used.

[routerfan]

Guys, I'll try to answer as soon as I have more time. Thanks

Thanks TV84！

Have you tried this one?

Yes, I have tried, neither the chip is taken down for burning or burning through jtag has solved my problem

[tv84]

I think I've finally found some answers:

- Both your original HWs (routerfan and alexitaly) are the same: HW 3-41-1.61
- The first number is the most important: 3
- This version is too old for crossflashing to Siglent FWs.

Nobody has ever done a successfull crossflash from a HW 3-x-x to Siglent!!!

All successfull Atten CAL conversions were for FWs: 6-x-x and 11-x-x

routerfan now has flashed the dumps of other guys which changed the HW version BUT, originally, it was 3-41-1.61.

So, the only way to solve routerfan's problem is, for example, to alexitaly make a dump of is own scope. 

With that dump we could do more experiments in order to upgrade the bandwidth.


BTW, what PCB references do you see on your PCB boards? I think you don't have any Siglent reference, right?

[routerfan]

I think I've finally found some answers:

- Both your original HWs (routerfan and alexitaly) are the same: HW 3-41-1.61
- The first number is the most important: 3
- This version is too old for crossflashing to Siglent FWs.

Nobody has ever done a successfull crossflash from a HW 3-x-x to Siglent!!!

All successfull Atten CAL conversions were for FWs: 6-x-x and 11-x-x

routerfan now has flashed the dumps of other guys which changed the HW version BUT, originally, it was 3-41-1.61.

So, the only way to solve routerfan's problem is, for example, to alexitaly make a dump of is own scope. 

With that dump we could do more experiments in order to upgrade the bandwidth.


BTW, what PCB references do you see on your PCB boards? I think you don't have any Siglent reference, right?
[/qu
Yes, I very much agree with you. The hardware version of 3.xx is really old, so that no suitable firmware can be returned, but there is indeed the word  Siglent on the motherboard. The earliest product, so I think the ultimate solution to the problem is to find the full dump flash files suitable for the pcb.