JVimes reacted to bluehash in 43oh vs E2E
I respectfully disagree. The interface is a little clumsy, yes, but there are a lot of intellectual people on there with a range of backgrounds from controllers/processors/analog/compiler chips. I do find alot of questions answered there. The good thing about E2E is that they have the people working at TI answer questions which is very assuring. If you know your way around e2e, it is a good place to ask questions.
43oh does not have the kind of restrictions that E2E has to take care off.. as they are a company and need to watch their every reply. They are much better than the st forums which is a total nightmare to navigate and filled with broken links.
JVimes reacted to ILAMtitan in Vetinari's Clock
I figured you guys might be interested in some of my tinkering with the Launchpad. Hopefully by putting a few of my projects up here it will also keep me accountable for finishing them.
This is one a cobbled together a few months ago. It's been up on the MCU projects page on E2E, so you might have already seen it: http://e2e.ti.com/group/microcontrollerprojects/m/msp430microcontrollerprojects/664670.aspx
The Vetinari clock is from a book series known as Discworld, where Lord Verinari has a clock in his waiting room which has an irregular tick. The idea of the clock is to add a sense of unease and anxiety to anyone in the waiting room since their brain doesn't filter out the ticks like a normal clock. Here's a video to get a better idea of the result. The tick is actually a lot louder in person.
To accomplish this task on a 430, we create an array of possible time frames to tick the clock, and parse through it at 4Hz. The array is 32 entries long, so it equates to 32 seconds in the real world. By randomly setting 32 of the elements high, we create a timing sequence. A high element will generate a tick of the clock. This means a second on the clock can be as little as 250ms, or as long as 24 seconds, and still keep accurate time. Check the attached software too see how it's all done; I did my best to comment it up. main.c
The clock coil is driven via an alternating polarity pulse. The easiest way to change a load's polarity with an MCU is using an h-bridge.
The schematic shown is a simple implementation using two NPN and two PNP transistors. I had the transistors and drive resistors laying around, so this part was easy to cobble together (along with the half used battery holder). It would be easy to use a single IO pin per side of the bridge, but the transistors fit better onto the launchpad, as shown in the image. To add the driving resistors in series, I cut a small gap in the traces, scrapped off the solder mask on either side to make pads, and put down a small SMA resistor. It's not pretty, but it works.
In the clock mechanism, there is a small control board with a crystal and epoxy glob IC that normally runs the clock. I just ripped that out and directly attached the coil to the h-bridge.
The resulting clock is actually more maddening than I expected in a quiet environment. By using 3V rather than the 1.5V that the original movement used, the ticks are much more pronounced and do an excellent job of ruining a person's calm.
JVimes reacted to rockets4kids in FET vs EEM
The use of the word "emulation" is archaic and is in no way appropriate to the way MCUs are used today. TI should have dropped the term a decade ago, as it serves only to confuse just about everyone who wasn't using microcontrollers well over ten years ago.
Historically, re-programmable memory was very expensive so most chips used either ROMs that were masked directly onto the chip or one time programmable memories. Even silicon was very expensive, so any debugging hardware at all was never included on the chips. Development and debugging was done on dedicated boards that that either implemented the processor with discrete components or emulated it with a more advanced processor. The program ROM was also typically emulated in RAM. Because these development systems were very complex and only produced in relatively small volumes, they were typically very expensive. Even at the very tail end of their use they still cost more than $1000.
However, new processes and technologies have made both FLASH memory and silicon cheap, and the cost to implement the hooks required to enable debugging on the chip itself add so little to the overall cost that just about all modern microcontrollers include them. The MSP430FET is merely a communications bridge between the host and the on-chip debug hardware.
JVimes reacted to roadrunner84 in FET vs EEM
Good question, I've never thought about it. The EEM is the part inside the controller that allows it to emulate code execution without having to flash the code in the flash memory. The FET is a programer/debugger, I doubt it will support actual emulation of the code inside itself, but rather communicate with the EEM in the target device to present a full emulation to the user.
JVimes reacted to vladn in Development kit terminology (newbie question)
Hi everyone. I am also new to the MSP430 and have few questions related to this topic.
(I have an engineering background and quite faimilar with coding and HW, but the last time I did micro work was >10yrs ago).
I've got a MSP-EXP430G2 Launchpad and installed the CCS. I can blink LEDs and do other simple stuff.
I am a bit confused on the Launchpad functionality though -
1. What exactly happens when I run debug (F11) in CCS ? Does the program run on the socketed device or in the emulator part ?
2. Does run->debug actually program the flash memory on the socketed device ?
2.a If "no" can I use the CCS+Launchpad to flash the socketed device when finished debugging (and use it outside of the launcpad) ?
2.b If "yes" how can avoid flashing the device every time I debug something ?
I apologise for dummy (and possibly repeated) questions. If you can point me to the a relevant thread or a TI document I would much appreciate the help !
JVimes reacted to roadrunner84 in Development kit terminology (newbie question)
debugger/programmer/fet all refer to the same thing, though the fet is a specific model/family.
booster (pack)/shield/add-on board/expansion board all refer to the same concept, verify that your pack/board is "launchpad compatible"
a breakout board refers to a chip that's so difficult to handle for experiments that a simple board has been designed around them to ease said experiments.
JVimes reacted to cde in Development kit terminology (newbie question)
These are quite interconnected in the MSP Launchpad world. A Debugger allows you to debug your code, through changing memory values and breakpoints. A Programmer allows you to program the chip using usb on one side, and SpyBiWire/Jtag on the other (a protocol adaptor). A FET, Flash Emulation Tool, allows a microcontroller to run code on memory outside of it's own memory, through the debugger/programmer setup.
A breakout board is often a blank pcb that an IC can be soldered to, changing it's package from one form to another, with all pins broken out. You find these for SMD chips alot. Sometimes it comes with the smd chip used, and sometimes has some needed parts, like a regulator or passive components.
Evaluation Kit is a board or module designed to show off the features of a chip. An experimenter board is really just marketing, or targeted to a education crowd [look at the neat things you can do] ( vs business crowd [look at the useful/purposeful things you can do]). A starter kit is a set of parts put together as a "these will get you started" method. A development board is a combination of an evaluation kit and experimenter board, targeted towards implementing final products.
The reason for that is that the F5529 is a high pin count thin/small smd chip, not a giant through hole chip. Its not practical for most experimenter/evaluation boards to have removable smd chips, and boards that do have sockets for those high pin count smd parts are expensive, because the sockets are expensive. BUT that does not mean you can't use the F5529 board to program other f5529s. They have jumpers that can be removed, and using a cable, can be connected to your own pcbs or break out boards, for in circuit programming.
JVimes reacted to spirilis in Development kit terminology (newbie question)
The F5529 launchpad is demonstrating the way of the future...
It's just expensive I'm guessing to produce a package that's removable that also happens to have 80 pins. For a microcontroller, it's impractical too. These things don't get swapped around much "in the real world".
The F5529 launchpad works fabulously as a programmer of external circuits. Incorporate the chip (or any other MSP430 for that matter) into your final board, and use jumper wires to attach the necessary FET pins on the F5529 launchpad to your target board (note they all have jumpers/shunts so you can disconnect the FET/debugger from the F5529 chip itself and use the FET to program other boards).