Re: [beagleboard] Re: How to access GPIO using derek molloy's GPIO Library

[jonnymo]

Since you are using a PocketBeagle, isn't P1_32 mapped to gpio1.10 and not
P1_36 which is mapped to gpio3.14?
https://github.com/beagleboard/linux/blob/4.14/arch/arm/boot/dts/am335x-pocketbeagle.dts
https://docs.google.com/spreadsheets/d/1fE-AsDZvJ-bBwzNBj1_sPDrutvEvsmARqFwvbw_HkrE/edit#gid=1518010293

Jon



On Sat, Mar 27, 2021 at 7:19 PM Piyush Raj ae19m009 <
ae19m...@smail.iitm.ac.in> wrote:

> Thanks for replying Dennis
>
> I tried changing the uBoot.env as suggested by you. Results weren't as
> expected. However I was able to find a work around method which I would
> like to share with the community.
>
> I was able to access gpio on P1 headers (almost all of them) using the
> bonescript library. Since my application is cpp based , I had to find a way
> to use these gpios on P1 header.
> Here's what I did:
> 1)Created a service which runs a javascript bonescript application with P1
> pins configured in bonescript.
> 2)allowed this service to run in background and then ran my main.cpp
> application using these additional pins on P1 as gpios.
>
> Results:
>
> Got access to 30 pins total, as gpio
>
> Assessment:
>
> Bonescript is doing the configuration of pins for me. Although I haven't
> deep dived into bonescript, someone who already has knowledge of it can
> better explain how is bonescript able to configure gpio.
>
> Regards
>
> Piyush
>
> On Fri, 26 Mar, 2021, 04:00 Dennis Lee Bieber, 
> wrote:
>
>> On Thu, 25 Mar 2021 10:07:13 -0700 (PDT), in
>> gmane.comp.hardware.beagleboard.user
>> "jeff-re5jqeeqqe8avxtiumw...@public.gmane.org"
>>  wrote:
>>
>>
>> >
>> >The following post shows a line in uEnv.txt for enabling, and I assuming
>> >disabling cape universal:
>> >
>> >https://github.com/beagleboard/bb.org-overlays/issues/79
>> >
>> >enable_uboot_cape_universal=1
>> >
>> >So, not sure if this means that if you change to 0 in uEnv.txt, that it
>> >would free up pins so that pin-config no longer gives an error.
>> >
>>
>> I seem to recall that disabling cape_universal ALSO disables any
>> use of
>> config-pin. More likely is that one needs to disable /other/ overlays that
>> are claiming the desired pins. From my BBB:
>>
>> ###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.14.x-ti kernel)
>> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
>> ###pru_rproc (4.19.x-ti kernel)
>> uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo
>> ###pru_uio (4.14.x-ti, 4.19.x-ti & mainline/bone kernel)
>> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
>> ###
>> ###Cape Universal Enable
>> enable_uboot_cape_universal=1
>>
>> Though what overlay claims P1_36 (PWM0 A) is not apparent. May
>> have to
>> search the device tree sources to find it.
>>
>>
>> --
>> Dennis L Bieber
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/IocB0viAW2A/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/gv2q5gpoi1o10hfvio4ishmebffvhlrusc%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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/CAD20Z3y-UmK7XDn39927cTNjiMC0FTAwcmSpW-94iur_NMHRFg%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAG99bkr2%3DeyB%2BDNGJngxvem4no3MdijLgxLKWabkXHgH6Q8mXA%40mail.gmail.com.

Re: [beagleboard] Re: How to access GPIO using derek molloy's GPIO Library

[Piyush Raj ae19m009]

Thanks for replying Dennis

I tried changing the uBoot.env as suggested by you. Results weren't as
expected. However I was able to find a work around method which I would
like to share with the community.

I was able to access gpio on P1 headers (almost all of them) using the
bonescript library. Since my application is cpp based , I had to find a way
to use these gpios on P1 header.
Here's what I did:
1)Created a service which runs a javascript bonescript application with P1
pins configured in bonescript.
2)allowed this service to run in background and then ran my main.cpp
application using these additional pins on P1 as gpios.

Results:

Got access to 30 pins total, as gpio

Assessment:

Bonescript is doing the configuration of pins for me. Although I haven't
deep dived into bonescript, someone who already has knowledge of it can
better explain how is bonescript able to configure gpio.

Regards

Piyush

On Fri, 26 Mar, 2021, 04:00 Dennis Lee Bieber, 
wrote:

> On Thu, 25 Mar 2021 10:07:13 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user
> "jeff-re5jqeeqqe8avxtiumw...@public.gmane.org"
>  wrote:
>
>
> >
> >The following post shows a line in uEnv.txt for enabling, and I assuming
> >disabling cape universal:
> >
> >https://github.com/beagleboard/bb.org-overlays/issues/79
> >
> >enable_uboot_cape_universal=1
> >
> >So, not sure if this means that if you change to 0 in uEnv.txt, that it
> >would free up pins so that pin-config no longer gives an error.
> >
>
> I seem to recall that disabling cape_universal ALSO disables any
> use of
> config-pin. More likely is that one needs to disable /other/ overlays that
> are claiming the desired pins. From my BBB:
>
> ###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.14.x-ti kernel)
> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo
> ###pru_rproc (4.19.x-ti kernel)
> uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-00A0.dtbo
> ###pru_uio (4.14.x-ti, 4.19.x-ti & mainline/bone kernel)
> #uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo
> ###
> ###Cape Universal Enable
> enable_uboot_cape_universal=1
>
> Though what overlay claims P1_36 (PWM0 A) is not apparent. May
> have to
> search the device tree sources to find it.
>
>
> --
> Dennis L Bieber
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/IocB0viAW2A/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/gv2q5gpoi1o10hfvio4ishmebffvhlrusc%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAD20Z3y-UmK7XDn39927cTNjiMC0FTAwcmSpW-94iur_NMHRFg%40mail.gmail.com.

Re: [beagleboard] Re: BIG problem with BBB and logging into ANY username

[Tom Paratore]

Try logging in as user : debian
Password: temppwd

Check your spelling after u enter user name

Sent from my iPhone

On Mar 27, 2021, at 7:12 PM, amf  wrote:


I followed your instructions, once I obtained the new ip, I was able to login 
as the user of the origanl BBB.
Without knowing details of your setup it is difficult to help
is your desktop/laptop a windows or linux machine?
if linux you can get the ip of the new BBB with "ping .local" 
provided 'avahi' is installed (there may be other ways, this works for me)

ping beaglebone.local
PING beaglebone.local (192.168.3.108) 56(84) bytes of data.
64 bytes from 192.168.3.108: icmp_seq=1 ttl=64 time=1.31 ms

if windows, someone else will need to chime in,



On Saturday, March 27, 2021 at 7:39:21 AM UTC-5 propg...@gmail.com wrote:
I duplicated my BBB setup to a SD card using this procedure:


Debian distribution:

  1.  Boot master BBB with no SD card in
  2.  Insert SD card
  3.  Log in (e.g. with serial terminal, SSH etc.) and run sudo 
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh. 
LEDs will flash in sequence whilst SD card is being written.
  4.  When the LEDs stop and the script terminates, remove the SD card.
  5.  Insert SD card into new BBB then power on.
  6.  eMMC will be flashed; LEDs on new BBB will flash in sequence until 
complete.

After doing this, I rebooted the BBB.

Now, I am unable to remotely log in using PuTTY, user is root, and root 
password.  Or any other username and password.

The BBB is running fine (collecting seismic data) but I am completely locked 
out!

Any suggestions on how to get access to the BBB?

--
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/833795ff-61b4-418c-a142-9aed980e01a7n%40googlegroups.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/MN2PR19MB33749FDD908386298B45CEFBF2609%40MN2PR19MB3374.namprd19.prod.outlook.com.

[beagleboard] Re: BIG problem with BBB and logging into ANY username

[amf]

I followed your instructions, once I obtained the new ip, I was able to 
login as the user of the origanl BBB.
Without knowing details of your setup it is difficult to help
is your desktop/laptop a windows or linux machine?
if linux you can get the ip of the new BBB with "ping .local" 
provided 'avahi' is installed (there may be other ways, this works for me)

ping beaglebone.local
PING beaglebone.local (192.168.3.108) 56(84) bytes of data.
64 bytes from 192.168.3.108: icmp_seq=1 ttl=64 time=1.31 ms

if windows, someone else will need to chime in,



On Saturday, March 27, 2021 at 7:39:21 AM UTC-5 propg...@gmail.com wrote:

> I duplicated my BBB setup to a SD card using this procedure:
>
> Debian distribution:
>
>1. Boot master BBB with no SD card in
>2. Insert SD card
>3. Log in (e.g. with serial terminal, SSH etc.) and run sudo 
>
> /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh. 
>LEDs will flash in sequence whilst SD card is being written.
>4. When the LEDs stop and the script terminates, remove the SD card.
>5. Insert SD card into new BBB then power on.
>6. eMMC will be flashed; LEDs on new BBB will flash in sequence until 
>complete.
>
> After doing this, I rebooted the BBB.
>
> Now, I am unable to remotely log in using PuTTY, user is root, and root 
> password.  Or any other username and password.
>
> The BBB is running fine (collecting seismic data) but I am completely 
> locked out!
>
> Any suggestions on how to get access to the BBB?
>

-- 
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/833795ff-61b4-418c-a142-9aed980e01a7n%40googlegroups.com.

[beagleboard] BIG problem with BBB and logging into ANY username

[Bob Hammond]

I duplicated my BBB setup to a SD card using this procedure:

Debian distribution:

   1. Boot master BBB with no SD card in
   2. Insert SD card
   3. Log in (e.g. with serial terminal, SSH etc.) and run sudo 
   /opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh. 
   LEDs will flash in sequence whilst SD card is being written.
   4. When the LEDs stop and the script terminates, remove the SD card.
   5. Insert SD card into new BBB then power on.
   6. eMMC will be flashed; LEDs on new BBB will flash in sequence until 
   complete.

After doing this, I rebooted the BBB.

Now, I am unable to remotely log in using PuTTY, user is root, and root 
password.  Or any other username and password.

The BBB is running fine (collecting seismic data) but I am completely 
locked out!

Any suggestions on how to get access to the BBB?

-- 
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/d73f6c74-3d01-44f2-8542-2a4368a47845n%40googlegroups.com.