- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Now I can download the app either in EEPROM or spi flash use the SDK,however ,here comes the question that the SDK has set the SPI1 or IIC as the interface,Our product want to set the SPI2 as the interface,I know I need to reconfig the SDK environment,but I did't find where to config the GPIO definition and SPI2,do you have any ideas?
Solved! Go to Solution.
- Labels:
-
FlashEEPROM
-
SDK 2.X
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Related to the I2C interface, SCL+SDA on pins shared with SPIFFY1 (SPI1).
So you are correct, I2C and SPI1 (SPIFFY1) cannot be used at the same time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It is not possible to configure SPI2 for nvram access.
More details is in "HW interfaces.pdf" within your IDE.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thank you ,but if we want to connect to some IIC sensors,there seems to no IIC lines for me to choose,do you have any sugestions.
best regards
1212470128@st.usst.edu.cn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Have you seen the WICED Sense Kit?
WICED Sense Table of Contents
This device leverages the SiP module and the I2C bus for interfacing with the onboard sensors.
The TOC link above links to the source code.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
sorry,we don't have this this kit,we are evaluating the tag3.
I can download it from the community.
1212470128@st.usst.edu.cn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
but the Hardware Interface says that when using IIC as NV storage,the SPI1 is not avalible.thus,if I use SPI1 as NV storage, Can I use the IIC to communicate with other slave device.
1212470128@st.usst.edu.cn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Besides,we select the SPI1 flash as the NVstorage and also want to connect to some other IIC slave device
1212470128@st.usst.edu.cn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Related to the I2C interface, SCL+SDA on pins shared with SPIFFY1 (SPI1).
So you are correct, I2C and SPI1 (SPIFFY1) cannot be used at the same time.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
get it,thank you.
1212470128@st.usst.edu.cn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks for the explanation about I2C and SPI1.
1. Can we get an update if I2C and SPI2 can be used at the NVRAM interface?
2. Can we get a pointer on making SPI2 the default SFLASH interface?
3. The "WICED Smart™ Hardware Interfaces.pdf" states "The SPIFFY1 interface supports only the master mode of operation which is dedicated to accessing non-volatile (NV) storage items such as configuration, patches, application code, and application data". Can we make SPIFFY2 in master mode as the NV Storage device?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
1.
I2C is used as the NVRAM interface on our development kit and on the WICED Sense experience kit. SPI2 is the slower of the two SOI interfaces on the device, so I have never seen it used as an NVRAM interface. SPI1 and I2C shares pins, so you can only use one or the other. The WICED Smart Hardware Interfaces document explains much of this.
2.
Again, I have never seen this done as it is much slower than SPI/SPIFFY 1. Not to say it wont work, just there are no examples to follow.
3.
See above.