-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to configure pins #76
Comments
@jackw2050 please add output off
|
git:/opt/scripts/:[70edebd65fe6ea7de16ea8efe3c48b2a4062034a] |
Your old bootloader in the eMMC is block u-boot overlays, you can fix it via:
and since your running:
Change in /boot/uEnv.txt, to get the correct pru overlay.
also make sure the bb-cape-overlays package is upto date..
Regards, |
It is working correctly now. Thank you for the help and quick response. Regards, Jack |
I am having a similar issue with the exception being that I have an NHD-7.0CTP-CAPE-N display attached. Without the display all works as it should. When the display is attached I have the above problem using to use GPIO pins and UART1, UART4, and SPI0. I believe I have done the updates listed above. Below is the listing from sudo /opt/scripts/tools/version.sh. Any help is appreciated. git:/opt/scripts/:[ea6ea9fca05f36f5044398884375b0231348d6e2] |
OK - I found that by adding the following line to the uEnv.txt the config-pin function works but, the touch screen function does not? uboot_overlay_addr4=/lib/firmware/cape-universal-00A0.dtbo |
What you ask is implemented in v4.16.x+ kernel's.. Regards, |
and our 2018.03 build of u-boot https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays Regards, |
OK - I believe I have everything up to date and still no touchscreen activity on the display. Any more thoughts? sudo ./version.sh | grep bootloader uname -a cat /proc/version |
@gemlrm which touchscreen? what's the full output of "version.sh".. Regards, |
Touchscreen is: NHD-7.0CTP-CAPE-N git:/opt/scripts/:[c190498f25b51d83e452a296de31e2e65883d001] |
Your overlays are fighting over pins...
In /boot/uEnv.txt Remove/Disable:
and disable
You can use:
Regards, |
Success. Thank you very much for your assistance and have a great day. |
All seems good until you loose the SPI bus. Display and touch are working, but SPI is now gone. Config-pin is showing correct for uart and spi. ls -al /dev/spidev* returns no such file or directory. Any thoughts on this? |
You can add them back via:
in /boot/uEnv.txt Regards, |
Hi,
I cannot see /dev/mmcblk1 after reboot but I have PWM's just fine:
My system:
My env:
|
@comarius answered here: https://groups.google.com/forum/#!category-topic/beaglebone/wMrXlY7R0Uw Closing thread, new questions = new issue.. |
i have bought a COMMS cape for my BeagleBone Black wireless. i want to use it to get CAN message. But i have not fund the overlay for this cape. |
@sychen917 , please don't directly spam everyone on a closed issue. In /boot/uEnv.txt use:
Should achieve what you want, but open a new issue, i'll be locking this "closed" issue. Regards, |
Unable to configure pins
I am attempting to setup Beagle Bone Wireless using the new U-Boot Overlays.
When I try to configure any of the pins I get the following errors:
GPIO:
debian@beaglebone:/var/lib/cloud9$ config-pin P8.03 gpio
P8_03 pinmux file not found!
Pin has no cape: P8_03
PWM:
debian@beaglebone:/var/lib/cloud9$ config-pin P9.14 pwm
P9_14 pinmux file not found!
Pin has no cape: P9_14
Following recommendations found for related issues I have updated the kernal and the boot loader.
I have tried configuring many other pins with the same result.
Based on documentation here: https://github.com/cdsteinkuehler/beaglebone-universal-io all pins are enabled and in a default condition.
It looks like Cape Universal is not loading.
What am I doing wrong?
Best regards,
Jack Walker
The text was updated successfully, but these errors were encountered: