atmel at45db161b what spi settings to use?

[sidlas]

connected to flash(RDID:0x01FFF REMS:0XFFFF
flashcatusb detected spi device but its not currently supported...
any help?
thanks

 

[D3m0n]

That chip is supported recheck your connections ,remember in fcusb your SI goes to SO and SO connects to SI

 

[sidlas]

am new in this,can you explain please how to exactly connect to it in details? am pretty sure i doing it wrong way... have movimento adapter,which get corupted memory couse of bad update, i open itthere was a place for 10 pin connector i solder it and now am here... do i need get straight to chip or it can be done tghru 10 pin?

 

[D3m0n]

It all depends if the 10 pin is connected to the pin , only way to know that is to find data related to this device , or to buzz out the pins with a multimeter.
If you can connect directly to the chip then it would be better , you can follow this diagram

 

[sidlas]

ill try,thank you

 

[sidlas]

Another noob question.. how trace atmel pins??? i tryed with multimeter but pins si,so,sck,cs they interfere on same lines,what i need to measure? to trace which is where exactly, or can somone point me to resources where i can learn that?
thanks

 

[D3m0n]

Your best bet is to connect directly to the SPI chip itself.

 

[sidlas]

ok not many hair left on my head , I trace the pins solder wires,double checked them,and still getting spi flash detected,but not supported... every time I press detect device I getting device detection at different addres?!?
someone know what manual settings must be for atmel at45db161b chip? I want to try read it manually.
thank you

this is the log
LibUsbDotNet version: 2.2.8.104
FlashcatUSB Script Engine build: 202
SPI database loaded: 159 devices supported
Welcome to FlashcatUSB interfacing software, build: 345
Running on: Microsoft Windows 7 Ultimate (32 bit)
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x070703 REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 0 (Fosc/2 MSB)
Connected to Flash (RDID:0xFFFFFF REMS:0xFFFF)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x0F0F0F REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x1F1F1F REMS:0x0103)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x1F0F0F REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x070F07 REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x0F0F0F REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Disconnected from FlashcatUSB
Device connected in SPI mode, firmware version: 3.05
Unable to connect to compatible SPI device
Device connected in SPI mode, firmware version: 3.05
Unable to connect to compatible SPI device
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x0F0F1F REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Disconnected from FlashcatUSB
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 LSB)
Connected to Flash (RDID:0xE0E0E0 REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x0F0707 REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x030301 REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x1F0F1F REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS
Device connected in SPI mode, firmware version: 3.05
Opening device in SPI Mode 8 (Fosc/2 MSB)
Connected to Flash (RDID:0x0F0F0F REMS:0x0000)
For read write support email contact@embeddedcomputers.net with RDID/REMS

 

[sidlas]

ahh and am sure it is not right but I tried connect usb cable to device with flashcat on and device shows in device manager recognized"movimento adapter" device working properly... admin020(program specifically to flash fw to device reads configuration,but if I trying to flash it getting error again...

 

[sidlas]

Btw this is tsop 28 chipq has 528 bytes pages

 

[D3m0n]

Can you upload a photo of your connection from FCUSB to the device please

 

[sidlas]

what that going change? I trace pins gnd,so,si,vcc,sck,cs to place where I can solder without damaging chip this chip very small so I cant go directly to it... but I trace pins double-triple checked that... possibility something else interfering in system??? that why I want to try manual settings.i have good memory dump so I can compare readings,btw what is cpu on reset??? read in other post guy mentioned that?

 

[sidlas]

is there wires length and gouge difference matter in this case? now I have about 20 inches different gouge connected...

 

[sidlas]

done,thread closed,i fix the unit without properly identifying the chip,am not good in electronics but I think my problem was another memory unit interfering. even without properly identifying flash I was able to fix unit.
p.s flashcat did big part in this fix.
thanks to D3m0n for help.

 

[D3m0n]

Glad you got it working but for future reference trying to input manual settings will not work unless fcusb detects a Jedec ID , the manual setting's was implemented for chips that were not in the supported list so that people could manually add them instead of waiting for a new fix in the software.

 

[sidlas]

I dont know why i cant detect chip,but flashcat opened access to chip so i was able to reprogram unit over its own usb.