Hi Mala Dies,
I have got the solution for the problem I faced. But for this solution, I need to have some changes in my old software. In /sys/class/pwm folder there are folders like pwmchip0, pwmchip1 etc. The names of these folders are much important. Just use the command ls -al root@beaglebone:/sys/class/pwm# ls -al total 0 drwxrwxr-x 2 root pwm 0 Jan 1 2000 . drwxr-xr-x 61 root root 0 Jan 1 2000 .. lrwxrwxrwx 1 root pwm 0 Oct 7 17:37 pwmchip0 -> ../../devices/platform/ocp/48300000.epwmss/48300100.ecap/pwm/pwmchip0 lrwxrwxrwx 1 root pwm 0 Oct 7 17:37 pwmchip1 -> ../../devices/platform/ocp/48300000.epwmss/48300200.pwm/pwm/pwmchip1 lrwxrwxrwx 1 root pwm 0 Oct 7 17:37 pwmchip3 -> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip3 lrwxrwxrwx 1 root pwm 0 Oct 7 17:37 pwmchip5 -> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip5 lrwxrwxrwx 1 root pwm 0 Oct 7 17:37 pwmchip6 -> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip6 Here we need to find the addresses like 0x4830_0100 corresponds to which pwm, by looking into the following documents 1) AM335x ARM Cortex A8 MicroProcessors Technical Reference Manual(Table 2-3) 2) http://beagleboard.org/support/bone101 And we should enable PWMs which is really available; pins alloted for other functions should not be configured as pwm (See the web page : http://beagleboard.org/support/bone101; Only 5 are there). Thank You very much for the support. Thanks & Regards, Sajeevan.K Thanks & Regards, Sajeevan.K On Thursday, December 20, 2018 at 3:19:29 AM UTC+5:30, Mala Dies wrote: > > Okay... > > This is what I currently understand about this whole idea involving the > pwmchip2 and /sys/class/pwm/... > > ... > > I think where we both should have been looking is in /dev/pwm/. There is > where the pwm peripherals are found w/ two pins for each one. > > Also...ecap2 in /dev/pwm/, which can be configured as a pwm output, > conflicts w/ HDMI audio on the boards. You may need to adjust your > /uEnv.txt file to suit the needs of this action. > > That file can found in the /boot directory. > > Seth > > P.S. Those symlinks in /dev/pwm/ should make it easy to understand which > pwm peripheral you are using and have configured. > > ... > > ... > > So...ls -l /dev/pwm should give you the correct printout of peripherals > available. > > On Wednesday, December 19, 2018 at 7:40:27 AM UTC-6, sajeevan k wrote: >> >> Hi Mala Dies, >> >> Sorry. I have been busy with scheduled tasks. So I couldn't spare time >> for testing your suggestions and giving a feedback. >> >> As You suggested, I took the latest image and immediately tried sudo >> config-pin P9.14 pwm command. It is working!! >> >> >> debian@beaglebone:~$ sudo config-pin P9.14 pwm >> debian@beaglebone:~$ cd /sys/class/pwm >> debian@beaglebone:/sys/class/pwm$ ls >> pwmchip0 pwmchip1 pwmchip3 pwmchip5 pwmchip6 >> debian@beaglebone:/sys/class/pwm$ >> >> >> But when I check /sys/class/pwm folder pwmchip2 folder is seen. In my >> previous software, I have used this folder. >> >> At present this is my feedback. It is in the late evening now. I will do >> more test tomorrow and give further feedback. >> >> Would You please tell me why pwmchip2 folder is not there now? >> >> Thanks in advance for the help. >> >> Thanks & Regards, >> Sajeevan.K >> >> On Wednesday, December 19, 2018 at 8:53:59 AM UTC+5:30, Mala Dies wrote: >>> >>> Hello, >>> >>> I say update to a newer image. bbb.io/latest-images has a new image >>> w/out GUI. You can use config-pin w/ that newer image/kernel. >>> >>> Seth >>> >>> P.S. Then what I typed out before is then relevant. >>> >>> On Saturday, December 15, 2018 at 7:26:18 AM UTC-6, sajeevan k wrote: >>>> >>>> Hi all, >>>> >>>> >>>> I was using the image bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img >>>> for a GUI application and pins and pwms were configured with config-pin >>>> command. This could be done with Cape Universal enabled. >>>> >>>> But now when I am using the latest images, the /boot/uEnv.txt is >>>> changed as per the >>>> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays. >>>> >>>> And with this image, when I try to run the application it is showing >>>> the following error messages: >>>> >>>> Pin has no cape: P9_13 >>>> P9_24 pinmux file not found! >>>> Pin has no cape: P9_24 >>>> P9_26 pinmux file not found! >>>> Pin has no cape: P9_26 >>>> P9_17 pinmux file not found! >>>> Pin has no cape: P9_17 >>>> >>>> Also in my code, I was accessing files from folders like >>>> /sys/class/pwm/pwmchip2. But these folders are not there now. >>>> >>>> I think, if we are changing to u-boot overlays, then we have to change >>>> our source code. So it is better to stick to the old kernel overlays. >>>> >>>> As per the web page >>>> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays, >>>> I tried to enable Cape Universal by disabling *"enable_uboot_overlays=1" >>>> in /boot/uEnv.txt.* But still it is not working >>>> *. * >>>> >>>> *Now I used the the image bone-debian-9.1-lxqt-armhf-2017-08-31-4gb.img >>>> and the uEnv.txt is as shown below.* >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0 >>>> <http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0>uname_r=4.9.45-ti-r57#uuid=#dtb=###U-Boot >>>> >>>> Overlays######Documentation: >>>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays >>>> <http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays>###Master >>>> >>>> Enable#enable_uboot_overlays=1######Overide capes with >>>> eeprom#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo#uboot_overlay_addr1=/lib/firmware/<file1>.dtbo#uboot_overlay_addr2=/lib/firmware/<file2>.dtbo#uboot_overlay_addr3=/lib/firmware/<file3>.dtbo######Additional >>>> >>>> custom >>>> capes#uboot_overlay_addr4=/lib/firmware/<file4>.dtbo#uboot_overlay_addr5=/lib/firmware/<file5>.dtbo#uboot_overlay_addr6=/lib/firmware/<file6>.dtbo#uboot_overlay_addr7=/lib/firmware/<file7>.dtbo######Custom >>>> >>>> Cape#dtb_overlay=/lib/firmware/<file8>.dtbo######Disable auto loading of >>>> virtual capes >>>> (emmc/video/wireless/adc)#disable_uboot_overlay_emmc=1#disable_uboot_overlay_video=1#disable_uboot_overlay_audio=1#disable_uboot_overlay_wireless=1#disable_uboot_overlay_adc=1* >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *######PRUSS OPTIONS###pru_rproc (4.4.x-ti >>>> kernel)#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo###pru_uio >>>> >>>> (4.4.x-ti & mainline/bone >>>> kernel)uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo######Cape >>>> Universal Enable#enable_uboot_cape_universal=1######Debug: disable uboot >>>> autoload of >>>> Cape#disable_uboot_overlay_addr0=1#disable_uboot_overlay_addr1=1#disable_uboot_overlay_addr2=1#disable_uboot_overlay_addr3=1######U-Boot >>>> >>>> fdt tweaks...#uboot_fdt_buffer=0x60000###U-Boot >>>> Overlays####cmdline=coherent_pool=1M net.ifnames=0 >>>> quietcmdline=coherent_pool=1M net.ifnames=0 quiet cape_universal=enable#In >>>> the event of edid real failures, uncomment this next >>>> line:#cmdline=coherent_pool=1M net.ifnames=0 quiet >>>> video=HDMI-A-1:1024x768@60e##Example >>>> v3.8.x#cape_disable=capemgr.disable_partno=#cape_enable=capemgr.enable_partno=##Example >>>> >>>> v4.1.x#cape_disable=bone_capemgr.disable_partno=#cape_enable=bone_capemgr.enable_partno=##enable >>>> >>>> Generic eMMC Flasher:##make sure, these tools are installed: dosfstools >>>> rsync#cmdline=init=/opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh* >>>> >>>> >>>> *And for this case * >>>> *sudo /opt/scripts/tools/version.sh is as follows* >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> *root@beaglebone:~# sudo >>>> /opt/scripts/tools/version.shgit:/opt/scripts/:[288a143ff1aaeb8f6df5c328b60b6d220082cd47]eeprom:[A335BNLT000C1827BBBG1897]model:[TI_AM335x_BeagleBone_Black]dogtag:[BeagleBoard.org >>>> >>>> Debian Image >>>> 2017-08-31]bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot >>>> 2018.09-00002-gd5b4c4b656]:[location: dd >>>> MBR]bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot >>>> 2016.03-00001-gd12d09f]:[location: dd >>>> MBR]kernel:[4.9.45-ti-r57]nodejs:[v6.15.0]pkg check: to individually >>>> upgrade run: [sudo apt install --only-upgrade >>>> <pkg>]pkg:[bb-cape-overlays]:[4.4.20181120.0-0rcnee0~stretch+20181120]pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]pkg:[kmod]:[23-2rcnee1~stretch+20171005]pkg:[roboticscape]:[0.4.4-git20180608.0-0rcnee0~stretch+20180609]:[GOT_REPLACED_BY_NEXT]WARNING:pkg:[librobotcontrol]:[NOT_INSTALLED]pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]groups:[debian >>>> >>>> : debian adm kmem dialout cdrom floppy audio dip video plugdev users >>>> systemd-journal i2c bluetooth netdev cloud9ide gpio pwm admin spi tisdk >>>> weston-launch xenomai]cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 >>>> ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet >>>> cape_universal=enable]dmesg | grep pinctrl-single[ 2.305156] >>>> pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568dmesg | >>>> grep gpio-of-helperroot@beaglebone:~# * >>>> >>>> Still I am not able to use config-pin command and so I think Cape >>>> Universal is not enabled. Please suggest some workaround to solve this >>>> issue. >>>> >>>> Thanks and Regards, >>>> Sajeevan.K >>>> >>>> -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/017a2bbc-4805-45bc-b8bf-06a856e5f772%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
