Hi Jon!
I upgraded the kernel to the same version as you have.
This is the output:
root@beaglebone:~# 
/opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
P2_18
P2_18 pinmux file not found!
Cannot read pinmux file: /sys/devices/platform/ocp/ocp*P2_18_pinmux/state

Still not working. In uEnv.txt file, I have this added:
uboot_overlay_addr6=/lib/firmware/PB-MCP2515-SPI1.dtbo
This is the MCP2515 which could read the SWCAN bus if it was set to HIGH.

jonn...@gmail.com a következőt írta (2020. október 19., hétfő, 3:32:13 
UTC+2):

> This is how to set say P2_18 as an output and high.
>
> debian@beaglebone:~$* 
> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
> P2.18*
> *P2_18 Mode: gpio Direction: in Value: 0*
> debian@beaglebone:~$ 
> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin 
> P2.18 gpio*
> debian@beaglebone:~$* 
> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin P2.18 
> out*
> debian@beaglebone:~$ 
> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin 
> P2.18 hi*
> debian@beaglebone:~$ 
> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin 
> -q P2.18*
> *P2_18 Mode: gpio Direction: out Value: 1*
>
>
> I don't think the /usr/bin/config-pin tool can do this.
>
> Cheers,
>
> Jon
>
> On Sun, Oct 18, 2020 at 6:17 PM jonnymo <jonn...@gmail.com> wrote:
>
>> With a PocketBeagle running Debian 10 (Buster) IoT image and kernel 
>> 4.19.94-ti-r51 I see this:
>>
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
>> P2_06*
>> *P2_06 Mode: default Direction: in Value: 0*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i 
>> P2_06*
>> *Pin name: P2_06*
>> *Function if no cape loaded: gpio*
>> *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input*
>> *Function information: gpio1_25 default gpio1_25 gpio1_25 gpio1_25 
>> gpio1_25*
>> *Kernel GPIO id: 57*
>> *PRU GPIO id: 89*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l 
>> P2_06*
>> *default gpio gpio_pu gpio_pd gpio_input*
>>
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -q 
>> P2_18*
>> *P2_18 Mode: default Direction: in Value: 0*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -i 
>> P2_18*
>> *Pin name: P2_18*
>> *Function if no cape loaded: gpio*
>> *Function if cape loaded: default gpio gpio_pu gpio_pd gpio_input qep 
>> pru_ecap pruin*
>> *Function information: gpio1_15 default gpio1_15 gpio1_15 gpio1_15 
>> gpio1_15 eqep2_strobe pru_ecap pru0_in15*
>> *Kernel GPIO id: 47*
>> *PRU GPIO id: 79*
>> *debian@beaglebone:~$ 
>> /opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin -l 
>> P2_18*
>> *default gpio gpio_pu gpio_pd gpio_input qep pru_ecap pruin*
>>
>>
>> *debian@beaglebone:~$ config-pin -q P2_18                                 
>>        *
>> *Current mode for P2_18 is:     default*
>>
>> *debian@beaglebone:~$ config-pin -q P2_06*
>>
>> *Current mode for P2_06 is:     default*
>>
>>
>> Note, I did do a 'sudo apt-get update' and sudo apt-get upgrade' and then 
>> updated the scripts and such listed in the following Beaglebone Upgrade 
>> link including the 'update_kernel.sh' script.
>> https://beagleboard.org/upgrade
>>
>>
>> Cheers,
>>
>> Jon
>>
>> On Sun, Oct 18, 2020 at 5:50 PM Szabó Benedek Ákos <szaboben...@gmail.com> 
>> wrote:
>>
>>> Hi there!
>>> Sorry for the late reply.
>>> So, here is a summary, what I already did, and what I tried:
>>> I have a problem configuring a pin P2_18 and P2_06 on PocketBeagle.
>>>
>>> What I'm trying is to get SWCAN working on a GM car, but I have to set 
>>> it up to HIGH.
>>> When I run config-pin P2_18 hi it returns error:
>>> config-pin P2_18 hi ERROR: open() for 
>>> /sys/devices/platform/ocp/ocp:P2_18_pinmux/state failed, No such file or 
>>> directory 
>>>
>>> I found no P2_18 or P2_06 pinmux file exists here:
>>>
>>> <https://user-images.githubusercontent.com/1343260/96346876-6d538780-109e-11eb-81aa-553fdff04e6e.png>
>>>
>>> /sys/devices/platform/ocp/ocp:
>>>
>>> version.sh output:
>>> opt/scripts/tools/version.sh
>>> git:/opt/scripts/:[7cdc270818b76d829d247cf05fe309c320a3929a]
>>> eeprom:[A335PBGL00A21743GPB30299]
>>> model:[TI_AM335x_PocketBeagle]
>>> dogtag:[BeagleBoard.org Debian Buster IoT Image 2020-08-25]
>>> bootloader:[microSD]:[/dev/mmcblk0]:[U-Boot 
>>> 2019.04-00002-gc9b3922522]:[location: dd MBR]
>>> UBOOT: Booted Device-Tree:[am335x-pocketbeagle.dts]
>>> UBOOT: Loaded Overlay:[AM335X-PRU-RPROC-4-19-TI-00A0]
>>> UBOOT: Loaded Overlay:[BB-ADC-00A0]
>>> UBOOT: Loaded Overlay:[PB-CAN0-00A0]
>>> UBOOT: Loaded Overlay:[PB-CAN1-00A0]
>>> UBOOT: Loaded Overlay:[PB-MCP2515-SPI1]
>>> kernel:[4.19.94-ti-r50]
>>> nodejs:[v10.21.0]
>>> /boot/uEnv.txt Settings:
>>> uboot_overlay_options:[enable_uboot_overlays=1]
>>>
>>> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/PB-CAN0-00A0.dtbo]
>>>
>>> uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/PB-CAN1-00A0.dtbo]
>>>
>>> uboot_overlay_options:[uboot_overlay_addr6=/lib/firmware/PB-MCP2515-SPI1.dtbo]
>>>
>>> uboot_overlay_options:[uboot_overlay_pru=AM335X-PRU-RPROC-4-19-TI-00A0.dtbo]
>>> uboot_overlay_options:[enable_uboot_cape_universal=1]
>>> pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
>>> <pkg>]
>>> pkg:[bb-cape-overlays]:[4.14.20200814.0-0~buster+20200814]
>>> pkg:[bb-wl18xx-firmware]:[1.20200813.1-0~buster+20200813]
>>> pkg:[kmod]:[26-1]
>>> pkg:[librobotcontrol]:[1.0.5-git20200715.0-0~buster+20200716]
>>> pkg:[firmware-ti-connectivity]:[20190717-2rcnee1~buster+20200305]
>>> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
>>> plugdev users systemd-journal input bluetooth netdev i2c gpio admin spi iio 
>>> docker tisdk weston-launch xenomai cloud9ide pwm eqep remoteproc]
>>> cmdline:[console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4 
>>> rootwait coherent_pool=1M net.ifnames=0 lpj=1990656 
>>> rng_core.default_quality=100 quiet]
>>> dmesg | grep remote
>>> [   53.832040] remoteproc remoteproc0: wkup_m3 is available
>>> [   54.008667] remoteproc remoteproc0: powering up wkup_m3
>>> [   54.008700] remoteproc remoteproc0: Booting fw image 
>>> am335x-pm-firmware.elf, size 217168
>>> [   54.008997] remoteproc remoteproc0: remote processor wkup_m3 is now up
>>> [   55.838857] remoteproc remoteproc1: 4a334000.pru is available
>>> [   55.872421] remoteproc remoteproc2: 4a338000.pru is available
>>> dmesg | grep pru
>>> [   55.838857] remoteproc remoteproc1: 4a334000.pru is available
>>> [   55.839046] pru-rproc 4a334000.pru: PRU rproc node pru@4a334000 
>>> probed successfully
>>> [   55.872421] remoteproc remoteproc2: 4a338000.pru is available
>>> [   55.872630] pru-rproc 4a338000.pru: PRU rproc node pru@4a338000 
>>> probed successfully
>>> dmesg | grep pinctrl-single
>>> [    0.895597] pinctrl-single 44e10800.pinmux: 142 pins, size 568
>>> dmesg | grep gpio-of-helper
>>> [    0.905153] gpio-of-helper ocp:cape-universal: ready
>>> lsusb
>>> Bus 002 Device 002: ID 148f:7601 Ralink Technology, Corp. MT7601U 
>>> Wireless Adapter
>>> Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>>> END
>>>
>>> What can cause this error?
>>> I tried to run pinmux-generator, but it throws error:
>>> root@beaglebone:/opt/source/bb.org-overlays/tools/pinmux-generator# 
>>> ./PocketBeagle.sh pinmux-4.0.1526-setup.run 
>>> 100%[=====================================================================================================================================================================>]
>>>  
>>> 39.87M 2.91MB/s in 14s 2020-10-17 15:20:15 (2.76 MB/s) - 
>>> ‘pinmux-4.0.1526-setup.run’ saved [41810329/41810329] ./lib/pinmux.sh: line 
>>> 220: ./pinmux-4.0.1526-setup.run: cannot execute binary file: Exec format 
>>> error cp: cannot stat 'tmp/pinmux/deviceData/AM335x/AM335x.json': No such 
>>> file or directory ################## P1_02 cat: AM335x.json: No such file 
>>> or directory cat: AM335x.json: No such file or directory cat: AM335x.json: 
>>> No such file or directory cat: AM335x.json: No such file or directory 
>>>
>>> Tried to install pinmux manually, but it doesnt support armhf 
>>> architecture.
>>>
>>> Also tried this config-pin command:
>>>
>>> */opt/source/bb.org-overlays/tools/beaglebone-universal-io/config-pin *
>>>
>>> Without any luck.
>>> jonn...@gmail.com a következőt írta (2020. október 18., vasárnap, 
>>> 23:24:17 UTC+2):
>>>
>>>> From my understanding, the PocketBeagle does not have an eMMC so the 
>>>> Flasher step is not needed.
>>>>
>>>> Jon
>>>>
>>>> On Sun, Oct 18, 2020 at 10:23 AM Dennis Lee Bieber <
>>>> dennis....@gmail.com> wrote:
>>>>
>>>>> On Sat, 17 Oct 2020 12:05:29 -0700 (PDT), in
>>>>> gmane.comp.hardware.beagleboard.user Szabó Benedek Ákos
>>>>> <szabobenedekakos-re...@public.gmane.org> wrote:
>>>>>
>>>>> >Btw, Im using a Pocketbeagle, I flashed during it was connected to an 
>>>>> USB 
>>>>> >HUB with external power supply. Is it ok or not?
>>>>>
>>>>>         Depends on the hub. USB 2 specs are for a maximum of 0.5A 
>>>>> (500mA) at 5V
>>>>> -- giving 2.5W. But if any other devices are attached to that hub, 
>>>>> they too
>>>>> are drawing power, and the hub may only be able to provide around 0.1A 
>>>>> per
>>>>> port.
>>>>>
>>>>>         A 3W charge-only USB power supply might be safer.
>>>>>
>>>>>         Unlike the BBB, the PB only has USB for power input. The BBB 
>>>>> has a 5V
>>>>> barrel connector for power-only supplies, and it is strongly 
>>>>> recommended
>>>>> that such be used for flashing on the BBB.
>>>>>
>>>>>         You never did answer the question of what the LEDs were doing 
>>>>> on those
>>>>> failed boot attempts. So far as I can tell from images, the PB has the 
>>>>> same
>>>>> four status LEDs as the BBB, just located differently. From
>>>>> https://groups.google.com/forum/#!topic/beagleboard/LHAxeSki-eU
>>>>>
>>>>> [] [] [] [] - off
>>>>> [x] [] [] [] - on, starting mmc scan...
>>>>> [x] [x] [] [] - scanning mmc...
>>>>> [x] [x] [x] [] - processed boot script...
>>>>> [x] [x] [x] [x] - jumping into boot... 
>>>>>
>>>>> (After that, if a flasher image is found, the LEDs run a Larson scanner
>>>>> pattern until flashing is done, and then the board is shutdown; 
>>>>> otherwise
>>>>> they show system activity: heartbeat, eMMC, CPU, SD card.)
>>>>>
>>>>>         Unfortunately, the show-pins PERL script is only BBB aware, 
>>>>> not PB.
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Dennis L Bieber
>>>>>
>>>>> -- 
>>>>> 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 beagleboard...@googlegroups.com.
>>>>>
>>>> To view this discussion on the web visit 
>>>>> https://groups.google.com/d/msgid/beagleboard/2atoof9ahtgabmgc3nosjfu56uclp506l4%404ax.com
>>>>> .
>>>>>
>>>> -- 
>>> 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 beagleboard...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/c6afc6c8-1959-4804-bd4c-09d2052f6385n%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/beagleboard/c6afc6c8-1959-4804-bd4c-09d2052f6385n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>>
>>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c8719f4a-e8ef-4aef-a54b-04adc8d29a26n%40googlegroups.com.

Reply via email to