วีดีโอ

Vivado runs on our Ubuntu server that we remote connect to.

What advantages does you CI Workflow Bring vs Classical GitLab/Bitbucket/Jenkins one ?

@@embetrix BeetleboxCI workflows are able to uniquely manage and orchestrate external devices. The software makes it simple to reprogram, connect to and run tests on-device. The workflow even manages the availability of a device to ensure two different tests do not clash with one another. This particular tutorial doesn't highlight these features so much because there isn't really an external device. However, we made it to provide the best education and support of any CI service in regards to embedded systems and hardware development.

Sounds very cool. We are looking at developing a Vitis AI and MLOps video as well.

@@beetlebox4858 Looking forward to it, thanks for putting in the work in these videos by the way! High quality stuff!

In the case of binary and ternary, FPGAs has huge advantage over GPUs because of their ability to exploit XOR operations. Problem is that accuracy drops badly below the 4 bit mark.

@@beetlebox4858 In the case Bitnet specifically the accuracy actually isn't terribly far off of full precision when trained with quantization aware training as described in the paper; the main issue is actually having to train the model from scratch, but it does work pretty well. And, as you noted, it's very efficient on FGPAs.

EC2 actually has some FPGA images called F1s that you can experiment with.

@@beetlebox4858 thanks

Thank you so much. More regular content has already been scheduled.

@@beetlebox4858 can’t wait

It depends on the specific hardware or sensor. Sometimes it is just as simple as connecting the microcontroller and sensor to the same breadboard. You can see an example in our STM32 demo where we use a I2C LED screen. All we do is just cycle the power and check the driver is responding properly before we write to the screen. In other cases, we have created more sophisticated setups where we use a seperate microcontroller to control a test kit with all the various sensors and hardware attached. The test kit and the device can then be synced together through CI. We do this setup if there are very specific test requirements like needing to know exactly how the system will respond if a sensor goes down.

This algorithm was realized with library openCV

opencv, it's in the video title