SPIMemory
SPIMemory copied to clipboard
Marzogh
Feature Request: Add Support for MX25R3235F
---------------------------- DO NOT DELETE OR EDIT anything above this line ----------------------------
Hey there! Thanks for using the SPIFlash library for Arduino.
Issue details
I'm submitting a ...
- [x] feature request
Do the checklist before filing an issue:
- [x] Is this an idea for a feature? Post the feature request as an issue here with a title that clearly says "Feature Request".
When opening an issue please include the following details:
- [x] Do you want to request a feature or report a bug? I thinks support, but perhaps feature. New chip support.
- [x] Which library version are you using? v.3.2.1
- [x] Which Arduino IDE version are you compiling the library on? Windows 1.8.5
- [x] Which OS are you compiling your code on? [Linux / Mac / Windows] Windows 7 64 bit.
- [x] Which microcontroller platform are you using? Arduino Uno
- [x] Which Flash memory module are you using? MX25R3235F (This chip is internatl to the Texas Instruments CC3220MOD on a WiFi Launchpad.
- [x] What is the current behavior? I try to read the Manufacturier ID and get inconsistant results. I get C4, 80, 88. The FlashDiagnostics throws many errors (see below).
- [x] What is the expected behavior? Was expecting to read Manufacturer ID of "C2" hex.
Bug reports only
-
If this is a bug report -
-
[x] Make sure you have run FlashDiagnostics.ino with
#define RUNDIAGNOSTICSuncommented in SPIFlash.h. List any error codes that pop up in your Serial output when you run FlashDiagnostics.ino.here:
Chip Diagnostics initiated.
Error code: 0x10
Error code: 0x02
SPIMemory Library version: 3.2.1
JEDEC ID: 0x8040A0
Man ID: 0x80
Memory ID: 0x40
Capacity: 0
Max Pages: 4294967295
-----------------------------------------------------------------------------------------------------------------------------
Testing library code
-----------------------------------------------------------------------------------------------------------------------------
Function Test result Runtime
-----------------------------------------------------------------------------------------------------------------------------
Power Down PASS 108 us
Power Up PASS 96 us
Erase Chip PASS 6.30 ms
Erase 72KB Error code: 0x01
FAIL
Erase 64KB Error code: 0x01
FAIL
Erase 32KB Error code: 0x01
FAIL
Erase 4KB Error code: 0x01
FAIL
-----------------------------------------------------------------------------------------------------------------------------
Data type I/O Result Write time Read time
-----------------------------------------------------------------------------------------------------------------------------
Error code: 0x01
Error code: 0x01
Byte FAIL 0 us 211.17 ms
Error code: 0x01
Error code: 0x01
Char FAIL 0 us 255.61 ms
Error code: 0x01
Error code: 0x01
Word FAIL 0 us 297.06 ms
Error code: 0x01
Error code: 0x01
Short FAIL 0 us 338.49 ms
Error code: 0x01
Error code: 0x01
ULong FAIL 0 us 379.95 ms
Error code: 0x01
Error code: 0x01
Long FAIL 0 us 421.40 ms
Error code: 0x01
Error code: 0x01
Float FAIL 0 us 462.84 ms
Error code: 0x01
Error code: 0x01
Struct FAIL 0 us 504.28 ms
Error code: 0x01
Error code: 0x01
Byte Array FAIL 1, FAIL 2, FAIL 3, FAIL 4, FAIL 5, FAIL 6, FAIL 7, FAIL 8, FAIL 9, FAIL 10, FAIL 11, FAIL 12, FAIL 13, FAIL 14, FAIL 15, FAIL 16, FAIL 17, FAIL 18, FAIL 19, FAIL 20, FAIL 21, FAIL 22, FAIL 23, FAIL 24, FAIL 25, FAIL 26, FAIL 27, FAIL 28, FAIL 29, FAIL 30, FAIL 31, FAIL 32, FAIL 33, FAIL 34, FAIL 35, FAIL 36, FAIL 37, FAIL 38, FAIL 39, FAIL 40, FAIL 41, FAIL 42, FAIL 43, FAIL 44, FAIL 45, FAIL 46, FAIL 47, FAIL 48, FAIL 49, FAIL 50, FAIL 51, FAIL 52, FAIL 53, FAIL 54, FAIL 55, FAIL 56, FAIL 57, FAIL 58, FAIL 59, FAIL 60, FAIL 61, FAIL 62, FAIL 63, FAIL 64, FAIL 65, FAIL 66, FAIL 67, FAIL 68, FAIL 69, FAIL 70, FAIL 71, FAIL 72, FAIL 73, FAIL 74, FAIL 75, FAIL 76, FAIL 77, FAIL 78, FAIL 79, FAIL 80, FAIL 81, FAIL 82, FAIL 83, FAIL 84, FAIL 85, FAIL 86, FAIL 87, FAIL 88, FAIL 89, FAIL 90, FAIL 91, FAIL 92, FAIL 93, FAIL 94, FAIL 95, FAIL 96, FAIL 97, FAIL 98, FAIL 99, FAIL 100, FAIL 101, FAIL 102, FAIL 103, FAIL 104, FAIL 105, FAIL 106, FAIL 107, FAIL 108, FAIL 109, FAIL 110, FAIL 111, FAIL 112, FAIL 113, FAIL 114, FAIL 115, FAIL 116, FAIL 117, FAIL 118, FAIL 119, FAIL 120, FAIL 121, FAIL 122, FAIL 123, FAIL 124, FAIL 125, FAIL 126, FAIL 127, FAIL 128, FAIL 129, FAIL 130, FAIL 131, FAIL 132, FAIL 133, FAIL 134, FAIL 135, FAIL 136, FAIL 137, FAIL 138, FAIL 139, FAIL 140, FAIL 141, FAIL 142, FAIL 143, FAIL 144, FAIL 145, FAIL 146, FAIL 147, FAIL 148, FAIL 149, FAIL 150, FAIL 151, FAIL 152, FAIL 153, FAIL 154, FAIL 155, FAIL 156, FAIL 157, FAIL 158, FAIL 159, FAIL 160, FAIL 161, FAIL 162, FAIL 163, FAIL 164, FAIL 165, FAIL 166, FAIL 167, FAIL 168, FAIL 169, FAIL 170, FAIL 171, FAIL 172, FAIL 173, FAIL 174, FAIL 175, FAIL 176, FAIL 177, FAIL 178, FAIL 179, FAIL 180, FAIL 181, FAIL 182, FAIL 183, FAIL 184, FAIL 185, FAIL 186, FAIL 187, FAIL 188, FAIL 189, FAIL 190, FAIL 191, FAIL 192, FAIL 193, FAIL 194, FAIL 195, FAIL 196, FAIL 197, FAIL 198, FAIL 199, FAIL 200, FAIL 201, FAIL 202, FAIL 203, FAIL 204, FAIL 205, FAIL 206, FAIL 207, FAIL 208, FAIL 209, FAIL 210, FAIL 211, FAIL 212, FAIL 213, FAIL 214, FAIL 215, FAIL 216, FAIL 217, FAIL 218, FAIL 219, FAIL 220, FAIL 221, FAIL 222, FAIL 223, FAIL 224, FAIL 225, FAIL 226, FAIL 227, FAIL 228, FAIL 229, FAIL 230, FAIL 231, FAIL 232, FAIL 233, FAIL 234, FAIL 235, FAIL 236, FAIL 237, FAIL 238, FAIL 239, FAIL 240, FAIL 241, FAIL 242, FAIL 243, FAIL 244, FAIL 245, FAIL 246, FAIL 247, FAIL 248, FAIL 249, FAIL 250, FAIL 251, FAIL 252, FAIL 253, FAIL 254, FAIL 255, PASS 0 us 545.90 ms
Error code: 0x01
Error code: 0x01
String FAIL 0 us 880.98 ms
-----------------------------------------------------------------------------------------------------------------------------
Feature Requests only
- [x] If this is a feature request, what is the motivation / use case for changing the behavior? This part is in an interesting Texas Instrument Launchpad for developing wireless IOT applications.
I'm afraid I do not have the CC3220MOD and will probably not be able to get my hands on one in the near future. I've added the 'help wanted' tag to this issue and will leave it open to see if anyone else can help.
My apologies for the late reply - I've been away for the last year-ish due to health issues.
