Would Love to Talk to Someone about Implementing HWIL on our own system

FC
Faber, Christopher C. (GRC-LCI0)[GRC-LERCIP]
Fri, Aug 20, 2021 7:06 PM

Hello!

I'm a NASA intern this summer with the Glenn Research Center. We've been in the process of converting our code base into a more modularized component framework with automated unit testing for our SDR. We've successfully implemented automated unit testing via using GitLab CI/CD and we're looking to take the next step toward implementing HWIL (hardware in the loop). However all of us are new to using this concept in our development workflow and it's been difficult to find resources to get started with this. I was wondering if anyone would be open to having a conversation with me about implementing HWIL on our projects. Particularly how to get started and the route you guys took to implement HWIL in GitLab CI/CD.

Thank you for your time and I'm excited to speak with you!

All the Best,
Chuck Faber

Hello! I'm a NASA intern this summer with the Glenn Research Center. We've been in the process of converting our code base into a more modularized component framework with automated unit testing for our SDR. We've successfully implemented automated unit testing via using GitLab CI/CD and we're looking to take the next step toward implementing HWIL (hardware in the loop). However all of us are new to using this concept in our development workflow and it's been difficult to find resources to get started with this. I was wondering if anyone would be open to having a conversation with me about implementing HWIL on our projects. Particularly how to get started and the route you guys took to implement HWIL in GitLab CI/CD. Thank you for your time and I'm excited to speak with you! All the Best, Chuck Faber
JK
James Kulp
Fri, Aug 20, 2021 7:34 PM

Hi Chuck,

There are three big parts to this.

  1. Infrastructure for remotely managing, loading, and executing code (including unit tests) on a "remote" embedded system. We call this "server mode", with the embedded system acting as a "compute" server.

  2. Unit testing framework that was designed from the start to support running unit tests on disparate remote hardware (as well as locally in the development environment on CPUs and simulators).

  3. Use of gitlab CI/CD to actually run unit tests across disparate hardware under the gitlab pipeline mechanisms.

Of course maintaining racks of equipment to be accessible to the testing system isn't a walk in the park either!

Jim

On 8/20/21 3:06 PM, Faber, Christopher C. (GRC-LCI0)[GRC-LERCIP] via discuss wrote:

@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}div.WordSection1
{page:WordSection1;}Hello!

I’m a NASA intern this summer with the Glenn Research Center. We’ve been in the process of converting our code base into a more modularized component framework with automated unit testing for our SDR. We’ve successfully implemented automated unit testing via using GitLab CI/CD and we’re looking to take the next step toward implementing HWIL (hardware in the loop). However all of us are new to using this concept in our development workflow and it’s been difficult to find resources to get started with this. I was wondering if anyone would be open to having a conversation with me about implementing HWIL on our projects. Particularly how to get started and the route you guys took to implement HWIL in GitLab CI/CD.

Thank you for your time and I’m excited to speak with you!

All the Best,

Chuck Faber

<pre class="moz-quote-pre" wrap="">_______________________________________________
discuss mailing list -- <a class="moz-txt-link-abbreviated" href="mailto:discuss@lists.opencpi.org">discuss@lists.opencpi.org</a>
To unsubscribe send an email to <a class="moz-txt-link-abbreviated" href="mailto:discuss-leave@lists.opencpi.org">discuss-leave@lists.opencpi.org</a>