Thank you for such an excellent reply. It points me in the right direction. We may be doing a custom U-Boot and kernel build anyhow. I am starting to become fond of this platform. I just picked up the Omega2S a couple weeks ago for the first time and had the streaming USB UVC video working on day one over Wifi.

Thank you. That means there is a good chance it is possible.

Yes, we are particular about the size format of the display. It has to fit in a specialized handle. The display is a constant where the variable comes in is the "when" I can update the display during the boot using I2C even at the bare hardware level. I figure I can add a driver load (and die no error) to several points spread-out across the boot list to hit the I2C for the display, but being with 40-years of expertise with microcontrollers but new to the Omega2S specifically, my guess is the hive-mind of this community has probably encountered this issue with brilliant solutions before.

I am embedding an Omega2s into a device case. Since it takes more than 60 seconds to boot to the point that the Wifi and USB host are fully ready to go I would like to display some type of booting status to the .98” 128 x 32 pixel OLED display. Writing to the display works great once the drivers and OS are loaded. But I want to initialize, clear, and write to the display from the time U-BOOT hands over control, until the OS is fully loaded.

As an example, something as simple as displaying “Booting” as early as possible after U-Boot and adding a “.” approximately every 5-seconds or so, finally clearing at the end of full-boot and display “Ready.”

Since the I2C driver is not loaded until way late in the boot process, I figure that I need to write something at the bare metal GPIO level. What would be a good clean strategy to accomplish displaying booting status to this I2C display?

Thank you,

Leonard

I have plugged in a high-speed USB 2.0 hub in to an Omega2S (and +). Plugged into it are two Logitech 930C USB 2.0 web cams. I run the two commands:

mjpg_streamer -b -i "input_uvc.so -d /dev/video0 -r 1280x720 -f 30" -o "output_http.so -p 8080 -w /www/webcam"
mjpg_streamer -b -i "input_uvc.so -d /dev/video1 -r 800 x 600 -f 30" -o "output_http.so -p 8081 -w /www/webcam"

Camera #1 at 1280 x 720 and Camera #2 800 x 600, both at full frame rates ~30fps. The performance is inspiring over Wifi! But, if I bump up Camera #2 to the 1280 x 720, with no surprise, it fails:

uvcvideo: Failed to submit URB 0 (-28).
Unable to start capture: No space left on device
i: Error grabbing frames

So here is the question; I have worked with devices where RAM is split into partitions. On some of these, you can futz around with the mapping and steal from one partition allocation to add to another. Does the potential exist that I can re-map and maybe grab just enough RAM to allow both cameras to run at the 1280 * 720? Both the Onion2S and Onion2S+ have the same error which is strange since the 2S+ has 2x RAM (DDR2 DRAM 128MB vs 64MB) of the 2S but running the same OS image. Where has my 2X RAM gone?

Thank you,

Leonard

I screwed up! Sent output to NUL in /root and not /dev/nul. I RM'ed NUL file but it did not recover storage even after a sync or firstboot / sync / reboot. Here is the df:
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 7936 7936 0 100% /rom
tmpfs 29916 80 29836 0% /tmp
/dev/mtdblock6 6720 428 6292 6% /overlay
overlayfs:/overlay 6720 428 6292 6% /
tmpfs 512 0 512 0% /dev
/dev/mmcblk0p1 7484816 33720 7051176 0% /mnt/mmcblk0p1

How can I recover the flash? I am on a Omega2s dev board with emm flash.

Thank you!