-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
I work on the development team of the Flexible Software Package (FSP). e2 studio is the IDE and FSP is the C code. We use GitLab CI extensively for internal development and want to improve the no-GUI experience with what we have publicly on GitHub. FYI, here are some thoughts I've had about using FSP outside of e2 studio. Using e2 studio is very useful for getting your base project up an running. For example, creating your pin configuration (pin multiplexing) is much easier using the graphical Pin Configurator than reading through the hardware manual and attempting to figure out the muxing for potentially hundreds of pins. It is also valuable for configuring RTOS threads (if you're using FreeRTOS or ThreadX) and configuring drivers and modules. Configuring a baud rate for UART, connecting an Ethernet driver to the TCP/IP stack, and connecting a SD card to a file system are good examples of things that can be done for you using e2 studio. Once this base project is setup and I'm ready to start my application, my preference would be to move to using my own development environment. This means that if I wanted to update something originally configured, then I could open e2 studio back up, make the changes, and regenerate the files. I'm fond of using vscode, git, GitLab CI, and my preferred Linux distro. For a build system, CMake is becoming increasingly popular. There are many different opinions in this space and many people prefer to stay in an IDE like e2 studio. These are just my thoughts. If there are any suggestions or questions, I'd like to hear them.