The element14 roadtests are a great way to learn new things. Whenever I see a test that interests me, I enroll.

Success is not guaranteed. I've been selected for some, not for others. In this series I'll explain how I decide to enroll or not.

I'll also show how I build my case, including some examples from my applications.

 

Renesas RX65N MCU EV Kit

 

(c) Why did you apply for this particular roadtest?

I am in particular interested in 2 aspects of the RX65N kit:

Hardware:

All the modules on the right side of the functional overview , related to security and safety.

I als would like to test the CAN peripheral and the DAC module.

Software:

It would be my first experience developing for a Renesas device. I’d like to verify how good the Eclipse based IDE is compared to other manufacturers, and if the examples are rich and helpo understand the device.

 

(d) What is your testing procedure or project plan (Be as specific as you can)?

For hardware:

  • test the security specific options, in isolation on the device, and together with controllers of competitors, to check compatibility and openness in a mixed manufacturer design
  • how is secure storage of keys implemented
  • validate the DAC (not so common peripheral in a microcontroller)
  • Use the CAN modules in a setup I have available. I made specific CAN driver here on element14 for this purpose.

 

Software:

  • validate the IDE. I have experience with the solutions from other hardware manufacturers (TI, Maxim, Silicon Labs, Siemens). I would validate how well the integration of the Renesas utilities , libraries, examples and documentation is. How easy it is to get Project 1 running. How good the debugoptions are.
  • Validate HAL and RTOS options
  • Validate how well the examples help to understand the device
  • validate the Man-Machine examples and if they give a headstart for industrial design control.
  • validate the support options available, if appliccable.

 

Trinamic TMC2300 EVAL KIT (2-PH Stepper Motor)

 

(c) Why did you apply for this particular roadtest?

I'm interested in motor drivers and power electronics. I've reviewed devices from TI before and used them in combination with programmable timers of the BeagleBone (PRU) and Hercules (HET).

I linked in references int section e.

 

(d) What is your testing procedure or project plan (Be as specific as you can)?

I will wire up a stepper motor to the device and evaluate the capabilities to generate stepper profiles.

How easy / difficult is it to define the parameters that define tork, speed, microsteps.

Look at the generated signals, general review of capabilities and settings.

Focus on specific possibilities (are there competitive advantages) of this design.

 

Infineon Blockchain Starter Kit

 

(c) Why did you apply for this particular roadtest?

Jan and <...> are applying together. We found a way of testing the kit in two ways:

- being in 2 different country's, we would create cards/keys for each other and mail cards.

- each using a blockchain ledger program running locally, trying to use the Infineon cards to sign/mark ledger exchanges

 

(d) What is your testing procedure or project plan (Be as specific as you can)?

1: - test the kit using Infineon's guidelines

2: - test if card generated by person 1 can be used in a trusted situation by person 2, or can be detected in an untrusted situation

3 - test as blockchain indentifiers with two separate instances, one in <...>' network, one in Jan's network, of blockchain focused ledger Hyperledger.

 

STM32H7B3I-DK -  DISCOVERY KIT (testers not selected yet)

 

(c) Why did you apply for this particular roadtest?

I have built a measurement instument here on element14.

It has a programmable interface and a screen showing stats, but no user interface.

I's like to use the STMicro's human interface capabilities, together with display and touch screen, to build the front end to this industrial design.

 

The capabilities I will use are: driving an LCD, using the touch screen integration, using the UART hardware.

If achievable (I have the skill but haven't used it on an ST device) show how to design with an RTOS.

 

I will not use some capabilities of the device in this test, such as WiFi and the inter-chip protocols, but I can test those in isolation.

 

(d) What is your testing procedure or project plan (Be as specific as you can)?

Build a real user interface on an existing programmable lab instrument.

The LCD interface will be used to present user options and give relevant feedback.

 

I will use the ST UART, LCD and Touch screen integrations using the abstraction layer.

This will allow me to validate and critique the controller and the ST libraries.

The hardware for which I'm developing the user interface exists and is fully documented on element14: Programmable Electronic Load

 

 

 

 

I have reviewed a Renesas controller that also has a human interface focus. I will compare the User Interface building and responsiveness compared to that.

 

Related blog
How I Enroll for a RoadTest - Part 1: yes or no
How I Enroll for a RoadTest - Part 2: success and failure
How I Enroll for a RoadTest - Part 3: Help Me
How I Enroll for a RoadTest - Part 4: Case for Programmable Electronic Load
How I Enroll for a RoadTest - Part 5: Case for Educational Switch Mode Converter Lab

How I Enroll for a RoadTest - Part 6: Case for CAN Analysis Tool

How I Enroll for a RoadTest - Part 7: Case for Some Other Road Tests
How I Enroll for a RoadTest - Part 8: Case for Harting Mica Road Tests
How I Enroll for a RoadTest - Part 9: Case for Renesas RX65N, Trinamic TMC2300, Infineon Block Chain, STM32H7B3I DISCOVERY KIT