AlexSTAL

I'm sorry, but I can get at least some answer. At least in the style of "what nonsense is written here?" or "why so perverted?" or "you need to try it yourself", etc.

Good afternoon! Tell me about the case, please, the post is great, but maybe I'm initially going the wrong way. Initial task: data exchange between a remote server and equipment with a USB interface and CDC RS-232 or HID protocols. Putting a computer / laptop next to it is not an option. I did not find any ready-made solutions, there are only options: 1. Single board computer. Fast, cheap, angry, easy to make a case and PoE power from ready-made components on the market. 2. Arduino - to assemble from prototyping boards is long, difficult and expensive. To develop something of my own - the navel will be untied with my knowledge. 3. Hardware "extension" USB over TCP / IP - expensive, redundant. 4. Ready-made USB print server / router - can you easily write your own firmware? I read that OpenWrt is installed on TP-Link TL-MR3020 ... I am leaning towards the first option with a single-payer based on a combination of factors - complexity, price, availability, etc. Question on the topic. If you choose a single boarder, is it possible to implement booting from an ISO image on an eMMC partition or SD card? How do I do it on industrial PC x86 architecture: 1. I deploy Linux in the usual way (in my case I use Debian) on the master computer. 2. Create an ISO image (snapshot) using Linux Live Kit (Tomas-M). 3. I mark up disks on working computers, install GRUB, copy the prepared ISO image and tell the bootloader to boot from it. Profit. We have a "firmware" version of the download. You need to update the operating system or programs - we do this on a master computer, create a new ISO image and simply copy it to all other working computers. On single-payers, I read, U-Boot is used mainly, but he does not know how to do this. but it seems like it is written that he can boot GRUB for the second time, which can already boot ISO ... Who has any thoughts?

Good day! I connect the real time clock, made according to the instructions: RTC time is set I set the wrong time in the RTC, reboot. I look at the time in the system clock - at first not the right one, from the RTC, then they are synchronized and it becomes the right one. But in RTC, the new correct time is not recorded. What am I doing wrong? Or what else needs to be done?