greeeg

I noticed people here love to use nokia B/W screens. If anyone wanted to see these on an oled. From top to bottom (colour) -MICR font by RobG (red) -12x16 font by RobG (Purple) -8x12 by RobG (light blue) -10x16 font by RobG (blue) -6x8 font by oPossum (green) -6x8 font by RobG (yellow) -8x8 font by oPossum (purple) -4x6 font by greeeg (white) Now I know why you use B/W screens. OLEDs are hard to photograph.

The classic Apple2 font is one I used to use alot, but I can't find any of my font tables for it :/ Here is a link for the truetype: http://www.kreativekorp.com/software/fonts/apple2.shtml I'd also like to ask how you guys make your fonts, scripts? by hand? I personally have done a few by hand, but also have made scripts ( processing, perl ) that take an image of characters and create a font array in C.

This is pretty cool but I'm not really sure how necessary it is. The SOIC package is pretty much identical in size to a 14pin TSSOP package. So you can't complain about running out of I/O's because there are alternatives available. Finally not being a prototype friendly package doesn't really mean much for MSP, because the CPUs are all identical (well all the value lines are) Just develop with a DIP packaged one, make sure your code fits in the required flash space and you can flash these devices with your identical code.

This is one I use when code space is tight. It can fit into the top part of infomem It's a 3x5 font, Dead simple to decode. take example '!' == font[0] == 0x4904 == 0100100100000100 break that up: 010 010 010 000 010 0 It might be clearer arranged like this: 010 010 010 000 010 I waste 1 bit per character :cry: const unsigned int font[] = { 0x4904, 0xb400, 0xbefa, 0x5d74, 0x3558, 0x71de, 0x4800, 0x5244, 0x4494, 0x1550, 0x0ba0, 0x0024, 0x0380, 0x0004, 0x2548, 0x56d4, 0x592e, 0xc54e, 0xc51c, 0xb792, 0xf31c, 0xf3de, 0xe524, 0xf7de, 0xf79e, 0x0820, 0x0824, 0x2a22,

It does look really nice. ebay has them at $6.30 a piece if you buy 2. Here is specs: http://osddisplays.com/productDetails.php?pid=10 Not sure how much OSD would charge for a handful.

I put some of my own music on it. MP3 @ 192kb/s and when it moves from 1 track to the next it locks up. Works fine if I stop the song move to the next and play it. When it locks up all the LEDs flash @ ~1Hz a couple of times. Then a few seconds later it's doing the startup LED cycle and the MSP resets the DSP. Related I've already set it up to advertise for 43oh.com

I wasn't sure to put this in here or in projects. I've been using SD/MMC cards in my projects as a media for bootloading from. I thought it would be great if the systems I've been working with had USB as removing and replacing SD cards is a timely task when you are developing code. So I designed this board to use with the USB MSP430 devices. It's sole purpose is to connect the USB and breakout all the IO pins of a difficult to breadboard package. But I added some niceties to it, to aid in development. 3 buttons 5 LEDs 1 Micro SD slot. A reset and bootloader button. External power

This wouldn't be too hard to create. The biggest hassle would be trying to add IO connections, a specialized small connector to a larger board would increase cost and make it more fragile. but OLED screens are tiny and MSPs are tiny. they could both easily be connected together. Here is something I made ages ago. it's a AVR XMEGA on a PCB behind a small 128x64 pixel OLED display

Nice work. In the video that temperature seemed to jump around quite a bit, thought of adding a SW filter to smooth it out? Or maybe slow the update rate of the temperature?

I ordered mine on the 4th. Came today. Now I know it's not a finished product, but I was only using mine for about 30 minutes and it's already locked up twice and has spent a few seconds rebooting itself. It does feel a bit weird to me to use a MSP430 as the master and the DSP as the slave. If you wanted to add captouch just use an MSP430 as a slave to the DSP All in all it's a nice addition and will be interesting to see what people come up with. I would personally like the source code for the DSP so I could add FLAC/OGG/WMA support which the DSP is capable off, just not impleme

Hmm I haven't done much with cap buttons except for buy a cap-touch booster pack. But they might operate through the fabricated case. As for power consumption it shouldn't add much more to a MSP running as an RTC. Here is alot of information on the pinosc feature which would be the easiest way to add cap sensing to your watch: http://processors.wiki.ti.com/index.php/MSP430_Low_Cost_PinOsc_Capacitive_Touch_Overview It will knock out 1 of your timers but you can use a 2nd timekeeping timer for interval measurement and for timekeeping. Note there are some useful PDFs at the end of tha

Wow that looks really nice. I was thinking of doing something similar with some nokia 1201 displays I have around the place. You may be able to utilize capacitive buttons, Not sure how well they would work on a watch. If you want an idea for a new revision a buzzer would add a handful of functionality, feed back for alarms, timers, button presses etc.

I think ti app notes say that 47k max should be used. 50k is pretty close so it SHOULD work, but if your still having issues try decreasing it a bit down to around 20k or so. You say you are measuring voltage of the batteries, I'm assuming these are limited to 2.4v as well (via voltage dividers). Are you sure you have set up the ADC properly with either VCC or 2.5v as the reference, if 1.5v is available and selected for reference that may be an issue.

I've been using the erase, load. erase throws some error (which according to mailing list is normal...) So here is the interesting thing. I'm programming in assembly using naken430asm, so I moved my program into the chips RAM .org 0x1c00. Programed fine except the reset word located in 0xfffe :/ So I changed PC manually, "set PC 0x1c00" then "run" program runs perfectly debug LEDs I set up in my program are flashing away. So now I still have 2 problems, the ezFET on the faunchpad is dead (won't enumerate), and I can't write to the FRAM. I've heard blowing a virtual fuse can hap

Nice looking board man. :thumbup: Makes me want to make one for the cc430's and F2274's I have sitting around. Did you ever start anything on the cc430 front? if not I might take a crack at it...

Some extra info. Just measured the voltage. it's 3.65v would that extra 0.05v over the recommend be enough to damage the F1612 in the ezFET? maybe even the FR5739 itself? I guess I was just unlucky with the (assumed) +-5% tolerance resisters on the voltage regulator, guess one was +5% and the other -5% :/

So I bought one of these neat fram boards late last year, thinking wow this will be neat to experiment with. I mean have you seen all those internal peripherals. :shock: Anyway long story short I hadn't touched it until today, when I had a neat idea that I wanted to test out. So I wrote up some code and plugged it in then typed "make all prog" like usual. This was the response from mspdebug MSPDebug version 0.18 - debugging tool for MSP430 MCUs usbutil: unable to find a device matching 0451:f432 WHAAA! a bit puzzeled I thought they might have had a different firmware

Be careful. Most MSP devices only contain 1 base timer module. Within that 1 timer module there may be several CCM's (Capture/compare modules) each CCM can cause an interrupt when the TAR (timer value) matches the CCR (Capture compare register) If you tell us what IC you are using I can clarify more, but if your device has got a timerB module you should be able to set it up identically to your timerA module just replace the A's with B's

This should be extremely handy to implement on the chronos watch. IMHO simpliciti seems better suited to multi node sensor networks rather than a watch, especially when all you want to do is talk to a single access point to sync the time, simpliciti seems over kill and takes up alot of code space.

I don't think the LP would work as a BSL flasher by itself. As the BSL interface requires 4 pins. the two serial pins RX,TX and then two pins connected to RST and TEST to perform the proper BSL entry signals. However a simple BSL flasher from a simple FTDI 232 usb->UART breakout board green wiring the CTS and DTR pins out to a header to connect to RST and TEST. If you have one of these breakout boards on had this will be an easy option. Otherwise... Since those signals need only be applied once to enter BSL mode, one could easily place a G series device to enter BSL mode on the target

Ordered mine 19/01/2012. Received them today (24/01/2012) all 3 are rev 1.5 boards. I kind of like how the headers are soldered on by default. I wonder how much extra that cost's them... Also they are a lot more shiny than the original 1.4 board I bought back in August 2010, they had alot of kind of powdery reside, likely from the cleaning process used. Interesting how they are not re-enforcing the front two USB tabs like on the older ones, I wonder if they decided it wasn't worth it. Or if they're strong enough as is.

That is the site that I first heard of powering a micro from it's I/O pins. This is how I cut my IC. I have left the programming interface intact. I'm not exactly sure if you could cut one more row of pins deep, of whether then you'd hit the silicon...I'm pretty sure it's a fairly tiny die in these parts, maybe only 1 pin spacing wide...I have a busted TSSOP package f2013 device I'll check later on. power can be applied to any I/O pin except XOUT, Due to the external oscillator control circuitry. but this pin can be used as general purpose I/O once P2SEL = 0; This leaves 2 I/O

Soic with custom made dip adaptor (reset and decoupling caps on top). Might be bigger height wise, but will be the size you want. Power + ground + 6 i/o? This is more what I want I'm using 2 I/O pins for input power via the internal latching diodes. this seems to work well and I've been successful in programming, debugging, and outputting to a small buzzer using TA0.1 on one of the two remaining I/O pins. What is the actual need for a 6 pin MSP micro controller? well I don't know. But it was fun to find out that it CAN be done.

I'll be trying to update my blog regularly. Most of the stuff on it is about MSP430. http://blog.greg.so

Interesting. Since the die is in the center of these devices. (I checked on one of my G2211 ICs) Cutting the top pins would create an even smaller package. Of course you would remove the voltage input Pins...I wonder how good the clamping diodes are on the IO pins are Further experiment time?