SST26VF064B Library… help?

According to the datasheet.

The WP# is used in conjunction with the WPEN and IOC bits in the Configuration register to prohibit write operations
to the Block-Protection register. This pin only works in SPI, single-bit and dual-bit Read mode

So it looks like you need to re-read chapter 4 of the datasheet “4.1 Device Protection.” .. and TABLE 4-1: WRITE PROTECTION LOCK-DOWN STATES

Unfortunately I don’t have the device to play with, so that is about as much as I can say on the subject.

That was the first thing I did But seems I need to re-read 4 or 5 more times
But even with WPEN and IOC disabled doesn’t seem to have effect.

I’m trying to copy the code from the microchip example to see if I can get better results.
I’ve tried to erase the full chip but don’t know if it worked correctly because I now read all zeroes…

Stay tuned for the next episode of “Flash wars”

rexnanet wrote:Stay tuned for the next episode of “Flash wars”

I’m still waiting for the next thrilling episode.

Image

@ahull
Wait no more!!!
Here it is:

Raw SerialFlash Hardware Test
Setup configuration register
GlobalBlockProtectionUnlock
Write prot clear
Done

Read Chip Identification:
JEDEC ID: BF 26 43
Part Nummber: SST26VF064
Memory Size: 1048576 bytes
Block Size: 65536 bytes
STATUS 0x05 = 0
CONFIG 0x35 = A

Reading Chip...
Reading...
addr = 0, data = FF FF FF FF FF FF FF FF
(..)
addr = FFFF8, data = FF FF FF FF FF FF FF FF

Writing 512 signatures

Double Checking All Signatures:
all 512 signatures read ok

Checking Signature Pairs
all 255 signature pairs read ok

Checking Read-While-Write (Program Suspend)
write 256 bytes at 256
write time was 1369 microseconds.
read-while-writing: 00 00 00 00 15 F5 95 4B
test passed, good read while writing

Checking Read-While-Erase (Erase Suspend)
erase time was 18573 microseconds.
erase correctly erased 65536 bytes
read-while-erasing: 00 00 00 00 15 F5 95 4B
test passed, good read while erasing

All Tests Passed :-)

Test data was written to your chip. You must run
EraseEverything before using this chip for files.

The story is staring to get pretty interesting.

Image

Keep us posted with your progress.

…on the quest to have the serial upload python script working in Windows… (yes, I said it… Windows…)
:arrow: Python – installed.
:arrow: Pyserial – installed.
:arrow: Testing… not yet

Let us know how the testing goes.

Image

Image

What is the purpose of this mysterious device?

BTW, I’ve used this library in the past to access different flavours of WinBond SPI Flash :
https://github.com/LowPowerLab/SPIFlash

ahull wrote:The story is staring to get pretty interesting.

Image

Keep us posted with your progress.

zmemw16 wrote:ahull wrote:

got the next generation interested? st is next

I love Python !
I’m using it since more than 16 years (almost never use Perl any more since then)
What is exactly the problem you’re facing ?

martinayotte wrote:I love Python !
I’m using it since more than 16 years (almost never use Perl any more since then)
What is exactly the problem you’re facing ?

martinayotte wrote:
What is exactly the problem you’re facing ?

Did you have first uploaded the CopyFromSerial sketch into your STM ?

(For the time printing and divide by zero, it is probably simply because your file is so small, it took less than a second)

martinayotte wrote:Did you have first uploaded the CopyFromSerial sketch into your STM ?

For debugging, I would rather use a second serial port to do some debug prints and leave the first one for the CopyFromSerial functionalities.

Yeeeaaaaaahhhh….
That might become the “last resort” option
I was hoping to keep this as simple as possible but that might seem the best option…

Going to try the “last resort” option

But I have a question:
What is the Serial-UART correlation?

“Serial” is used by the USB serial connection.
I’ve tried to use “Serial2” and connected the serial adapter to USART2 (PA_2 and PA_3 pins) but got no output. Then got to switch attention to other things and stopped there…

I’ve found this code from Roger but haven’t checked whether the constant is defined or not:
/*
* Roger Clark
*
* 2015/05/28
*
* Moved definitions for Hardware Serial devices from HardwareSerial.cpp so that each board can define which Arduino "Serial" instance
* Maps to which hardware serial port on the microprocessor
*/

#ifdef SERIAL_USB
DEFINE_HWSERIAL(Serial1, 1);

DEFINE_HWSERIAL(Serial2, 2);

DEFINE_HWSERIAL(Serial3, 3);
#else
DEFINE_HWSERIAL(Serial, 1);

DEFINE_HWSERIAL(Serial1, 2);

DEFINE_HWSERIAL(Serial2, 3);
#endif

New episode:

Finally got USART2 to work.
After making a test sketch that was successful, I returned to the original sketch and…tada… it works
Did I make any modification for it to work… no. But it did, so next…

Debugging episodes:

1- After adding debug found out the first problem:
I made a test text file with some letters in it and named it “test.txt”.
Then I found that on the sketch the only letters allowed are CAPS!!!! I was like “what?!?!?!? why?????? It’s not that difficult to add and would save me a lot of work…”
So I added it to the sketch… (but also renamed the file to move forward, just in case…)

2- After some small mods, the sketch would end but nothing was written…
The Flash Buffer is set to 4096 bytes but the USB Buffer is set to 128 bytes. The file had 908 bytes and after 128 bytes the sketch moved on and ended without nothing written on the flash.
Still haven’t found out what is going on but moved the USB Buffer to 4096 and the sketch ended successfully.

Uploaded the “read files from flash” sketch I made and BAAAAMMM the file got written!!!

This is a big step forward

Now somethings still need to be done:
1- find out what is the deal with the USB buffer size, because I suspect I can’t write files bigger than 4096 bytes with this issue…
2- test with multiple files being written.
3- test the speed!!!!
4- connect to the ILI9341 and get some pictures going!!!!

Edit:
1- find out what is the deal with the USB buffer size, because I suspect I can’t write files bigger than 4096 bytes with this issue… – haven’t looked at this
2- test with multiple files being written. – OK
3- test the speed!!!! – Working OK @ SPI=36Mhz. Overclock still to come
4- connect to the ILI9341 and get some pictures going!!!! – “most probably” OK (Got some picture showing but the image was not ok in the flash because of the “Esc” stuff on the sketch. I’ll explain that later…