We use cookies to provide our visitors with an optimal site experience. View our privacy notice and cookie notice to learn more about how we use cookies and how to manage your settings. By proceeding on our website you consent to the use of cookies.
3v3 and 5v0 are voltage rails directly connected to the regulators.
Same as answer 1, already configured…
Nice catch, looks like a typo in the spread sheet. One quick test, after configuring D11 in Linux, grab your LED and try both locations while toggling the pin in Linux. Very quickly you’ll discover the correct location.
Yes, you are free to use any gpio’s, however you had specifically requested a step by step direction on utilizing gpio_40. You can use those same directions to configure any the pins the P8 header.
@RobertCNelson
Do the results for the ./tools/rebuild.sh command look okay?
is the NXP software only used to verify Magic values?
Question 01: In this part I have a difficulty. I commanded a ums 0 mmc 0 (in picocom) and on the ubuntu-server computer lsblk and got the result of the photo. It doesn’t seem ok for me to go to Setup extlinux.conf (sudo mkdir -p /media/rootfs/boot/extlinu/), correct?
Well first check that you booted the new kernel, just type:
uname -v
debian@bbb-pwr01-ser09:~$ uname -v
#1buster SMP PREEMPT Tue Aug 25 01:48:27 UTC 2020
The “build date” in above is “Tue Aug 25 01:48:27 UTC 2020” in your case it should match your build time of today…
Your photo’s are missing the pin defines, from “./KERNEL/” just run “git diff” and pastebin the changes…
all "./ignore/’ directories are a local cache for git…
PS, looking at your screen log, why did you rewrite /etc/fstab? you just need to update the kernel, module and device tree blobs and then extlinux.conf, don’t touch anything else…
So it’s still September??? Nope it’s now middle of November, so you booted the ‘old’ kernel. Try copying over the Kernel/modules and device-tree again.
@RobertCNelson
It’s like I told you before. I have difficulties to update only the kernel. The times it worked, I went back to pico-imx7d in factory condition (via mfgtool2) and started from scratch. The photo below indicates the error (I think). Instead of sdd1 - part - /media/neuberfran/rootfs should be /media/rootfs, correct?
That’s no error, that’s just your desktop “auto-mounting” the drive.
On the wiki i state:
On most systems these partitions may be auto-mounted…
sudo mkdir -p /media/rootfs/
for: DISK=/dev/mmcblkX
sudo mount ${DISK}p1 /media/rootfs/
for: DISK=/dev/sdX
sudo mount ${DISK}1 /media/rootfs/
So in your case, it “auto-mounted” thus just use “/media/neuberfran/rootfs/” instead of “/media/rootfs/”…
If you woried about it, just unmount it:
sudo umount /media/neuberfran/rootfs/
and correctly mount it…
sudo mount /dev/sdd1 /media/rootfs/
EDIT; thinking more about this, i don’t know what your version of FUSE, or the auto-mount settings did, i’d just advise to un-mount it and properly mount it.
Regards,
Hum, the led’s are showing up… I bet, the ‘date’ was set when you originally built the kernel, whereas ./tools/rebuild.sh only builds the changes… Since only the device-tree changed, the kernel build date wasn’t updated…
@RobertCNelson
I had problems (died) my mobo p8h61m lx3 r2.0. I’ll only be back on 25.11.2020 with another. I re-recorded the bios(bin file), but it didn’t work. Before, there was time to make echo 0 and echo 255 and turn off/on led on gpio40
@RobertCNelson Can you help me just one more time? Why can’t I use gpioset commands on my pico-imx7d with debian (after being able to use sysfs correctly)?
