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.

Please help a student with application

Other Parts Discussed in Thread: CC3100

Good evening,

I have an application that I would like to implement. My application is fairly simple:

1. A camera will take pictures and output them to a microcontroller

2. A microphone will record audio and output it to a microcontroller

3. The microcontroller will send the pictures and audio wirelessly to a computer

4. The computer will have a program running that will process that data

5. The computer will send audio data back to the microcontroller

6. The microcontroller will output that audio to a speaker

This is what I'm thinking:

1. Using an Arducam to send JPEG pictures via SPI to a TM4C1294 MCU

2. Using the TM4C's analog-to-digital converter to record and digitize analog mic data

3. Using a CC3100 WiFi Boosterpack for the TM4C to wirelessly send the digitized camera and audio data to the computer program on the desktop

4. Send audio data via WiFi back to the MCU from the desktop, and then send that via SPI to a digital-to-analog converter which then goes to a speaker

Is this system architecture right, and if so, will this hardware get the job done? Does anyone have any suggestions, preferably on hardware (although all advice much appreciated) for this application?

Thank you,

Charles

  • Charles Asquith said:
    My application is fairly simple

    Many applications - when viewed from (at/around) 50 thousand feet - seem "simple."      

    During the (usual) course of implementation - endless & cascading details invade - and what was (from a great distance) viewed as "simple" - may no longer - be so noted!

    Untold is your:

    • time-frame for completion
    • resources & existing skill-set (beyond "student")
    • computer program - resident upon the desktop
    • performance specifications - especially that of the camera & its data transfer

    Is it possible that your (initial) choice proves too broad - too demanding?     What penalties attach - should you be, "Unable to complete (everything) - w/in the (yet unspecified) time-frame?"    

    Would it not prove "safer" - for you to (somewhat) - reduce the depth & breadth of this challenge?     Every one of the items you've listed - has resulted in posters - having "Crashed-Burned" - then landing here - bleeding & pleading for help...     You may NOT want to,  "Join that group..."

  • Hi Charles,

    I agree with cb1, you are setting yourself up for a daunting task. Also TM4C may not be the best fit for you given the project scope. We don't have much support for WiFi chips like the CC3100 outside of our TI design for it, whereas the MSP432 (also an ARM core MCU) is plugged into the SimpleLink library and therefore offers much more collateral for working with the CC3100 including up-to-date SDK's. The MSP432 also offers good ADC performance, so you wouldn't be lacking there. You may want to leverage that setup which is a bit better positioned for your application as I don't see any mention of TM4C peripherals that would give it an advantage over MSP432 (USB, CAN, Ethernet etc.) once you also add WiFi into the equation.
  • Good afternoon cb1,

    I was trying to make it sound less intimidating than it actually is to hopefully foster discussion. To give you a little more information...

    - There is no time-frame for completion, this device is something that I am making as an individual inventor

    - I am still a student, although I have experience configuring peripherals for microcontrollers as well as interfacing different devices for various applications

    - The computer program resident on the desktop simply needs to be able to access the data being sent from the microcontroller and store it in a variable so that a software library that I am using can access it. The program might read the audio data and wrap it into a header to make it a specific type of file, like a .mp3 or something. Not really sure yet.

    - The camera just needs to be able to send a few pictures in a few seconds at the push of a button. There isn't really a specific criteria here. I believe right now the Arducam outputs a 1 or 2 Mb picture over a SPI bus that (I think, off of the top of my head) runs at 8 MHz, which means that it can output a few pictures in a few seconds just fine.

    cb1_mobile said:

    Is it possible that your (initial) choice proves too broad - too demanding?     What penalties attach - should you be, "Unable to complete (everything) - w/in the (yet unspecified) time-frame?"    

    Would it not prove "safer" - for you to (somewhat) - reduce the depth & breadth of this challenge?     Every one of the items you've listed - has resulted in posters - having "Crashed-Burned" - then landing here - bleeding & pleading for help...     You may NOT want to,  "Join that group..."

    Of course, it is possible that I might be getting myself in too deep here. The problem that I'm having right now is that I have an application in mind, I have some ideas for hardware, but I don't really know precisely what I need. Just looking for a sanity check that it is possible to get what I'm trying to get done with what I have. More importantly, I'm looking for suggestions on product choices that possibly come with resources to make this development easier.

    I should also mention that my TM4C MCU is already able to read mic data using the ADC and output data to the speaker via SPI, I'm mainly just struggling with the wireless connectivity part and shipping this stuff to/from the desktop computer.

    Thank you again.

    Charles

  • Thank you - yet I believe your response should have been directed to (both) Ralph & myself.      (He & I are in fundamental agreement.)

    Ralph makes very pertinent points re: WiFi support - yet I would note that while you have "unspecified" performance demands for your camera-aspect - you should know that Cortex M4 devices exist - which include (proper) "Camera Peripheral Modules" - which eliminate (entirely) the camera data's transmission requirement - AND the (entire) Arducam!      While greatly improving performance!     That's a substantial design improvement - is it not?

    It is suspected that your design would greatly benefit from your proper investigation of "commercial products" - which come (reasonably) close to  your project.      (i.e. creates a, "Frame of Reference" for you)     Such would - at minimum - provide (some) insight into, "Performance Specifications" - which should advise your design - guide your component selections - and enable your project to become (somewhat) competitive...

  • "Does anyone have any suggestions, preferably on hardware (although all advice much appreciated) for this application?"

    a microprocessor, not a microcontroller, is a much better starting point for you.

  • Hi Danny,

         I recommend to use these below components. See, links

    1. CC3200 Launchpad or CC3200SF Launchpad - ARM Cortex M4 + WiFi Network Processor.
    2. Audio Booster Pack BOOSTXL-AUDIO - Pin compatible with CC3200XX Launchpad I2S pins.
    3. MT9D111 Camera Module for CC3200XX Launchpad

         You need to first make the CC3200XX Launchpad work with Audio Booster Pack and then MT9D11 Camera Module Example Programs. Then you integrate all together. But, if you are new to this, this is difficult. You can ask for help at the TI SimpleLink WiFi Forum.

    -kel

  • Wonderful ... yet poster "Danny" has not presented this requirement.  

    Are ANY of those components noted for their, "Features, Functions, Performance Benefits?      Or - are they just "conveniently available" - is that to be the "Driving Source" of any "invention?"   

    The ABSENCE of a (proper) Camera Peripheral Module - w/in the MCU - is (almost) guaranteed to render this project, "Non-Competitive!"

    Any such "invention" - providing sub-standard performance - without  (even) "awareness" of  "competitive standard norms" - is unlikely to "go-far/prosper..."

    Should not a VERY KEY PART of any "invention" - be the focused & in-depth study of,  "Near competitive offerings" - to "glean their specs, capabilities, & prices?"     To choose from a "so limited" - Vendor Grab Bag - (strictly due to ease/familiarity) rather than devote the time & effort to "choose properly" - casts "grave doubt" on any such "invention(?)"