Hi tv84, first of all thanks for your help.
Attached there is the Siglent FW that is installed in my scope.
Note that the FPGA in my scope is a CYCLONE III (is this the problem? Old hw?).Quote from: tv84Have you tried using the latest CML/CNL firmware 5.01.02.32 (Release Date 07.09.15 )?
Yes, i've tried and the problem is the same.
Thanks...
(https://i.imgur.com/Q8PE5BZl.jpg)
(https://i.imgur.com/sipzaLil.jpg)
SDS1000CML_SSP_V100R005B01D02P32.ADS / CRC32: 68A992F5
File Header Size: 00000048
00000000 - File Checksum: F554D6CF [00000004-00173142] (with only the File Header decrypted) CKSM OK
00000004 - File Size: 001730FB (without 0x48 bytes of the File Header)
00000008 - # Blocks: 0000881C
0000000C - Blocks Area Size: 000F698B [0007C770-001730FA]
00000010 - Product_ID: 79
00000026 - Contents: The help info
0000003A - USB Host Controller: ISP1763
****************************************************
Decrypting the 0x2800 and 0x1400 blocks...
Reversing file...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x000B987E until 0x001730FA
****************************************************
00000000 - Section Checksum: FCE1FD30 [00000004-0007C76D] CKSM OK
00000004 --- 0007C76D ***** Menus / Help Section *****
****************************************************
0007C770 - Removing block encapsulations from Block Area [0007C770-001730FA]
Total bytes extracted (from the blocks): 000CC0E5 Block area processed OK
Buffer Size: 00006DEA bytes (after converting from 16 to 8 bits)
00000000 --- 0x00000000 DXE 0000 (Data Size: 00006DD4) [00000000-00006DE1]
Processor Type: ADSP-BF533/534/536/537/538/539 (boot address: 0xFFA00000)
Orig Offset: Offset: Block: Target Add: Byte Count: Flags: [ start - end ]
00000000 +++ 0x00000000 0000 FF800040 00000004 0012 [0000000A-0000000D] resvect ignore
0000001C +++ 0x0000000E 0001 FF800000 000022B0 0002 [00000018-000022C7] resvect
00004590 --- 0x000022C8 0002 FF8022B0 00000010 0003 zero-fill resvect
000045A4 --- 0x000022D2 0003 FF8022C0 00000010 0002 [000022DC-000022EB] resvect
000045D8 --- 0x000022EC 0004 FF8022D0 0000029E 0002 [000022F6-00002593] resvect
00004B28 --- 0x00002594 0005 FF80256E 0000000E 0003 zero-fill resvect
00004B3C --- 0x0000259E 0006 FF80257C 000009BA 0002 [000025A8-00002F61] resvect
00005EC4 --- 0x00002F62 0007 FF802F36 000000AA 0003 zero-fill resvect
00005ED8 --- 0x00002F6C 0008 FF802FE0 0000000C 0002 [00002F76-00002F81] resvect
00005F04 +++ 0x00002F82 0009 FF902000 00000004 0002 [00002F8C-00002F8F] resvect
00005F20 --- 0x00002F90 000A FF902004 00000068 0003 zero-fill resvect
00005F34 +++ 0x00002F9A 000B FFA00000 00003E32 0002 [00002FA4-00006DD5] resvect
0000DBAC +++ 0x00006DD6 000C FFA00000 00000002 000A [00006DE0-00006DE1] resvect init
0000DBC4 --- ZLIB Decompressed Size: 001EEE90
0000DBCC --- ZLIB Compressed Block Size: 000BE511 [0000DBD4-000CC0E4]
****************************************************
Section Processed OKThis is the parsing of SDS1000CML_SSP_V100R005B01D02P32
****************************************
SDS1000CML_SSP_V100R005B01D02P32.ADS / CRC32: 68A992F5
...
Processor Type: ADSP-BF533/534/536/537/538/539 (boot address: 0xFFA00000)
****************************************
Processor Type: ADSP-BF533/534/536/537/538/539 (boot address: 0xFFA00000)
After rolling back to 1102cal, the waveform still makes people crash, the machine can run, it makes no sense
Alex,
If you want to downgrade to Atten CAL 3.01.01.31.16 here is the file.
I'll try to modify the Atten CAL (Product ID 79) to allow flashing from a Siglent CML/CNL (Product ID 80).
|O
It's referring to the "Product Type" which is SDS1102CNL !
I changed the "Product ID" of the FW.
SHow me what is the response to these SCPI comands:
MD5_CMPY?
MD5_PR?
MD5_SRLN?
routerfan,
Try flashing this file (through the upgrade method).
If it succeeds, it will change the "Product Type" of your scope to "ADS1102CAL". I hope... Then you can flash my previous .ADS.
If it doesn't succeed, don't blame me! :)
This file was done specifically for you since your are able to recover the flash via programmer, I think you should be able to recover if anything goes wrong.
You upgraded with the .cfg also?
Show me the results of those SCPI commands.
So, you still can't upgrade with the Atten firmware, right?
Show me the results of those SCPI commands.
Thank you tv84, I will try to use this CFG file to upgrade the configuration after work, and will also try to install Easysysope and use SCPI commands.Be sure to install EasyScopeX correctly and before connecting the DSO to the PC otherwise Windows can install a generic USB driver and it won't work ! Then you will need to edit/replace the USB driver in Device Manager.
Thank you tv84, I will try to use this CFG file to upgrade the configuration after work, and will also try to install Easysysope and use SCPI commands.
You are right, I can try boldly, because I can recover any file through the programmer, thank you again for your efforts! :clap: :-+
Here is the official .CFG file of Atten CAL scopes. This will place back all Atten settings, including the splash screen.
Let's try this one.
Yes, I can dumps through JTAG, I am talking about hardware. But I don't quite have the skills in this area, so I need some basic guidance. And I do n’t have JTAG pins installed on my oscilloscope, if I want to do this I have to install them,This will take some time， thank you, TV84!
Tell me the responses to the SCPI commands.
And try again to flash the Atten FW (ID 79 and 80).
With EasyScopeX ?Tell me the responses to the SCPI commands.
I'm trying and i've little driver problems.
With EasyScopeX ?Tell me the responses to the SCPI commands.
I'm trying and i've little driver problems.
Please see attached tips for correcting them.
Tell me the responses to the SCPI commands.
Tell me the responses to the SCPI commands.
I can't find the commands that you want in this document:
https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/ProgrammingGuide_forSDS-1-1.pdf
Do you need other special commands?
I think that, if you can, you have to change also product type in ATTEN fw with product_ID=79 (siglent): from ADS1102CAL to SDS1102CNL... what do you think?
Thanks!
Tell me the responses to the SCPI commands.
I can't find the commands that you want in this document:
https://siglentna.com/wp-content/uploads/dlm_uploads/2017/10/ProgrammingGuide_forSDS-1-1.pdf
Do you need other special commands?
I think that, if you can, you have to change also product type in ATTEN fw with product_ID=79 (siglent): from ADS1102CAL to SDS1102CNL... what do you think?
Thanks!
You can't find those commands because Siglent doesn't want to publicize them. They are internal commands.
About the Prod_ID: I included Atten FW in 79 and 80 versions. If that was the filter, it would work. There is another check and I think we need a memdump to find out.
Tell me the responses to the SCPI commands.
ATTEN_ADS1000CAL_V100R003B01D01P31R16.ADS / CRC32: 3195554C
File Header Size: 00000048
00000000 - File Checksum: F55C9872 [00000004-0018773E] (with only the File Header decrypted) CKSM OK
00000004 - File Size: 001876F7 (without 0x48 bytes of the File Header)
00000008 - # Blocks: 0000935B
0000000C - Blocks Area Size: 0010AF87 [0007C770-001876F6]
00000010 - Product_ID: 80
00000026 - Contents: The help info
0000003A - Version: 2.0.3.10
****************************************************
Decrypting the 0x2800 and 0x1400 blocks...
Reversing file...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x000C3B7C until 0x001876F6
****************************************************
00000000 - Section Checksum: FD8543B6 [00000004-0007C76D] CKSM OK
00000004 --- 0007C76D ***** Menus / Help Section *****
****************************************************
0007C770 - Removing block encapsulations from Block Area [0007C770-001876F6]
Total bytes extracted (from the blocks): 000DCEA4 Block area processed OK
Buffer Size: 00006DEA bytes (after converting from 16 to 8 bits)
00000000 --- 0x00000000 DXE 0000 (Data Size: 00006DD4) [00000000-00006DE1]
Processor Type: ADSP-BF533/534/536/537/538/539 (boot address: 0xFFA00000)
Orig Offset: Offset: Block: Target Add: Byte Count: Flags: [ start - end ]
00000000 +++ 0x00000000 0000 FF800040 00000004 0012 [0000000A-0000000D] resvect ignore
0000001C +++ 0x0000000E 0001 FF800000 000022B0 0002 [00000018-000022C7] resvect
00004590 --- 0x000022C8 0002 FF8022B0 00000010 0003 zero-fill resvect
000045A4 --- 0x000022D2 0003 FF8022C0 00000010 0002 [000022DC-000022EB] resvect
000045D8 --- 0x000022EC 0004 FF8022D0 0000029E 0002 [000022F6-00002593] resvect
00004B28 --- 0x00002594 0005 FF80256E 0000000E 0003 zero-fill resvect
00004B3C --- 0x0000259E 0006 FF80257C 000009BA 0002 [000025A8-00002F61] resvect
00005EC4 --- 0x00002F62 0007 FF802F36 000000AA 0003 zero-fill resvect
00005ED8 --- 0x00002F6C 0008 FF802FE0 0000000C 0002 [00002F76-00002F81] resvect
00005F04 +++ 0x00002F82 0009 FF902000 00000004 0002 [00002F8C-00002F8F] resvect
00005F20 --- 0x00002F90 000A FF902004 00000068 0003 zero-fill resvect
00005F34 +++ 0x00002F9A 000B FFA00000 00003E32 0002 [00002FA4-00006DD5] resvect
0000DBAC +++ 0x00006DD6 000C FFA00000 00000002 000A [00006DE0-00006DE1] resvect init
0000DBC4 --- ZLIB Decompressed Size: 001FC96C
0000DBCC --- ZLIB Compressed Block Size: 000CF2D0 [0000DBD4-000DCEA3]
****************************************************
Section Processed OKAs you can see, the FW header has a Product_ID but it doesnt have a Product_Type! So, I don't know what they can be verifying.
I asked routerfan for a memdump so that we can see what they might be verifying.
BTW, what FW do you have flashed at this moment?
Has to be the Atten FW. Because the Siglent CNL/CML would return something like this:
OK, Alex.
In that case, let's do an experiment: Flash the CNL .cfg file and try to see the responses to the 3 SCPI commands that I said.
Here is the .cfg file.
And show me the other half of the attributes tab:
Can be with Atten or Siglent .CFG.
Tell me this:
When you try to upgrade with Atten FW ProdID=79 or Atten FW ProdID=80 the error is exactly the same? About Product Type?
Try flashing this file (Prod_ID=59).
Did you try it after .CFG Atten or .CFG SIGLENT ?
I want that you try it in both.
SCPI commands: look at the different answers with siglent.cfg file and with atten.cfg file.
The only working SCPI command is SRLN.
Running out of ideas...
Flash this .CFG file and then try the Atten .ADS files (79, 80, 59).
With this last .CFG please show a photo of the Hardware version in system menu.
So that you understand what I'm trying to do:
So that you understand what I'm trying to do:A red flag to me is:
Reversing 1st part of the file [00000000-000000D7]...
XORing with 0xFF (incrementing pattern)...
XORing with 0xFF from 0x0000006C until 0x000000D7
00000000 - Main Checksum: FC5AD47B [00000004-00052517] CKSM OK
00000004 - Product_Type: ATTEN
00000024 - CFG Type: SDS1204CF
00000038 - Manufacturer: ATTEN
00000043 - CML/CNL flag: 0
00000044 - Product_ID: 79
00000048 - Image Size: 00052440 (112 320 pixels)
0000004C - USBTMC_Product_IDs: EE39 EE38 EE3A
00000052 - USBTMC_Vendor_ID: F4EC
00000054 - Product Family: ADS
00000058 - Manufacturer_Name: Atten Technologies Co,. Ltd.
00000098 - CFG Flags: 01 00 00 00 00 00 00 00 0000 00
000000C8 - ***** Boot Logo image (480x234 RGB24) ***** [000000C8-00052517] CKSM: FC5AEA31
00052518 - Footer Checksum: FFFF9C53 [0005251C-000525B8] CKSM OK
00052520 - Model Name 0:
0005252F - Model Name 1:
0005253E - Model Name 2: ADS1062CAL
0005254D - Model Name 3: ADS1102CAL
0005255C - Model Name 4: ADS1152CAL
0005256B - Model Name 5:
0005257A - Model Name 6:
00052589 - Model Name 7:
00052598 - Model Name 8:
000525A7 - Model Name 9:
The .CFG file has some "flags" that seem to influence the way the scope will work. I've tried messing with some of them. Everytime you change one, you have to correct the 1st Checksum.
This list describes the contents of this latest Atten_CAL_all0.cfg. I changed a lot of flags to 00. To see which influences IDN, for example, we must turn on one by one.
I updated the previous mail.
The green part is fixed in ALL .CFG files. Atten, Lecroy, Siglent... I think the CF means "Config Format".
The string that decides the scope model are the ones in blue, and are chosen accordingly to the BW of your scope.
Ok BW... but... memory depth? The bug that plagues my oscilloscope is related to wrong writes in memory with slow time bases... this is why i want to downgrade to an old fw version. I want to verify if in that version there is the same bug. :'( :'( :'( :'( :'( :'(Part of this might just be the memory depth management at differing timebases.
Or test with the CML .CFG file, to see if the CML flag makes any difference.
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?
Try this one.
Big hopes...
ALLELUIA! :popcorn:
Do you want to buy an oscilloscope? ADS1102CAL :D
Routerfan,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.
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!
Do you want to buy an oscilloscope? ADS1102CAL :D
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?
Guys, I'll try to answer as soon as I have more time. ThanksThanks TV84！
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 :popcorn:
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.
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.
Or test with the CML .CFG file, to see if the CML flag makes any difference.
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.
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.
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.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 :popcorn:
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, I have tried, neither the chip is taken down for burning or burning through jtag has solved my problemGuys, I'll try to answer as soon as I have more time. ThanksThanks TV84！
Have you tried this one?
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.
Alex,
Thanks for helping.
I think you could buy this one: https://www.ebay.com/itm/J-Link-JLink-V8-USB-ARM-JTAG-Emulador-Debugger-Programador-chips-ARM/264086370459 (https://www.ebay.com/itm/J-Link-JLink-V8-USB-ARM-JTAG-Emulador-Debugger-Programador-chips-ARM/264086370459)
Hope it's not fake because it's very good offer. Maybe it's better to hear what routerfan has to say (and what he bought).
Also, I would like you to redo the Siglent conversion in your scope with the:
- SDS1000CNL_SSP_V100R005B01D02P13
- reboot
- flash the Siglent CNL .CFG
- and to a self calibration! Did you ever do this self calibration?
If it worked for bithead it has to work for you! :)
Hello everyone, the repair of 1102cal is still going on. Recently I accidentally found the data that was previously backed up with the programmer. Unfortunately, it was backed up after the problem, but it restored me to the hardware version of 3.xx, but not 3. -41-1.61 but 34-1-2.3, my original serial number is back. The system was left by refreshing 1102cnl at that time, and I will try to restore the most original state through the TV84 patch firmware.
Regarding jlink, I use jlink v8. Of course, it will not be genuine, but it was given by the seller when they bought something. Similar things are very cheap in our place for well-known reasons. The use effect is also very good, it only takes one and a half hours to burn an 8M firmware, compared to WIGGLER CABLE
It's a lot faster. I also have an Altera downloader USB Blaster debugger, I tested it, it can be used on this oscilloscope, alexitaly I can give it to you if necessary, but you are responsible for postage.
In addition, I contacted domestic resources that can be reached. I got the calibration procedure of the oscilloscope, I think about it again and again, not very good to announce here. If alexitaly you need it, I can send it to you for research. But I haven't used it myself, and the technical risks must be acceptable to you. Thanks!
V84, I used jlink v8 to finish the work. Altera USB Blaster has also been tested by the way, and they all work very well.
Hello everyone, the repair of 1102cal is still going on. Recently I accidentally found the data that was previously backed up with the programmer. Unfortunately, it was backed up after the problem, but it restored me to the hardware version of 3.xx, but not 3. -41-1.61 but 34-1-2.3, my original serial number is back. The system was left by refreshing 1102cnl at that time, and I will try to restore the most original state through the TV84 patch firmware.
Regarding jlink, I use jlink v8. Of course, it will not be genuine, but it was given by the seller when they bought something. Similar things are very cheap in our place for well-known reasons. The use effect is also very good, it only takes one and a half hours to burn an 8M firmware, compared to WIGGLER CABLE
It's a lot faster. I also have an Altera downloader USB Blaster debugger, I tested it, it can be used on this oscilloscope, alexitaly I can give it to you if necessary, but you are responsible for postage.
In addition, I contacted domestic resources that can be reached. I got the calibration procedure of the oscilloscope, I think about it again and again, not very good to announce here. If alexitaly you need it, I can send it to you for research. But I haven't used it myself, and the technical risks must be acceptable to you. Thanks!
Routerfan,
which one did you use to make your FW dump? The Altera USB Blaster?
Or you were also able to do a dump with J-Link v8 ?
Since I am a private individual and do not use it for work, can this (https://it.farnell.com/segger/8-08-91-j-link-edu-mini/unit-didattica-cortex-m/dp/3106578) be fine?Of course there is no problem, PM your mailbox, I will send it to you. It is done through the rs232 interface and a host computer, as I said before, I have not tested it and have no experience in this area. You have to be prepared for failure.
Of course there is no problem, PM your mailbox, I will send it to you. It is done through the rs232 interface and a host computer, as I said before, I have not tested it and have no experience in this area. You have to be prepared for failure.
Of course there is no problem, PM your mailbox, I will send it to you. It is done through the rs232 interface and a host computer, as I said before, I have not tested it and have no experience in this area. You have to be prepared for failure.
Hi routerfan: don't worry. Do not ship anything: there are problems with customs due to covid.
I've buyed this (https://www.amazon.it/Adattatore-Debugger-ICprog-OpenOCD-JTAG/dp/B00J8H9QMO/ref=lp_11597590031_1_1?srs=11597590031&ie=UTF8&qid=1589413612&sr=8-1)
I'm waiting for shipping. I will do everything I can to help you. :-+
Please post the connectors pinout of the oscilloscope mainboard.
Thanks alexitaly！
1、 You need to solder the bf 531 JTAG socket before starting work. This seat does not exist on our motherboard, you need to add it.
2、Make a cable, taking care to include a 1k resistor.
3、Make a connection bf531-Lattice-downloader (your Adattatore USB Debugger ICprog OpenOCD JTAG)。Note that the 3.3v on the sco motherboard should be used to power the downloader.
I am just a rookie in this regard. I will only complete limited work according to the information obtained online, so I used TopFlash to burn the program. The command line of OpenOCD is sealedbook for me. :phew:
Maybe in the future there is a chance to hack to 200M ds1202z-e :box:
Hi TV84！Maybe in the future there is a chance to hack to 200M ds1202z-e :box:
That is also an interesting challenge. ;) That one is non-existent in Europe.
Get me a direct link to download the FW.
Continuing the discussion of 1102cal, I have burned all the BIN files I can find through JTAG in the past few days. The software I use is TOPFLASH. The 8M capacity is divided into 135 sectors（8kx8sector+64kx127sector=8192kb）, but the file of the first sector cannot be deleted. . So I intentionally changed a BIN file. Change the data of the first sector to 0xFF. After burning, read back to the PC and observe that the data has not been changed. Simply put, the data of the first sector cannot be changed by JTAG at present. Is it wrong? (I used the configuration data DSO.topflash in the dso_jtag file package), this problem also exists in other tests in this post.
I think that this problem will not be solved if the JTAG dump is not resolved.
I still need to learn a lot :popcorn:
Start and end addresses is 0x0000 to 0x1fff 8192kContinuing the discussion of 1102cal, I have burned all the BIN files I can find through JTAG in the past few days. The software I use is TOPFLASH. The 8M capacity is divided into 135 sectors（8kx8sector+64kx127sector=8192kb）, but the file of the first sector cannot be deleted. . So I intentionally changed a BIN file. Change the data of the first sector to 0xFF. After burning, read back to the PC and observe that the data has not been changed. Simply put, the data of the first sector cannot be changed by JTAG at present. Is it wrong? (I used the configuration data DSO.topflash in the dso_jtag file package), this problem also exists in other tests in this post.
I think that this problem will not be solved if the JTAG dump is not resolved.
I still need to learn a lot :popcorn:
In your 8MB dump, what is the area that you call 1st sector? Start and end addresses?
Start and end addresses is 0x0000 to 0x1fff 8192k
Yes,I compared multiple files, and the data from 0x00 to 0x003FFF are indeed consistent. According to the parameters in the datesheet, they belong to the first 4 sectors. 8192 bytes (8K bytes) per sector, not 8192k bytes.Sorry, I made a mistake in front.Start and end addresses is 0x0000 to 0x1fff 8192k
You mean 8 kB and NOT 8 MB , right?
0x2000 bytes = 8 kBytes!
If that is the case, I think it's no problem because the beginning of the FW can be the same in those bytes.
The first 6 or 7 sectors of 8 kBytes each (of the firmwares) are always the same so that doesn't mater for us! That is where the decompressing function of the firmware resides. And that function is always the same.
Thanks alexitaly！
1、 You need to solder the bf 531 JTAG socket before starting work. This seat does not exist on our motherboard, you need to add it.
2、Make a cable, taking care to include a 1k resistor.
3、Make a connection bf531-Lattice-downloader (your Adattatore USB Debugger ICprog OpenOCD JTAG)。Note that the 3.3v on the sco motherboard should be used to power the downloader.
I am just a rookie in this regard. I will only complete limited work according to the information obtained online, so I used TopFlash to burn the program. The command line of OpenOCD is sealedbook for me. :phew:
Hello tv84 and routerfan :DWelcome back alexitaly
Today the JTAG programmer is arrived!
Which sw should i use to dump osciloscope memories?
Is OpenOCD ok or have you other advice?Thanks alexitaly！
1、 You need to solder the bf 531 JTAG socket before starting work. This seat does not exist on our motherboard, you need to add it.
2、Make a cable, taking care to include a 1k resistor.
3、Make a connection bf531-Lattice-downloader (your Adattatore USB Debugger ICprog OpenOCD JTAG)。Note that the 3.3v on the sco motherboard should be used to power the downloader.
I am just a rookie in this regard. I will only complete limited work according to the information obtained online, so I used TopFlash to burn the program. The command line of OpenOCD is sealedbook for me. :phew:
In the photo that you have published, the hw revision of the mainboard is SAT7.820.681.K but, in previous photos of your oscilloscope, the revision is SAT7.820.681.H (the same revision of mine).
What are the differences between the two revisions? Is there any difference in connectors' pinout? And what is your revision? It's very important.
Hi routerfan,1. Confirm that the devices below Windows can be recognized normally.
i've installed driver and TopJTAG software. A question: after 20 days from installation, does it stop working if the license is not purchased?
From your electric drawing, bf531 JTAG and Lattice JTAG lines are the same. How do you select the one or the other?
Can you explain me the procedure that you have performed with TopJTAG to dump memories please?
Thanks!
Hi routerfan :-+Hi alexitaly
Thanks for your help with the .rar file :D
I'm trying, and i've a question.
I've made the connection cable from programmer to Lattice JTAG connector.
In the oscilloscope mainboard i've not found the connections in red (see the image attached). I not understand if the scheme is of all the connection cable or if i've to made only the connection to the programmer (and the connection between BF531 JTAG and Lattice JTAG connectors are in the mainboard).
Please excuse me for this question, but i haven't any electric scheme of the mainboard, and i don't want to make damages.
Can you help me please?
Hi routerfan,Hi alexitaly，
i've made and verified the JTAG cable, but the software give me the message "FAILED TO INITIALIZE JTAG CHAIN".
I've controlled the cable and the sw settings, the ftdi drivers, but i haven't obtained any result.
In these days i will continue to try... if someone has any idea i'm grateful.
Excuse me, thanks for your attention.
Excuse me, thanks for your attention.
Totally excused! :(
I wish all the best and good luck in getting a new job.
Stay safe!