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

MKR WAN 1310, No coms. #234

Open
adamtclark opened this issue Mar 29, 2022 · 0 comments
Open

MKR WAN 1310, No coms. #234

adamtclark opened this issue Mar 29, 2022 · 0 comments
Assignees
Labels
possible bug Possibly a bug. Needs verification before moving to *bug* status.

Comments

@adamtclark
Copy link

Any bug report raised here MUST be submitted according to this template or it will be flagged with 'Not enough information'. No action will be taken till all the prerequisite information is provided. If no information is provided for over a month after the 'Not enough information' label is applied, the issue will be closed.

Pre-bug report checklist:

Do this checklist before filing an bug report:

  • [no ] Is this something you can debug and fix? Send a pull request! Bug fixes and documentation fixes are welcome.
  • [ no] Is this an idea for a feature? Post it as a Feature request. NOT a bug report.
  • [ yes] Is this a bug that you cannot fix? Go ahead with filing a bug report below

Bug Report

Describe the bug

I am trying to run the SPIMemory library with the Arduino MKR WAN. I have updated the pin connections following this documentation (https://github.com/arduino/ArduinoCore-samd/blob/5dced38e81e6001a4b6e237e3462bc8db962127a/variants/mkrwan1300/variant.h#L220), i.e. with SPIFlash flash(FLASH_CS, &SPI1 (and various variants thereof, i.e. with SPIFlash flash(32, &SPI1), etc.).

When I run the FlashDiagnostics.ino code, I still get the error message:
SPIMemory Library version: < 2.5.0
No comms. Check wiring. Is chip supported? If unable to fix, raise an issue on Github

I actually have v. 3.4.0 of SPIMemory installed, and did un-comment RUNDIAGNOSTICS in the header file before I ran the FlashDiagnostics script.

At this point, I don't know whether this is a hardware issue, or a software bug (though I have reproduced this problem with 5 separate units, all of which show the same behavior). Since the error message says to post an issue on GitHub, that's what I'm doing.

  • Make sure you have run FlashDiagnostics.ino with #define RUNDIAGNOSTICS uncommented in SPIFlash.h. Paste the relevant sections of the output from your Serial console when you run FlashDiagnostics.ino.here:
Initialising..........

SPIMemory Library version: < 2.5.0

No comms. Check wiring. Is chip supported? If unable to fix, raise an issue on Github

  • If you have a problem with a particular function, call the flash.error() function (after you have made sure you have started up your Serial port with a Serial.begin(BAUD) ). Provide details of the function, the data given to/ expected from the function and the error code here: (Please repeat this for every function you have an error with)
    - Function: (e.g. writeByte())
    - Data: (e.g. 3.14 or Struct)
    - Error code: (e.g. 0x0A)

To Reproduce

Provide a minimal code snippet example that reproduces the bug (If you're using one of the examples that came with the library, just tell us which one instead of pasting the entire example's code). Please make sure you wrap any code in the proper code blocks like below

FlashDiagnostics script, with L44 commented out, and L47 set to SPIFlash flash(FLASH_CS, &SPI1).

Expected behavior

Ought to be able to connect to the chip, and run the diagnostics script.

Software environment (please complete the following information):

  • Library version: v3.4.0
  • Arduino IDE version: 1.8.19
  • OS: Windows 10
  • Micro controller platform: MKR WAN 1310
  • Flash/Fram memory module: W25216
DO NOT DELETE OR EDIT anything below this

Note 1: Make sure to add all the information needed to understand the bug so that someone can help. If any essential information is missing we'll add the 'Needs more information' label and close the issue until there is enough information.

Note 2: For support questions (for example, tutorials on how to use the library), please use the Arduino Forums. This repository's issues are reserved for feature requests and bug reports.


GitHub issue state GitHub issue title GitHub issue author GitHub issue label GitHub issue comments GitHub issue age GitHub issue last update

@adamtclark adamtclark added the possible bug Possibly a bug. Needs verification before moving to *bug* status. label Mar 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
possible bug Possibly a bug. Needs verification before moving to *bug* status.
Projects
None yet
Development

No branches or pull requests

2 participants