Products > Test Equipment

Picoscope Hack

<< < (16/18) > >>

b_force:

--- Quote from: jasonRF on May 27, 2023, 09:39:36 am ---I can verify that there is at least one Picoscope that doesn't follow this hacking recipe.    :-DD

I have a 2204a I purchased in 2016.  The hardware version is 17.  Anyway, increasing byte 0B by 1 and decreasing byte 1B by 1 did not do the trick.  I have tried a bunch of other options as well, but so far all of the trials have resulted in a device that the picoscope software does not recognize. 

Edit:forgot to say that i am trying to turn it into a 2205a, which has identical hardware. 

The eeprom on my 2204a is definitely different than the one discussed on the sigroc page.  For example, B7-D9 and F8-FD are all non-zero.  I have of course mucked with some of these bytes as well - especially F8-FD that look less like cal data than some of the other areas. 

I am very inexperienced when it comes to this kind of stuff, so any suggestions you-all might have would be helpful.  For the trial and error approach I have been using so far, it might be time to write a python script to automate it more. 

In any case, it has been fun to play with this. 

cheers,

jason

--- End quote ---
We meet here as well! :D :D

I am still curious how this adventure ended up and if/how it works with the 2000 series? :)  8)

jasonRF:

--- Quote from: b_force on June 30, 2023, 12:53:36 pm ---
We meet here as well! :D :D

I am still curious how this adventure ended up and if/how it works with the 2000 series? :)  8)

--- End quote ---
I was never able to get the unit upgraded, although there is at least one person here who did change a 2204a to a 2205a.  My 2204a isn’t used very much anymore so it really doesn’t matter to me.   It was just fun to poke at.   I would brute force it with a python script using an arduino and the pico api (and I even started to), but everytime you test to see if the api recognizes the scope you hear relays clicking.   After a  hundred unsuccessful attempts I killed my script since didn’t want to wear out the relays for no good reason. 

Jason

MiDi:

--- Quote from: jasonRF on May 27, 2023, 09:39:36 am ---I can verify that there is at least one Picoscope that doesn't follow this hacking recipe.    :-DD

I have a 2204a I purchased in 2016.  The hardware version is 17.  Anyway, increasing byte 0B by 1 and decreasing byte 1B by 1 did not do the trick.  I have tried a bunch of other options as well, but so far all of the trials have resulted in a device that the picoscope software does not recognize. 

Edit:forgot to say that i am trying to turn it into a 2205a, which has identical hardware. 

The eeprom on my 2204a is definitely different than the one discussed on the sigroc page.  For example, B7-D9 and F8-FD are all non-zero.  I have of course mucked with some of these bytes as well - especially F8-FD that look less like cal data than some of the other areas.

--- End quote ---

Had no problems to hack 2204A (HW Version 17, cal 2023-04-17) to 2205A using fx2tool as described in the Saleae thread.

Save to eeprom.hex:

--- Code: ---fx2tool -B -d 0CE9:1007 read_eeprom -W 1 0 256 -f eeprom.hex
--- End code ---

Changed byte 0B from 1A to 1B and reduced the serial by one (bytes 13-1B) and used HEX file checksum online calculator for correcting checksum at the line ends.

Upload from eeprom_hack.hex:

--- Code: ---fx2tool -B -d 0CE9:1007 write_eeprom -W 1 -f eeprom_hack.hex
--- End code ---

Replug the scope, otherwise it will not be recognized.


--- Quote from: markone on December 04, 2022, 09:25:03 pm ---
It's my friend from a while, to be more precise Cypress USB Console + EZ-USB Interface (but I guess you already know).

It happens that maaany years ago I developed a 14bits ADC streamer based on commercial PATA HDD external case (Cypress CY7C68013 inside) in conjunction with a Labview application, this joke was able to push flawlessly 16MS/s x 16bits (32MB/s) toward a medium windows PC of the time, with some real time computation and disk logging.

Now you can understand why I smell BS if I read that the 2204A streaming mode is limited to 1MS/s due to the fact that the board has a buffer on only 8Kpts (inside the FPGA).

I had no FPGA and no buffer, but the system worked like a charm, so I would say that the 2204A sounds like a cripple fest.

--- End quote ---

The limit with current SDK is 150ns/6.67MSPS for continuous fast streaming for one CH, but sometimes it drops a couple of samples.

b_force:

--- Quote from: MiDi on December 19, 2023, 07:07:50 pm ---
--- Quote from: jasonRF on May 27, 2023, 09:39:36 am ---I can verify that there is at least one Picoscope that doesn't follow this hacking recipe.    :-DD

I have a 2204a I purchased in 2016.  The hardware version is 17.  Anyway, increasing byte 0B by 1 and decreasing byte 1B by 1 did not do the trick.  I have tried a bunch of other options as well, but so far all of the trials have resulted in a device that the picoscope software does not recognize. 

Edit:forgot to say that i am trying to turn it into a 2205a, which has identical hardware. 

The eeprom on my 2204a is definitely different than the one discussed on the sigroc page.  For example, B7-D9 and F8-FD are all non-zero.  I have of course mucked with some of these bytes as well - especially F8-FD that look less like cal data than some of the other areas.

--- End quote ---

Had no problems to hack 2204A (HW Version 17, cal 2023-04-17) to 2205A using fx2tool as described in the Saleae thread.

Save to eeprom.hex:

--- Code: ---fx2tool -B -d 0CE9:1007 read_eeprom -W 1 0 256 -f eeprom.hex
--- End code ---

Changed byte 0B from 1A to 1B and reduced the serial by one (bytes 13-1B) and used HEX file checksum online calculator for correcting checksum at the line ends.

Upload from eeprom_hack.hex:

--- Code: ---fx2tool -B -d 0CE9:1007 write_eeprom -W 1 -f eeprom_hack.hex
--- End code ---

Replug the scope, otherwise it will not be recognized.


--- Quote from: markone on December 04, 2022, 09:25:03 pm ---
It's my friend from a while, to be more precise Cypress USB Console + EZ-USB Interface (but I guess you already know).

It happens that maaany years ago I developed a 14bits ADC streamer based on commercial PATA HDD external case (Cypress CY7C68013 inside) in conjunction with a Labview application, this joke was able to push flawlessly 16MS/s x 16bits (32MB/s) toward a medium windows PC of the time, with some real time computation and disk logging.

Now you can understand why I smell BS if I read that the 2204A streaming mode is limited to 1MS/s due to the fact that the board has a buffer on only 8Kpts (inside the FPGA).

I had no FPGA and no buffer, but the system worked like a charm, so I would say that the 2204A sounds like a cripple fest.

--- End quote ---

The limit with current SDK is 150ns/6.67MSPS for continuous fast streaming for one CH, but sometimes it drops a couple of samples.

--- End quote ---
So I assume the 2204A can only be "upgraded" to the 2205A ?

I still really like the picoscope software, so much better than my physical scope.
It's just that they are so pricey :(

coromonadalix:
at the price we paid a 3406d   i would have bought an huge siglent model  loll

lost  my arms and legs  loll

picoscope newest sw  need some improvements,  but getting there

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