Hi 
I am new to the BBB but I will try to help you, I am running Debian Version 
8.7 so perhaps something has changed...
Are you sure you have HDMI disabled as these pins are used by the HDMI?
I found the show-pins pearl script very useful in tracking down pin-mux 
issues. https://github.com/mvduin/bbb-pin-utils 
Below is a snip of its output. Any pin that is not in mode 7 is not 
accessible as a GPIO
If you run this scrip it will tell you what mode the pin is in and what is 
claiming it. So my first step would be to determine the pin mode and work 
form there.
Hope this helps

Regards
Tom

P8.45 / hdmi / sysboot 0          40 fast rx down 7 gpio 2.06 << lo  P8_45 
(pinmux_P8_45_default_pin)
P8.46 / hdmi / sysboot 1          41 fast rx down 7 gpio 2.07 << lo  P8_46 
(pinmux_P8_46_default_pin)
P8.43 / hdmi / sysboot 2          42 fast rx down 7 gpio 2.08 << lo  P8_43 
(pinmux_P8_43_default_pin)
P8.44 / hdmi / sysboot 3          43 fast rx down 7 gpio 2.09 << lo  P8_44 
(pinmux_P8_44_default_pin)
P8.41 / hdmi / sysboot 4          44 fast rx down 7 gpio 2.10 << lo  P8_41 
(pinmux_P8_41_default_pin)
P8.42 / hdmi / sysboot 5          45 fast rx          7 gpio 2.11 lo >>  
P8_42 (pinmux_P8_42_gpio_pin)
P8.39 / hdmi / sysboot 6          46 fast rx          7 gpio 2.12 hi >>  
P8_39 (pinmux_P8_39_gpio_pin)
P8.40 / hdmi / sysboot 7          47 fast rx down 7 gpio 2.13 << lo  P8_40 
(pinmux_P8_40_default_pin)
P8.37 / hdmi / sysboot 8          48 fast    down 4 uart 5 txd      
 ocp/P8_37_pinmux (pinmux_P8_37_uart_pin)
P8.38 / hdmi / sysboot 9          49 fast rx down 4 uart 5 rxd      
 ocp/P8_38_pinmux (pinmux_P8_38_uart_pin)
P8.36 / hdmi / sysboot 10         50 fast rx down 7 gpio 2.16 << lo  P8_36 
(pinmux_P8_36_default_pin)
P8.34 / hdmi / sysboot 11         51 fast rx down 7 gpio 2.17 << lo  P8_34 
(pinmux_P8_34_default_pin)
P8.35 / hdmi / sysboot 12         52 fast rx          7 gpio 0.08 lo >>  
P8_35 (pinmux_P8_35_gpio_pin)
P8.33 / hdmi / sysboot 13         53 fast rx down 7 gpio 0.09 << hi  P8_33 
(pinmux_P8_33_default_pin)
P8.31 / hdmi / sysboot 14         54 fast rx down 7 gpio 0.10 << lo  P8_31 
(pinmux_P8_31_default_pin)
P8.32 / hdmi / sysboot 15         55 fast rx down 7 gpio 0.11 << hi  P8_32 
(pinmux_P8_32_default_pin)



On Tuesday, February 20, 2018 at 7:49:18 AM UTC, madhuri depuru wrote:
>
> Hello,
>
> i am working over beagle bone black. i have got a new board for which i 
> have downloaded a new debian image of version 9.3 from beagleboard.org
>
> the image is getting uploaded into my beaglebone.but it has a new gpio 
> directory structure as shown below.
>
> export gpio12 gpio20 gpio3 gpio45 gpio5 gpio65 gpio7 unexport
> gpio112 gpio13 gpio22 gpio30 gpio46 gpio50 gpio66 gpiochip0
> gpio114 gpio14 gpio23 gpio31 gpio47 gpio51 gpio67 gpiochip32
> gpio115 gpio15 gpio26 gpio4 gpio48 gpio60 gpio68 gpiochip64
> gpio116 gpio2 gpio27 gpio44 gpio49 gpio61 gpio69 gpiochip96
>
> but my application requires gpio 70 - 80 which are not present in new 
> debian version. my old beaglebone black is of debian versio 7.9 and my old 
> gpio directory structure was
>
> export gpio44 gpio65 gpio70 gpio75 gpio8 gpio88 gpiochip64
> gpio10 gpio45 gpio66 gpio71 gpio76 gpio80 gpio89 gpiochip96
> gpio11 gpio46 gpio67 gpio72 gpio77 gpio81 gpio9 unexport
> gpio23 gpio47 gpio68 gpio73 gpio78 gpio86 gpiochip0
> gpio27 gpio61 gpio69 gpio74 gpio79 gpio87 gpiochip32
>
> can anyone please tell me how can i get gpio 70-80
>

-- 
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/e3ff3681-3ce2-4918-89b5-ed1754dfefed%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to