<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>I2C pins used in ISP130301</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/19466/i2c-pins-used-in-isp130301</link><description>I plan on using the ISP130301 and would like to ask the following: 
 
 I would like to start my schematic and layout using the ISP130310 from Insight Sip and would like to know the preferred I2C pins for a given firmware load. 
 Ideally I would like</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 06 Feb 2017 13:49:16 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/19466/i2c-pins-used-in-isp130301" /><item><title>RE: I2C pins used in ISP130301</title><link>https://devzone.nordicsemi.com/thread/75615?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 13:49:16 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:ddcaf595-7c9a-41b5-8435-b0868bed6a92</guid><dc:creator>bjorn-spockeli</dc:creator><description>&lt;p&gt;@jpaetau : As both RK and Endnode has pointed out, we only provide the BLE Stack(our SoftDevices). In order to have a functional BLE product you need to develop the application firmware that uses the SoftDevice yourself. Our customers usually start from the examples provided in our SDK and use them as base for their own custom application. You can download our SDK from &lt;a href="http://developer.nordicsemi.com/"&gt;http://developer.nordicsemi.com/&lt;/a&gt;.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C pins used in ISP130301</title><link>https://devzone.nordicsemi.com/thread/75613?ContentTypeID=1</link><pubDate>Mon, 06 Feb 2017 01:34:02 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:430f9ad0-62fa-4605-aa4c-9a9d4cf5de5d</guid><dc:creator>RK</dc:creator><description>&lt;p&gt;This doesn&amp;#39;t make any sense. Looking at the datasheet for the ISP130301 nothing is &amp;quot;connected to two sensor chips&amp;quot;, nothing is connected to anything, the GPIOs are all available for you to choose and connect as you wish. So if something is connected to two sensor chips that means you already have a schematic and you&amp;#39;ve already chosen and connected two GPIOs so you can do that for two more.&lt;/p&gt;
&lt;p&gt;The only firmware (XYZ) which Nordic provides is the bluetooth softdevice. That doesn&amp;#39;t deal with GPIO connections or peripheral usage &lt;em&gt;at all&lt;/em&gt;. That&amp;#39;s all code you need to write.&lt;/p&gt;
&lt;p&gt;Perhaps you&amp;#39;d be better off buying an nRF51 development kit, breadboarding your peripherals and developing the firmware, then you design the board.&lt;/p&gt;
&lt;p&gt;And the nRF52 series has (limited) NFC capabilities built-in, so if you only need a simple NFC peripheral, you might be better off with that chip.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C pins used in ISP130301</title><link>https://devzone.nordicsemi.com/thread/75614?ContentTypeID=1</link><pubDate>Sun, 05 Feb 2017 20:38:48 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fa0d5408-1b8a-482e-a66a-2d082dd74b46</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;Hi,&lt;/p&gt;
&lt;p&gt;Just my view (maybe Nordic support will help you more):&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Any of GPIO pins can be I2C, there is no preference. If you want to use specific FW then you need to say which one. Have you chosen any of examples in Nordic nRF5/nRF51 SDK? As far as I know Nordic don&amp;#39;t supply other FWs with source code beside these examples.&lt;/li&gt;
&lt;li&gt;Are you asking Nordic on their forum to develop some BLE FW for you? For free?;)&lt;/li&gt;
&lt;li&gt;I guess having any module pre-programmed can be done only by its supplier so you should talk to Insight Sip.&lt;/li&gt;
&lt;li&gt;If this is not evident from &lt;a href="http://www.insightsip.com/fichiers_insightsip/pdf/ble/ISP130301/isp_ble_DS130301.pdf"&gt;ISP130301 data sheet&lt;/a&gt; then you should again talk to Insight Sip.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Cheers Jan&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C pins used in ISP130301</title><link>https://devzone.nordicsemi.com/thread/75612?ContentTypeID=1</link><pubDate>Sun, 05 Feb 2017 16:03:33 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:8ed6a887-a24b-428e-bcc1-3bc42090eee1</guid><dc:creator>jpaetau</dc:creator><description>&lt;p&gt;the ISP130301 is from Insight Sip and it is based on the Nordic nrF51. Apparentlyit has 2 I2C outputs. Currently one is connected to two sensor chips. I need the other I2C to come out somewhere out of the ISP130301 package to an NFC controller&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: I2C pins used in ISP130301</title><link>https://devzone.nordicsemi.com/thread/75611?ContentTypeID=1</link><pubDate>Sat, 04 Feb 2017 22:47:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:6052e9d6-ec8e-418d-865f-1a40bc5e3ce2</guid><dc:creator>endnode</dc:creator><description>&lt;p&gt;One would ask: what the hell is ISP130301?;)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>