forked from Marzogh/SPIMemory
-
Notifications
You must be signed in to change notification settings - Fork 0
Update to latest Master #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous version of the library returned a wrong value. This has now been fixed. Refer to comments in _getSFDPFlashParam(void) for further details.
This is because no default _pageSize value was set in this scenario. This has now been fixed.
SPIFlash::_beginSPI will not call _startSPIBus opening an SPI transaction if SPIBusState is 'true'. Without specifically initializing _startSPIBus to false, its possible that it could on bootup be set to true. Another SPI bus could set some SPI settings and then attempting to run a SPIFlash transaction fails because beginTransaction never gets called to set the required SPIFlash settings.
Initialize SPIBusState to false
Added support for Microchip SST26VF016B SST26VF032B chips. thanks @mix86 mix86
Changed the lists from nested bullet lists to tables to make it easier for the end user.
Jumper wires and breadboards (especially solderless ones) have very poor high-frequency characteristics leading to weird problems in high-speed communications.
Update SPIFlash.h Fixes #151
Add a Gitter chat badge to README.md
``` SPIFlash flash(int8_t *SPIPinsArray); ``` can be used (only with ESP32 boards as of now) to enable the use of custom SPI pins. ```SPIPinsArray``` has to be a 4 element array containing the custom SPI pin numbers (as signed integers - int8_t) in the following order - sck, miso, mosi, ss. Refer to the wiki for more information. Resolves #113 - Created new error code `NOCHIPSELECTDECLARED` for errors with declaring custom SPI pins. - Using other SPI ports (HSPI, VSPI, SPI1, SPI2 etc.) is now also supported on ESP32 boards - along with SAMD and STM32 boards (supported since v3.0.0). Resolves #117
…log.md - and moved it to root folder of the library.
Latest stable changes from development - Custom SPI pins and multiple SPI support for ESP32
Make it possible to configure SPI clock right from the beginning
…ts them to Serial when RUNDIAGNOSTICS is enabled
Final code for v3.4.0 from Development
Final code for v3.4.0 from Stable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.