checkslogoboss

1. Spi Interface Schematic

FeatureSF600 Plus is high speed 'in System Programming' programmer to update the SPI Flash soldered on board (In Circuit Programming) or in the socket adaptor (Offline programming). The programmer is easily controlled by the computer DediProg Software through the USB bus offering a friendly interface and powerful features to users.SF600 Plus combines the advantages of SF100 with additional improvements: High-speed USB and higher SPI performances.SF600 Plus is an upgrade version of SF600.

High performance (25MHz, Single IO) USB ModeReference ICDensity(Program + Verify)Memory sizeW25X80VSSIG8Mb9sW25Q16VSSIG16Mb11.6sW25Q32VSSIG32Mb12.6sW25Q64FVSSIG64Mb31sW25Q128BVFIG128Mb61.7sW25Q256FVFIG256Mb89.2sS25FL512SAGMFI011512Mb147.4s.Please note the programming and verify time will depend on different IC type; please refer to the IC specification before programming.HardwareSF600 Plus is designed with ISP header, through an appropriate connector, users can connect the programmer and drive the SPI signals, supply the memory and control the controller or application status. Please refer to Table 1 for the SF600 Plus 2x10 header pin out. Google font.

DediProg also provides the SF600 Plus ISP Cable which is used to connect the programmer to the 2X6 2.54mm ISP Pin Header on board, please refer to Table 2 for the SF600 PlusISP Cable 2x6 pin out.Table 1: SF600 Plus ISP Header Pin Out (2x10) 1VppCS223CS1Vcc45MISO/DQ1Hold/DQ367Wp/DQ2CLK89GNDMOSI/DQ01011NCReset/IO31213NCNC1415NCNC1617NCNC1819GPIO1GPIO220Table 2: ISP Cable Connector Pin Out (2x6) 1VppCS223CS1Vcc45MISO/DQ1Hold/DQ367Wp/DQ2CLK89GNDMOSI/DQ01011NCReset12The SF600 Plus USB software tool chain offers high flexibility and fits the different and highest requirements.

If you are simply looking for a way to program the Winbond SPI flash with 'pre-loaded' data that your microcontroller would read for use when it is running then what you will want to look into is a programmer that can do in-circuit programming of the SPI Flash chip. This also known as in-system-programming (ISP).One choice is the. This USB connected device can program in circuit if you design your board correctly. They even sell an adapter clip that can attach into the SOW-16 package without having to design in a separate programming header on your board. DediProg has application information bulletins available to help with correct design for in circuit use.

The main strategy for the design is to find a simple way to isolate the SPI interface drivers in your MCU system so that they do not interfere with the drivers in the SPI programming pod. The simplest way to do this is to put series resistors in the MCU driven lines between the MCU and the SPI Flash.

The programmer would connect on the SPI flash side of the series resistors. Alternate methods could include adding a MUX or analog switches in the driven interface lines. An even more clever scheme is to add a 'programming enable' input to the MCU that makes the software disconnect all the SPI I/Os from the SPI Flash chip (i.e. Make all those GPIOs as inputs).A second choice to also consider is.

The Presto is able to do various types of SPI and I 2C devices including SPI Flash devices. I have one of these devices specifically for programming Atmel MCUs and various types of SPI Flash devices. It is a more cost effective solution than the above unit but not quite as flexible.

Spi Interface Schematic

Their more expensive device called the Forte is able to do more things because it has more target interface pins.Sometimes it can be beneficial to be able to connect a programmmer to a target board without having to add a programming header. One nice solution for this is to place a small set of pads in a special footprint defined. They manufacture and sell a series of quick connect programming cables that have pogo pins that engage the special footprint on the board. There are 6-pin, 10-pin and 14-pin versions of the cable available to suit a range of applications. Cost of the cables are very reasonable.

I have never heard of any other tools talking SPI directly to such a chip, and I think it is impossible since 'all' chips require different calls for different operations.The chip needs SPI calls for write, read, change sector, data size etc. Under 7.2 Instructions chapter in the datasheet you can see all the SPI commands you can send to it. Hence, since all external flash memories does not have the same instruction set, you need to write a customized application for this one.EDIT: Being a follow up, I would really recommend one of Atmels own SPI flash memories, since most of them already has written open available code for them.

Looking at from will provide you with code for some of Atmels AT45xxxx serial flash chips. I purchased a ' programmer from Embedded Computers for about $30 US. It was surprisingly easy to connect to the PC via USB and write files to the Winbond flash memory. The methods and programmers in other answers are probably just as good, some more expensive or DIY, but this is a cheap and simple way that fits what I was seeking.Here's a picture of the setup:The FlashCAT programmer is at left, connected to USB. It's running the SPI programming firmware (as opposed to JTAG) and supplying power to the flash memory. The supplied power is selectable (3.3V or 5V) with a jumper.I have a SOIC to DIP socket on the breadboard to make it easy to program multiple chips.

(You can see another flash memory IC sitting on the breadboard as well.)I haven't yet converted my audio file to the proper binary format, but I wrote a 211KB WAV file to memory just to test, pictured above. I then read it back and saved it as a new file, renamed it to.wav, and it plays correctly on the PC.The next step will be to properly encode the file, and write the AVR software to read the data and send it through a DAC.Disclaimer: I am not affiliated with Embedded Computers, I'm just a customer who picked something inexpensive and am sharing information about the experience with the product.

Kind of late to the discussion, but for anyone reading it after a search.One thing I did not see mentioned, which is absolutely critical when programming SPI Flash chips is control of the Chip Select (CS) pin. The Chip Select pin is used to punctuate commands to the SPI Flash. In particular, a transition from CS high to CS low must immediately precede the issuance of any Write operation op code (WREN, BE, SE, PP). If there is activity between the CS transition (i.e. After CS has gone low) and before the write op code is transmitted, the write op code will usually be ignored.Also, what's not commonly explained in SPI Flash datasheets, because it's an inherent part of the SPI protocol, which is also critical, is that for every byte one transmits on the SPI bus, one receives a byte in return. Also, one cannot receive any bytes, unless one transmits a byte.Typically, the SPI Master that the user is commanding, has a Transmit Buffer, which sends bytes out on the MOSI line of the SPI bus and a Receive Buffer, which receives bytes in from the MISO line of the SPI bus.In order for any data to appear in the Receive buffer, some data must have been sent out the Transmit Buffer.

Similarly, any time one sends data out of the Transmit buffer, data will appear in the Receive Buffer.If one is not careful about balancing Transmit writes and Receive reads, one will not know what to expect in the Receive buffer. If the Receive buffer overflow, data is usually just spilled and lost.So, when one sends a read command, which is a one byte op code and three address bytes, one will first receive four bytes of 'garbage' in the SPI Master Receive buffer.

These four bytes of garbage correspond to the op code and three address bytes. While those are being transmitted, the Flash does not yet know what to Read, so it just returns four words of garbage.After those four words of garbage are returned, in order to get anything else in the Receive Buffer, you must Transmit an amount of data equal to the amount that you want to Read. Contrary to some of the statements here, while there are some quirky SPI PROMs out there, there are also some standard instructions used by a large variety of SPI PROMs, including the one you've chosen.As vicatcu already mentioned, there are good 'bit-bash' cables available that can directly program SPI. Signal-wise, SPI looks a lot like JTAG, so any bit-bash type of cable should be able to be used provide the interface is open source. The internal protocol of the flash is fairly simple.We use the big brother of the part you're looking at to boot our FPGA boards (256M - 2G).

The addressing has an extra byte to handle the storage volume, but otherwise the commands are basically identical.The type of PROM you're using has to be erased by sector, then programmed by page. Reading is significantly faster than writing (in the case of the ones we use, programming can take half an hour, but reading the whole PROM takes under a second at 108MHz).Now for the commands: There are way more commands available in these devices than are actually required to program them. You should be able to re-purpose the USBtiny to program a flash memory instead of a target MCU if you are comfortable changing it's programming. However, there may not be enough memory on that to make it versatile enough to program both the MCU and the flash.Somewhere I have a board from a project which has both an ATTINY and an SPI flash, and uses as an Arduino as a readily available 'programmer'. A slight modification of the ISP sketch is used to program the MCU with avrdude, then a custom utility sends a sequence which puts the sketch in a special mode and writes blocks of data to the SPI flash.