oPossum

Testing with Windows 7 64 bit and HyperTerminal PE 6.3 using a 'scope to determine bit rate by measuring time between falling edges of ASCII character 'x'. Bit rates tested: 110, 300, 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200 9600 bps 4800 bps 2400 bps 1200bps All other tested bit rates did not change the bit rate - it was the same as the last supported bit rate. It was often necessary to open the port several times to get the bit rate to change. I don't know if this a bug with the TI firmware or the Windows CDC ACM driver.

54xx, 55xx, 56xx, and 66xx series can be programmed with the Launchpad. 54xx have up to 16k RAM, up to 256k Flash, and run at up to 25 MHz 56xx and 66xx have USB, up to 16k RAM, up to 256k Flash and up to 20 MHz 55xx have USB, up to 10k RAM, up to 128k Flash and up to 25 MHz

Where did you get the BOB for the flex cable?

Concurrent drive of 3 steppers This is for "smart" controllers with step/direction inputs, but it could easily be adapted for "dumb" H-Bridge controllers.

http://search.digikey.com/us/en/cat/sta ... materials/ 4" x 6" $6.63 / 100 http://search.digikey.com/us/en/product ... -ND/299788 5" x 8" $10.50 / 100 http://search.digikey.com/us/en/product ... -ND/299789

void delaySec(unsigned n) { do __delay_cycles(1000000); while(--n); } Your code does not work because i, j, & k are not declared volatile, so the compiler removes the empty for() loops.

Grid-Style PC Board with 371 Holes

A counter has uniform distribution, but is not random. The order of the numbers isn't really important. A typical PRNG - LFSR for example - has a cycle that repeats.

It would be the same general pinout. The LP has power, reset, test, P1 and P2 on the 20 pins. The Flip Board would have... Top Board: power, reset, test, P3 and P4 Bottom Board: power, reset, P1 and P2 Side Board: power, reset, P5 and P8 XT1 and XT2 do not share any pins with any boards, so both LF and HF crystals could be used without sacrifice of any GPIO.

Oh, it wasn't clear that there are transistor on the bottom too.

Dual Half Bridge ??? That is unusual terminology. H-Bridge usually means "full" bridge. So this would be a single H-Bridge.

To ensure the pull up resistor remains a pull up and is not changed to pull down.... P1OUT = BIT3 | dice_values[counter]; or... P1OUT = (P1OUT & (BIT0 | BIT1 | BIT2 | BIT3)) | dice_values[counter]; or... P1OUT = (P1OUT & ~(BIT4 | BIT5 | BIT6 | BIT7)) | dice_values[counter];

FET-Pro430 programming software for Texas Instruments MSP430 microcontrollers

Here is a crazy idea I had - looking for feedback. This is a small development board that can use up to three Launchpad Boosters concurrently. It has nine 1 x 10 pin headers. Two are on the bottom, and carry the same signals as two on the top. A 1 x 6 pin header is used for program/debug and power. (click images to make scroll bars go away) The "Flying Solo" single booster configuration. The headers surrounding the booster board allow access to I/O lines not used by the booster. The "Flip Board" configuration. One booster is on top of the dev board (green) and the other i

You are missing a 's' in the ISR - dice_values

You can make the ISR much faster by not using the modulus operator (%) - it is rather slow. Make the sine table a size that is a power of 2 (32, 64, 128, 256, 512, etc...) and then just mask off the needed number of lower bits. For example a sine table of 256 entries would use a mask of 0x00FF (0000000011111111 binary). That will limit the table index to values of 0 to 255 - just like using % 256. A smart C compiler may optimize modulus to the power of 2 to be a mask operation, but there is no guarantee. To get a cosine value, just add 1/4 of the table size before masking. Only one table i

Put it outside of all the functions. #include #include //#include void configureClocks(); // Global variables volatile unsigned int i; // volatile to prevent optimization const int dice_values[] = { 0, 16, 32, 48, 96, 112, 224 }; // const to prevent change int counter; void main(void) { WDTCTL = WDTPW + WDTHOLD; // Stop watchdog timer configureClocks(); int operator = 1; counter = 1; ....

I am currently using a 5418A because it has 16K RAM and runs at 25 MHz (good for VGA). The code is mostly C, so the amount of flash required depends upon what functions are used. It may not all fit in a G series chip, but a useful subset certainly would. I think the library could be adapted to use SPI/IIC RAM with SPI/IIC LCD. Most of the drawing functions call pixel set/clear/xor functions, so making those functions work with external RAM would support everything except bitmaps. I will try to add support to any hardware that is provided to me. I expect OLED to have much better respons

I got this working with the Nokia 5110 LCD. Added support for vertical frame buffers so more output devices can be supported. Currently works with NTSC, PAL, VGA, and Nokia 5110. Now has vector font in addition to bitmap font. Still have some work to do before code is ready to release. The 5110 is a passive matrix LCD, so the response time and contrast are not very good. Animation really reveals the weaknesses of this type of display. The response time of a pixel seems to be influenced by the state of adjacent pixels.

This is a method to measure the DCO frequency by timing serial data. The ASCII character 'x' has two falling edges that are 8 bit times apart. There are also two 4 bit times from falling to rising and rising to falling. At 9600 bps the time between edges will be 833.33 us. Counting the number of DCO clock ticks that occur between the falling clock edges will allow the DCO frequency to be calculated. The stored DCO calibrations are shown and then frequency measurement begins. Each time the 'x' character is sent a line of info will be displayed. RSEL - Range SELect - the lower f

I think they may have greatly underestimated the difficulty of porting to MSP430. I suspect the MSP430 version will probably not work with most G series chips. "Soon" may become many years.

You can use an oscillator module like this. Not supported by TI, but it works. Code to enable the external osc input would be the same as this.

What MCU? The G series can't use high frequency xtal, only 32 kHz. They will work with an oscillator module, but that is not a supported feature.

Tie RST to Vcc if you don't need to allow SBW programming.