Jump to content
43oh

TI_Trey

Members
  • Content Count

    225
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by TI_Trey

  1. Pheo, Thanks for the tutorial! I've added it to the C2000 Wiki page along with a few more of Francesco's tutorials. Keep up the great work! http://processors.wiki.ti.com/index.php/C2000_LaunchPad#Tutorials
  2. Quick Update: I just wanted to make everyone aware that I am actively working to get get us open cross platform tools. The entire Energia team is aware of the issue and we are talking with the compiler and tools guys to see if we can find a solution. It might take some time for us to get to a full open source cross platform solution for the C2000 LaunchPad, BUT I think we will be able to come up with some interim solutions that can coexist with the Energia license a little quicker. I can't promise anything right now, but I wanted to let the community know that I am fighting for you.
  3. Absolutely true. Dealing with multiple OSes can be painful but in this day and age it is necessary. Because the Energia project has a lot of backing within TI, I'm going to try to see if I can get some of the tools open sourced so they are easier to integrate with Energia (and easier to make cross platform).
  4. Imp, This is part of the design. The buffer on the LEDs are inverting buffers, so when you give it a logic high they put out a logic low which then sinks current from the LEDs. Another thing which is kinda cool is that the buffers have a very high input impedance, so much so that you may have noticed when the buffers aren't driven that you can change the LEDs state by touching the GPIO pins. This was done intentionally to show users what a floating node looks like and how it acts.
  5. Rei, Sadly there is no MacOS support for C2000 devices right now. Our tools teams are working to add support for Macs but there is no firm timeline for when this will occur. That said, some folks have been able to get the 430 LaunchPad working with Apple computers. There is a guide here: http://processors.wiki.ti.com/index.php/MSP430_LaunchPad_Mac_OS_X I'm no Mac expert, but to me it appears that all the main pieces needed to support MacOS are in place. Our teams just need the time to stitch everything together. Trey
  6. I'm pulling CS high in the ISR. That way I know the transmission is done and it's safe to pull up CS. Yes this device does have a hardware CS line, but the boosterpack standard doesn't define CS pins and the pin the GLCD CS is routed to is an analog IO.
  7. Ok, first let me explain why ya'll were having trouble getting this running on the hardware SPI. If you simply setup the code for hardware SPI and call: PinLow(CS_PIN); // pull CS LOW SPI_write(LCDSpi, spidata); PinHigh(CS_PIN); You'll end up seeing something like this on the bus: The third trace is of course CS and you'll notice it goes high during the bitstream...no good. For testing purposes I simply added a short delay after SPI_write and before I pulled CS high and sure enough the display started working. I actually ended up cleaning up Lar's code quite a bit to make it more
  8. Sorry for the delay..life has been happening and I haven't had the free time I need to devote to my LaunchPad. I went ahead and forked the Energia repo, and committed what I have so far. The project should build in eclipse, but I don't think it can compile sources yet. Rei Vilo, I've added you as a collaborator. If anyone else would like to contribute to this project please let me know and I will be happy to give you access. The fork can be found here: https://github.com/treygerman/Energia
  9. Blue, I've got the SD booster, but I'm having trouble figuring out what goes where...silkscreening could definitely be improved on this board. I found the pdf schematic, but not the design files. Could you track down the SCH and BRD file?
  10. CorB and Lars, As promised I resolved the issue with the hardware SPI. Turns out the bitstream was still being shifted out when CS went high. I added a short delay before PinHigh(CS_PIN) and it started working. I'm going to clean up the code and perhaps add interrupts so that I don't have to use a delay. Look for an update and explanation of the issue and the fixes soon!
  11. Hi Erinender, Yes, ADCIN pins can be used as GPIO and are read and written using the AIODAT register.
  12. TI_Trey

    Geek Pumpkin

    C2kCentral, I just got an email from our marketing team that we are having an internal TI geeky pumpkin contest. The goal clearly being to develop the most geeky pumpkin. There isn't really a prize other than bragging rights and the time table is pretty short (needs to be completed by Oct 17), but it sounds like a really fun project and I've already got a start on the hardware since I've got the C2000 LaunchPad and LED BoosterPack (no need for candles here!). Curious if you guys have an ideas for extra functionality I could add that would add some wow factor. I was thinking I might
  13. Ya I was gonna try to get Lar's LCD working on hardware SPI. I also ordered a SD card booster...Blue, I'll race you to see who can get FatFS running first
  14. An update did go out yesterday to add support for our new F28M36x Concerto Device (M3+C28x cores). I suspect what happened is that when you installed the update you let it install to the default location (c:\ti\controlsuite) whereas originally you had installed it in f:\path\to\controlsuite. This would have broken both of the GUI's (both external and internal to CCS). You ought to be able to fix the standalone GUI by copying the c:\ti\controlSUITE folder on top of the folder you have in F:. If you want to fix the internal GUI too, we can do that too, but I'll have to give you further i
  15. I'd really like to see this working on the hardware SPI. I suppose I should just go order a board and give this a shot myself. EDIT: LCD and SD card boosterpacks ordered...I'll get to the bottom of this one way or another...
  16. Be careful that you don't overdrive the LEDs. Some of the pre-production boards we sent out to some of our third party partners were fried when they tried driving them too hard. I was in fact able to get the LED lighting application running inside of our RTOS (SYS/BIOS). I've got a slide deck and some source code. I'll try to get it cleaned up and posted this weekend.
  17. ...maybe I should have put a warning on the circuit board. The LEDs are rated for 50ma peak and we are driving them at 20ma I believe. Before we cost reduced this board it actually had LEDs that were rated for 350ma. Imagine staring at that!
  18. I did too, but I googled it and found the third party website. http://www.rapidqualitysystems.com/Products/CodeRocketEclipse
  19. Hi Todd, Good to see you over here on C2kcentral! I can't say I've every tried using it, but it looks like it would be a pretty cool tool. Thanks for the hint. Trey
  20. Yes, you can use the same CCS install for both. Its kinda annoying how they've done the licensing, but I have a fix for you. Go to help, Code Composer Studio Licensing Information. Somewhere in this dialog box you should find a way to switch the license you're using from the code size limited 430 version to the XDS100 version...why these are two separate license options is beyond me... I would tell you more specific steps, but because I'm on the TI network CCS licensing behaves differently for me.
  21. Replace your common directory with this Import the driverlib project from this directory Build the driverlib project Rebuild the SPI example with the code posted above The example should work now. f2802x_common.zip
  22. CorB, I solved the issues with the original example. It turns out the order in which the FIFO register bit fields are configured is important. To the best of my knowledge this isn't documented in the user guide for the SPI peripheral. If you replace the initialization code with the following code you should see the example start working. I'm glad you were able to get the LCD working and I think a good next step would be to try to get the LCD working using the actual SPI peripheral. Cheers! void spi_init() { SPI_reset(mySpi); SPI_enable(mySpi); // Reset on, rising edge, 16-b
  23. CorB, Were you able to get the LCD working? I took a look two weeks ago at this and it appears the SPI FIFOs will spit out a few characters of garbage if they are not initialized correctly. I'll try to come to a full understanding of the issue this week and provide a fix in the next controlSUITE release.
  24. It could work...I would be concerned about the debug interface. It should scale down in speed, so no problems with timing critical IO, but I'm worried about all those layers of drivers working correctly. If you are able to successfully access the host machines USB ports, it should work...albeit slowly.
×
×
  • Create New...