7/22/2021 4:02 PM | |
Joined: 6/29/2015 Last visit: 4/17/2023 Posts: 2 Rating: (1) |
We received the first batch of IOT2050's with the pre-installed industrial OS. ..But I can't, for the life of me, understand why you would set the mmc1 mmc0 boot order as default. It used to be very straightforward now to install your own package : - insert SD - log into SSH - isntall to eMMC Now you need either an UART or a display/keyboard combo to simply re-enable that possibility. Why wasn't networking/ssh enabled by default on the OS ? Why isn't fw_env.config preinstalled ? Why is `mmc1 mmc0 usb...` the default boot order ? It's making stuff so much more complicated... The steps we need to take now are the following : - Plug your IOT2050 on a display+keyboard - Run the installer for no reason since you're gonna flash another OS anyway - Copy the fw_env.config to the right place - fw_setenv boot_targets ... - Reboot with your SD - Login to SSH - Install to eMMC OR you have to deal with the UART, which isn't really any better. It's madness!... The proper way to have dealt with this, in my opinion, would have been : - `mmc0 mmc1 usb0 usb1 usb2` default boot order (or any of the other boot devices BEFORE mmc1) - Setup DHCP on one port and fixed IP on the second - Enable SSH by default with an autostarting installer - Add an option at the end of the installer to change the bootorder to `mmc1 mmc0 usb...` to "harden" the system if you don't plan on using the SD and don't want people to stick their stuff in the IOT - Definitely include the fw_env.config on the OS by default Is there any way to see any of this in the next batch of devices ? Otherwise, I'd really much rather receive them blank... ------------------------------------------------------------------------------------------ |
Last edited by: Jen_Moderator at: 07/23/2021 08:17:15New subject after splitting |
|
Follow us on