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.

Video Enconding Using Stellaris

Hi

Im working on my first real project for school. Im using the Stellaris Launchpad for testing. I want to be able to transmit a live video feed wirelessly from a camera located on a remote control car to my android device. I was planning on using the CC3000 simple wifi to establish a link between my camera and android. I was wondering if would be able to use both the CC3000 and Stellaris launchpad to work together to transmit my video feed in real time. I have no real experience in video encoding, I basically want to know if the stellaris can handle the video encoding so that I may proceed. Thank you!

 

Allen

  • IMHO the Cortex M class is not targeted at those video applications. Just take your preferred video resolution, colour mode, frame throughput and en/decoding algorithms, and estimate the buffer size and performance requirements. I'm afraid the Stellaris/Tiva launchpad will drop out. Either you drastically cut down your requirements, or evaluate some Cortex A chip.

  • Beyond f.m.'s usual, sound advice - might I (ever diplomatically) direct some mention to the rather large, elephant - trumpeting loudly/unhappily - this room?

    Your, "first real project" indeed.  Might it be a "tad" of an over-reach?  Has any advisor read and/or approved this quest? 

    On a sister forum (hallowed rebrand) a grad student reports his difficulty in "taming" a relatively simple UART.

    IMHO your project - in its stated forum - is wildly "off-mark" for not only a "first" - but likely first 10 such projects!  Your desired intermix of Video, RF, ARM MCU and an Android device may deserve some re-think...  (schools really should better address, "reality"...)

  • IMHO your project - in its stated forum - is wildly "off-mark" for not only a "first" - but likely first 10 such projects!  Your desired intermix of Video, RF, ARM MCU and an Android device may deserve some re-think...  (schools really should better address, "reality"...)

    For a starter project, I totally agree. It would look more feasable when using a Cortex A<x> under Linux, hardware gfx acceleration, and lots of high level libraries.

    BeagleBone (Black) comes to my mind ...

  • Mon ami,

    Mais oui - of course you're right.  Newest BeagleBone is very nice. 

    Yet  - even with its power/capability - to properly harness - and correctly blend w/ RF, Video, and an Android - is a most daunting task.

    The apparent lack of over-sight/guidance - of mating a challenge to "some" (minimal) reality - is beyond troubling.

  • Thank you for your responses.

     

    I've actually had the chair of electrical engineering approve our project at my university, and I feel it's possible to do. I've had experience with the UART and the MSP430 already. However, I do not have any experience with video so I was not sure what the processor requirements may be. I know it's a daunting task, luckily I'm in a group of four and have two semesters to complete the project. Thank you f.m. I will look into the beagle.

  • The apparent lack of over-sight/guidance - of mating a challenge to "some" (minimal) reality - is beyond troubling.

    I don't feel in posession of the knowledge to judge the OP capabilities in this regard entirely ... But the idea of starting with a Cortex M points towards missing experience, though.

    And the BBB - just see it as a prominent representative of it's class, the Cortex A Linux SBC's - have the distinct advantage of running a proper OS. You can manage large parts of the development at a desktop PC, and even run the application on both host and target. IMHO you are very true so far, most beginners --heavily-- underestimate the effort in coming to grips with a bare-metal toolchain. Links to such fora threads, here and elsewhere, would fill pages ...

  • f. m. said:
    underestimate the effort...coming to grips.... Links to such fora threads, here and elsewhere, would fill pages ...

    Indeed - and my intent was to sound some alarm - generate some sound/proper "rethink" - prior to (what I continue to sense) an unnecessary - and significant over-reach.

    Must question the currency and focus of even an esteemed, "chair" - who approves a far too simple M3 or M4 - for so demanding - & multi-disciplined engineering effort.  If the proper mating of, "tool to task" escapes such "over-sight?..."

    I may have some basis for my concern - in past life - was design-team member responsible for the development of the top-selling, "Set-top" box.  And - early in this project we explored use of low-power RF as remote-control. (I had both Amateur Extra, First Class Radiophone w/Radar, and Military Officer communications experience)  Our effort was huge - on-going - and pressure packed.  And never/ever would have been delegated to, "first project" personnel!  Beyond this - decade earlier co-founded then "took public" hi-tech firm.  (continues today - some 25 years later - although minus all (non-CPA founders)  (there were none!)

    The fact that the request was launched here (home to M3 (may they rest in NRND peace) and M4 - rather than a more suitable (i.e. properly investigated/chosen) forum - and the "first project" revelation - strongly signaled, "insufficient knowledge/capability/experience."  (suspect - to you as well...)

    Knew that Alert sounding would jeopardize valued green-tick - and yet - for long, unexplained reasons - vendor staff avoids this vital, "Capability/Experience vs. Task" guideline/suggestion.  But not you - nor I...

    I've witnessed great harm befall those who, "launch w/out proper investigation" - even and especially when "approved/encouraged" by those who may not have fully/energetically explored all of the fine - yet requisite detail...  Silence - in this instance - may offer false comfort...

     

  • Allen Davila said:
    m working on my first real project for school. Im using the Stellaris Launchpad for testing. I want to be able to transmit a live video feed wirelessly from a camera located on a remote control car to my android device. I was planning on using the CC3000 simple wifi to establish a link between my camera and android. I was wondering if would be

    A question about why encode video stream and from which level? Do you wish acquire an analog CCIR PAL/NTSC camera or read digital data from a digital cam module? Or read from a digital cam? In this case I see someone reading video using blamed arduino, so this case MSP430 is more able to do and also TIVA of course can do better. Encoding video if you are at early stage is a non sense due to complexity of understanding all math is underlying video compression and streaming. A MJPG  (not MPEG) or RAW is simple to stream from cam to network and is simple to display on android screen too.

     Beagle board black has enough power to sample and encode an incoming video signal but IMHO is a nonsense to have a CCIR cam couopled to a digital system these day.

     What to do is linked to your final goal on learning.