Jump to content
43oh

TI_Trey

Members
  • Content Count

    225
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by TI_Trey

  1. I can't say with 100% certainty, but I believe this is just a documentation error on the page. The limit should be removed in the software itself. I believe there is a bug filed to fix the wording on that page. Also of note, all of the APIs are tested and working (except for i2c). Things are looking good for a beta release near the end of the month!
  2. I forgot something... This device has an errata for the ADC. Basically the first conversion in a group of conversion can give bad data. Whenever you do a sample, you should do a dummy sample with another SOC before sampling the desired signal. Look at how this is done in the adc_soc example. The errata is here: http://www.ti.com/lit/er/sprz292j/sprz292j.pdf
  3. The graph properties look ok. An antenna won't really help much on its own. The problem here is the strength with which the signal is driven into the ADC. To accurately sample a signal the ADC needs to be driven with some amount of current. With your current setup, current must capacitively couple from the mains power in the walls through the air into the board. Only a very small amount of current will reach the ADC. If you insert a buffer (an opamp would be perfect), its input will have a high impedance and will be able to pick up the 50Hz signal and its output will have a low impedance
  4. Quick Update on Energia Support: More good news! I just finished adding serial programming support for the C2000 LaunchPad to Energia. Its slow as molasses, but it works and its lightweight. Also of note, the C2000 compiler no longer has a size restriction!!! I'm hoping we'll have a beta build with C2000 support later this month. No guarantees though, as I'm doing this in my free time.
  5. Kayla, It looks like it is working to me. The 50Hz mains power is capcitively coupling into the ADC input, therefore you see a 50Hz sine wave in the graph window. The noise on the sin wave is due to the fact that this signal isn't really being driven with any strength. If you were to pick up the signal with an antenna and then buffer it with an opamp before sampling, I would venture to say that the sin wave would be much more ideal.
  6. The controlCARDs are nice ways of evaluating the different devices in your system. We sell the matching DIMM connectors so you can easily integrate those in a test board. Also, don't spend big bucks on a debugger. The XDS100v2 (which is already on most of the controlCARDs) will do just about everything you could want and is <$100.
  7. Mike, You're absolutely right to question the friggin ARM's taking over. They are great general purpose devices, but the C2000 devices are tailored for real time control applications. The core CPU in all of our devices is the C28x. I often refer to it as a mini-DSP because it has MAC instructions as well as a Harvard architecture bus, that said we call it an MCU because it is just as easy to use. Our higher end devices have floating point units, DMA, and extensions to the instruction set (through the use of accelerators) which speed up certain math operations. As a group, C2000 is sol
  8. Yes, but you need to SCI peripherals. The LaunchPad only has one SCI on it. This is why I suggested writing a software based serial port. We are working on one for Energia, and its supposed to be working (but I have not personally tested it). I'll go ahead and post it and you can play with it if you'd like. ...ok, I can't upload because I've "exceeded my allocated disk space for attachments"....bluehash can you help me with that? For now here is the code for the header file and source: TimerSerial.h /* TimerSerial.h - Timer based serial library for MSP430 Copyright (c) 2012 Ro
  9. Hahahha, nothing more that I would like in the world! Right now it looks like we'll be able to support both Windows and Linux with the closed compiler. If anyone is coming to MakerFaire, I'll be there with a few of my toys and some type (suggestions?) of Energia demo running on the C2000 LaunchPad!
  10. I'm excited to say that at 11am Central time today, the first successful build of a C2000 project took place within Energia!
  11. No Problem, always happy to help out. Sorry no one got to your e2e post sooner. I'll give Devin a poke in the ribs Your work statement is correct, but I'm not aware of any PeripheralAddress_ASM.h...where did you find this? This is probably just the indexer in CCS being silly. It basically goes and parses everything in a project so that it can highlight and provide assistance on known symbols. In my experience this piece of software has problems, so I take it with a grain of salt. Try compiling, if you don't get compile errors you're good. Remember you may need to EALLOW to
  12. I just confirmed with the guy who brought up the ramp generator, this feature is here and was documented after the part was released. Everything above is true.
  13. Toby, I'm not an expert on the comparators, but I'll do my best to answer your question. I too have been unable to find these registers in the normal header file structures, but I was able to find the DACVAL register in the comparator structures. I believe what is going on here is that the ramp generator was a feature that was not documented for a long while. Someone eventually got time to test and document this feature and it was probably added to the device after the device was released. While it was added in the documentation, the necessary software updates probably got lost and
  14. Indeed it is! I've been able to get some resources to use to implement the wiring APIs. We are making good progress and are hoping to have something to show around MakerFaire. The bad news is that we still won't have Mac OS support. The only option for this is for us to use the TI tools.
  15. Well, I'm actually working on arduino support for this board, so hold tight and in a month or two I should have something a little easier to use.
  16. ...well that looks awefully like a motor driver for a quadcopter...Nice work! For a sensored BLDC application we are certainly overkill, but the beauty of our device is that we have the hardware and software to do sensorless control.
  17. Hi! Yes, there are differences between these files. The f2802x_common directory contains drivers and some helper files like linker command files. The F2802x_headers directory contains header files that can be used to access the peripherals using structures. You shouldn't need to use anything in the GEL directories. CCS will automatically take care of this. adc.h is not identical to F2802x_adc.h. adc.h is a header file for the driver library while f2802x_adc.h is header for some legacy driver code. Try starting out by importing some of the examples and figuring out how they
  18. Anguel, Yes you are correct. Those drivers have been around for several years now.
  19. Anguel, You're absolutely right...our memory is 16 bits wide and in some applications this wastes space. We are not really a general purpose micro-controller though. The C2000 family of devices are more like mini DSPs and as such they are architected to perform best when doing complex math/control algorithms. Like I said these devices really aren't designed for string manipulation, but you certainly could hack something together (as you suggested) to try to save some space. I, however, do not know of a good way to do this currently in an automated fashion. Trey
  20. Anguel, Sorry for my slow reply, I've been busy the last few days. Sometimes the real time debug mode can cause the debug interface to get a little weird. I've had pretty good luck with it as long as I don't try to load code in while the real time debug mode is enabled. Otherwise it will behave like you've described above. Just turn off real time debug mode before loading code. Trey
  21. Anguel, Perhaps untested is not the right word...I think incomplete better describes the state of the I2c driver. The other drivers are in fact tested and working, but are relatively new. As with any new software we expect to find some bugs. Please let me know if you find anything that I can improve/fix. The C2000 LaunchPad is my baby (so to speak), and I do everything I can to support and improve support for it. Other than the lack of a complete I2c driver, what do you find unprofessional about the C2000 LaunchPad.
  22. You are somewhat correct. LaunchPad and F2802x software are basically the same. There are two sets of software in there, one new and one old. The old stuff is prefixed with F2802x_XXX.c. The new drivers are simply the module name.c. All these drivers reside in the common folder. The new driver (i.e. i2c.c) is in fact untested. I was working to get this done before release but this is one of the items that slipped through the cracks.
  23. Anguel, The driver in the F2802x_i2c.c file are limited at best, but they do work. This isn't really a driver but more of a GPIO setup function. The other i2c file is a driver, but it is not complete or fully tested. I was the only one developing all the LaunchPad hardware and software and as such I ran out of time before release and haven't had a chance to revisit it.
  24. Anguel, Good question! You are correct the LaunchPad has 1 SCI (UART) 1 SPI and 1 I2c. SCI can either be connected to the USB/UART present on the FTDI device (using the big switch) or to an external device through the header pins. You are also correct that SPI and I2c are connected to the same pins. This was done to maintain compatibility with the MSP430 LaunchPad. They can however both be used simultaneously. You'll notice in the schematic there are a set of jumpers before the actual pins these functions are connected to. The footprint of these jumpers is an 0402 resistor with a trac
  25. Sam, Connecting at J3 should be ok if the jumpers JP1 and JP2 are disconnected. I wonder if the battery is maybe a little low on charge and doesn't have enough power to supply the device. Your motor controller's 5V output might be ok to use. It just depends on its power output. You ought to be able to look up in its datasheet how much current it can source out of that pin. If that value is 200+ mA you ought to be able to use this to power the board. You can connect 5V at J5.1 and ground wherever. JP1 JP2 and JP3 will need to be jumpered. Try looking at the schematic of the LaunchPad
×
×
  • Create New...