Skip to content
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

Minor fix in API description #117

Merged
merged 1 commit into from
Mar 11, 2018
Merged

Minor fix in API description #117

merged 1 commit into from
Mar 11, 2018

Conversation

polaroi8d
Copy link
Contributor

There is a little typo in the getManID().

@Marzogh Marzogh self-assigned this Mar 11, 2018
@Marzogh Marzogh added this to the v3.1.0 milestone Mar 11, 2018
@Marzogh Marzogh added the bugfix Fixes an existing bug in the current version of the code label Mar 11, 2018
@Marzogh Marzogh merged commit 5703890 into Marzogh:development Mar 11, 2018
@polaroi8d
Copy link
Contributor Author

It's okey, thanks for the merge.

@polaroi8d polaroi8d deleted the patch-1 branch March 12, 2018 12:56
Marzogh added a commit that referenced this pull request Jun 1, 2019
```
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Fixes an existing bug in the current version of the code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants