Jump to content


  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by TI_Trey

  1. OSX support will continue to be limited for now. Like bluehash said, there is no compiler, and it is questionable whether the debugger would work. That being said, TI is aware of the growing number of engineers using Apple products. We are actively working to add support for Mac OS to our products.
  2. AWESOME!! I can't wait to see this...sounds like a great boosterpack idea!
  3. I noticed two things I'd like to comment on: The LEDs are setup such that they are on when the associated GPIO is low. The buffers driving them are non-inverting and the LEDs are setup such that the buffer sinks current. There is no design reason for this...its just how I implemented it at the time. Initially all the GPIOs are Hi-Z at reset. The buffers which drive the LEDs also have a Hi-Z input, so it very easy for a little bit of charge to build up and change the voltage on these nets when the GPIOs are unconfigured. This is purposeful as this is a learning tool and this makes a great
  4. No, problem. Once again, sorry for the trouble. All this stuff is still very new and ya'll are the first brave souls (beside myself) to test this stuff out (its only been public for a month). With any new software there are going to be a few bugs to be worked out, but I'm confident that with this community's help we can get the software polished and some amazing projects developed with this board. Trey
  5. Indeed! Welcome! Let me know if you run into any issues with the driver library. Its relatively new, and I'd like any criticism or suggestion such that I can improve it. Happy Tinkering!
  6. Hi Stunner! There are some good training videos here: http://www.ti.com/lsds/ti/microcontroller/32-bit_c2000/training.page#Videos The online 1 day workshop would be a great place to start. Even though it covers the 06x devices, 99% of the material will still apply to the LaunchPad. I'm going to try to start doing some LaunchPad specific videos, but time to do so is hard to come by. There is also the processors wiki which has some videos and some tutorials. You can find that here: http://processors.wiki.ti.com/index.php/C2000_LaunchPad And hey if worst comes to worst, yo
  7. Also....I'm not super familiar with laser diodes, but they effectively need a constant current source to drive them, yes? The ideal way to drive this would be to use the C2000 to do a digital control loop around a boost/buck converter in a constant current control scheme. That is what the chip is designed to do.
  8. Also very much looking forward to seeing this thing light up! When you say it doesn't see C2k and doesn't give you any options are you referring to the GUI interface (Resource Explorer)? I have been getting varying reports about this working for some people, but not working for others. What OS are you using and are you on a 32 bit or 64 bit machine? You can always import examples by going to file import in the main CCS window. I would start with the ADC_SOC example. It will show you how to start a conversion (SOC). There was a bug that was found in that example that prevented it f
  9. I'm traveling right now....actually doing a LaunchPad Training at McMaster University close to Toronto Canada on Wednesday. When I get back to work later this week, I'll create the branch and upload the work that I've done so far on supporting the C2000 LaunchPad in Energia.
  10. I dig it CorB! Once we get this more mature I'll see if I can't get this rolled into the code we release.
  11. Hi Rei! YES! I'm already working on adding C2000 support to Energia. I have all the modifications done to the IDE, but I still need to write the wrappers for the drivers to make them Arduino compatible. I just have the code local on my machine right now, but I'm planning on creating a branch in the main Energia repo. I'd love to get some help from the community if anyone has the time and expertise to dedicate to helping out. Since the LaunchPad has launched I have been super busy and don't have the time I need to really support the LaunchPad correctly. Trey
  12. They are different code generation tools and we have a significantly more complex memory map than an MSP430. In the directory where the .out file sits after a program is compiled you should find a .map file. This files contains a map of all of the memory in the device, where your program code and data is located, and how much of that space is taken up. Here's an example of a project I'm working on porting from MSP430...notice the out file's name... ****************************************************************************** TMS320C2000 Linker PC v6.1.0 ***********************
  13. Well you could do this: #define AIO4toGPIO {EALLOW; \ GpioCtrlRegs.AIOMUX1.bit.AIO4 = 0; \ GpioCtrlRegs.AIODIR.bit.AIO4 = 1; \ GpioDataRegs.AIODAT.bit.AIO4 = 1; \ EDIS; } There might also be functions in the driver library to do this for you...I forget. If there aren't, I can add them in a month or two....I'm sooo busy right now.
  14. Looks good Mihai. What did you think of the drivers? They are pretty new so I'm trying to get some feedback. Were they helpful?
  15. Glad to have you James! Interested to see what you come up with! Cheers!
  16. I'm taking myself out of the running for the free LaunchPad...I'm up to my eyeballs in LaunchPads, BUT Here's what I would do: Class D Audio Amplifier (switching amplifier...very efficient) Stepper Motor Driver (for use with RepRaps or other 3D printers/CNC equipment) iOS Audio Data Interface (Ya know how the Square payment thing works?!? You would use the PWM as a poor man's DAC and the ADC to modulate/demodulate audio signals. This could be used to send digital data to and from an iPhone/iPad without Apple's security chip....I think this has been done, but it would be cool to see suppor
  17. Don't give up!!! Take heart, I believe I've found your issue. The chip select for the LCD is routed to ADCINA4 (which can be used as a GPIO). You need to configure this pin to be a GPIO...perhaps something like this: EALLOW; GpioCtrlRegs.AIOMUX1.bit.AIO4 = 0; GpioCtrlRegs.AIODIR.bit.AIO4 = 1; GpioDataRegs.AIODAT.bit.AIO4 = 1; EDIS; and then when you transmit and recieve you need to drive this pin low. Perhaps you could change LCDSPI to something like this: void LCDSPI(uint16_t command, uint16_t data) { char first = (command << 7) | (data >> 1); char second = (data &l
  18. Gotcha, ya that's the older code that hasn't been touched in a few years. Those examples are nice for that reason, its very easy to see what bits in each register are set to. That beings said, we are trying to move away from the bitfield approach because it isn't standard and can potentially cause issues. They are fine to use for learning though. Check it out All you really should need to do to get it to run in flash it to switch out the linker command file for one of the Flash ones. If you are using any functions that are linked to RAM you'll need to make sure there is a call to m
  19. CorB, Where did you get this sample code from? Specifically what directory in controlSUITE? This is a really old version of the example. The newer examples do in fact have the dual build configuration and use the new driver library. FYI I'm gonna try to start doing some videos to help explain some of the quirks related to C2000. Hopefully that will help ya'll learn the chip a little easier.
  20. Hrmmm...weird. Maybe you are linking your application to run from RAM and have not reprogrammed the flash yet. That would cause the behavior you're seeing. All the example projects should have two build configurations: one for RAM and one for Flash. You ought to be able to easily switch between the two by right clicking on the project in CCS and going to the Build Configurations entry.
  21. You could potentially add some clamp diodes between the analog input and the two supply rails. We do this on the larger controlCARDs but space was limited so we omitted these on the LaunchPad. The part we use on the F2802x controlCARD is NUP4201MR6: http://www.onsemi.com/PowerSolutions/product.do?id=NUP4201MR6 These will stand up to a little abuse, but they are really designed to protect the pins from ESD. If you put 50 volts on one of the LaunchPad pins you WILL fry the board.
  22. CorB, You're sooooo close! Turns out our SPI is a little different because of the 16 bit wide memory architecture. Data must be written to the transmit register LEFT justified (check the guide SPRUG71 page 30). The register is 16 bits wide so if you want to transmit 8 bit wide data you need to shift it up by 8. Try changing your transmit function to something like this: void spi_xmit(char sdata) { SpiaRegs.SPICTL.bit.TALK = 1; // Enable Transmit path SpiaRegs.SPITXBUF = (sdata << 8); // Master transmits data // while(SpiaRegs.SPISTS.bit.INT_FLAG !=1) {} // CORB COMMENTED OU
  23. Ya kinda! Check it out: http://dangerousprototypes.com/docs/Sick_of_Beige_standard_PCB_sizes_v1.0
  24. Love It! Actually I was thinking it would be really cool if we did a base board which had the Danger Prototypes case form factor. Then we could really easily put together cases for projects.
  25. Pjkim, Yes the diagram is incorrect. It should be XINT1CR/XINT1CTR...etc. Yes, you are correct. Only 3 GPIOs at any given time can be used to create an interrupt, but you may select any 3 GPIOs. You may want to look at using the capture module. You could add a little external hardware to figure out the direction and then just use one of the quadrature signals piped into the capture to figure out rotations/velocity etc. There is only one channel though, so you'll probably need to use external interrupts and the capture. Trey
  • Create New...