Cg3300 netgear

[usbbdm]

The reason is that for flash larger than 16M it needs 4 byte address. The current commands set only needs 3 bytes address. We also need to enter the 4 byte mode.
I searched my library and found most of the work was already done back in 2012. I just do not have any target to test.
I need to re-factory the code and separate the SPI flash definition from the flash.xml (I think we might need NAND flash definition in the future).
Give me some time and I will release 0.70 to solve these issues.

[andy m]

cheers on the info on needed as i will wait till you get the nxt release done ... a get it detect on the nt but it will not give me full dumb

when will nxt release out

[usbbdm]

I am adding a CFI like interface for SPI flash, this way we do not need to manually add to flash.xml for most newer SPI flash. In SPI api it is called DMC. Basically there are certain parameters that is already stored in the flash that we can read back. It provides more information that we can get from the flash.xml.
I will add this to 0.70.

[U129718]

I am adding a CFI like interface for SPI flash, this way we do not need to manually add to flash.xml for most newer SPI flash. In SPI api it is called DMC. Basically there are certain parameters that is already stored in the flash that we can read back. It provides more information that we can get from the flash.xml.
I will add this to 0.70.

Very well. Good job. I am anxious to try the new version of software for this type of flashes.

[andy m]

cant wait for this already have got the modem at the ready for this

[usbbdm]

Development is almost done other than the auto flash parameters. Just need a target to test. The flash on my SB6120 and SBV6220 does not support this mode.

[usbbdm]

CG3300 does not seem to have the 32M flash. It might have TWO 16MB flash. Which makes the new development useless. The new development is to support flash larger than 16M per chip.
http://www.spansion.com/Support/Datashe ... 29P_00.pdf
It is 128MBit which is 16MB. The current software works with this flash. Only when flash size is larger than 16M which needs 32 bit address.

[usbbdm]

Found this interesting
http://www.spansion.com/Support/Datashe ... 56P_00.pdf
Which has TWO die of 25L129P.

[usbbdm]

There is no need to release 0.70 to support this device. 0.70 will leave for future 32M flash.

To access this device you need to create TWO xml. One for each die.
When you read/write the first half, connect CS1 to NT and let CS2 high.
Then you can read/write second half with connect CS2 to NT and let CS1 high.

On 16 pin chip, CS1 is pin y and CS2 is pin 6.

[U129718]

There is no need to release 0.70 to support this device. 0.70 will leave for future 32M flash.

To access this device you need to create TWO xml. One for each die.
When you read/write the first half, connect CS1 to NT and let CS2 high.
Then you can read/write second half with connect CS2 to NT and let CS1 high.

On 16 pin chip, CS1 is pin y and CS2 is pin 6.

Really, really fantastic job.You were right from start. There is a second flash in this type of flashes, S7FL256, and now both are detected.

Great job!!!!!

[andy m]

have you geting this to work detect the flash and did you wire up the NT to the spanion chip

if possible is there any pic of the wiring diagram

[andy m]

here is 00000000 25L128 part 1 n 2 read see what make of it pin 7 part 1 n pin 6 part 2

[andy m]

part 1 n 2 of the dump and read using 6120 xml erased the both banks of the chip used a modify env1 got got giving to me see if a could access snmp flashed it all back modem doesn,t want to boot with the modify env1 on both part 1 n 2

i have tryed to flash it back the normal way what already saved still success any one else tried this

[usbbdm]

here is 00000000 25L128 part 1 n 2 read see what make of it pin 7 part 1 n pin 6 part 2

Your part 1 is only 4M.
You should have 16M part 1 and 16M of part 2.

[andy m]

need the XML first before can get 16mb from chip part 1 n 2