Squashfs needs a block device to run, thus you need the block emulation over UBI. First make sure it is enabled in your kernel.
You can test this by using the ubiblock command on a running system. For example, running ubiblock -c /dev/ubi0_0 will create the devnode /dev/ubiblock0_0.
Once you have the dependency, you can enable the UBI block on the cmdline ...
Commands that just work
To make absolutely sure that it will work, we can make Buildroot build QEMU for us, and use the exact QEMU CLI provided by Buildroot at: https://github.com/buildroot/buildroot/blob/2019.05/board/qemu/x86_64/readme.txt
git clone https://github.com/buildroot/buildroot
git checkout 2019.05
Expanding on Vladimir's answer, I set this specifically in my /etc/asound.conf file:
Alternatively, add a hint to your custom pcm control device:
hint.description "Describe your device here"
I haven't yet found documentation on this, but you can find an ...
Very partial answer, based on dmesg and the msc313e datasheet:
The camera module itself is controlled via I2C, it transfers image data via DVP/MIPI, and there are several hardware image encoders, color processing blocks etc.
MSYS: DMEM request: [S1:VENCDMP1]:0x00069AE0
MSYS: DMEM request: [S1:VENCDMP0]:0x00069AE0
MSYS: DMEM request: [S1:VENCDMOUT]:...
The README file for the board, which is found at board/ti/am335x/README in the source tree has a section on writing to the eMMC. It talks about Falcon Mode, which is having U-Boot run Linux, but covers flashing U-Boot itself as part of that.
I have been directed to use haveged and it actually dramatically shortens startup time:
[ 12.477886] random: crng init done
I will leave this answer for whoever will stumble into the problem.
I will wait for better answers before accepting this.
Note: this source hints there could be some kind of kernel bug responsible for entropy pool exhaustion, but ...
Here is my opinion: Sorry for verbosity in advance.
When we are specifically talking about ubifs we should always either sync / similar options.
ubifs supports write-back caching
That means changes written on the files do not go to flash directly. They are stored on the page cache first and later written to flash.
(Read more on write buffers for NAND ...
That looks like the kernel is getting an illegal instruction exception (700 is a Program exception - which can be a number of things, but sig: 4 is SIGILL).
There are a number of unimplemented instructions in the e300 core - double check the compiler you are using to build the kernel is correct and using the right command line options and that the correct ...
It sounds like you already know enough to choose a permission design for /home/user1, or equivalent. You're asking about the rest of the system. There are already a few discussions here, at least on a related topic:
Limit a user to his own home directory
Allow user to connect using SSH or SFTP but limit to home dir (Centos7)
How to access to specified ...
How can I set the environment during boot (aka without logging in) or let SysVinit doing it, in a nice way?
During the boot environment is clean (isn't initialised jet). You need put env variables via source or . commands for sh (if your service is a script) or initialise it in the program (i.e. via config file).
Small example of service script header:
Create an udev rule to match it.
It shouldn't be necessary to run the script "after a module is loaded" – it deals with a specific device, so it would be better to run it "after the device is detected". Doesn't matter how the device was detected; as long as the kernel reports it as a 'new' device, it'll work.
That said, modules have a presence in /sys just ...
You can use hwclock which should be built into every embedded linux distro.
$hwclock is - as the command name suggest - a hardware clock, independent of the OS being used. These days it uses a low-power oscillator built into the motherboard, that tracks the passage of time even when the machine is powered down (uses mb battery that will last a long time)
Updating to kernel 4.20 the error no longer appears. I can't determine exactly which kernel commit fixed it. There are a few that might have played a roll, but nothing I could identify as an exact fit.
To really speed up boot time build a custom kernel.
One can build a custom kernel by removing all the devices not needed on your computer from the "stock" or original kernel.
It's easier than it sounds.
You get the kernel file and edit out all the things your computer does not need. For instance, if your computer does not have wifi then remove from the ...
If cross-compiling is acceptable, one of the ways to do it is to use oe-alliance's build enviroment:
Use git to clone the build-environment repository and switch to some recent branch, e.g. 4.3.
Check if there is a Bitbake recipe for tvheadend. It should be located at meta-openembedded/meta-multimedia/recipes-dvb/tvheadend/tvheadend_git.bb. If it is not ...