• State Not Answered
  • Replies 5 replies
  • Subscribers 62 subscribers
  • Views 1386 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 119465
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

I2C pins used in ISP130301

jpaetau

I plan on using the ISP130301 and would like to ask the following:

  1. 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.
  2. Ideally I would like to receive from Nordic a firmware load (XYZ) that you recommend for the BLE sip so I could do my layout and schematic accordingly, and preferrably order this parts and recommended firmware to avoid any risk. I understand that the I2C pins can go on any GPIO but at this stage we just want to try it and have it work. Later we may need to modify the BLE firmware..but not now
  3. Could we get the ISP13301 preprogrammed with your firmware so we just populate the boards?
  4. Are there any other external components necessary to the ISP130301 I need to add to my schematic?

thanks for your help

Bay6Sense is a new startup with connections in the Bay Area California developing Consumer wearables and Power management systems. this BLE device will go on both of these projects.

  • 0

    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

  • 0

    Hi,

    Just my view (maybe Nordic support will help you more):

    1. 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't supply other FWs with source code beside these examples.
    2. Are you asking Nordic on their forum to develop some BLE FW for you? For free?;)
    3. I guess having any module pre-programmed can be done only by its supplier so you should talk to Insight Sip.
    4. If this is not evident from ISP130301 data sheet then you should again talk to Insight Sip.

    Cheers Jan

  • 0

    This doesn't make any sense. Looking at the datasheet for the ISP130301 nothing is "connected to two sensor chips", 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've already chosen and connected two GPIOs so you can do that for two more.

    The only firmware (XYZ) which Nordic provides is the bluetooth softdevice. That doesn't deal with GPIO connections or peripheral usage at all. That's all code you need to write.

    Perhaps you'd be better off buying an nRF51 development kit, breadboarding your peripherals and developing the firmware, then you design the board.

    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.

  • 0 in reply to endnode

    @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 http://developer.nordicsemi.com/.

Related