• Visit https://www.embeddedcomputers.net/ for Hardware; Software and all other things related to FlashcatUSB

There is probably a problem in build 480 flashcat software

poya22

New Member
hi
when I select i2c mode in build 480 there are signal on pins SDA and SCL even if it's not eeprom ic connect to programmer
and do not detect any eeprom flash


signal on SDA pin

 

Attachments

  • 20171126_105705.jpg
    20171126_105705.jpg
    4 MB · Views: 19
  • 20171126_105928.jpg
    20171126_105928.jpg
    1.6 MB · Views: 40
Last edited:
I take it you are connected as per the diagram shown in the first post ?
What does it show in the console window of the software ?

Need to gather as much info as possible so i can pass this onto the developer to check.
 
I take it you are connected as per the diagram shown in the first post ?
What does it show in the console window of the software ?

Need to gather as much info as possible so i can pass this onto the developer to check.
Yes my connection as the same in pic. and also i have 8 pin SOIC flashcat adapter.

FlashcatUSB Script Engine build: 300
Welcome to the FlashcatUSB interfacing software, build: 507
LibUsbDotNet version: 2.2.8.104
Running on: Microsoft Windows 7 Ultimate (32 bit)
Serial NOR memory database loaded: 320 devices supported
Serial NAND database loaded: 26 devices supported
Parallel NOR memory (x8/x16) database loaded: 207 devices supported
SLC NAND memory (x8) database loaded: 70 devices supported
Connected to FlashcatUSB Classic, firmware version: 4.32
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect I2C EEPROM device
Address byte: 0xAE
I2C EEPROM device size: 32,768 bytes
I2C protocol speed: 400kHz
Unable to connect to I2C EEPROM
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB Classic, firmware version: 4.32
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect I2C EEPROM device
Address byte: 0xAE
I2C EEPROM device size: 32,768 bytes
I2C protocol speed: 400kHz
Unable to connect to I2C EEPROM
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB Classic, firmware version: 4.32
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect I2C EEPROM device
Address byte: 0xAE
I2C EEPROM device size: 32,768 bytes
I2C protocol speed: 400kHz
Unable to connect to I2C EEPROM
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB Classic, firmware version: 4.32
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect I2C EEPROM device
Address byte: 0xAE
I2C EEPROM device size: 32,768 bytes
I2C protocol speed: 400kHz
Unable to connect to I2C EEPROM
Disconnected from FlashcatUSB Classic device
Connected to FlashcatUSB Classic, firmware version: 4.32
Firmware features supported: SPI, I2C, EXTIO
Attempting to detect I2C EEPROM device
Address byte: 0xAE
I2C EEPROM device size: 32,768 bytes
I2C protocol speed: 400kHz
Unable to connect to I2C EEPROM
 
U say you have the 8 pin SOIC adapter , are you using this to try to read the EEPROM ? , if so then you can't you need to use the DIP-8 adapter.

In any case i will ask the developer to test out this function for the EEPROM's
 
Strange that it is detected in that old 326 build as I2C was not implemented in the code back then
 
build 507 detect me eeprom 24aa256 on SPI eeprom with all the eeprom list but is not the info to read.
 
hi
Two pin in programmer SDA pin and SCL are for I2C mode when selected I2C mode in protocol setting and if there is not any eeprom in programmer when push detect, there is signal on these pins And they will stay .
This Square waves signal show with oscilloscope in my first post
In fact, there should be no signal on these pins after detect action down. In this case programmer can not detect any eeprom .
build 507 also has same problem in PCB version 2.2

sorry with my bad English
 
Last edited:
bulid 446 detect eeprom but information is corrupted
 

Attachments

  • desktop 1_004.jpg
    desktop 1_004.jpg
    380.9 KB · Views: 48
Newer than build 464 do not detect .but with old driver until build 464 work fine and read or write is ok
 

Attachments

  • build464.jpg
    build464.jpg
    110.2 KB · Views: 37
  • not detect in build 507 with same eeprom.jpg
    not detect in build 507 with same eeprom.jpg
    47.2 KB · Views: 34
Newer than build 464 do not detect .but with old driver until build 464 work fine and read or write is ok
Your right build 464 detect eeprom 24aa356 with soic 8 test clip but in my case info still in blank you can see in the pic.I think my soic 8 adapter is not making a good contact the only way build 464 detect eeprom with adapter is pressing down soic adapter pcb to flashcat very hard and then detect eeprom with bad info.
 

Attachments

  • test clip.jpg
    test clip.jpg
    404.8 KB · Views: 31
  • 8 soic adapter.jpg
    8 soic adapter.jpg
    380.9 KB · Views: 30
Last edited:
The developer has tested an EEPROM on the newest firmware and driver and says it functions perfectly , could you guys provide us with photos of how you are connected to your FCUSB device.
 
Back
Top