energia 485 Posted March 20, 2014 Share Posted March 20, 2014 I am happy to announce that release 0101E0012 just went up on energia.nu. I want to thank everybody for their support and contributions. Energia would not have been possible without such an awesome community! Details of the release can be found on http://energia.nu spirilis, abecedarian, Rei Vilo and 1 other 4 Quote Link to post Share on other sites
bluehash 1,581 Posted March 20, 2014 Share Posted March 20, 2014 MSP430 Energia Support- Go here. Tiva-C/Stellaris Energia Support- Go here/this thread. Quote Link to post Share on other sites
spirilis 1,265 Posted March 20, 2014 Share Posted March 20, 2014 Yay! This also has the fully fixed HardwareSerial for Tiva that lets you custom-declare buffer size. Run .setBufferSize(unsigned long txsize, unsigned long rxsize) before .begin() to get a custom-sized buffer- Serial.setBufferSize(256, 2048); // TX buffer 256b, RX buffer 2KB Serial.begin(115200); Default for both is 256b if not specified. Quote Link to post Share on other sites
abecedarian 330 Posted March 20, 2014 Share Posted March 20, 2014 Still no support for MSP430X / large memory like F5529LP? I know it's a gcc thing but just curious. Quote Link to post Share on other sites
spirilis 1,265 Posted March 20, 2014 Share Posted March 20, 2014 Still no support for MSP430X / large memory like F5529LP? I know it's a gcc thing but just curious. Tiva don't need it abecedarian 1 Quote Link to post Share on other sites
abecedarian 330 Posted March 20, 2014 Share Posted March 20, 2014 Tiva don't need it Yeah, but still a bit frustrating having memory on the 5529LP that can't be accessed. Quote Link to post Share on other sites
spirilis 1,265 Posted March 20, 2014 Share Posted March 20, 2014 Yeah, but still a bit frustrating having memory on the 5529LP that can't be accessed.Short answer is, Energia doesn't want to use a potentially unstable ver of gcc... Peter's last ver was a "dev" release supporting large memory, and RH's GCC port is still considered unstable or insufficient. That said, I use Peter's last dev release with satisfactory results in my non-Energia msp430 apps. (Should have done this over @ 43oh since @@bluehash is trying to keep them separate) Quote Link to post Share on other sites
reaper7 67 Posted March 21, 2014 Share Posted March 21, 2014 output file generated by 0101E0012 is bigger than 0101E0011 (for stellaris board) Examples->Basics->Blink v12: 2596bytes v11: 1952bytes ------------------- 644bytes bigger! anyone can explain me why? newer, bigger, better Quote Link to post Share on other sites
energia 485 Posted March 21, 2014 Author Share Posted March 21, 2014 I will have to look at this what is causing this increase. A couple bytes is OK but 664 is a bit drastic. I have on my list to do some optimization for the next release and I hope that will bring down the size for both msp430 and tiva. Quote Link to post Share on other sites
Rei Vilo 695 Posted March 21, 2014 Share Posted March 21, 2014 You can compare the two ELF files with arm-none-eabi-readelf Here are the two outputs for releases 11 and 12 for the same standard blink example. release11.txt release12.txt Quote Link to post Share on other sites
reaper7 67 Posted March 21, 2014 Share Posted March 21, 2014 on MSP430 result files size is the same, only stellaris and tiva giving difference @@Rei Vilo - in Your readelf outputs, I see that all debug_* sections are greater in v12 Quote Link to post Share on other sites
reaper7 67 Posted April 2, 2014 Share Posted April 2, 2014 @@energia - tell me something about i2c on TM4C1294, default module declared in Wire.h is 3 but in Wire.cpp module 3 is not declared for TM4C1294. What happens, when user write Wire.begin() ? I think that for TM4C1294 must be declared alternative i2c module... Quote Link to post Share on other sites
Bernard 7 Posted April 2, 2014 Share Posted April 2, 2014 Thank you Energia team Quote Link to post Share on other sites
spirilis 1,265 Posted April 2, 2014 Share Posted April 2, 2014 @@energia - tell me something about i2c on TM4C1294, default module declared in Wire.h is 3 but in Wire.cpp module 3 is not declared for TM4C1294. What happens, when user write Wire.begin() ? I think that for TM4C1294 must be declared alternative i2c module... If I'm reading that right, the i2cModule variable is merely an index into the various g_ulii2c* arrays, in which case "module 3" would actually be I2C7 on the 4NCPDT version of the chip used in the Connected LP. That's PD_0 and PD_1, located in what's normally the SPI MOSI/MISO lines on the upper boosterpack header (but also happens to be the I2C pins on the original MSP430G2 LP). So setModule() with 0 = I2C0 (PB2/PB3, in the "new standard" boosterpack I2C location in the upper BP header), 1 = I2C2 (PN4/PN5, in the "new standard" boosterpack I2C location in the lower BP header), 2 = I2C8 (PA2/PA3, can't find those on the bpak headers), 3 = I2C7 (PD0/PD1, typically the SPI MISO/MOSI pins on the upper BP header) (referring to @@Rei Vilo 's excellent diagram here- http://energia.nu/Guide_ConnectedLaunchPad.html ) Quote Link to post Share on other sites
vladn 3 Posted April 17, 2014 Share Posted April 17, 2014 I have a strange problem with Energia. On certain simple projects it generates huge (512M) .bin file and hangs during the upload, although the binary sketch size reported in the shell is perfectly normal. It is reproduceable, but I can not find what in the code triggeres it. Has anyone noticed something similar ? Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.