hvontres

Just found 100 20 pin headders for $5: http://www.goldmine-elec-products.com/prodinfo.asp?number=G19546 Perfect for mounting boosterpacks to the bottom of the launchpad

Well, for the original launchpad, the mapping from Processor to pins is 1:1 As stated, this could be done for the newer ones as well. I might work on one for the Tiva C later this weekend. I just happened to be working on a MSP design and thought I'd share the concept.

I played with it a little before, but it seems very bloated and I am not sure it handles multiplexed pins very well. This sheet is intended as an early brain-storming tool where you can very quickly move things around or see why that cool widget you were just going to code up is just not going to work with the parts you have around It seems that Grace is designed for a much later stage in the design process, and at that point it might be useful, but I'll have to try it some more first.

I have attached a simple spreadsheet I am using to plan out how to use the resources on a 430g2553 for a project. It is simply all of the functions for each pin in a seprate cell with a symbolic representation of the chip in the center. The color coding is completely up the the user. This way one can try to make decisions on which peripheral can be used and how it might need to be shared by other functions. I hope this helps The .zip file has both a OpenOffice and an excel version, since I couldn't attache the sheets directly 430G2553_pin_plan.zip

I realize this is kind of an old thread, but I finally got around to re-organizing my space in the garage. Here is the Before Picture, kind of my Bob Pease Memorial Shrine on a desk: Here is the new improved Setup: Note, I have not moved over all of the parts and tools from the old pile yet. I am hoping to keep most of my stuff in the big black cabinet. Most of the stuff here is surplus stuff from work. We are moving to a smaller building, so I scored the ESD safe bench, the cabinet, the two standard monitors, the chair and the magnifier. The scope I got off of Ebay for ~

A DC motor (either brushed or brushless) will need some kind of feed back to control position. With a stepper, the encoder can be used for servo like control, or it can be used to detect missed steps after the motion is done. This way, the motor is run in open loop and if there were any missing steps during the move, you could command a couple of extra steps at the end. With a stepper, you are more likely to loose steps at higher speeds, since motor torque falls off pretty rapidly. Having worked around servo systems for the last 18 years, I would not reccomend them for the uninitiated. Pro

I would suggest a shaft encoder, especially once the new Tiva Launch pads get out. That one will have TWO quadarature counters on board, so interfacing to the encoder should be very simple. As far as controlling the position of a Hydraulic cylinder, you might be better off getting your feedback from the rod itself. One way that I played with years ago while working on the animation system for a Rose Parade Float (http://www.csupomona.edu/~library/specialcollections/rosefloat/floatimages/1993photo.html) is to use a 10 turn pot with a torstion spring, a large wheel and some steel cable. As the r

Until then, try using ' spi' or ' i2c' as a workaround

UPDATE: I just posted the hardware docs on Github (https://github.com/hvontres/LCD-Controller/tree/master/Hardware/LCD%20Driver) The project was done using the latest snapshot of kicad. One modification that is not shown in the current pdf documents was to remove C6. It seemed to be causing a nasty 20 Hz ripple in the -27 Bias supply that would show up as a 20Hz flicker in the display. I also found a couple of drill holes were a bit small on the first prototype. I will try to get a new version of the gerbers out soon.

There may be licensing issues. The peripheral driver is licensed under a BSD license, but the Grlib and USBlib fall under the "Ti Clickwrap license". this license includes the following clause: This might be keeping that library out of Energia.

well, my two xl120G's are here.... Ship date for my Tiva order is 7/3/2013 so it looks like I'll have fun over the 4th of July weekend

Well, I think I know what happened here... you need to add the Tiva board to your wishlist and then order it. I think I saw the picture at the bottom of the page and added it to the cart not realizing that that was a link to the old EK120XL... so now what will I do with two more

Hmm, that would suck... I just placed a pre-order for two in order to get the Encoder and PWM features...

Actually the display is really dumb. The MSP is in charge of doing the refresh and fetching the data. The Stellaris mostly supplies the memory needed to hold the display data. The Driver chips on the display have enough memory to hold one LINE of data at a time. So the max refresh rate is limited by how fast the MSP can process the data. This display was originaly meant to be driven by something like a SED1335 controller chip. But that would have been too easy By having the MSP handle all of the display timing and refresh, the Stellaris only needs to use ~4% CPU time to manage the display

Also, one other thing to keep in mind is that one of the configurations for the SPI pins confilicts with the pins used for the on-board RGB LED. So in order to use all four SPI ports, you would need to remove some 0-ohm resistors.

Nope, no memory on the LCD, other than the shift registers in the controllers. The chips on the controller are a MSP4302542 to handle the data transfers between the stellaris and the lcd, a 74HCT245 used as a level shifter from 3.3V to 5V, a 4N29 isolator to turn the display on and off and a Max774 to supply the bias voltage. The framebuffer for the lcd is actually in the stellaris. https://github.com/hvontres/LCD-Controller/blob/master/Docs/Controller%20Design.pdf has a more detailed description on how this thing works

I would like to submit the folowing project for the POTM contest: http://forum.stellarisiti.com/topic/484-lcd-controller-using-stellaris-and-msp430/

This project attempts to control a surplus LCD (http://www.goldmine-elec-products.com/prodinfo.asp?number=G18246) using a MSP430 and the Stellaris Launchpad. Brief Description: This project is designed to run a 320x240 monochrome LCD with minimal CPU overhead. A seprate controller board supplies the VEE for the display, controls the Backlight and has a MSP430G2542 running as a SPI Master. The MSP also controls the clocks for moving the data to the display. The Stellaris side sets up a 1BPP offscreen display for Grlib and also sets up a UDMA job that transfers the display buffer to th

What is the input capacitance for your scope probes? For fast square waves, I built one of these: http://koti.mbnet.fi/jahonen/Electronics/DIY%201k%20probe/ For this to work, your scope needs to either have a 50 Ohm input mode or you need to use an inline 50 Ohm terminator. This will give you ~1Ghz response for only a couple of $

To get the CPU to 80 Mhz, you need to set the divisor to 2.5: SysCtlClockSet(SYSCTL_SYSDIV_2_5 | SYSCTL_USE_PLL | SYSCTL_OSC_MAIN |SYSCTL_XTAL_16MHZ); It looks like the default is 12.5 Mhz (see Table 5-4 in the datasheet)

Thanks for pointing that out... That will give me some time to get this thing cleaned up some...

Hmmm, almost the end of the month and only one entry..... Is Dec 31st the last day to add a post? My project is getting closer, but I still have some HW issues, and so far I have only gotten it to the proto board stage (no real PCB)

Actually, driverlib and the include files are now BSD licensed. The problem comes with grlib,usblib and most importantly ALL of the example code provided by ti, including the startup code. So if you want to be able to post the project, one cannot use the Ti examples as a starting point.

Just a heads up to people considering using Stellarisware for their Open Projects (like Project of the Month): While drivelib is now released under a BSD licence, the other libraries and all of the examples fall under the original Stellarisware Licence which includes this rather ominous passage: This seems to preclude us from posting modified Ti-Example code on this board. While I can see why TI wants to protect the library code, it would have been nice to use a less restrictive license for the Examples.