I have some touchscreen(s) at home and I want to get one working on my raspberry pi. But the problem is that I must recompile the kernel. I followed this tutorial (http://engineering-diy.blogspot.be/2013/02/raspberry-pi-raspbian-xbmc-and-egalax-7.html?m=1).
I downloaded the kernel but I don't know how to find the lib folder on my SD card. If I place the kernel in the lib folder, the raspberry pi boots up but the mouse and the keyboard freezes.
Where can I find the /lib folder of my rpi?
To awnser your question: The lib folder is at the root of your SD card. You say you can't find it but you did place the kernel image in it? Seems contradicting :)
I wanted to install the same touschscreen.
Use this website:
http://engineering-diy.blogspot.nl/2013/01/adding-7inch-display-with-touchscreen.html
The following files should be replaced:
- kernel.img
- kernel7.img
- bootcode.bin
- /lib/firemwire
- /lib/modules
- /opt/vc
When you put your SD card in your computer you should see the boot partition and the big partition (of 2+gb depends on your sd card).
In the boot partition you place: the kernel, kernel7.img and bootcode.bin
In the big partition you should see the folders:
- bin
- boot
- dev
- etc
- home
- lib
and more..
Here you navigate to /lib and here you place the firmware and modules.
In /opt you place the vc folder.
Good luck!
Edit
I created a repos where you can find all files you need: de-rpi2
Related
i'm working on building U-Boot boot loader for raspberry pi 4. i have followed all the documentation instructions and building has finished well, but the results files are the following
u-boot
u-boot.bin
u-boot.cfg
u-boot.cfg.configs
u-boot.lds
u-boot.map
u-boot-nodtb.bin
u-boot.srec
u-boot.sym
i can't find MLO or u-boot.img to put them on the SD card.
so the question is; is there any specific or custom configurations should i take before building to generate MLO and img files ?
Does this happend because the new design of rpi4, which has EEPROM that alreadey contains the SPL and no need for MLO and img files ?
could any one give me some tips?
also i have used rpi_4_defconfig from uboot/configs, and generate custom toolchain for raspberrypi 4 using cross-ng
The MLO file is specific to Texas Instruments (TI) SoCs and their ROM. What you'll want to do in the case of a Raspberry Pi 4 is to copy u-boot.bin to kernel8.img and that will cause the Pi's firmware to load U-Boot.
So i have a Raspberry Pi 3 with the latest OS (10-04-2021) and i have apache2 running. I created a website which is in the directory /var/www/html/ with a few folders (e.g css, img, etc.) and i used the image tag with src="" to the usb drive path, but the video doesn´t load. I tried, if i made any mistakes while coding the website. So i also placed the website folder on the desktop with also the video path to my usb drive and i could play it on the website. I can´t place the .mp4 files in the /var/www/html/ path just because my SD card only has a few GB and my video folder is about 100 GB. How can i use my .mp4 files from my USB drive on the server/localhost?
What i tried and didn´t work was:
chmod -R a+r /media/pi/KINGSTON/*
I am just a beginner with raspberry pi and its OS.
That's a totally correct behavior. For security reasons Apache won't let you access files outside the document root, which in your case should be /var/www/html/. There are multiple approaches to do this, the first is to create symlinks in the document root and instruct apache2 to follow symlinks in the configuration file. Another approach is to use aliases. You can read here
I have connected an MCP2515 to the Raspberry Compute-Module and now it would be nice if I could make it work.
We use a distribution based on buildroot - but unfortunately we can't manage to load the devicetree-overlay for the MCP2515.
We activated device-tree in the linux-menuconfig plus we created overlay folder in /boot plus we activated dtoverlay in /boot/config.txt
What else should we take care of, to make CAN work on our system?
Thank you.
I'm currently trying to build poky-tiny for imx6ulevk (using the BSP Yocto Project Environment provided by NXP).
I first followed the Quick Start Guide, tested and everything worked just fine. I then went to the usual local.conf file (/build/conf/local.conf) and changed the DISTRO variable to poky-tiny.
In poky-tiny distro file (/sources/poky/meta-yocto/conf/distro/poky-tiny.conf), I changed the virtual/kernel in the variable PREFERRED_PROVIDER_virtual/kernel to linux-imx and the PREFERRED_VERSION_linux-imx to 3.14.38 which is compatible (I think).
I finally added to the local.conf the variable IMAGE_FSTYPES with the value tar.bz2 ext3 sdcard.
At this point I tried to build using:
bitbake core-image-minimal
this runs without any problems. But it doesn't generate sdcard image or any u-boot images as is expected. The only files generated are:
core-image-minimal-imx6ulevk-20160517152114.rootfs.cpio.gz
core-image-minimal-imx6ulevk-20160517152114.rootfs.manifest
core-image-minimal-imx6ulevk.cpio.gz
core-image-minimal-imx6ulevk.manifest
modules-imx6ulevk.tgz
zImage
zImage--3.14.38-r0-imx6ul-14x14-evk-20160517152114.dtb
zImage--3.14.38-r0-imx6ul-14x14-evk-csi-20160517152114.dtb
zImage--3.14.38-r0-imx6ulevk-20160517152114.bin
zImage-imx6ul-14x14-evk-csi.dtb
zImage-imx6ul-14x14-evk.dtb
zImage-imx6ulevk.bin
And I got stuck without knowing how to deploy to the imx6ulevk. What did I do wrong? Why is yocto not generating the usual sdcard image?
If anyone gets this what worked for me was the following:
Turns out poky-tiny for imx6ulevk does not create sdcard images normally. So what you need to do, once you build it with a proper kernel, is to manually create a bootable sdcard. This can be done by using gparted cleaning everything in it and adding 2 partitions, then proceed as follow:
1 - First you use gunzip in the file core-image-minimal-imx6ulevk-...-rootfs.cpio.gz.
2 - Call cpio on the generated file: cpio -i -vd < core-image-minimal...-.cpio
3 - You just generated the root file system copy everything into one of the partitions.
4 - the zImage...* files are the generated kernel for the poky-tiny distro. Copy all but the symbolic links to the second partition. You might need to rename the files (I had to) if you're not sure what to rename to, first build regular poky using sdcard image and check out the proper names.
That's pretty much it, you should be able to boot imx6ulevk using the provided files.
I'm trying to build a LabVIEW plug and play instrument driver project for a device we sell. I followed the instructions to create a project, and it created the project in with the LabVIEW program:
C:\Program Files\National Instruments\LabVIEW 2011\instr.lib
I suppose I could connect that folder to source control and just do all the work there, but it feels weird to be working under Program Files. When I tried to move the project folder out into my regular workspace folder, it broke all the subpalette files (*.mnu). I could recreate them, but I'm afraid they wouldn't work for our customers when they install the driver from the LabVIEW web site.
Is it possible to move a driver project around, or does it have to stay in the default location? If one of our customers has installed LabVIEW in a different location (say on drive D:) will the driver menus not work for them?
I'm not in favour of user.lib for SCC'd items. using several LabVIEW versions at a time is a big problem.
Here is my routine:
Create the instrument library and save all code in a folder starting with an underscore ('_') (_foo)
Create an .mnu file in the parent folder of '_foo' Mylib.mnu, add the icons you need.
With OpenG package builder I create an installer routine that placed the the mnu file and the folder in instr.lib
After a restart of LabVIEW the instrument driver shows up in the instruments palette.
If you keep the code in the same relative position to the mnu file there is no problem with missing VIs.
Ton
Instrument drivers are always located in the 'instr.lib' folder in the current LabVIEW version folder. There is an environmental path set up in LabVIEW for this intrument driver folder so it will always point to the correct drive for the installation of LabVIEW used.
You should keep the folder in the location used by the wizard to ensure that when distributed to your customers the sub palette menus point to the correct location and all the VIs link correctly.
I use source control for user.lib which is in a similar location and have no problems.