• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 29 subscribers
  • Views 535 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

How to connect EK-TM4C123GXL and CC2530 ?

po chao
Prodigy 20 points
Other Parts Discussed in Thread: EK-TM4C123GXL, CC2530, ENERGIA

I have a co2 sensor and I want to use EK-TM4C123GXL launchpad to send the data into CC2530.

My plan is : Using Energia let EK-TM4C123GXL launchpad to get the data from co2 sensor  and send it to CC2530 with I2C .

 I'm trying to use "wire.h" to make the connection between EK-TM4C123GXL launchpad and CC2530 .

To compile CC2530 , which must  be compiled with IAR 8051 , and EK-TM4C123GXL launchpad could be compiled with IAR AVR or Energia (I'd choosen it) , there is incompatible between the software.

This is my problem: How to use I2C to let those software connecting with each other ?

  • 0
    Guru 117855 points

    po chao said:
    and xEK-tm4C123 launchpad could be compiled with IAR AVR

    That's unlikely - AVR denotes another vendor & to my best knowledge has no overlap to TM4C family.   Perhaps you meant, "IAR ARM" which indeed works very well w/this vendor's MCUs.  (and multiple, other ARM MCUs - as well.)

    We note that you've failed to detail your sensor's output.   (may be analog or digital - such is required - is it not?)

     My firm lives/breathes KISS - your issue may be divided into smaller, more manageable pieces - mais non?

    • Avoid any/all use of the CO2 sensor until after all of the following is achieved
    • master the ability to have the TM4C transact w/a slave device via I2C.   Suggest a small, simple EEProm as fastest, easiest, (almost free).
    • master the ability to have the xCC2530 transact (likely just receive) w/the TM4C via the I2C channel
    • if - and only if - you are able to regularly & robustly pass I2C data (i.e. transact) between the TM4C & xCC2530 - only then would I attempt to interrogate the sensor

    Starting w/the sensor is likely to delay & frustrate - following the procedure outlined above raises the chances of "inter-device" communication success.   (which usually proves the highest hurdle)   Once that's achieved - let the "sensor battle" begin...

    Suggest that you use IAR ARM (free 32KB code size KS (only)) and use external pull-up Rs (not enfeebled MCU ones)  if you value time/effort/sanity/signal robustness...)

  • 0 in reply to cb1_mobile
    Prodigy 20 points
    Appreciate for your suggest , I think I do not understand enough to ask the question like that. I should think about it ,sorry.
    Oh , my co2 sensor is call ogm220 , whose output is digital output .
  • 0 in reply to po chao
    Guru 117855 points

    A digital output sensor usually - but not always - follows I2C, SPI or dreaded, "1-wire" protocol.    You must adapt your TM4C's (likely) serial interface to match that of your sensor.  (i.e. the "sensor" is the "boss" - in this case)

    Perhaps if you read several times the suggestions may become clearer.   I broke them into small parts - not much more I can do to assist further...