PC applications to assist in developing embedded devices:
* wrapper for JLink to upload firmware to the devices
* wrapper for our own programming- and test-adapter
* bootloader client for our bootloader to upload firmware to the devices
* A subset of IO-Link master functionality to interface with IO-Link devices
* GUI-Tools that assist during firmware development and debugging, to interface with the device, log realtime data and control various functions
* GUI-Tools using any of the above to automate production, calibration and testing of the products
* GUI-Tool to control a 5 axis Flash- and Test robot
* GUI-Tool to control a 6 axis (2 of them dispense pumps) potting glue dispenser
* Firmware-updater or configuration-tools to ship to customers
Currently working with 3 developers on these various projects.
When we are not using Lazarus/FPC for GUI stuff we are using C (for the firmware) and Python (for various scripting stuff, code generators, etc).
Everything (Developer workstations and production machines) is running on Linux.
Nice these are pretty good usages, Can I see a preview or link or anything to demonstrate these usages?
These are all tools for internal use in the company only, and even the firmware updater I talked about (it implemented a TFTP server to update the firmware of a Toradex SBC) was for use by the contracting entity only, so I cannot share it.
The only thing so far that has publicly come from it so far is my hidapi binding (which I am using to access some of our usb connected internal gizmos) is here:
https://github.com/prof7bit/HIDAPI.pas (and the counterpart on the device which implements a HID device driver on a KL25Z (NXP Kinetis) is here:
https://github.com/prof7bit/frdm-kl25z-minimal-usb-hid And some early stuff from me that was used when we still used AVR and the only means to debug was UART was this:
https://github.com/prof7bit/DebugTerminal (now unmaintained, I don't use it anymore)
I am trying to help the FPC/Lazarus projects as best as I can with bug reports or merge requests, because I rely on these tools every day, and I want them to become better every day. Sometimes I spend entire days of company time to hunt down a Lazarus bug or bisect a regression to help fixing it because we all need it to function properly.