Thank you Kevin, I will do that and give feedback on it. But before I will take a second look at this addressing question. Regards. Fausto.
On Tue, Jan 12, 2021 at 6:41 AM Kevin Grant <elect...@mykolab.com> wrote: > Fausto > > If you can't read the device, writing won't work either. I think there is > still some addressing problem. > > A search with your package manager or internet search might help you find > a binary editor. > > Alternatively, a few lines of python could make a binary file for you: > > import os > filename = os.path.join(os.path.dirname(__file__), "eeprom-new.bin") > with open(filename,'wb') as f: > f.write(bytearray([0xc0,0x50,0x1d,0x8d,0x60])) > > Then write the new data with > > fx2tool -B -d 16c0:296d write_eeprom -W 2 -a 0 -f ./eeprom-new.bin > > Good luck, I hope you get it working. > > > On 2021-01-12 00:01, Fausto Barbosa wrote: > > Kevin, > in that case, which editor would I use to edit the bin eeprom file? I will > try to insert that information and flash the modified file. > Thank you. > Fausto. > > On Mon, Jan 11, 2021 at 6:27 PM Kevin Grant <elect...@mykolab.com> wrote: > > Hmm. That's still not good. Probably something wrong with eeprom > addressing. > I would expect to see the VID PID in the first few bytes like this: > > fx2tool -B -d 16c0:296d read_eeprom -W 2 0 256 > c0 c0 16 6d 29 00 00 00 ff ff ff ff ff ff ff ff > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ... > > Then you would select a new VID PID, maybe this one from api.c: > sigrok FX2 based 16-channel logic analyzer 1d50:608d > Then you would write something like this back to the EEPROM. > c0 50 1d 8d 60 00 00 00 > > > On 2021-01-11 20:49, Fausto Barbosa wrote: > > As you guessed, the line > $ fx2tool -B -d 16c0:296d read_eeprom -W 2 0 256 > failed but in fact, the model my board has a jumper (J2) that, when > opened, associates address 0x51 to the i2c port. > See this reference (which is identical to my board. J2 is at the bottom of > the figure 1) > > https://community.cypress.com/t5/Knowledge-Base-Articles/Cypress-EZ-USB-FX2LP-based-Logic-Analyzer-using-Open-Source/ta-p/252866 > > Then I opened the jumper, ran the command line again and, voila, got the > empty firmware output again :\ > ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff > ... > > Is this output expected to show the VID PID numbers in some place? > > Best regards. > Fausto. > > > >
_______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
