Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


dellwoodbu last won the day on September 22 2012

dellwoodbu had the most liked content!

About dellwoodbu

  • Rank
    Advanced Member
  1. Worth noting... The floating point unit is single precision. C/C++ language defaults to a double for constants in code (that include a decimal point). Unless you need double precision constants i always suffix all my constants with 'f'. So "3.141f" is more efficient on this machine than "3.141".
  2. It also includes support for the new EK-TM4C1294XL Connected LaunchPad. Out of the box cloud connected. Support with working examples for CC3000 on EK-TM4C123GXL and the new Connected LaunchPad. NFC support on the boost-dlptrf7970abp with both launchpads Built in support with examples for the QVGA 3.5" Kentec BoosterPack on the new Connected LaunchPad. Built in support and example for the boostxl-battpack Battery Booster. Probably missing some other good stuff that i am currently forgetting as well. Dellwood.
  3. If you choose to use Code Composer and are new to MCU's then the LaunchPad workshop is a great resource as well. http://processors.wiki.ti.com/index.php/Getting_Started_with_the_TIVA%E2%84%A2_C-Series_TM4C123G_LaunchPad?DCMP=tivac&HQS=TM4C123G-Launchpad-Workshop Dexter
  4. I suggest connecting the center pin to the outside pin. This way if the switch is to the left it is still "off" for your application. If you connect the outer two then the switch will always be "on". Also look at adding the two resistors to PB0 and PB1 so you can monitor VBUS and ID with the USB peripheral. Be aware this could put 5V on the boosterpack pins that aren't normally getting that much voltage. Dellwood
  5. The transistors have 10 k built in series and pull down resistance. If you are using PF1 - PF3 as an output no action is required. If using as an PF1 - PF3 as an input you need to evaluate if your drive signal can overcome the pull down resistance created by the transistor built in resistance.
  6. start with the launchpad workshop http://processors.wiki.ti.com/index.php/Getting_Started_with_the_TIVA%E2%84%A2_C-Series_TM4C123G_LaunchPad?DCMP=tivac&HQS=TM4C123G-Launchpad-Workshop Chapter 10 covers the display and graphics library. The workshop has lots of other good stuff as well.
  7. Spoke with TI on this the other day and they expected to clear the remaining back-orders and have units in stock by early September. Original EK-LM4F120XL shows still in stock at $9.95 on the TI eStore. Dellwood
  8. Lm flash programmer has an unlock feature. Far right tab. Use fury class for 1968 device.
  9. John, This was a known problem with the REV A boards. On REV B the connector moved out closer to the edge of the board. The problem was that with the connector mounted in the flare of the SMD connector would float and cause the whole connector to lift in re-flow. By moving the connector out the whole connector sits more flat to the board and makes a stronger bond. Even on REV B it is not a super strong solder joint care and gentleness encouraged. If you have solder equipment a bit of extra solder on the outside of the SMD housing could be a good idea. Don't use too much or it w
  10. You can use the LaunchPad to program standalone chips that you purchase and install on your own PCB. There is a how-to at http://processors.wiki.ti.com/index.php/Stellaris_LM4F120_LaunchPad_Debug_How_To I'd suggest putting a standard ARM connector on any board you create and interface that to the pins on the LaunchPad http://www.keil.com/support/man/docs/ulinkpro/ulinkpro_hw_if_jtag10.htm This is what the programmers from Keil, IAR and others use this gives you flexibility if you want a different "standard" programmer later. The chip you buy from TI will identical to the chip on the
  11. http://e2e.ti.com/support/microcontrollers/tiva_arm/f/908/p/266853/942510.aspx#942510 TI posted updated code for the MPU9150.
  12. dellwoodbu

    UART problem

    I have not tried this personally. However, you are using UART0 which is connected to the ICDI microcontroller. The baud rate therefore must match between the ICDI microcontroller and the target. It is possible that the ICDI is not correctly changing its baud rate to match the settings in PuTTY. At a minimum the ICDI will come out of reset or power up with settings at 115200 and it may just not be in sync with PC. You could try sending characters in PuTTY and see with a scope what baud rate they get sent from the ICDI to the target. The test points are near the reset button TXD and
  13. Make the variable scope wide enough to include the interrupt function. static global or global. Make it volatile. Make the interrupt handler a dummy function that passes the variables to another sub-function. This still requires that the int handler have visibility to the variables in question.
  14. Soldering iron to gently heat and remove best choice. Side cutters will also cut the resistors. Or cut trace (last choice). No side effects. They are there for msp launchpad compatibility. Puts i2c and spi on same boosterpack pin.
  15. It seems to be working here. I download the drivers and tried to attach but they are 9MB and over the file size limit. I split it in two parts with 7zip tried to upload the parts and get a file type not permitted error. Tried to change file extension and still get the same error. Keep trying back on the ti website http://www.ti.com/tool/stellaris_icdi_drivers Sorry.
  • Create New...