You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
overview: I created a custom chip that emulates the behavior of an I2C IMU, my idea is that I can check if students are correctly accessing the register bank to make settings on the sensor, or if they can read specific values and process them (with the aim of extracting information from the manual and implementing it correctly in code).
My original idea would be to put some printfs on the custom chip, when the student writes/reads and check this in test.yml with wait-serial, as illustrated below:
But now I realized that wait-serial doesn't check the output of the custom chip, any suggestions on what we can do? Maybe create a wait-serial-custom-chip? Or add the custom chip log to the serial output?
The log is there, but we cant check!
The text was updated successfully, but these errors were encountered:
I was actually thinking about a different mechanism:
Provide an API for chips to declare some kind of output variables, which will complement the "controls" that provide inputs to the chip.
For instance, a chip implementing a servo controller could declare an "angle" output variable, and then the tests could read this variable and assert on its value. And like controls, these output variables will only support floating point values (at least initially).
Hi! I think this is more complex than necessary because we will need to handle different variable types. What if the angle is a float, or what if it's an array? How would we check for these different kinds of data?
Make sense - output variables may still be useful for more constrained use cases (e.g. angle of a servo), but I agree that just looking for a specific pattern in the chip output can be very useful.
hello @urish !
overview: I created a custom chip that emulates the behavior of an I2C IMU, my idea is that I can check if students are correctly accessing the register bank to make settings on the sensor, or if they can read specific values and process them (with the aim of extracting information from the manual and implementing it correctly in code).
My original idea would be to put some printfs on the custom chip, when the student writes/reads and check this in test.yml with
wait-serial
, as illustrated below:But now I realized that wait-serial doesn't check the output of the custom chip, any suggestions on what we can do? Maybe create a wait-serial-custom-chip? Or add the custom chip log to the serial output?
The log is there, but we cant check!
The text was updated successfully, but these errors were encountered: