27 de octubre de 2023

While testing Multicast Loopback in a testing infrastructure for VxWorks, there were some packets being lost. After a careful analysis, the application code seemed to be ok. Thus, I created a simple reproducer and sent it to WindRiver, which was able to reproduce it. After some back and forth it was accepted as a bug. […]

Starting in armv8-a ISA, all instructions are hard-float, and therefore all CPUs have a floating-point unit. This was not the case before, and thus I found out about it while porting our software to QNX 6..0 for an armv7-based board. This board comes with a Zynq-7000 CPU, which does have a hardware FPU, thus my

While the Embedded Lab Lead I had the chance to work on setting up physically embedded systems from a variety of hardware architectures (Intel, ARM, MIPS, PowerPC, Spark) as well a wide range of Operating Systems, both standard and real-time (VxWorks,VxWorks 653, Integrity, Lynx, Lynx-178, AIX, Ubuntu, Debian, Wind River Linux, Yocto, RedHawk, Android, AOSP). 

WindRiver VxWorks 7 SR0660 ships with C++ Boost 1.7.4, therefore using their own headers. However, we had been supporting C++ Boost for VxWorks for a while and we also had our own C++ Boost and headers. When any common customer would create a DKM application, they would include both C++ Boost, and that would mean

To set up these Emerson embedded boards it is important to understand first what these are PowerPC-based projects, using the MPC7457 CPU which uses a core with a generic FPU unit. The reason why I bring this up as an interesting project is because the issue I run into with the 6500. These are boards

WindRiver Linux is a modified version of Linux tuned and compiled by WindRiver, providing their own tools and compiler to develop, deploy, and operate robust, reliable, and secure embedded solutions running on a purpose-built Linux operating system. It is officially supported, which gives it an advantage for projects that require such services. Besides, Wind River

Yocto Linux is a custom Linux that any user can build on their own with the components and the configuration they need for the hardware they have. This project required knowledge to be able to build both a QNX and a Yocto kernel, make sure all components needed are included and compile it for the

For a long time, while a member of the Platforms Team and working mainly on ports, I was also in charge of the embedded lab at RTI. My personal passion for hardware and to find out how things work led me to maintaining and setting up new embedded hardware in our continuously increasing lab. Specifically,

This project required deep knowledge of VxWorks 653 inner workings, kernel settings, memory layout, VIP and VSB projects, as well as Perl language to be able to automate the whole build and test infrastructure to leverage existing perl automated infrastructure.

What was ported? I encountered bugs related to casting from a pointer to a 32-bits integer in a 64-bit architecture, wrong endianness for big-endian TCP architectures, and other issues related to openSSL.The code changes where mostly in C to fix bugs and unit-tests. The compiler options were important as well.