semicolo

That is a very nice feature, even just the trick to refresh the expressions values in realtime is great.

Great work guys. I think you've asked before if the previous version is displaying an update notification. Version 0101E0013 is not showing that an update is available on windows 8 64bits. Edit: But maybe that's because of the firewall at work, I'll try to remember testing it at home. Edit2: No notification at home either.

The default AT commands mode communication speed the modules come with is 57600/115200 bps, maybe if you run the code directly on the micro you can get a better speed.

The serial monitor is not supposed to print what you send. You cannot debug with energia, you have to use ti's code composer studio. Now you can load your energia sketches in CCS by the way. Send a picture of your setup so we can see if something is wrong with your jumpers.

I don't have a 1.3 board but I don't see why you'd need to connect anything, the microcontroller pins should be connected to both the header and jumper field. If you connected a jumper between RXD and TXD, that explains why you see an echo of what you type in the serial monitor.

This works on my launchpad: void setup() { Serial.begin(9600); } void loop() { if (Serial.available()) { long frequency = Serial.parseInt(); Serial.println(frequency); } } when I type a number, say 1234 in the serial monitor, the launchpad reads it in the frequency variable and prints it back to the serial monitor I find it strange that you see data in the serial monitor when your code doesn't send anything. Again try the Ascii table example you should see a bunch of lines when you hit reset on the launchpad and try the simpler code above to test reading in a variable.

I think the port numbers are mixed, try Serial2 or 3 or 4...

You have to initialize the hardware serial in the setup function: Serial.begin(9600); (9600 bps is the maximum speed using the launchpad usb serial) then in the loop wait for serial data and when available use Serial.parseInt() something like void loop() { if (Serial.available()) { long frequency = Serial.parseInt(); sendFrequency(frequency); } } Have a look at the Communications examples (in File/Examples/4.Communication) Run the ASCIITable example if you didn't already to make sure the jumpers on the launchpad are set correct, that's a common mistake for beginners.

What project are you talking about? Please add your code or a reference to it.

Just tried with energia 12, it works. I suppose that com3 goes away from the port list when you unplug the board? Edit: Works with energia 13 too.

I just checked the serial code in energia, you can't do it directly. I suppose you could play with the registers after doing a serial.begin to enable the parity bit but I don't know if this would conflict with the interrupt routines.

If your question is how to enable parity and check it, I don't think there's anything in energia to make this happen (or the documentation is outdated) If you don't need all 8 bits, you could use the msb as a parity bit and implement it in software.

I have a few usb2serial cables based on the PL-2303X that is not supported anymore since windows 8 (you can actually install windows 7 drivers to make them work but it's a hassle). Never had a problem with these cables. Seems like other chips than PL-2303HXA and PL-2303X should have working drivers. I also tried high speed serial transfers with a stellaris launchpad once, I don't remember when it stopped being reliable but It could go up to a few Mbps (testing wasn't really scientific, the launchpad was just sending the ascii table over and over and I looked at some strange or out of plac

If I'm not mistaken the F5529 has an ADC_12_A but it doesn't seem to be handled in the energia sources, there's ADC10, ADC10_B, ADC12_PLUS and ADC12_B. What do you think @@energia?

I don't have a F5529,it looks like it's reading the 2.5V reference instead of half_VCC, I'll try to get the datasheet and have a look if you don't figure it out first.