vladn

Tiva-C. Tried switching modules with setModule() and also instantiating two SPIClass objects. Did not work. However I found a workaround at the HW level so the issue is resolved for me. (Problem was that the OLED display did not have CS input and I have other SPI devices)

Is there a way to use multiple SPI modules simultaneously in Energia ? Switching modules on the fly with setModule() does not seem to work properly for me.

I gave up for now. Switched back to Tiva-C and the serial monitor works as it should. Also the build is noticeably faster. I do like the MSP432 for many reasons, but will probably wait for better Energia support or use the CCS.

I get this message 80% of attempts to start the serial monitor in Energia 16 on win10 using the MSP432 launchpad. Have to restart Energia few times to get it running. There are no confilcts in the ports section of the windows device manager. Drivers came with the latest CCS. Any ideas ?

Thanks. Here is how the menu looks on my computer with font smoothin off

Interesting. Adding "editor.laf=..." string to the preferences.txt (on Windows) did not change anything in my case. I do not have JRE installed, only what comes with the Energia. (BTW how to upload an image to this board ?)

I know how to change the editor font - it is well documented. I am curious if it is possible to change the IDE menu font, and if not - the name of the font used for the IDE menu.

Which font is used in the Energia IDE menu in Windows ? Asking because I normally disable OS font smoothing on large, medium DPI monitors and the menu font looks particularly ugly without smoothing. Is there a way to change the IDE menu font via the preferences.txt ? If not - I can do font substitution in the registry, but I need to know which font the IDE uses for menus.

I think I should be able to build a "fuse blower" re-using some code from LowLevelFunc430.c (slau320q.zip). Then the emulator portion of a LP can be used as a programmer and the LP target as a dedicated fuse blower for external targets. I am not going to spend much time on this, if it works right away - I'll post the code, if not - I'll get the FET (old or new). Regarding the user firmware upgrade options. I want it to work with any generic USB UART with no dedicated pins (like cheap ebay dongles). Plus I want to add simple firmware encryption. Hence I think I'll avoid the built-in BSL alt

I am also entering a "semi-production" phase and have few questions: 1. What is the least expensive gadget to blow the security fuse in G2 series ? Is there anything cheaper than TI MSP-FET ? 2. Do I need full JTAG access to blow the fuse ? (the PCB is small and fitting the standard 14pin connector is difficult) 3. User firmware upgrade via BSL seem to require toggling RST/TEST lines in a certain sequence. It seems that one needs more than a plain USB-UART thingy to trigger BSL ? edit- From reading slau320 it appears that it is possible to blow the poly fuse using only SBW pins (SBWTCK

Are there any serial (I2C, SPI etc) graphics display with a built in 2D acceleration ? At a minimum I need very fast and flicker free BITBLT for smooth panning. Ideally the 2D engine should have line draw, rectangle fill and character draw primitives. I do not need color but it has to be fast (no ghosting). I guess this limits the choice to TFT or OLED.

I have tested the scheduler library only with the Energia framework. I have CCSv5 but I used it solely for msp430 projects and do not have it configured for Tiva. I'll look into it when I get some spare time, could be memory allocation issues or unsupported pragmas, hard to say...

The beauty of a coop task switcher for simple projects is that there is no true concurrency . If you are inside a loop or a task - nothing else executes, unless you call yield or exit the loop. Hence you can use simple flags and not worry about reentrant functions, atomic operations, mutexes and such... There is a more sophisticated task switcher code in the Arduino external libraries. I personally like the minimalistic approach of this simple switcher. The next step is too serious IMHO and somewhat specific to the chosen RT paradigm.

It is technically possible, however since it is a cooperative scheduler such measurements can be easily done outside the scheduler library if required. Task scheduling, prioritization and time stamping in a serious RT system is a complex issue and IMHO is outside the scope of the simple cooperative context switcher. This is a realm of RTOS and system design.

According to the "Procedure Call Standard for the ARM® Architecture" document the floating point registers S16-S31 should be saved by the callee. Hence to be fully compliant, the coop scheduler for the M4F core should have these saved in the task context. For efficiency reasons perhaps an explicit flag should be used during the loop/task spawn (so that S16-S31 saving occurs only if the loop/task uses the FPU). This is a fairly easy mod to the Scheduler library. I'll probably do that when I get some spare time.