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.

Airmouse example: LEDs inactive in "Device" mode

So, to say I'm new to microcontrollers is generous. I'm certain that the solution to my problem is embarrassingly simple.

I have a TM4C123G LaunchPad with a BOOSTXL-SENSHUB sensor hub booster pack. I have been using the SPMU295 document (Sensor Hub BoosterPack Getting Started Guide) for instructions. I believe I have both connected the LaunchPad and booster pack correctly and installed the appropriate drivers.

I programmed the device using the LM Flash Programmer. I picked the TM4C123G LaunchPad configuration quick set. I chose the file under ...\ek-tm4c123gxl-boostxl-senshub\airmouse\ccs\Debug\airmouse.bin, and I selected the appropriate options indicated by the SPMU295 document. When I finally clicked the program button, the RGB LED began intermittently flickering red.


Now, the next step as indicated by SPMU295 is to "slide the power select switch to the left to choose power from the USB device port." Upon doing this, all the lights instantly turn off. Nothing I did would turn them on, except sliding the switch back to the right. The RGB LED would then begin flickering red again, and the other LEDs would illuminate as well.

So, my question is the following: is there something I've done wrong in my setup? Something/ some step I'm missing? Or do I have a lemon board, where switching to device power will always end up shutting down the board?

If this isn't the correct place to pose this question, please redirect me! Thanks.

  • Hello Elizabeth,

    Was the USB connector changed from the top side to the left side?

    Regards
    Amit
  • Speaking of "generous" - what a terrific posting! Hard to fathom (if & how) this could be your first post ever - here.

    All too often the precision description, "Does not Work!" fills this space. (as if the fault is ours - never the poster's) Yours however is thorough, sequential - best enabling your issue's successful resolution.

    Sad to say - "Intermittent flickering" usually is not good. The presence of two USB connections - and a power selector switch - demands great attention to detail - which explains the nature of vendor rep's "Amit's" question...  (he's outstanding)

    Good luck to you - it's neat to memorialize an, "All time great" first posting.

  • D'oh. That was exactly my problem. Thanks Amit!
    Out of curiosity, why two USB connectors? Wouldn't one be sufficient? Adding a second one would just seem to increase the size of the board/ cost of quality assurance testing/ possible points of failure. Not to mention confusion (as evidenced by my issue). I know this is a tangential question, but I'm interested in what pros would outweigh these cons.
  • Hello Elizabeth

    The first USB connector is for the ICDI JTAG and COM port which is used download and debug the code. This goes via the ICDI MCU which is near to the switch. If we remove that MCU and its MCU, the Cost of the board will go down, but then you would need to bug a 35$ debugger to be able to do the same.

    Regards
    Amit
  • Aww, thanks! I figured the best way to get a response was to thoroughly yet concisely describe the situation/ problem. Looks like it worked!
    Next time I won't skimp on reporting exactly what the lights are doing. Thanks for the recommendation.
  • Glad that you're, "On the Air" - most of that due to your thoroughness.   You'd probably want to (later) "buy" a debugger - although to "bug" a (debuyer) cannot be all bad...