I am referring to Section 14 (and Section 15) of the Azure Sphere Guardian 100 Hardware User Guide (v1.4).
In section 14 it states " This uses a pre-compiled, production-signed application that is side-loaded into the MT3620 device from the azsphere command window."
Whoever created this pre-compiled program without any transparency on the code is asking the user to take a huge risk side-loading this onto the Guardian 100. Legal matters aside (production signed? where's the proof) this makes it rather difficult to troubleshoot when it does not work as described.
The instructions go on to say:
The Guardian iPerf3 application is preconfigured to connect to an iPerf3 server at a specific static address. It is therefore necessary to set the computer’s ethernet adaptor to have a static IP address of 192.168.1.35 (plus the other highlighted settings shown below...)
Unfortunately my LAN does not make use of 192.168.1.... as an option. How can you expect such rigidity?
Hence the need to check what's going on and maybe have an option to compile my own customised test code. So, what's the reason for hiding this code? Where's the transparency?
The same can also be said for section 15.1 Guardian: Test Application Installation.
EDIT: PS. The user guide also does not provide instructions on how to remove the side-loaded images, meaning they remain on the device until manually removed. So, how is this best done?
