amykyta3

Its isolated enough to be safe. With both hot and neutral wires having a cap on them, it allows the circuit's DC component to float to match the chassis/person handling it. As long as the capacitors are small, they will not be able to transmit enough AC current through them to be able to do any damage. In fact, I'm quite sure the little USB wall-plug adapters for your cell phone use capacitive coupling the same way. The forum you linked did bring up a few good points, although a little bit of an overreaction. Probably want some higher-rated capacitors on the mains end. Also, the linked PDF do

@nuetron: Close, but that design will vary depending on the load. I would've linked you directly but this is a new account so I can't post URLs. Do a google search for "Make a Transformerless Power Supply - Bright Hub". It should be the top result. The last one on that page is the best since it electrically isolates the circuit from the mains. This one produces 12v that is somewhat regulated by the zener diode. I would then put a typical 3.3v linear regulator at the end to power the msp430.

Great to hear! I've been wanting to fully migrate to mspgcc for a while now. That was one of the things holding me back. I ended up avoiding the CALL/CALLA situation entirely by leaving that up to compiler and writing the body of the function using inline asm() statements. (ew.. i know, but it works). For example: uint16_t myfunction(uint16_t a, uint16_t { //For CCE, a:R12, b:R14, retval:R12 asm(...); asm(...); asm(...); asm(...); } Which seems to work fine on CCS and mspgcc (with different register assignments of course). Is there any reason this would not work based on compile

I am optimizing some code and I want to have a C function call an ASM function. (no problem here). Problem is that depending on compilation settings, the ASM function will be called using either a CALL instruction or CALLA. Is there any way to detect this at compile-time in a header file or similar so that the ASM function can have a matching RET or RETA instruction. Any mismatch would surely blow up the stack. I would like to make the code as portable as possible and work for any device. The MSP430X devices have #defines in the header such as __MSP430_HAS_MSP430XV2_CPU__ which indicate th