[beagleboard] Re: ODBC & SQL SERVER

[amf]

Is this the source your looking at, it does indicate it supports 32 bit. (I 
have not used it)
https://github.com/microsoft/msphpsql

On Friday, July 30, 2021 at 9:14:23 AM UTC-5 Micka wrote:

> Hi,
>
> I would like to know if anyone has succeeded to install the driver
> msodbcsql on the beaglebone black ?
>
> Looks like that it's only available for 64 bit machine :(
>
>
> Michael,
>

-- 
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/0c4630b6-311a-4d82-ac6c-6c4f72af9bcen%40googlegroups.com.

Re: [beagleboard] Re: PRU Assumptions - True or False

[amf]

Hi lazarman,
on ubuntu 20.04, this builds ok

git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev
git checkout remotes/origin/ti-linux-rt-5.4.y -b ti-linux-rt-5.4.y
./build_kernel.sh

I've used VirtualBox before with Ubuntu 16/18/20 without any issues, what 
VM are you using?
Several years ago a company that I worked for used some other VM, it was a 
pain in the azz to get to work, if i hear the name again i'll know if that 
was the one.
I haven't used Debian for a desktop, so I can't help you with that. 

On Saturday, May 29, 2021 at 3:45:46 PM UTC-5 lazarman wrote:

> Hello 
>
> I've failed to build following those instructions twice in Mainline  and 
> twice using the TI BSP.version. the 2nd attempt of TI BSP is hung as we 
> speak after resolving dependencies for several hours. Each attempt takes 
> hours and the build_kernel script doesnt care you already cloned 2G of code 
> it clones torvald.git
> so I retried 4 times by running build_kernel.sh twice in both directories
>
> The Mainline had some git branch errors today
>
> I paid to upgrade my internet for this testing and was ready to buy a 64 
> bit box but am scared these instructions need a refresh and I will waste $$
>
> what would be lovely is a 2 line like is in the instruction pasted below 
> with something that will work for sure.
> the two directories I created are both on wrong branches and  dont 
> complete a buil d
>
> Be nice not keep downloading the 2G kernel source I know there is  a 
> rebuild.sh but I am assuming that is used after a successful build
> If these instruction need I tweek I can understand I can test them. If it 
> old and not supported a heads up would be appreciated. So I need something 
> like this below with everything needed to build a kernel including the 
> previous two steps as my two directories are on the wrong branches
>
> Thanks
>
>
> For TI v5.4.x: Real-Time
>
> #~/ti-linux-kernel-dev/
> git checkout origin/ti-linux-rt-5.4.y -b tmp
>
> Build:
>
>
>
>
> Build:
>
> #user@localhost:~/ti-linux-kernel-dev$
> ./build_kernel.s
>
>
>
> Build:
>
> #user@localhost:~/ti-linux-kernel-dev$
> ./build_kernel.s
>
>
> Build:
>
> #user@localhost:~/ti-linux-kernel-dev$
> ./build_kernel.sh
>
>
>
>
>
> On Friday, May 28, 2021, 02:56:38 PM CDT, Robert Nelson <
> robert...@gmail.com> wrote: 
>
>
> On Fri, May 28, 2021 at 2:53 PM Robert Nelson  wrote:
> >
> > On Fri, May 28, 2021 at 2:45 PM Robert Nelson  
> wrote:
> > >
> > > On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz  
> wrote:
> > > >
> > > > Thanks!!
> > > >
> > > > Think of it as I'm validating the instructions I think having these 
> is something good. Unfortunately my VM blew up just now.
> > > >
> > > > I KNOW your adamant about not supporting VM.
> > > >
> > > > So I'll build a dedicated Debian 8 dev box.
> > > >
> > > > Any hints tips lessons learned what you use be appreciated.
> > > >
> > > > Have a great long weekend.
> > >
> > > VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the
> > > failure point..
> >
> > I think mainline might work:
> >
> > debian@beaglebone:~$ uname -r
> > 5.13.0-rc3-bone2.2
> > debian@beaglebone:~$ dmesg | grep pru
> > [2.044506] remoteproc remoteproc1: 4a334000.pru is available
> > [2.045701] remoteproc remoteproc2: 4a338000.pru is available
> > debian@beaglebone:~$ ls /dev/remoteproc/pruss-core*
> > /dev/remoteproc/pruss-core0:
> > coredump  device  firmware  name  power  recovery  state  subsystem  
> uevent
> >
> > /dev/remoteproc/pruss-core1:
> > coredump  device  firmware  name  power  recovery  state  subsystem  
> uevent
> >
> > @Mark Yoder can you test? ;)
>
> debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "start" > state
> [  243.355728] remoteproc remoteproc1: powering up 4a334000.pru
> [  243.366533] remoteproc remoteproc1: Booting fw image
> am335x-pru0-fw, size 32456
> [  243.374135] remoteproc remoteproc1: remote processor 4a334000.pru is 
> now up
>
> debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "stop" > state
> [  296.981371] remoteproc remoteproc1: stopped remote processor 
> 4a334000.pru
>
>
> Regards,
>
> -- 
> Robert Nelson
> https://rcn-ee.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/6dcb2683-2d69-45fa-a4a8-62bb6c6e3ed0n%40googlegroups.com.

Re: [beagleboard] Re: Verifying Yocto image in Beagle

[amf]

short answer, yes yocto gatesgarth  branch does work on BBB,
However I have two meta- bbb and jumpnow from jumpnowtek, 
I can ssh in as root with a password (provided in local.conf)

On Tuesday, April 20, 2021 at 4:03:09 AM UTC-5 muruges...@gmail.com wrote:

> I tried with debug-tweaks option. I have built the image with 
> openssh-sftp-server and booted BBB.
> But still It is not working for me. I am not able to connect with BBB 
> through ssh from my computer(Ubuntu).
> Note: I am building using core-minimal-image
>
> Any support please.
>
> On Mon, 19 Apr 2021, 9:13 pm amf,  wrote:
>
>> The following applies if you have BBB w/o wireless, other wise you have 
>> to build with wpa_supplicant and firmware.
>> if you have this in conf/local.conf, you should be able to ssh in as root 
>> without a password (been a while, going from memory)
>> EXTRA_IMAGE_FEATURES = "debug-tweaks"
>>
>> adding this to conf/local.conf will set root password
>> INHERIT += "extrausers"
>> EXTRA_USERS_PARAMS = "usermod -P rootpassword root; "
>>
>> you will need to have openssh-server or equivalent for ssh
>>
>>
>> On Monday, April 19, 2021 at 6:21:45 AM UTC-5 muruges...@gmail.com wrote:
>>
>>> Hello
>>>
>>> I have built the Yocto gatesgarth image for Beaglebone black. Then I 
>>> loaded the image in SD card and booted with beagle.
>>>
>>> Is there any way to check whether the image is built and working with 
>>> beagle correctly?
>>>
>>> Please suggest.
>>>
>>> Note: I don't have UART to usb converter with me.
>>>
>>> Thanks.
>>>
>>> -- 
>> 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/646f83d8-ef90-4e16-a3a7-76d889d778a4n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/beagleboard/646f83d8-ef90-4e16-a3a7-76d889d778a4n%40googlegroups.com?utm_medium=email_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/ddb47011-db93-4730-b0a5-fc3eac88d031n%40googlegroups.com.

[beagleboard] Re: Verifying Yocto image in Beagle

[amf]

The following applies if you have BBB w/o wireless, other wise you have to 
build with wpa_supplicant and firmware.
if you have this in conf/local.conf, you should be able to ssh in as root 
without a password (been a while, going from memory)
EXTRA_IMAGE_FEATURES = "debug-tweaks"

adding this to conf/local.conf will set root password
INHERIT += "extrausers"
EXTRA_USERS_PARAMS = "usermod -P rootpassword root; "

you will need to have openssh-server or equivalent for ssh


On Monday, April 19, 2021 at 6:21:45 AM UTC-5 muruges...@gmail.com wrote:

> Hello
>
> I have built the Yocto gatesgarth image for Beaglebone black. Then I 
> loaded the image in SD card and booted with beagle.
>
> Is there any way to check whether the image is built and working with 
> beagle correctly?
>
> Please suggest.
>
> Note: I don't have UART to usb converter with me.
>
> Thanks.
>
>

-- 
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/646f83d8-ef90-4e16-a3a7-76d889d778a4n%40googlegroups.com.

[beagleboard] Re: Connecting RS232 with Beaglebone black Wireless

[amf]

I have a BBB non-wireless, serial is on J1 (maybe wireless called it 
something else) anyway, as long as you ttl is 3.3 volts you should be ok. 


On Monday, April 5, 2021 at 8:25:10 AM UTC-5 pranav...@teksun.com wrote:

> hello,
>
> I am trying to connect a RS232 to ttl module with my beaglebone black 
> wireless on X1 headers with are used for serial  communication. I don't 
> know if I can connect my RS232 to ttl with an RS232 male to USB male and 
> can I establish serial connection through it??
>
> So, the final heirarchy of my connection is 
> *USB(M)>RS232(M)>RS232-to-ttl>X1 header of BB black*
>
> Please let me know if I am going right.
>
>
>

-- 
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/b1ebe416-6610-4d5d-bf20-1a8f49fc035fn%40googlegroups.com.

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

[amf]

I'm going out on the limb here, but putty seem to have an issue with logins 
without a password. I'm sure some one can provide more input on this.

On Wednesday, March 31, 2021 at 12:59:59 PM UTC-5 propg...@gmail.com wrote:

>
> debian@beaglebone:/mnt/media/etc$ su root
> Password:
> su: Authentication failure
> debian@beaglebone:/mnt/media/etc$ su root
> Password:
> su: Authentication failure
> debian@beaglebone:/mnt/media/etc$ sudo nano shadow
>   GNU nano 2.7.4 File: shadow
>
> root::18717:0:9:7:::
> daemon:*:18112:0:9:7:::
> bin:*:18112:0:9:7:::
> sys:*:18112:0:9:7:::
> sync:*:18112:0:9:7:::
> games:*:18112:0:9:7:::
> man:*:18112:0:9:7:::
> lp:*:18112:0:9:7:::
> mail:*:18112:0:9:7:::
> news:*:18112:0:9:7:::
> uucp:*:18112:0:9:7:::
> proxy:*:18112:0:9:7:::
> www-data:*:18112:0:9:7:::
> backup:*:18112:0:9:7:::
> list:*:18112:0:9:7:::
> irc:*:18112:0:9:7:::
> gnats:*:18112:0:9:7:::
> nobody:*:18112:0:9:7:::
> systemd-timesync:*:18112:0:9:7:::
> systemd-network:*:18112:0:9:7:::
> systemd-resolve:*:18112:0:9:7:::
> systemd-bus-proxy:*:18112:0:9:7:::
> _apt:*:18112:0:9:7:::
> dnsmasq:*:18112:0:9:7:::
> messagebus:*:18112:0:9:7:::
> avahi:*:18112:0:9:7:::
> sshd:*:18112:0:9:7:::
> usbmux:*:18112:0:9:7:::
> lightdm:*:18112:0:9:7:::
> debian:rcdjoac1gVi9g:18112:0:9:7:::
> bob::18717:0:9:7:::
>
>
>
>
>
>
>
>
>
>
>[ Read 31 lines ]
> ^G Get Help ^O Write Out^W Where Is ^K Cut Text ^J Justify 
>  ^C Cur Pos  ^Y Prev PageM-\ First Line
> ^X Exit ^R Read File^\ Replace  ^U Uncut Text   ^T To 
> Spell ^_ Go To Line   ^V Next PageM-/ Last Line
>
> On Wed, Mar 31, 2021 at 10:23 AM Bob Hammond  wrote:
>
>> Well, I thought it worked great but it doesn't.
>>
>> I applied all these commands to the BBB in question and specifically to 
>> the root password entry but I am still unable to get into it.
>> When I attempt to log in with root, and enter a null password, I still 
>> get "access denied".  Same with all other usernames and passwords.
>>
>> Could it be a file permissions problem?
>>
>> On Wed, Mar 31, 2021 at 9:10 AM Bob Hammond  wrote:
>>
>>> amf,
>>>
>>> THIS works great!  Thanks so much for the help.
>>>
>>> On Tue, Mar 30, 2021 at 8:52 AM amf  wrote:
>>>
>>>> If you just want to reset the password on the new imaged BBB (this does 
>>>> not explain why you had issue in the first place, but does allow you to 
>>>> access the system)
>>>> clear the encrypted password as follows, (if you need detailed steps 
>>>> let me know)
>>>> create a sdcard with a new image (one you download) and boot the BBB 
>>>> with it.
>>>> then mount the emmc device 
>>>> edit /etc/shadow file in the mounted emmc device (requires sudo)
>>>> find the user name you want to remove the password on 
>>>> for example, my user name is 'amf'
>>>> amf:$6$jlBY96dq$V7tFs2xEv.a3kXArkyTEcEbGDX43d6UpzMcy/aplV8khxUFJKPMg0ugGBfWVZMpJRpaMXAATEAb5inu7/G.Iz1:16406:0:9:7:::
>>>>  
>>>>
>>>> delete the stuff between the first two '::' 
>>>> pi::16406:0:9:7:::
>>>> save the shadow file
>>>> power off the BBB
>>>> remove sdcard, and power on the BBB
>>>> log in with the user name that the encrypted password was deleted on, 
>>>> no login password is required, then set new password for the user.
>>>>
>>>> Hope this helps.
>>>> amf
>>>> On Tuesday, March 30, 2021 at 9:02:25 AM UTC-5 propg...@gmail.com 
>>>> wrote:
>>>>
>>>>> I am now attempting to get into GRUB during boot.  I never see a GRUB 
>>>>> menu show up by pressing/holding ESC or left shift.  What I do see is 
>>>>> that 
>>>>> I can interrupt boot by pressing the spacebar.  I then get a command 
>>>>> prompt 
>>>>> in ??.  And I have no idea what to do after that.
>>>>>
>>>>> On Monday, March 29, 2021 at 6:27:52 AM UTC-7 Bob Hammond wrote:
>>>>>
>>>>>> Thanks Andrea.  Once I get in, I will check the logs.  The sshd is 
>>>>>> likely up as you state.  The BBB is protected by a firewall on my router 
>>>>>> as 
>

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

[amf]

If you just want to reset the password on the new imaged BBB (this does not 
explain why you had issue in the first place, but does allow you to access 
the system)
clear the encrypted password as follows, (if you need detailed steps let me 
know)
create a sdcard with a new image (one you download) and boot the BBB with 
it.
then mount the emmc device 
edit /etc/shadow file in the mounted emmc device (requires sudo)
find the user name you want to remove the password on 
for example, my user name is 'amf'
amf:$6$jlBY96dq$V7tFs2xEv.a3kXArkyTEcEbGDX43d6UpzMcy/aplV8khxUFJKPMg0ugGBfWVZMpJRpaMXAATEAb5inu7/G.Iz1:16406:0:9:7:::
 

delete the stuff between the first two '::' 
pi::16406:0:9:7:::
save the shadow file
power off the BBB
remove sdcard, and power on the BBB
log in with the user name that the encrypted password was deleted on, no 
login password is required, then set new password for the user.

Hope this helps.
amf
On Tuesday, March 30, 2021 at 9:02:25 AM UTC-5 propg...@gmail.com wrote:

> I am now attempting to get into GRUB during boot.  I never see a GRUB menu 
> show up by pressing/holding ESC or left shift.  What I do see is that I can 
> interrupt boot by pressing the spacebar.  I then get a command prompt in 
> ??.  And I have no idea what to do after that.
>
> On Monday, March 29, 2021 at 6:27:52 AM UTC-7 Bob Hammond wrote:
>
>> Thanks Andrea.  Once I get in, I will check the logs.  The sshd is likely 
>> up as you state.  The BBB is protected by a firewall on my router as well 
>> as iptables.  And no, I didn't have enforced sshd to accept only user 
>> connection.
>>
>> All very good ideas!
>>
>>
>> On Sunday, March 28, 2021 at 6:05:22 AM UTC-7 andrea@gmail.com wrote:
>>
>>> I found this for the serial connection.
>>>
>>>
>>> https://www.dummies.com/computers/beaglebone/how-to-connect-the-beaglebone-black-via-serial-over-usb/
>>>
>>> Some ideas :
>>> Once in as root, I would 
>>> - change the root password :
>>> # passwd
>>> - The user password:
>>> # passwd username
>>> Check the logs focus in the time you had attempted the remote login - 
>>> find why it was not allowed to login.
>>> Check the sshd service is enabled  (however should be up) 
>>> Have you hardened your configuration? Ie any firewall (iptables) , any 
>>> fail2ban or something else;
>>> Enforced  sshd to accept only user connection (no root)?
>>>
>>> A.
>>>
>>> On Sun, 28 Mar 2021, 14:48 Bob Hammond,  wrote:
>>>
>>>> I am using a windows machine with PuTTY to connect to the BBB.
>>>>
>>>> On Sun, Mar 28, 2021 at 5:44 AM Bob Hammond  wrote:
>>>>
>>>>> I am able to connect to the BBB with PuTTY and get a prompt to log 
>>>>> in.  I have tried debian/temppwd and that doesn't work.
>>>>>
>>>>> I've read about using a serial connection to the BBB and interrupting 
>>>>> the boot sequence to gain access.  Anyone done that?
>>>>>
>>>>> On Saturday, March 27, 2021 at 4:41:30 PM UTC-7 myi...@hotmail.com 
>>>>> wrote:
>>>>>
>>>>>> 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:
>>>>>>
&

[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] Re: Servomotor Herkulex Beaglebone

[amf]

page 17 of the manual that Dennis attached implies that a serial interface 
module is needed. see the second caution on that page.


On Friday, March 19, 2021 at 7:24:31 AM UTC-5 Dennis Bieber wrote:

> On Thu, 18 Mar 2021 08:27:40 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user Adnane Dinar
>  wrote:
>
> >I need someone who know how control a herkulex servo with my beagle bone 
> in 
> >python or c 
>
> Typically, servos are controlled by using a PWM signal. cf:
> https://stackoverflow.com/questions/50203064/pwm-on-beaglebone-black-v4-14
>
> However, the documentation for this servo
>
> https://www.robotshop.com/media/files/pdf2/_eng_herkulex_manual_20140218.pdf
> indicates that this servo uses 115200bps 8n1 TTL level SERIAL communication
> -- eg: a UART.
>
> Unfortunately, the diagram on page 51 indicates that "TTL" means
> original 5V TTL. 5V will kill a Beagle -- the pins are limited to 3.3V. The
> diode/resistor set shown at the top left /might/ imply that the TTL is
> using a pull-up circuit -- in which case feeding 3.3V instead of 5V may be
> sufficient.
>
>
> -- 
> 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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/eba5bae0-eb23-4798-a8ed-c19e2efafaffn%40googlegroups.com.

[beagleboard] Re: BBB

[amf]

Please clarify, soft copy of what?

On Friday, February 26, 2021 at 10:13:40 AM UTC-6 kushaln...@gmail.com 
wrote:

>
> HI,
>
> I need soft copy of 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/6ea53f4f-940b-4ad7-8385-e5c787972aa4n%40googlegroups.com.

[beagleboard] Re: Super Dumbbutt Move

[amf]

Here is what I used the last time I tested it. the '--in-interface' value 
will be machine specific.
fyi, copy paste messes with '-' and '--' 

# required on BBB 
echo "nameserver 8.8.8.8" | sudo tee /etc/resolv.conf 
sudo route add default gw 192.168.7.1

# Ubuntu 18.04 Desktop
sudo iptables --table nat --append POSTROUTING --out-interface enp0s25 -j 
MASQUERADE 
sudo iptables --append FORWARD --in-interface enxb0d5cccd8ab8 -j ACCEPT 
echo 1 | sudo tee /proc/sys/net/ipv4/ip_forward

Hope it helps,

On Tuesday, February 9, 2021 at 7:48:40 PM UTC-6 Matthew Wright wrote:

> Hello I started to this procedure to connect my bbb to the internet 
> through my computer.  
>
>
> https://www.digikey.com/en/maker/blogs/how-to-connect-a-beaglebone-black-to-the-internet-using-usb#:~:text=You%20now%20need%20to%20share,connection%E2%80%9D%2C%20then%20click%20ok
> .
>
> I ran 
>
> sudo /sbin/route add default gw 192.168.7.1
>
> on the bbb  (debian)
>
> Now I can only connect to the device through wifi.  I lost my usb 
> connection.  I tried to remove the default
>
> sudo /sbin/route del default gw 192.168.7.1
>
> but that didn't help.  
>
> I would like the bbb to get the internet through the wifi and connect to 
> my computer through the usb connection.
>
>

-- 
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/6b086c2c-00a2-4546-90f4-b35cd9950796n%40googlegroups.com.

[beagleboard] Re: Interfacing a 16x2 char HD44780 LCD display

[amf]

I may not have answered your question, the dts is bbb-4dcape70t

On Tuesday, November 3, 2020 at 3:36:42 PM UTC-6 amf wrote:

> Hi Mark,
> I do custom builds with yocto, the meta data is from jumpnowtek. kernel 
> version linux-stable_5.7
> In addition to the info that RCN provided, I added the pin mux stuff to 
> define all the gpio pins. 
>
> looked at the driver for the R/W issue, seems they do not set the R/W bit, 
> they do set the RS bit, so maybe just need to add the same for the R/W bit. 
>
> amf
>
>
>
> On Tuesday, November 3, 2020 at 1:29:28 PM UTC-6 Mark A. Yoder wrote:
>
>> Thanks to all for following up on this.  
>>
>> amf:  What device tree are you using?
>>
>> --Mark
>>
>> On Tuesday, November 3, 2020 at 10:26:52 AM UTC-5 amf wrote:
>>
>>> Just wanting to follow up on this. The LCD display is working, just had 
>>> to remove the R/W parameter from the dts and tie the LCD R/W to ground. The 
>>> driver does not seem to support reading from the display, so no harm in 
>>> doing it this way.
>>>
>>> amf
>>>
>>> On Monday, November 2, 2020 at 6:56:25 PM UTC-6 amf wrote:
>>>
>>>> Hi Mark
>>>> Seen RCN's response below. I have several of the *hd44780 LCD displays 
>>>> also, *spent the weekend trying to get it to work with the info RCN 
>>>> provided. Seems the R/W line is always high, thus all the data signals are 
>>>> distorted. If I pull the R/W line low, then the data signals are ok, but 
>>>> nothing is written to the display. I know the displays are good, I wrote a 
>>>> uart-to-parallel with an atmel chip several years ago. if you have success 
>>>> with the Linux driver, I would like to know. 
>>>> amf
>>>>
>>>> On Thursday, October 29, 2020 at 1:39:54 PM UTC-5 Mark A. Yoder wrote:
>>>>
>>>>> I've just recently discovered I have access to lots of 16x2 LCD 
>>>>> displays.
>>>>>
>>>>> I see there are many examples of interfacing it to a Linux machine, 
>>>>> but most are via user space.  I'm looking for kernel space examples.  
>>>>> *modinfo 
>>>>> hd44780* shows a driver is there, but how do I use it.  
>>>>>
>>>>> Is there a device tree for the hd44780 for a parallel interface?
>>>>>
>>>>> --Mark
>>>>>
>>>>

-- 
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/4ee6f3ed-d7e1-42ec-a3bd-d882e445b290n%40googlegroups.com.

[beagleboard] Re: Interfacing a 16x2 char HD44780 LCD display

[amf]

Hi Mark,
I do custom builds with yocto, the meta data is from jumpnowtek. kernel 
version linux-stable_5.7
In addition to the info that RCN provided, I added the pin mux stuff to 
define all the gpio pins. 

looked at the driver for the R/W issue, seems they do not set the R/W bit, 
they do set the RS bit, so maybe just need to add the same for the R/W bit. 

amf



On Tuesday, November 3, 2020 at 1:29:28 PM UTC-6 Mark A. Yoder wrote:

> Thanks to all for following up on this.  
>
> amf:  What device tree are you using?
>
> --Mark
>
> On Tuesday, November 3, 2020 at 10:26:52 AM UTC-5 amf wrote:
>
>> Just wanting to follow up on this. The LCD display is working, just had 
>> to remove the R/W parameter from the dts and tie the LCD R/W to ground. The 
>> driver does not seem to support reading from the display, so no harm in 
>> doing it this way.
>>
>> amf
>>
>> On Monday, November 2, 2020 at 6:56:25 PM UTC-6 amf wrote:
>>
>>> Hi Mark
>>> Seen RCN's response below. I have several of the *hd44780 LCD displays 
>>> also, *spent the weekend trying to get it to work with the info RCN 
>>> provided. Seems the R/W line is always high, thus all the data signals are 
>>> distorted. If I pull the R/W line low, then the data signals are ok, but 
>>> nothing is written to the display. I know the displays are good, I wrote a 
>>> uart-to-parallel with an atmel chip several years ago. if you have success 
>>> with the Linux driver, I would like to know. 
>>> amf
>>>
>>> On Thursday, October 29, 2020 at 1:39:54 PM UTC-5 Mark A. Yoder wrote:
>>>
>>>> I've just recently discovered I have access to lots of 16x2 LCD 
>>>> displays.
>>>>
>>>> I see there are many examples of interfacing it to a Linux machine, but 
>>>> most are via user space.  I'm looking for kernel space examples.  *modinfo 
>>>> hd44780* shows a driver is there, but how do I use it.  
>>>>
>>>> Is there a device tree for the hd44780 for a parallel interface?
>>>>
>>>> --Mark
>>>>
>>>

-- 
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/6149769b-4050-4ca7-a0c4-cba6b642bd23n%40googlegroups.com.

[beagleboard] Re: Interfacing a 16x2 char HD44780 LCD display

[amf]

Just wanting to follow up on this. The LCD display is working, just had to 
remove the R/W parameter from the dts and tie the LCD R/W to ground. The 
driver does not seem to support reading from the display, so no harm in 
doing it this way.

amf

On Monday, November 2, 2020 at 6:56:25 PM UTC-6 amf wrote:

> Hi Mark
> Seen RCN's response below. I have several of the *hd44780 LCD displays 
> also, *spent the weekend trying to get it to work with the info RCN 
> provided. Seems the R/W line is always high, thus all the data signals are 
> distorted. If I pull the R/W line low, then the data signals are ok, but 
> nothing is written to the display. I know the displays are good, I wrote a 
> uart-to-parallel with an atmel chip several years ago. if you have success 
> with the Linux driver, I would like to know. 
> amf
>
> On Thursday, October 29, 2020 at 1:39:54 PM UTC-5 Mark A. Yoder wrote:
>
>> I've just recently discovered I have access to lots of 16x2 LCD displays.
>>
>> I see there are many examples of interfacing it to a Linux machine, but 
>> most are via user space.  I'm looking for kernel space examples.  *modinfo 
>> hd44780* shows a driver is there, but how do I use it.  
>>
>> Is there a device tree for the hd44780 for a parallel interface?
>>
>> --Mark
>>
>

-- 
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/43062355-7d24-40aa-a24d-2c0753116e5en%40googlegroups.com.

[beagleboard] Re: Interfacing a 16x2 char HD44780 LCD display

[amf]

Hi Mark
Seen RCN's response below. I have several of the *hd44780 LCD displays 
also, *spent the weekend trying to get it to work with the info RCN 
provided. Seems the R/W line is always high, thus all the data signals are 
distorted. If I pull the R/W line low, then the data signals are ok, but 
nothing is written to the display. I know the displays are good, I wrote a 
uart-to-parallel with an atmel chip several years ago. if you have success 
with the Linux driver, I would like to know. 
amf

On Thursday, October 29, 2020 at 1:39:54 PM UTC-5 Mark A. Yoder wrote:

> I've just recently discovered I have access to lots of 16x2 LCD displays.
>
> I see there are many examples of interfacing it to a Linux machine, but 
> most are via user space.  I'm looking for kernel space examples.  *modinfo 
> hd44780* shows a driver is there, but how do I use it.  
>
> Is there a device tree for the hd44780 for a parallel interface?
>
> --Mark
>

-- 
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/8b717597-fc50-4b33-bc6a-27a96032e4b8n%40googlegroups.com.

[beagleboard] Re: 4G dongle keeps debouncing

[amf]

don't know about this dongle, but a quick google, this device seems to have 
several modes of operation. your log shows it changing pid which implies it 
is changing modes. see the following link, they seemed to have had the same 
issue and have posted a possible solution. 

https://gist.github.com/jfstenuit/13becfe728046074f5aaa0cb7f899ab9

On Wednesday, October 28, 2020 at 6:16:13 PM UTC-5 atiqu...@gmail.com wrote:

>
> HI All,
> I have a 4G dongle which keep on denouncing between two interfaces
> Kernel version "3.8.13-bone80" (Sorry we are stuck with this)
> here is dmesg for the dongle behavior:
> [ 1764.764123] usb 1-1.1: Product: HUAWEI_MOBILE
> [ 1764.764133] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
> [ 1764.764573] usb 1-1.1: usb_probe_device
> [ 1764.764589] usb 1-1.1: configuration #1 chosen from 1 choice
> [ 1764.815748] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
> [ 1764.816114] cdc_ether 1-1.1:1.0: usb_probe_interface
> [ 1764.816185] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
> [ 1764.842656] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at 
> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
> [ 1764.842806] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
> [ 1764.843398] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1767.309575] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1767.309715] hub 1-1:1.0: port 1, status 0100, change 0001, 12 Mb/s
> [ 1767.309734] usb 1-1.1: USB disconnect, device number 95
> [ 1767.309745] usb 1-1.1: unregistering device
> [ 1767.309757] usb 1-1.1: unregistering interface 1-1.1:1.0
> [ 1767.309972] cdc_ether 1-1.1:1.0 eth1: unregister 'cdc_ether' 
> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device
> [ 1767.316709] usb 1-1.1: unregistering interface 1-1.1:1.1
> [ 1767.317000] usb 1-1.1: usb_disable_device nuking all URBs
> [ 1767.535142] hub 1-1:1.0: debounce: port 1: total 200ms stable 100ms 
> status 0x101
> [ 1767.601538] usb 1-1.1: new high-speed USB device number 96 using 
> musb-hdrc
> [ 1767.615236] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
> [ 1767.695706] usb 1-1.1: default language 0x0409
> [ 1767.695919] usb 1-1.1: udev 96, busnum 1, minor = 95
> [ 1767.695933] usb 1-1.1: New USB device found, idVendor=12d1, 
> idProduct=1f01
> [ 1767.695945] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 1767.695955] usb 1-1.1: Product: HUAWEI_MOBILE
> [ 1767.695964] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
> [ 1767.695973] usb 1-1.1: SerialNumber: 0123456789ABCDEF
> [ 1767.696417] usb 1-1.1: usb_probe_device
> [ 1767.696434] usb 1-1.1: configuration #1 chosen from 1 choice
> [ 1767.696943] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
> [ 1767.697360] usb-storage 1-1.1:1.0: usb_probe_interface
> [ 1767.697387] usb-storage 1-1.1:1.0: usb_probe_interface - got id
> [ 1767.700483] scsi418 : usb-storage 1-1.1:1.0
> [ 1767.701194] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1768.368244] usb-storage 1-1.1:1.0: disconnect by usbfs
> [ 1768.589625] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
> [ 1768.589777] hub 1-1:1.0: port 1, status 0101, change 0001, 12 Mb/s
> [ 1768.589863] usb 1-1.1: USB disconnect, device number 96
> [ 1768.589875] usb 1-1.1: unregistering device
> [ 1768.589887] usb 1-1.1: unregistering interface 1-1.1:1.0
> [ 1768.590231] usb 1-1.1: usb_disable_device nuking all URBs
> [ 1768.699418] hub 1-1:1.0: debounce: port 1: total 100ms stable 100ms 
> status 0x101
> [ 1768.765758] usb 1-1.1: new high-speed USB device number 97 using 
> musb-hdrc
> [ 1768.779445] hub 1-1:1.0: port 1 not reset yet, waiting 10ms
> [ 1768.859861] usb 1-1.1: skipped 1 descriptor after configuration
> [ 1768.859886] usb 1-1.1: skipped 3 descriptors after interface
> [ 1768.859995] usb 1-1.1: default language 0x0409
> [ 1768.860170] usb 1-1.1: udev 97, busnum 1, minor = 96
> [ 1768.860184] usb 1-1.1: New USB device found, idVendor=12d1, 
> idProduct=14db
> [ 1768.860196] usb 1-1.1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=0
> [ 1768.860206] usb 1-1.1: Product: HUAWEI_MOBILE
> [ 1768.860215] usb 1-1.1: Manufacturer: HUAWEI_MOBILE
> [ 1768.860673] usb 1-1.1: usb_probe_device
> [ 1768.860692] usb 1-1.1: configuration #1 chosen from 1 choice
> [ 1768.912011] usb 1-1.1: adding 1-1.1:1.0 (config #1, interface 0)
> [ 1768.912540] cdc_ether 1-1.1:1.0: usb_probe_interface
> [ 1768.912557] cdc_ether 1-1.1:1.0: usb_probe_interface - got id
> [ 1768.939763] cdc_ether 1-1.1:1.0 eth1: register 'cdc_ether' at 
> usb-musb-hdrc.1.auto-1.1, CDC Ethernet Device, 00:1e:10:1f:00:00
> [ 1768.939972] usb 1-1.1: adding 1-1.1:1.1 (config #1, interface 1)
> [ 1768.940562] hub 1-1:1.0: state 7 ports 4 chg  evt 0002
>
> This keep on repeating forever.
> Any help is appreciated
>

-- 
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 

[beagleboard] Re: Temporary failure resolving 'deb.debian.org'

[amf]

can you ping 8.8.8.8?
if not, then does /etc/resolv.conf have "nameserver 8.8.8.8" or "nameserver 
8.8.4.4"?
if nameserver is not in resolv.conf, you need to add one there.
If you have the above, then there is some other issue. need more info
like does your board have an ip.

amf

On Friday, October 16, 2020 at 7:35:05 AM UTC-5 divyansh verma wrote:

> i am using debian 9 on bbb over NFS using ethernet cable and not able to 
> access internet, screenshot attached below please help
>
>

-- 
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/6d11c97e-ebfe-47bf-9d38-846573501a54n%40googlegroups.com.

Re: [beagleboard] Re: Can't connet to BBB over Ethernet

[amf]

try setting your gateway, in your case it should be 192.168.0.1, this is 
the routers ip, at lease in my case.

On Monday, October 12, 2020 at 8:46:40 AM UTC-5 py.o...@sunrise.ch wrote:

> Could someone share their wired connection settings on a Linux machine 
> (preferably on Ubuntu).
> In my case I can't share wifi Internet connection on Ubuntu with BBB. BBB 
> is connected to Ubuntu over ssh(ethernet cable) also over terminal.
> With these setting (please, see screenshot below) I can connect to BBB 
> over *ssh*, but can't get Internet. When I specify *DHCP* nothing works: 
> I even can't get connection over *ssh*.
> Thanks.
>
> [image: Screenshot from 2020-10-12 15-38-59.png]
>
>

-- 
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/a212c2ff-6d77-47c8-b3e2-c7cc16f4b863n%40googlegroups.com.

[beagleboard] Re: External USB 2TB HD not spinning up.

[amf]

My experience,
I have had a BBB powered with an external 2amp supply with an external ssd 
plugged into usb port for over a year with no issues. In the last several 
months or so, the drive was not available via samba at least twice a week, 
had to reboot BBB to get smb drive back. added a powered usb hub for the 
ssd, and  all is back to normal. 
do updates on this system every so often. 
Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 2018 
armv7l GNU/Linux
I know this is not a one to one, but maybe it helps.

On Thursday, September 10, 2020 at 11:59:10 AM UTC-5 dan.ann...@gmail.com 
wrote:

> I have a WD 2TB external USB drive. It mounts fine on my linux laptop. 
> When I plug it into the beagleboneblack, it times out.  Any help would be 
> appreciated!
>
> lsusb finds the device:
> Bus 001 Device 003: ID 1058:2626 Western Digital Technologies, Inc. 
> Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>
> dmesg:
> [ 3965.568158] musb-hdrc musb-hdrc.1: VBUS_ERROR in a_wait_bcon (89, 
>  [ 3966.776484] usb 1-1: new high-speed USB device number 3 using musb-hdrc
> [ 3966.977419] usb 1-1: New USB device found, idVendor=1058, 
> idProduct=2626, bcdDevice=10.28
> [ 3966.977438] usb 1-1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [ 3966.977446] usb 1-1: Product: My Passport 2626
> [ 3966.977454] usb 1-1: Manufacturer: Western Digital
> [ 3966.977461] usb 1-1: SerialNumber: 5758573245313048344E394B
> [ 3966.985267] usb-storage 1-1:1.0: USB Mass Storage device detected
> [ 3967.008783] scsi host0: usb-storage 1-1:1.0
> [ 3968.041574] scsi 0:0:0:0: Direct-Access WD   My Passport 2626 
> 1028 PQ: 0 ANSI: 6
> [ 3968.042213] scsi 0:0:0:1: Enclosure WD   SES Device   
> 1028 PQ: 0 ANSI: 6
> [ 3968.055140] sd 0:0:0:0: Attached scsi generic sg0 type 0
> [ 3968.061239] scsi 0:0:0:1: Attached scsi generic sg1 type 13
> [ 3968.063025] sd 0:0:0:0: [sda] Spinning up disk...
> [ 3969.096578] ...not responding...
>
>
> The BBB specs:
>
> System:Host: DataIntegrity-Secondary Kernel: 4.19.94-ti-r42 armv7l 
> bits: 32 compiler: gcc v: 8.3.0 Console: tty 1 dm: N/A 
>Distro: Debian GNU/Linux 10 (buster) 
> Machine:   Type: ARM Device System: TI AM335x BeagleBone Black details: 
> Generic AM33XX rev: N/A serial: 1516BBBK13E1 
> Memory:RAM: total: 483.4 MiB used: 128.3 MiB (26.5%) 
>RAM Report: unknown-error: dmidecode was unable to generate 
> data 
> PCI Slots: ARM: No ARM data found for this feature. 
> CPU:   Topology: Single Core model: ARMv7 v7l variant: cortex-a8 bits: 
> 32 type: UP arch: v7l family: 7 model-id: 3 
>stepping: 2 microcode: N/A bogomips: 995 
>Speed: 1000 MHz min/max: 300/1000 MHz Core speed (MHz): 1: 1000 
>Features: edsp fastmult half neon thumb thumbee tls vfp vfpd32 
> vfpv3 
>Vulnerabilities: No CPU vulnerability/bugs data available. 
> Graphics:  Message: No ARM data found for this feature. 
>Display: tty server: N/A driver: tty: 197x45 
>Message: Advanced graphics data unavailable in console for 
> root. 
> Audio: Device-1: simple-audio-card driver: asoc_simple_card bus ID: 
> N/A chip ID: simple-audio-card:sound 
>Sound Server: ALSA v: k4.19.94-ti-r42 
> Network:   Message: No ARM data found for this feature. 
>IF-ID-1: can0 state: down mac: N/A 
>IF-ID-2: can1 state: down mac: N/A 
>IF-ID-3: eth0 state: up speed: 100 Mbps duplex: full mac: 
> 80:30:dc:53:f6:f6 
>IP v4: 192.168.1.212/24 scope: global broadcast: 192.168.1.255 
>IP v6: 2600:1700:6d52:b1f0:8230:dcff:fe53:f6f6/64 type: dynamic 
> mngtmpaddr scope: global 
>IP v6: 2600:1700:6d52:b1f0::31/64 scope: global 
>IP v6: fe80::8230:dcff:fe53:f6f6/64 scope: link 
>IF-ID-4: usb0 state: up speed: N/A duplex: N/A mac: 
> 80:30:dc:53:f6:f8 
>IP v4: 192.168.7.2/24 scope: global broadcast: 192.168.7.255 
>IP v6: fe80::8230:dcff:fe53:f6f8/64 scope: link 
>IF-ID-5: usb1 state: up speed: N/A duplex: N/A mac: 
> 80:30:dc:53:f6:fc 
>IP v4: 192.168.6.2/24 scope: global broadcast: 192.168.6.255 
>IP v6: fe80::8230:dcff:fe53:f6fc/64 scope: link 
>WAN IP: No WAN IP data found. Connected to the web? SSL issues? 
> Drives:Local Storage: total: 3.56 GiB used: 2.34 GiB (65.6%) 
>ID-1: /dev/mmcblk1 model: S10004 size: 3.56 GiB block size: 
> physical: 512 B logical: 512 B serial: 0x7ae2584c 
>rev: 0x6 scheme: MBR 
>Message: No Optical or Floppy data was found. 
> RAID:  Message: No RAID data was found. 
> Partition: ID-1: / raw size: 3.56 GiB size: 3.44 GiB (96.67%) used: 2.34 
> GiB (67.9%) fs: ext4 block size: 4096 B 
>dev: /dev/mmcblk1p1 label: rootfs uuid: 
> 39168434-dd05-449f-aa8a-c455aec0e138 
> Unmounted: Message: No unmounted partitions 

Re: [beagleboard] Re: 192.168.7.2 is NOT opening or reachable

[amf]

Only way to update the emmc os without a ethernet connection is by using a 
USB-to-SERIAL adapter, make sure to get the 3.3 volt version. 
Not sure if you answered the prior question. does your laptop show 
192.168.6.1 and/or 192.168.7.1 when doing 'ifconfig -a' from a terminal 
window? 
If it does, I don't see any reason why you cannot at least ping the BBB at 
6.2 or 7.2. 

On Tuesday, July 14, 2020 at 10:19:21 AM UTC-5, Pankaj Rai wrote:
>
> Hi,
> Currently I'm working with my personal laptop only. And also i've ordered 
> a 16 gb sd card for sure. But meanwhile i was trying to make it work with 
> with preinstalled os in eMMC only.
>
> Is there any way we can update the eMMC OS? So that it may able to connect 
> to 192.168.7.2 or 192.168.6.2 ( this is because somewhere i've seen that 
> Linux system uses this ip to connect with BBB).
>
> Thanks
> Pankaj
>
> On Tue, Jul 14, 2020, 20:25 amf > wrote:
>
>> connecting the ethernet to the computer will not provide you with an IP 
>> address on the BBB. BBB wants to use dhcp to get an IP, which what happens 
>> when connected to the router. 
>> You should be able to ping 192.168.7.2 from the laptop, if you see 
>> 192.168.7.1 on the laptop. 
>> Is this your personal laptop or a company laptop? companies tend to 
>> secure laptops such that ping and ssh aren't allowed (My personal 
>> experience)
>> Would recommend getting an sdcard, again if this is a company laptop, it 
>> may not help. 
>>
>>
>>
>> On Monday, July 13, 2020 at 9:58:28 PM UTC-5, Pankaj Rai wrote:
>>>
>>> Hi,
>>> Can we connect the BBB using ethernet cable to the computers ethernet 
>>> port?
>>> ( It's because I'm living in hostel and here we have the hostel wifi 
>>> available)
>>>
>>> And can we power the BBB using 5 V charger?
>>>
>>>
>>> If not, then will it work out on using the flashed sd card as boot? (I'm 
>>> thinking to buy one(16gb) for this if doesn't work)
>>>
>>> Thanks
>>> Pankaj
>>>
>>> On Tue, Jul 14, 2020, 00:19 Dennis Lee Bieber  
>>> wrote:
>>>
>>>> On Mon, 13 Jul 2020 23:24:06 +0530, in 
>>>> gmane.comp.hardware.beagleboard.user
>>>> Pankaj Rai <> wrote:
>>>>
>>>> >Hi,
>>>> >I've enabled the port 22 on my pc and I'm not using sd card for 
>>>> flashing so
>>>> >I don't think i need to press the s2 button.
>>>> >And also i don't have any debugger and i tried pinging the BBB on that
>>>> >address but it shows all the sent packets are lost so i think I'm 
>>>> unable to
>>>> >ping.
>>>> >
>>>> >Is there any other way to work this out?
>>>> >
>>>>
>>>> The surest is to NOT USE THE USB "network".
>>>>
>>>> I presume your main computer is connected to some router.
>>>>
>>>> Run an ethernet cable from the BBB to the same router. Connect 
>>>> a 5V
>>>> power supply to the barrel connector on the BBB. (If you must, you 
>>>> might be
>>>> able to use a 5V USB phone charger connected to the USB port -- but for
>>>> this debugging you do NOT want the USB port connected to the main
>>>> computer!)
>>>>
>>>> Check the router configuration pages for what IP # it assigned 
>>>> to the
>>>> BBB (note: if the router is modern enough, it may do DNS and have 
>>>> assigned
>>>> the host name beaglebone.local to the BBB, in which case you can connect
>>>> using the host name instead of the router assigned IP #).
>>>>
>>>> -=-=-=-
>>>> IP Allocation
>>>> IPv4 Address / Name MAC Address Status  Allocation  Action
>>>> 192.168.1.68 / EPSONF4EF32  00:26:ab:f4:ef:32   on  DHCP 
>>>> Allocation 
>>>> 192.168.1.65 / DIRECTV-HR54-C94828D718:16:c9:48:28:d9   on  
>>>> DHCP
>>>> Allocation  
>>>> 192.168.1.93 / unknown5ca39d084ab9  5c:a3:9d:08:4a:b9   on  
>>>> DHCP Allocation
>>>> 192.168.1.74 / unknown64c6670531d3  64:c6:67:05:31:d3   off
>>>>  DHCP
>>>> Allocation  
>>>> 192.168.1.70 / Galaxy-S98c:45:00:6d:1a:4c   on  DHCP 
>>>> Allocation 
>>>> 192.168.1.79 / pi-star-3b   b8:27:eb:4b:0b:d5   on  DHCP 
>>&g

Re: [beagleboard] Re: 192.168.7.2 is NOT opening or reachable

[amf]

connecting the ethernet to the computer will not provide you with an IP 
address on the BBB. BBB wants to use dhcp to get an IP, which what happens 
when connected to the router. 
You should be able to ping 192.168.7.2 from the laptop, if you see 
192.168.7.1 on the laptop. 
Is this your personal laptop or a company laptop? companies tend to secure 
laptops such that ping and ssh aren't allowed (My personal experience)
Would recommend getting an sdcard, again if this is a company laptop, it 
may not help. 



On Monday, July 13, 2020 at 9:58:28 PM UTC-5, Pankaj Rai wrote:
>
> Hi,
> Can we connect the BBB using ethernet cable to the computers ethernet port?
> ( It's because I'm living in hostel and here we have the hostel wifi 
> available)
>
> And can we power the BBB using 5 V charger?
>
>
> If not, then will it work out on using the flashed sd card as boot? (I'm 
> thinking to buy one(16gb) for this if doesn't work)
>
> Thanks
> Pankaj
>
> On Tue, Jul 14, 2020, 00:19 Dennis Lee Bieber  > wrote:
>
>> On Mon, 13 Jul 2020 23:24:06 +0530, in 
>> gmane.comp.hardware.beagleboard.user
>> Pankaj Rai <> wrote:
>>
>> >Hi,
>> >I've enabled the port 22 on my pc and I'm not using sd card for flashing 
>> so
>> >I don't think i need to press the s2 button.
>> >And also i don't have any debugger and i tried pinging the BBB on that
>> >address but it shows all the sent packets are lost so i think I'm unable 
>> to
>> >ping.
>> >
>> >Is there any other way to work this out?
>> >
>>
>> The surest is to NOT USE THE USB "network".
>>
>> I presume your main computer is connected to some router.
>>
>> Run an ethernet cable from the BBB to the same router. Connect a 
>> 5V
>> power supply to the barrel connector on the BBB. (If you must, you might 
>> be
>> able to use a 5V USB phone charger connected to the USB port -- but for
>> this debugging you do NOT want the USB port connected to the main
>> computer!)
>>
>> Check the router configuration pages for what IP # it assigned to 
>> the
>> BBB (note: if the router is modern enough, it may do DNS and have assigned
>> the host name beaglebone.local to the BBB, in which case you can connect
>> using the host name instead of the router assigned IP #).
>>
>> -=-=-=-
>> IP Allocation
>> IPv4 Address / Name MAC Address Status  Allocation  Action
>> 192.168.1.68 / EPSONF4EF32  00:26:ab:f4:ef:32   on  DHCP 
>> Allocation 
>> 192.168.1.65 / DIRECTV-HR54-C94828D718:16:c9:48:28:d9   on  
>> DHCP
>> Allocation  
>> 192.168.1.93 / unknown5ca39d084ab9  5c:a3:9d:08:4a:b9   on  
>> DHCP Allocation
>> 192.168.1.74 / unknown64c6670531d3  64:c6:67:05:31:d3   off
>>  DHCP
>> Allocation  
>> 192.168.1.70 / Galaxy-S98c:45:00:6d:1a:4c   on  DHCP 
>> Allocation 
>> 192.168.1.79 / pi-star-3b   b8:27:eb:4b:0b:d5   on  DHCP 
>> Allocation 
>> 192.168.1.252 / microdiversity  b8:27:eb:ce:b1:eb   on  DHCP 
>> Allocation 
>> 192.168.1.66 / ElusiveUnicorn   b8:ca:3a:79:0c:36   on  DHCP 
>> Allocation 
>> 192.168.1.84 / HP7C548D c4:65:16:7c:54:8d   on  DHCP 
>> Allocation 
>> 192.168.1.69 / beaglebone   d0:39:72:18:3e:e5   on  DHCP 
>> Allocation 
>> -=-=-=-
>>
>> (my router does not show the .local, but access from Win10 works with or
>> without it)
>>
>> Microsoft Windows [Version 10.0.19041.329]
>> (c) 2020 Microsoft Corporation. All rights reserved.
>>
>> C:\Users\Wulfraed>ping 192.168.1.69
>>
>> Pinging 192.168.1.69 with 32 bytes of data:
>> Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
>> Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
>> Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
>> Reply from 192.168.1.69: bytes=32 time<1ms TTL=64
>>
>> Ping statistics for 192.168.1.69:
>> Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
>> Approximate round trip times in milli-seconds:
>> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>>
>> C:\Users\Wulfraed>
>> C:\Users\Wulfraed>ssh deb...@192.168.1.69 
>> The authenticity of host '192.168.1.69 (192.168.1.69)' can't be
>> established.
>> ECDSA key fingerprint is
>> SHA256:PLZds8/FuHaVEqsTatoE6YFgSC+cakdD0OfPqEoTDQ8.
>> Are you sure you want to continue connecting (yes/no)? yes
>> Warning: Permanently added '192.168.1.69' (ECDSA) to the list of known
>> hosts.
>> Debian GNU/Linux 10
>>
>> BeagleBoard.org Debian Buster IoT Image 2020-04-06
>>
>> Support: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>>
>> default username:password is [debian:temppwd]
>>
>> deb...@192.168.1.69 's password:
>>
>> The programs included with the Debian GNU/Linux system are free software;
>> the exact distribution terms for each program are described in the
>> individual files in /usr/share/doc/*/copyright.
>>
>> Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
>> permitted by applicable law.
>> Last login: Sun Jul  5 

Re: [beagleboard] Re: 192.168.7.2 is NOT opening or reachable

[amf]

So this is the original image that came with the BBB?
Like some one else just mentioned, you may want to use a ethernet cable 
connected to your router. 
Without knowing what image is on the BBB, it's going to be difficult to 
trouble shoot this.



On Monday, July 13, 2020 at 12:14:00 PM UTC-5, Pankaj Rai wrote:
>
> Hi,
>
> Pc does play a sound while connecting BBB to pc. And I've not changed any 
> configuration of the BBB.
>
> Thanks.
>
> On Mon, Jul 13, 2020, 22:40 KenUnix > 
> wrote:
>
>> If you have not modified it's configuration you should ssh to 196.168.7.2
>>
>> 192.168.7.1 is the P.C. side.of the connection.
>>
>> When powering the BBB up and connecting the USB cable does the PC play 
>> the UP tone?
>>
>>
>> -- 
>> 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 beagl...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/e25cf4ca-1c8b-445a-aef8-f7168aafc48do%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/f050cff5-ab6b-4452-9c55-c9f6658ad3a3o%40googlegroups.com.

Re: [beagleboard] Re: 192.168.7.2 is NOT opening or reachable

[amf]

Your using Ubuntu 18.0.04 good, this is what I'm using also. Are you using 
any firewall software, like ufw, if you are, make sure port 22 is allowed.
Yes, BBB comes with pre-install OS. If your BBB boots without and sdcard, 
then it is booting form the emmc. 
to boot from the sdcard, you have to hold the 'USER' button during the boot 
process. (that is from the time the power is applied, till the leds start 
flickering)
Do you have a USB-TO-SERIAL converter that can be connected to J1, it may 
help in debugging the issue. 
Can you ping 192.168.7.2 from your lap top?
When you ssh, are you using debian or root? 
*You do have openssh*-
*server installed on the laptop, right?*


On Sunday, July 12, 2020 at 1:40:15 PM UTC-5, Pankaj Rai wrote:
>
> ssh: connect to host 192.168.7.1 port 22: Connection timed out
>
> this is what i'm getting as error while connecting BBB to 192.68.7.2
>
> what could be the reason and how can we resolve this issue.
>
> thanks
> Pankaj
>
> On Sun, Jul 12, 2020 at 11:14 PM Pankaj Rai  > wrote:
>
>> Hi amf,
>> it's been a while since I've started using BBB. So, I dont know actually 
>> how to get started with BBB. 
>>
>> I haven't installed any image on BBB on my own. I just followed the steps 
>> mentioned in Readme of BBB. (I've attached the SS for your reference). Do 
>> we need to install any image to BBB first? 
>> Don't the BBB comes with the preinstalled OS (or image)?
>>
>> kindly guide me through this.
>>
>> thanks
>> Pankaj
>>
>> On Fri, Jun 26, 2020 at 9:31 PM amf > 
>> wrote:
>>
>>> What Image are you using?
>>> cat /etc/dogtag (provided it is a debian image)
>>> or sudo /opt/scripts/tools/version.sh
>>> or uname -a (might help)
>>> How are you powering the board, 5v supply or usb? if usb, is it via a 
>>> powered hub?
>>> can you also provide the output of ifconfig from the beaglebone black?
>>> Does Nautilus show BEAGLEBONE folder?
>>>
>>> I'm running 'BeagleBoard.org Debian Image 2019-08-03' and am able to ssh 
>>> to the beaglebone black on 7.2 and 6.1 from desktop (ubuntu 18.04)
>>>
>>>
>>>
>>> On Friday, June 26, 2020 at 6:59:47 AM UTC-5, Pankaj Rai wrote:
>>>>
>>>> HI,
>>>> I'm just getting started with the BBB and i'm trying to go to on board 
>>>> server 192.168.7.2 as mentioned in the Getting started doc. 
>>>> But the problem is that 192.168.7.2 is not opening or not reachable. 
>>>> While I have interfaced the BBB with mini B cable to laptop(I'm using 
>>>> Ubuntu 18.0.04 in it) and also connected the BBB with ethernet cable to my 
>>>> laptop.
>>>>
>>>> Please suggest the possible cause and how to debug and make it work.
>>>>
>>>> thanks
>>>> Pankaj
>>>>
>>> -- 
>>> 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 beagl...@googlegroups.com .
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/c8ec1a3d-08ee-4f59-9e80-be2128244b80o%40googlegroups.com
>>>  
>>> <https://groups.google.com/d/msgid/beagleboard/c8ec1a3d-08ee-4f59-9e80-be2128244b80o%40googlegroups.com?utm_medium=email_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/dd617cf7-6d67-4ace-bd08-f8392f5369d6o%40googlegroups.com.

[beagleboard] Re: apt-show-versions

[amf]

Hi sam,

Just followed RobertCNelsons instructions from 6/24/14 and the install 
worked.
Debian Image 2019-08-03 is what I'm working with.


On Tuesday, July 7, 2020 at 1:59:32 PM UTC-5, sam@gmail.com wrote:
>
> Hi All,
>
> I am still getting this error when installing apt-show-verisons:
>
> Error: No information about packages! (Maybe no deb 
> entries?)   
> dpkg: error processing package apt-show-versions 
> (--configure): 
>  installed apt-show-versions package post-installation script subprocess 
> returne
> d error exit status 
> 255 
> Processing triggers for man-db (2.8.5-2) 
> ...
> Errors were encountered while 
> processing:   
>  apt-show-versions
>   
>
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
> I have tried all the solutions mentioned above but its still not working.
>
> Thank you
>
> On Thursday, June 20, 2019 at 8:21:52 AM UTC-6, janwi...@gmail.com wrote:
>>
>> 2019:  `apt-get -o Acquire::GzipIndexes=false update` still works around 
>> this  good solution.
>>
>> On Sunday, December 9, 2018 at 3:27:26 AM UTC+1, mike@ieee.org wrote:
>>>
>>>
>>> Thanks for the help.  The base issue appears to be that compressed 
>>> packages (.lz4) do not work at this time.  Replacing them with uncompressed 
>>> packages works.  Check in rm /var/lib/apt/lists to see if the packages are 
>>> .gz or .lz4.  Remove them in either case and follow the instructions to 
>>> finish the job.  Very satisfying now that it works.  
>>>
>>

-- 
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/c7d5722e-8210-4212-8878-fb8d4d3eef0co%40googlegroups.com.

[beagleboard] Re: 192.168.7.2 is NOT opening or reachable

[amf]

What Image are you using?
cat /etc/dogtag (provided it is a debian image)
or sudo /opt/scripts/tools/version.sh
or uname -a (might help)
How are you powering the board, 5v supply or usb? if usb, is it via a 
powered hub?
can you also provide the output of ifconfig from the beaglebone black?
Does Nautilus show BEAGLEBONE folder?

I'm running 'BeagleBoard.org Debian Image 2019-08-03' and am able to ssh to 
the beaglebone black on 7.2 and 6.1 from desktop (ubuntu 18.04)



On Friday, June 26, 2020 at 6:59:47 AM UTC-5, Pankaj Rai wrote:
>
> HI,
> I'm just getting started with the BBB and i'm trying to go to on board 
> server 192.168.7.2 as mentioned in the Getting started doc. 
> But the problem is that 192.168.7.2 is not opening or not reachable. While 
> I have interfaced the BBB with mini B cable to laptop(I'm using Ubuntu 
> 18.0.04 in it) and also connected the BBB with ethernet cable to my laptop.
>
> Please suggest the possible cause and how to debug and make it work.
>
> thanks
> Pankaj
>

-- 
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/c8ec1a3d-08ee-4f59-9e80-be2128244b80o%40googlegroups.com.

[beagleboard] Re: building a Image for beaglebone board

[amf]

google jumpnowtek and beaglebone black, This will be a Yocto build, there 
is a learning curve to Yocto, but it allows you to also configure what's in 
the filesystem also.
The other option is buildroot, allows for a very light weight filesystem. 
These are the only two methods that I know of to build uboot, linux and 
filesystem.

On Wednesday, June 17, 2020 at 7:12:11 AM UTC-5, ashu diggi wrote:
>
> Hi all,
>
> I am trying to build a image for beaglebone black,which supports only 
> specified peripherals  like USB ,Ethernet , Display screen with consisting 
> a basic kernel files,
>
> I am trying to ask ,how to build a customization Image(operating system) 
> for beaglebone board?
>
> If any one have any idea ,any link for this then please send it,
>
> Regards,
> Asha. 
>

-- 
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/efe7f421-b4bf-4ea5-b72e-39281d3cd481o%40googlegroups.com.

Re: [beagleboard] Re: SPI Linux Kernel Device Drivers

[amf]

Hi Drew,
If you find the .h file that contains the definition of 'struct net_device' 
you will see that 'trans_start' is no longer part of it, maybe just a name 
change (if your lucky).
As for 'alloc_netdev' the api has changed. Try to find another driver that 
calls 'alloc_netdev', this will give you an idea of what the parameters are 
and how they are used.
If your serious about debugging this driver, for every error your seeing, 
find another driver that calls the api that have different parameters and 
see if you can figure out how to work the changes. As for 'struct's that 
have changed, find another driver that uses this same structure and see if 
you can make heads or tails of what has changed. 

Just a quick google, here are some links that may help.
http://e2e.ti.com/support/processors/f/791/t/722999?Linux-TMDSSK3358-QCA7000-driver-configuration

This one looks like there is some support in linux 4.12,
https://cateee.net/lkddb/web-lkddb/QCA7000.html
(found in Linux kernels: 3.18–3.19, 4.0–4.12)

This link implies there is 5.6.3 support 
https://elixir.bootlin.com/linux/latest/source/Documentation/devicetree/bindings/net/qca,qca7000.txt

You may want to do some more searching on this driver.

amf


On Wednesday, April 8, 2020 at 1:32:46 PM UTC-5, Drew Fustini wrote:
>
> On Thu, Apr 2, 2020 at 6:50 PM amf > 
> wrote: 
> > 
> > The driver appears to be 8 yrs old, this puts it in kernel version 3.x 
> or possibly 2.x, a lot of kernel api calls have changed since then. A 
> starting point would be to get the kernel source that your using in the 
> Stretch release, add the driver (if it is not already there) and see if you 
> can build it. However you will most likely need to make driver changes to 
> get it to build. (IMO). 
> > 
> > Freescale (NXP) maintained there own kernel for LTIB/MX28. So IMO, you 
> will have some work to do. 
> > 
> > Good luck. 
> > Amf 
> > 
> > On Wednesday, April 1, 2020 at 4:12:18 PM UTC-5, beagleInThePocket 
> wrote: 
> >> 
> >> Currently I have a program that sends/receives data over the 
> ethernet/wlan etc. network interface on the PocketBeagle. What I'm trying 
> to achieve is simply have the SPI port configured as a Linux network 
> interface to send/receive data to a Qualcomm QCA7000 chip 
> (serial-to-powerline bridge chip). 
> >> Qualcomm provides the following drivers and only the following drivers 
> to access their QCA7000 chip over SPI (qca-spi). How does one actually use 
> these SPI drivers on the PocketBeagle (running Debian Stretch IoT)? Are the 
> drivers necessary and will they even work at all, or will I need to make 
> use of Linux kernel spidev device driver? Not sure if the device tree needs 
> to be considered here too, I am very overwhelmed by this concept. 
>
> I did give it a go and try to compile on my BeagleBone Black running 
> 5.5.9 kernel. 
>
> Here are the results: 
> https://gist.github.com/pdp7/22442e49c75570e52e473aa81ec5f68f 
>
> Notably: 
> qca-spi/qca_spi.c:828:5: error: ‘struct net_device’ has no member 
> named ‘trans_start’; did you mean ‘mem_start’? 
>
> qca-spi/qca_spi.c:1079:80: error: macro "alloc_netdev" requires 4 
> arguments, but only 3 given 
>
> -Drew 
>

-- 
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/93b7d1f3-603d-4f0f-a7c3-5a3a63cb7428%40googlegroups.com.

[beagleboard] Re: SPI Linux Kernel Device Drivers

[amf]

The driver appears to be 8 yrs old, this puts it in kernel version 3.x or 
possibly 2.x, a lot of kernel api calls have changed since then. A starting 
point would be to get the kernel source that your using in the Stretch 
release, add the driver (if it is not already there) and see if you can 
build it. However you will most likely need to make driver changes to get 
it to build. (IMO).

Freescale (NXP) maintained there own kernel for LTIB/MX28. So IMO, you will 
have some work to do.

Good luck.
Amf

On Wednesday, April 1, 2020 at 4:12:18 PM UTC-5, beagleInThePocket wrote:
>
> Currently I have a program that sends/receives data over the ethernet/wlan 
> etc. network interface on the PocketBeagle. What I'm trying to achieve is 
> simply have the SPI port configured as a Linux network interface to 
> send/receive data to a Qualcomm QCA7000 chip (serial-to-powerline bridge 
> chip). 
> Qualcomm provides the following drivers and only the following drivers to 
> access their QCA7000 chip over SPI (qca-spi). 
> <https://github.com/qca/qca7000/tree/master/qca-spi> How does one 
> actually use these SPI drivers on the PocketBeagle (running Debian Stretch 
> IoT)? Are the drivers necessary and will they even work at all, or will I 
> need to make use of Linux kernel *spidev* device driver? Not sure if the 
> device tree needs to be considered here too, I am very overwhelmed by this 
> concept.
>
>

-- 
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/e3e709b2-4483-4786-b396-bea906f4c041%40googlegroups.com.

[beagleboard] Re: Flashed Beaglebone Black with the latest "Stretch LXQT (with graphical desktop)" image and received "No space left on device" immediately after when updating the package index.

[amf]

Have you run this script?
/opt/scripts/tools/grow_partition.sh


On Wednesday, January 1, 2020 at 7:52:21 AM UTC-6, jenny_s...@yahoo.com 
wrote:
>
> I have had a Beaglebone Black for a couple years sitting in a closet and 
> decided to update to the latest image, with the ultimate goal of setting it 
> up for an OpenHab server. As the title says, I successfully flashed the 
> eMMC on the BBB with the latest "Stretch LXQT (with graphical desktop)" 
> Debian image. On initial boot I SSH'ed into the BBB entered the "sudo apt 
> update" command to update the package index, aiming to eventually install 
> Java, and received multiple "No space left on device" messages as the 
> command executed.
>
> I am very new to the BBB and Linux in general, but I find it hard to 
> believe the supplied image with GUI takes up all of the BBB storage such 
> that nothing else can be done with it. Is it possible that there are a 
> large amount logs, temp files, etc. that can be removed to free up space? 
> Any suggestions (detailed steps please) on how to free up space would be 
> appreciated, if that is an option.
>

-- 
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/25b0a26a-31d8-4891-9fdb-5462f859e8c2%40googlegroups.com.

[beagleboard] Re: Using NVMe SSD with BBB?

[amf]

I have been using a USB-to-SSD for about 6mo, no issues, just need to use 
external power to power BBB.
As for the NVMe cards, I've heard it's a hit/miss on getting the 
USB-to-NVMe to work reliably. Plus these converters are somewhat more 
expensive than the ones for SSD.  

On Sunday, December 29, 2019 at 11:04:02 PM UTC-6, bryan...@owasp.org wrote:
>
> Has anyone attempted using an SSD card like the NVMe interface cards from 
> Samsung EVO?
>
> I would love to be able to use storage that is more reliable than SD cards.
>

-- 
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/cae0fb79-061a-4cc9-a8dd-a231a6443ce9%40googlegroups.com.

[beagleboard] Re: BBB on yocto

[amf]

On Tuesday, December 17, 2019 at 4:50:17 PM UTC-6, Siva Subrahmanyam wrote:
>
> I am trying to bring up BBB with yocto. fallowed this document 
> https://bootlin.com/doc/training/yocto/yocto-labs.pdf 
>
> to generate images and  load these to SD card.
>
> u-boot was unable to load kernel with data abort error.  With same SD Card 
> everything was working fine with beaglebone green board.
>
> U-Boot SPL 2018.01-gefdd6cd5ab (Dec 09 2019 - 15:02:18)
> Trying to boot from MMC1
> reading u-boot.img
> reading u-boot.img
>
>
> U-Boot 2018.01-gefdd6cd5ab (Dec 09 2019 - 15:02:18 +)
>
> CPU  : AM335X-GP rev 2.1
> I2C:   ready
> DRAM:  512 MiB
> No match for driver 'omap_hsmmc'
> No match for driver 'omap_hsmmc'
> Some drivers were not found
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Net:   cpsw, usb_ether
> Press SPACE to abort autoboot in 2 seconds
> reading zImage
> data abort
> pc : [<9ff6672c>]  lr : [<9ff4e9f9>]
> reloc pc : [<8081972c>]lr : [<808019f9>]
> sp : 9df2cb40  ip :  fp : 0ab2
> r10: 0200  r9 : 9df2ced8 r8 : 0802
> r7 : 0200  r6 : 0020 r5 : 003d0200  r4 : 4806
> r3 : 08020200  r2 : 13105a4d r1 : 0020  r0 : 0001
> Flags: Nzcv  IRQs off  FIQs on  Mode SVC_32
> Resetting CPU ...
>
> resetting ...
>
> U-Boot SPL 2018.01-gefdd6cd5ab (Dec 09 2019 - 15:02:18)
> Trying to boot from MMC1
> reading u-boot.img
> reading u-boot.img
>
> Added uEnv.txt file with below commands.
> bootdir=/boot
> bootfile=zImage
> console=ttyO0,115200n8
> fdtaddr=0x8800
>

This dtb is not on your sdcard, might want to change it to what you listed 
below. 
Just for reference, I'm using jumpnow how to and meta and BBB boots and 
works.

fdtfile=bbb-4dcape70t.dtb
> loadaddr=0x8200
> mmcroot=/dev/mmcblk0p2 ro
> mmcrootfstype=ext4 rootwait
> optargs=consoleblank=0
> nohdmi=bbb-nohdmi.dtb
> mmcargs=setenv bootargs console=${console} ${optargs} root=${mmcroot} 
> rootfstype=${mmcrootfstype}
> findfdtfile=if test -e mmc ${bootpart} ${bootdir}/nohdmi; then setenv 
> fdtfile ${nohdmi}; fi;
> loadfdt=run findfdtfile; load mmc ${bootpart} ${fdtaddr} 
> ${bootdir}/${fdtfile}
> loadimage=load mmc ${bootpart} ${loadaddr} ${bootdir}/${bootfile}
> uenvcmd=if run loadfdt; then echo Loaded ${fdtfile}; if run loadimage; 
> then run mmcargs; bootz ${loadaddr} - ${fdtaddr}; fi; fi;
>
> here is the snapshot of boot partition and  rootfs/boot/ on sd card. 
> am335x-boneblack.dtb  MLO  u-boot.img  uEnv.txt  uEnv.txt~  zImage
>
>

-- 
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/f7f1b449-b171-43ef-a0ec-28335610c375%40googlegroups.com.

Re: [beagleboard] disable beaglebone black leds

[amf]

Thank you very much.


On Wednesday, October 23, 2019 at 7:15:30 PM UTC-5, RobertCNelson wrote:
>
> On Wed, Oct 23, 2019 at 6:55 PM alric fitterer  > wrote: 
> > 
> > Hi all 
> > I'm trying to disable the leds on a beaglebone black 
> > When issuing this (with and without sudo) 
> > echo none > /sys/class/leds/beaglebone\:green\:usr0/trigger 
>
> sudo sh -c "echo none > /sys/class/leds/beaglebone\:green\:usr0/trigger" 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.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/07cebc0d-5e5e-4e4b-8f98-5f761ef0513b%40googlegroups.com.

[beagleboard] Re: Using an spi digipot

[amf]

look at spidev in linux/Documentation/spi
this is a generic spi driver
The Linux kernel (4.9.x) that I'm using does not have a driver for this 
device
You will need to add an overlay to associate the spidev with the spi bus 
that you will be connecting the device to, this link shows you how to do 
this.
https://learn.adafruit.com/introduction-to-the-beaglebone-black-device-tree/device-tree-overlays
Make sure you only power this device with 3.3 volts, that is what 
beaglebone black's pins use

You have a lot of learning here, good luck



On Sunday, September 29, 2019 at 6:33:49 PM UTC-5, Frederico Alves de 
Oliveira Silva wrote:
>
> Hello amf,
>
> I am using a MCP41010. It is an SPI digipot  with a total resistence of 10 
> kOhm.
>
> Em domingo, 29 de setembro de 2019 17:49:28 UTC-3, amf escreveu:
>>
>> Please provide which digipot your looking at using, there are spi, i2c, 
>> and some custom types like microchip.
>>
>> On Saturday, September 28, 2019 at 10:57:13 AM UTC-5, Frederico Alves de 
>> Oliveira Silva wrote:
>>>
>>> Hello,
>>>
>>> I am a total newbie with BeagleBone Black.
>>> Is there a minimal example of how to work with spi digipots?
>>>
>>> Thank you for the attention!
>>> Frederico
>>>
>>

-- 
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/023df467-68a5-4e20-b159-ad1f97ffd208%40googlegroups.com.

[beagleboard] Re: Using an spi digipot

[amf]

Please provide which digipot your looking at using, there are spi, i2c, and 
some custom types like microchip.

On Saturday, September 28, 2019 at 10:57:13 AM UTC-5, Frederico Alves de 
Oliveira Silva wrote:
>
> Hello,
>
> I am a total newbie with BeagleBone Black.
> Is there a minimal example of how to work with spi digipots?
>
> Thank you for the attention!
> Frederico
>

-- 
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/b1541874-d32b-4219-813b-4283d79311dc%40googlegroups.com.

[beagleboard] Re: Extending linux kernel recipe & kernel config fragmentation in Yocto for BBB

[amf]

No, add the .bbappend to your meta layer, you just need the same directory 
structure as in meta-ti and add your meta layer to bblayers.conf in your 
build directory

On Sunday, September 22, 2019 at 9:42:31 AM UTC-5, Hee-cheol Yang wrote:
>
> Hello, I am writing this mail to ask something about Yocto Project BSP for 
> BBB.
>
> My question is, when I want to make some change in BSP, is it good 
> practice to add some .bbappend files into the meta-ti BSP layer instead of 
> adding a new my own layer?
>
>
> Ya, found this to be true also, depends on which yocto version. I tend to 
keep a copy of the defconfig in my meta data and just update it with 
changes. There are other ways, all depends on your preference.

> To be specific, it seems that *do_configure function* in meta-ti doesn't 
> search kernel configuration fragment file (.cfg) outside of meta-ti working 
> directory. For example, when I firstly tried to add a new layer created new 
> .bbappend file and .cfg file to that directory bitbake -c do_menuconfig 
> virtual/kernel returns error because even though *do_configure* *function* 
> doesn't traverse my new layer directory. So my alternative way is move my 
> new bbappend file and .cfg files into meta-ti directory and do something. 
>
>
> But as I know, modifying other's layer is not recommend in Yocto 
> project(not modify, but, extend it). But is BSP layer exception in this 
> rule? Can I get some advises for it?
>
>
> Thanks a lot
>
> Heecheol Yang.
>

-- 
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/5705c404-aa6e-4b72-80a0-8f5fee5f6fcc%40googlegroups.com.

[beagleboard] Re: Beagle Board Or Raspberry

[amf]

I used a Raspberry Pi zero with usb-to-ethernet adapter and usb-to-ssd 
converter, found transfer rates to be slow. 
Being RPi zero uses the same usb bus, this most likely is the cause of 
being slow.
I used it as a git server for u-boot and Linux source code for Yocto builds
Then moved it to a beaglebone black with wired ethernet and usb-to-ssd 
converter, was much happier.
So it comes down to what kind of bandwidth you need. 
Don't recall the exact number, but I think beaglebone black will draw about 
3x or 4x of power (pi zero < 100ma, bbb > 350ma) idle state
That's my experience, hope it helps

On Thursday, September 19, 2019 at 1:25:05 PM UTC-5, anubh...@gmail.com 
wrote:
>
> Hi Friends,
>
> I am thinking of creating a small System, which will be able to backup my 
> Website  everyday, automatically on an external 
> hard Disk. Can someone guide me if it would be best to move ahead with 
> Beagle or Raspberry.
>

-- 
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/77d476ba-96e5-4c1e-8d53-7de5cbd8aa22%40googlegroups.com.

[beagleboard] Re: Gateway problem

[amf]

On Tuesday, September 17, 2019 at 4:17:33 PM UTC-5, Dennis Lee Bieber wrote:
>
> On Tue, 17 Sep 2019 11:25:20 -0700 (PDT), amf 
> > declaimed the 
> following: 
>
> > 
> >Is this a typo? should be 'wifi on' 
> >#connmanctl> tether wifi off 
> > 
>
Under stood, but why is he using connmanctl for eth0? 

> The OP stated "BeagleBone Black" -- the base BBB does not have 
> WiFi 
>
> >The 'auto eth0' should not be commented out, unless you are not using a 
> >connected ethernet cable 
> ># auto eth0 
> >iface eth0 inet static 
> > 
> And my BBB shows: 
>
> debian@beaglebone:~$ cat /etc/network/interfaces 
> # This file describes the network interfaces available on your system 
> # and how to activate them. For more information, see interfaces(5). 
>
> # The loopback network interface 
> auto lo 
> iface lo inet loopback 
>
> # The primary network interface 
> #auto eth0 
> #iface eth0 inet dhcp 
> # Example to keep MAC address between reboots 
> #hwaddress ether DE:AD:BE:EF:CA:FE 
>
> IE: both lines for eth0 are commented out -- works fine with a DHCP router 
> (which is why I'm suspicious of setting a static mode in the file; like 
> something is set up before the file is processed) 
>
> debian@beaglebone:~$ ifconfig 
> eth0: flags=-28605  mtu 1500 
> inet 192.168.1.69  netmask 255.255.255.0  broadcast 192.168.1.255 
> inet6 2600:1700:e630:890:d239:72ff:fe18:3ee5  prefixlen 64 
>  scopeid 
> 0x0 
> inet6 fe80::d239:72ff:fe18:3ee5  prefixlen 64  scopeid 0x20 
> inet6 2600:1700:e630:890::44  prefixlen 64  scopeid 0x0 
> ether d0:39:72:18:3e:e5  txqueuelen 1000  (Ethernet) 
> RX packets 103  bytes 19904 (19.4 KiB) 
> RX errors 0  dropped 0  overruns 0  frame 0 
> TX packets 145  bytes 20821 (20.3 KiB) 
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
> device interrupt 55 
>
>
>
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com 
> http://wlfraed.microdiversity.freeddns.org/ 
>
>

-- 
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/59f71fb1-8d36-4928-b90d-e47a3d14c393%40googlegroups.com.

[beagleboard] Re: Gateway problem

[amf]

Is this a typo? should be 'wifi on'
#connmanctl> tether wifi off

The 'auto eth0' should not be commented out, unless you are not using a 
connected ethernet cable
# auto eth0
iface eth0 inet static

Also, I don't see a 'wlan0' in your 'route' output, are your trying to 
connect via wifi or usb0? 
more info might help

I'm using an Edimax wifi dongle and connected Ethernet cable, the image is 
the same that you posted

For 'route' this is what I get
debian@beaglebone:~$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse 
Iface
default 192.168.3.1 0.0.0.0 UG0  00 eth0
192.168.2.0 0.0.0.0 255.255.255.0   U 0  00 
wlan0
192.168.2.1 0.0.0.0 255.255.255.255 UH0  00 
wlan0
192.168.3.0 0.0.0.0 255.255.255.0   U 0  00 eth0
192.168.3.1 0.0.0.0 255.255.255.255 UH0  00 eth0
192.168.6.0 0.0.0.0 255.255.255.252 U 0  00 usb1

On Tuesday, September 17, 2019 at 7:52:59 AM UTC-5, massa...@gmail.com 
wrote:
>
> Hi
>
> I have a BeagleBone Black with a huge Problem
>
> I i flashed the image Debian 9.5 2018-10-07 4GB SD IoT 
> 
>  
>
> I have one PC in Network 192.168.144.xxx Gateway 192.168.144.254
> The Beaglebone is in network 192.168.143.xxx  Gateway 192.168.143.254
>
> My interfaces file:
>
> 
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo eth0
> iface lo inet loopback
>
> # The primary network interface
> # auto eth0
> iface eth0 inet static
> address 192.168.143.207
> netmask 255.255.255.0
> gateway 192.168.143.254
>
> # Example to keep MAC address between reboots
> #hwaddress ether DE:AD:BE:EF:CA:FE
>
> ##connman: ethX static config
> #connmanctl services
> #Using the appropriate ethernet service, tell connman to setup a static IP 
> address for that service:
> #sudo connmanctl config  --ipv4 manual   
>  --nameservers 
>
> ##connman: WiFi
> #
> #connmanctl
> #connmanctl> tether wifi off
> #connmanctl> enable wifi
> #connmanctl> scan wifi
> #connmanctl> services
> #connmanctl> agent on
> #connmanctl> connect wifi_*_managed_psk
> #connmanctl> quit
>
>
>
>
> # Ethernet/RNDIS gadget (g_ether)
> # Used by: /opt/scripts/boot/autoconfigure_usb0.sh
> iface usb0 inet static
> address 192.168.7.2
> netmask 255.255.255.252
> network 192.168.7.0
> gateway 192.168.7.1
>
> 
>
> I can't ping the BeagleBone from the PC. It is possible to ping the 
> Gateway in 192.168.143.xxx from PC and Beaglebone.
>
> After booting the BeagleBone,  the "route" command shows:
>
> 
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric RefUse 
> Iface
> default 0.0.0.0 0.0.0.0 U 0  00 
> eth0
> default 192.168.143.254 0.0.0.0 UG0  00 
> eth0
> link-local  0.0.0.0 255.255.0.0 U 0  00 
> eth0
> 192.168.6.0 0.0.0.0 255.255.255.252 U 0  00 
> usb1
> 192.168.7.0 0.0.0.0 255.255.255.252 U 0  00 
> usb0
> 192.168.143.0   0.0.0.0 255.255.255.0   U 0  00 
> eth0
>
> 
> There are two default routes!?!?!?!?!  WHY?
>
> If i restart the network service, the first default route disappears and i 
> can successfully ping the Beaglebone from the PC in the 192.168.144 network.
> What did i wrong?
>

-- 
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/47d8bf20-9c33-4085-aab8-5a415ddbef32%40googlegroups.com.

[beagleboard] Re: replacement for StrawsonDesign Robotic Cape Installer

[amf]

Builds fine on a beaglebone black

image was build with poky from Jumpnowtek
Linux beaglebone 5.0.9-jumpnow #1 Sat Apr 27 20:56:21 UTC 2019 armv7l 
armv7l armv7l GNU/Linux

root@beaglebone:~/librobotcontrol# make all
made: build/led.o
made: build/start_stop.o
made: build/version.o
made: build/pru/encoder_pru.o
made: build/pru/pru.o
made: build/pru/servo.o
made: build/math/matrix.o
made: build/math/ring_buffer.o
made: build/math/vector.o
made: build/math/quaternion.o
made: build/math/polynomial.o
made: build/math/algebra_common.o
made: build/math/algebra.o
made: build/math/kalman.o
made: build/math/filter.o
made: build/math/other.o
made: build/model.o
made: build/pthread.o
made: build/mpu/mpu.o
made: build/pinmux.o
made: build/mavlink_udp.o
made: build/cpu.o
made: build/bmp/bmp.o
made: build/deprecated.o
made: build/motor.o
made: build/dsm.o
made: build/time.o
made: build/io/gpio.o
made: build/io/encoder_eqep.o
made: build/io/adc.o
made: build/io/i2c.o
made: build/io/pwm.o
made: build/io/spi.o
made: build/io/uart.o
made: build/encoder.o
made: build/button.o
Done making lib/librobotcontrol.so.1.0.4
made: bin/rc_bind_dsm
made: bin/rc_test_servos
made: bin/rc_balance
made: bin/rc_test_algebra
made: bin/rc_test_filters
made: bin/rc_calibrate_accel
made: bin/rc_test_encoders
made: bin/rc_test_polynomial
made: bin/rc_test_dmp_tap
made: bin/rc_test_leds
made: bin/rc_test_mpu
made: bin/rc_test_adc
made: bin/rc_cpu
made: bin/rc_calibrate_gyro
made: bin/rc_test_motors
made: bin/rc_test_encoders_pru
made: bin/rc_benchmark_algebra
made: bin/rc_dsm_passthrough
made: bin/rc_test_kalman
made: bin/rc_test_escs
made: bin/rc_calibrate_escs
made: bin/rc_model
made: bin/rc_test_matrix
made: bin/rc_test_dmp
made: bin/rc_version
made: bin/rc_test_drivers
made: bin/rc_blink
made: bin/rc_test_bmp
made: bin/rc_test_encoders_eqep
made: bin/rc_altitude
made: bin/rc_check_battery
made: bin/rc_test_mavlink
made: bin/rc_test_pthread
made: bin/rc_test_complementary_filters
made: bin/rc_spi_loopback
made: bin/rc_calibrate_mag
made: bin/rc_calibrate_dsm
made: bin/rc_kill
made: bin/rc_test_vector
made: bin/rc_test_time
made: bin/rc_test_buttons
made: bin/rc_uart_loopback
made: bin/rc_test_dsm
made: bin/rc_battery_monitor
made: bin/rc_startup_routine

amf


On Sunday, June 23, 2019 at 11:07:10 AM UTC-5, amf wrote:
>
> Are you building this on a beaglebone or desktop?
> I get missing .h files when doing it on a desktop (using cross compile 
> tools)
> building it on a Raspberry Pi, I get "build/cpu.o: file not recognized: 
> File format not recognized" most likely because its not being build on the 
> correct target.
> Will have to find a bone to build it on.
>
> amf
>
>
> On Saturday, June 22, 2019 at 6:49:05 PM UTC-5, Steven Coddington wrote:
>>
>> got it. got librobotcontrol installed.  Tried to run led.c. Would not 
>> compile and got message "
>> led.c:12:29: fatal error: rc/robotcontrol.h: No such file or directory
>>  #include 
>>  ^
>> compilation terminated.
>> : recipe for target 'led' failed
>> make: *** [led] Error 1
>>
>> I can see the led.h file in the directory above (in library/include/rc.
>> Do I need to do something to make these includes available to compiler.  
>> I am using cloud9.
>> Apologies for being an idiot.  Just getting started.  Thanks in advance.
>>
>>
>> On Friday, June 21, 2019 at 4:56:56 PM UTC-6, Steven Coddington wrote:
>>>
>>> Just getting started with bb blue.  Watched the Arrow Video on getting 
>>> started.  At end it directed me to github for StrawsonDesign 
>>> "Robotics_Cape_Installer.
>>> Unfortunately the video is two years old and that package is no longer 
>>> there.  Those files are supposed to be on the board as shipped but I cannot 
>>> find them.  Is there a replacement for the Strawson package, or can you 
>>> help me find the replacement that is allegedly on my board?
>>> Thanks
>>>
>>

-- 
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/4b5603d4-473f-4e31-a051-b10fb94ce96c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: replacement for StrawsonDesign Robotic Cape Installer

[amf]

Are you building this on a beaglebone or desktop?
I get missing .h files when doing it on a desktop (using cross compile 
tools)
building it on a Raspberry Pi, I get "build/cpu.o: file not recognized: 
File format not recognized" most likely because its not being build on the 
correct target.
Will have to find a bone to build it on.

amf


On Saturday, June 22, 2019 at 6:49:05 PM UTC-5, Steven Coddington wrote:
>
> got it. got librobotcontrol installed.  Tried to run led.c. Would not 
> compile and got message "
> led.c:12:29: fatal error: rc/robotcontrol.h: No such file or directory
>  #include 
>  ^
> compilation terminated.
> : recipe for target 'led' failed
> make: *** [led] Error 1
>
> I can see the led.h file in the directory above (in library/include/rc.
> Do I need to do something to make these includes available to compiler.  I 
> am using cloud9.
> Apologies for being an idiot.  Just getting started.  Thanks in advance.
>
>
> On Friday, June 21, 2019 at 4:56:56 PM UTC-6, Steven Coddington wrote:
>>
>> Just getting started with bb blue.  Watched the Arrow Video on getting 
>> started.  At end it directed me to github for StrawsonDesign 
>> "Robotics_Cape_Installer.
>> Unfortunately the video is two years old and that package is no longer 
>> there.  Those files are supposed to be on the board as shipped but I cannot 
>> find them.  Is there a replacement for the Strawson package, or can you 
>> help me find the replacement that is allegedly on my board?
>> Thanks
>>
>

-- 
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/e8bce54f-5776-4c6b-8dff-07e35619ef26%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: ST1633 Touch screen on PB(ish) board.

[amf]

is CONFIG_TOUCHSCREEN_ST1232  configured as built in or a module of linux,
if it's a module, then use modprobe  and see if it loads

On Monday, April 8, 2019 at 1:53:58 AM UTC-5, Dave wrote:
>
> Trying to get an ST1633 touch screen working with a PB derived board. 
> I had to jump to Linux 5.1-rc3 (cross building with bb-kernel) to get the 
> sitronix driver patched with st1633 support. 
>
> I have CONFIG_TOUCHSCREEN_ST1232 enabled in .config. 
>
> I have I2C2 working on the board - I can use 
> i2cdetect -y -r 2
> to find i2c devices that I breadboard onto I2C2 for testing
>
> I can not seem to detect the ST1633 when connected to the PB board, 
> But I can detect it if I bread board it to another Linux box. 
> I am guessing at the moment that the st1633 reset line may be in the wrong 
> state. 
>
> I am trying to make sure I have the TS.RES set correctly. 
> I have verified that I have the right pin by setting it to a gpio_led in 
> the device tree overlay, breadboarding an LED to it and I can toggle the 
> LED from /sys/
>
> Currently I have the devicetree pinctl as 
>
> pinctrl_st1633: pinmux_pinctrl_st1633 {
> pinctrl-single,pins = <
> /* (B13) mcasp0_fsx   GPIO111 GPIO3_15 
> LCD.TS.INT */
> AM33XX_IOPAD(0x0994, PIN_INPUT_PULLDOWN | MUX_MODE7) 
> /* (A13) mcasp0_aclkx GPIO110 GPIO3_14 LCD.TS.RES */
> AM33XX_IOPAD(0x0990, PIN_OUTPUT_PULLUP | MUX_MODE7) 
> >;
>
> I have the st1633 setup as 
>
> fragment@6 {
> target = <>;
> __overlay__ {
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <_i2c2_pins>;
>
> /* this is the configuration part */
> clock-frequency = <10>;
> #address-cells = <1>;
> #size-cells = <0>;
>
> sitronix_ts@55 {
> status = "okay";
> compatible = "sitronix,st1633";
>   reg = <0x55>;
> 
> pinctrl-names = "default";
> pinctrl-0 = <_st1633>;
>
> interrupt-parent = <>;
> interrupts = <15 0>;
> reset-gpios = < 14 GPIO_ACTIVE_LOW>;
>
> touchscreen-size-x = <272>;
> touchscreen-size-y = <480>;
> touchscreen-swapped-x-y;
> };
> };
> };
>
> But when linux boots I am not seeing anything in the logs that suggested 
> in even tried to load the sitronix driver. 
>
> Any ideas ?
>
>
>
>
>
>
>  
>
>
>
>
>

-- 
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/35388839-4c6a-415b-a5d1-00c5fbe918bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UART "callibration"?

[amf]

Mike,
What baud rate are you running at? The higher, the more critical the timing 
is.
With an oscilloscope, measure the period for a single bit, BR = 1/period 
A logic analyzer will not work for this.
Even if you could change some setting, without knowing the period of a 
single bit, you would be guessing at the timing.

amf

On Thursday, March 7, 2019 at 8:25:53 PM UTC-6, Mike Brandon wrote:

> While I am likely getting in way over my head, are there any settings that 
> can be modified on a BeagleBone black as it relates to the UART oscillator? 
> I have seen some reference to the specification of the AM335x regarding:
>
> The UART modules each have a 48MHz clock to generate their timing. They 
> can be configured in one of two modes: UART 16x and UART 13x, in which 
> that clock is divided by 16 and 13, respectively.
>
> I am still trying to get an application I wrote to communicate with a 3rd 
> party controller and grasping at straws at this point.I just can't figure 
> out why everything works fine when I go through /ttyUSB0 (using a 
> USB-serial adapter), but when I try to utilize the /tty04 UART, I can't 
> communicate.
>
> Without drowning this thread with every little thing I have done, I have 
> come to the following conclusions:
>
> 1) My application works because I can confirm it's functionality when 
> connected via USB-serial adapter
> 2) My UART circuit (have tried with a MAX3232 and a MAX232) works because 
> I can open up minicom and do a loopback test successfully. I have also 
> communicated from mt BB to a Windows PC at the same baud rate that I am 
> attempting to use with my application, so based on the fact that the manual 
> communication between BB and PC was successful, I feel confident that my 
> UART circuit is ok.
> 3) Currently I have a logic analyzer hooked up and I am looking at the 
> data I am transmitting from my BB. The applicatio I use with the analyzer 
> decodes the protocol and the data I am seeing from my circuit is the data I 
> am expecting to see.
>
> This snapshot is from the USB-serial connection transmission:
>
> [image: usb.JPG]
> This snapshot is from the UART circuit transmission:
>
> [image: uart.JPG]
>
>

-- 
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/f4230b38-af80-4719-b971-026f242f18bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: GPIO output

[amf]

That pin is clamed by MMC1_DAT6, have you disabled MMC1?

On Tuesday, March 27, 2018 at 8:25:09 AM UTC-5, nagarjuna reddy wrote:
>
> Hi,
>
> I have enabled GPIO output(P8-3) pin. i would given output value is HIGH 
> (/sys/class/gpio/gpio38). than i am checking using multi-meter the value is 
> showing 3.3v. after that i am changing output value is LOW , than i again 
> checked but it not showing 0. its showing 3.3v. can you solve this problem 
> anybody. Thank you.
>

-- 
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/8cf9758e-7f69-428e-9a87-f13a6d1f245e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Network Fail on Rev C boards

[amf]

if you want dhcp on eth0 then uncomment
#auto eth0
#iface eth0 inet dhcp

if you want a static ip on eth0, then do like you have on usb0

amf

On Monday, January 22, 2018 at 6:19:02 AM UTC-6, James S wrote:

> We have some legacy software running on BB White and BB Black (PCB Rev B6) 
> for a while. Recently we have to build some more and using the Rev C BBB, 
> the network fails to start. We are booting Debian from the same SD card, 
> version 3.8.13-bone67.
>
> Can anyone tell me why the more recent hardware stops the network working? 
> How can I get it going again? 
> Looking at the revision history on the schematics, the only difference 
> from Rev B to Rev C is the larger eMMC.
>
> Thanks,
> James
>
> *ifconfig gives the following output:*
> eth0  Link encap:Ethernet  HWaddr 38:d2:69:57:93:ed
>   inet6 addr: fd78:6a89:d8ad:3100:3ad2:69ff:fe57:93ed/64 
> Scope:Global
>   inet6 addr: fe80::3ad2:69ff:fe57:93ed/64 Scope:Link
>   UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>   RX packets:87010 errors:0 dropped:7 overruns:0 frame:0
>   TX packets:79 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:7151565 (6.8 MiB)  TX bytes:16941 (16.5 KiB)
>   Interrupt:40
>
> loLink encap:Local Loopback
>   inet addr:127.0.0.1  Mask:255.0.0.0
>   inet6 addr: ::1/128 Scope:Host
>   UP LOOPBACK RUNNING  MTU:65536  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:0
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
> usb0  Link encap:Ethernet  HWaddr 92:7f:c3:3b:c8:09
>   inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
>   UP BROADCAST MULTICAST  MTU:1500  Metric:1
>   RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>   TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>   collisions:0 txqueuelen:1000
>   RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
>
>
> The following is part of the output of *journalctl*. It seems to show 
> attempts to connect to the network?
> Oct 09 01:28:04 beaglebone systemd[1]: Starting Multi-User System.
> Oct 09 01:28:04 beaglebone systemd[1]: Reached target Multi-User System.
> Oct 09 01:28:04 beaglebone systemd[1]: Starting Graphical Interface.
> Oct 09 01:28:04 beaglebone systemd[1]: Reached target Graphical Interface.
> Oct 09 01:28:04 beaglebone systemd[1]: Starting Update UTMP about System 
> Runlevel Changes...
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast 
> group on interface usb0.IPv4 with address 192.168.7.2.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
> usb0.IPv4 for mDNS.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
> record for 192.168.7.2 on usb0.IPv4.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Withdrawing address record 
> for 192.168.7.2 on usb0.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Leaving mDNS multicast 
> group on interface usb0.IPv4 with address 192.168.7.2.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Interface usb0.IPv4 no 
> longer relevant for mDNS.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Joining mDNS multicast 
> group on interface usb0.IPv4 with address 192.168.7.2.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: New relevant interface 
> usb0.IPv4 for mDNS.
> Oct 09 01:28:05 beaglebone avahi-daemon[1206]: Registering new address 
> record for 192.168.7.2 on usb0.IPv4.
> Oct 09 01:28:05 beaglebone udhcpd[1518]: udhcpd (v1.20.2) started
> Oct 09 01:28:05 beaglebone kernel: IPv6: ADDRCONF(NETDEV_UP): usb0: link 
> is not ready
> Oct 09 01:28:05 beaglebone systemd[1]: Started Update UTMP about System 
> Runlevel Changes.
> Oct 09 01:28:05 beaglebone systemd[1]: Startup finished in 8.601s (kernel) 
> + 15.137s (userspace) = 23.738s.
> Oct 09 01:28:06 beaglebone dhclient[1540]: isc-dhclient-4.2.2
> Oct 09 01:28:06 beaglebone dhclient[1541]: isc-dhclient-4.2.2
> Oct 09 01:28:12 beaglebone login[1226]: pam_unix(login:session): session 
> opened for user root by LOGIN(uid=0)
> Oct 09 01:28:12 beaglebone systemd-journal[210]: Forwarding to syslog 
> missed 62 messages.
> Oct 09 01:28:12 beaglebone login[1546]: ROOT LOGIN  on '/dev/ttyO0'
> Oct 09 01:28:13 beaglebone kernel: net eth0: initializing cpsw version 
> 1.12 (0)
> Oct 09 01:28:13 beaglebone kernel: net eth0: phy found : id is : 0x7c0f1
> Oct 09 01:28:13 beaglebone kernel: libphy: PHY 4a101000.mdio:01 not found
> Oct 09 01:28:13 beaglebone kernel: net eth0: phy 4a101000.mdio:01 not 
> found on slave 1
> Oct

[beagleboard] Re: Debug for USB client port

[amf]

Dragos

You will need differential probe to monitor the usb signal. 

amf

On Wednesday, January 11, 2017 at 2:35:34 AM UTC-6, DragosP wrote:

> Hi all,
>
> I try to figure out if my USB client connection to PC is working. 
> The goal is to have an application in BBB that sends some bytes over USB 
> host and use an oscilloscope to see if there is any activity on USB.
>
> Thank you.
>

-- 
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/69f1f859-42d7-4b0f-8ed9-a877fd308f6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: No usb on 3.14

[amf]

Manish,

What board?

I'm currently working with Beagleboard Rev-c and BBB
At least for me these need to be enabled in the kernel.

CONFIG_USB_EHCI_HCD=y
CONFIG_USB_EHCI_HCD_OMAP=y
CONFIG_USB_OHCI_HCD=y
CONFIG_USB_OHCI_HCD_OMAP3=y

amf

On Friday, September 4, 2015 at 11:51:32 AM UTC-5, Manish Shakya wrote:

>  Hi everyone,
>
> I moved from 3.12 to 31.4, usb doesn't seem to work. It fails at the boot.
>
> [2.576280] musb-hdrc musb-hdrc.0.auto: Failed to request rx1.
> [2.582243] musb-hdrc musb-hdrc.0.auto: musb_init_controller failed 
> with status -517
> [2.656156] musb-hdrc musb-hdrc.1.auto: Failed to request rx1.
> [2.662110] musb-hdrc musb-hdrc.1.auto: musb_init_controller failed 
> with status -517
>
> It was working fine with 3.12. Any ideas why it is failing?
>
>
> Thanks
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: linux-4.0 on Beagleboard Rev-C D-Link DWA-160 wifi not working

[amf]

noobe mistake

failed to set these in kernel config
CONFIG_WEXT_CORE=y
CONFIG_WEXT_PROC=y
CONFIG_CFG80211=y
CONFIG_CFG80211_WEXT=y
CONFIG_MAC80211=y

both DWA-160 and DWA-121 are working

hope this helps someone else,
amf


On Tuesday, September 1, 2015 at 3:07:00 PM UTC-5, amf wrote:

> Hi all,
>
> My first post here, did some searches but came up blank.
>
> I'm trying to get D-Link DWA-160 wifi working with linux-4.0 on the old 
> Beagleboard Rev-C
> Many version back (do not recall which) this device worked.
> I have listed all I can think of that may help, if I missed something 
> please let me know.
>
> Any help will be appreciated, 
> amf
>
> D-Link
> DWA-160
> HW Ver B1
> FW Ver 2.00
> Ralink
> driver: rt2870 
> rt2800lib.ko
> RT chipset 2860, rev 0103 detected
> 07d1:3c11
>
>
> /etc/wpa_supplicant
> ctrl_interface=/var/run/wpa_supplicant
> fast_reauth=1
> ap_scan=1
> eapol_version=1
> network={
> ssid="router ssid"
> psk="passwd"
> scan_ssid=0
> proto=WPA RSN
> key_mgmt=WPA-PSK WPA-EAP
> pairwise=CCMP TKIP
> group=CCMP TKIP
> auth_alg=SHARED OPEN
> }
>
> also tried with 
> key_mgmt=NONE
> and the router encryption turned off
>
>
> /etc/networks/interfaces
> auto lo
> iface lo inet loopback
> auto wlan0
> iface wlan0 inet dhcp
>
>
> *last part of kernel booting*
> Starting network...
> [3.566223] usb 2-2.3: new high-speed USB device number 3 using 
> ehci-omap
> ip: SIOCGIFFLAGS: No such device
> ip: SIOCGIFFLAGS: No such device
> [3.726135] usb 2-2.3: New USB device found, idVendor=07d1, 
> idProduct=3c11
> [3.733428] usb 2-2.3: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
> [3.741302] usb 2-2.3: Product: 802.11 n WLAN
> [3.745941] usb 2-2.3: Manufacturer: Ralink
> [3.750366] usb 2-2.3: SerialNumber: 1.0
> ip: can't find device 'eth0'
> ip: SIOCGIFFLAGS: No such device
>
>
> *script ran after drivers are loaded*
> wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf -Dwext &&
> dhcpcd wlan0 
>
>
> *output on terminal after running script*
>
> Successfully initialized wpa_supplicant
> [   89.307525] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading 
> firmware file 'rt2870.bin'
> [   89.334045] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware 
> detected - version: 0.29
> [   89.920074] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> ioctl[SIOCSIWPMKSA]: Invalid argument
> ioctl[SIOCSIWMODE]: Invalid argument
> ioctl[SIOCGIWRANGE]: Invalid argument
> ioctl[SIOCGIWMODE]: Invalid argument
> ioctl[SIOCSIWAP]: Invalid argument
> ioctl[SIOCSIWESSID]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWENCODEEXT]: Invalid argument
> ioctl[SIOCSIWPMKSA]: Invalid argument
> wlan0: adding address fe80::af1:9d76:7833:e833
> wlan0: waiting for carrier
> timed out
> dhcpcd exited
>
>
> *# dmesg | tail*
> [   14.738891] usbcore: registered new interface driver rtl8192cu
> [   15.126220] usb 2-2.3: reset high-speed USB device number 3 using 
> ehci-omap
> [   15.258361] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 2860, rev 
> 0103 detected
> [   15.322326] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0002 
> detected
> [   15.377807] ieee80211 phy0: Selected rate control algorithm 
> 'minstrel_ht'
> [   15.384948] usbcore: registered new interface driver rt2800usb
> [   16.512756] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading 
> firmware file 'rt2870.bin'
> [   16.532989] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware 
> detected - version: 0.29
> [   17.119445] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> [   26.714233] random: nonblocking pool is initialized
>
>
> *# dhcpcd --version*
> dhcpcd 6.8.1
>
> *# lsmod*
> Module  Size  Used byNot tainted
> arc41719  2
> rt2800usb  15034  0
> rt2x00usb  11492  1 rt2800usb
> rt2800lib  76924  1 rt2800usb
> rt2x00lib  45930  3 rt2800usb,rt2x00usb,rt2800lib
> rtl8192cu  98537  0
> rtl_usb14724  1 rtl8192cu
> rtl8192c_common70336  1 rtl8192cu
> rtlwifi   104207  3 rtl8192cu,rtl_usb,rtl8192c_common
> mac80211  513955  6 
> rt2x00usb,rt2800lib,rt2x00lib,rtl8192cu,rtl_usb,rtlwifi
> cfg80211  428348  3 rt2x00lib,rtlwifi,mac80211
>
>
>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] linux-4.0 on Beagleboard Rev-C D-Link DWA-160 wifi not working

[amf]

Hi all,

My first post here, did some searches but came up blank.

I'm trying to get D-Link DWA-160 wifi working with linux-4.0 on the old 
Beagleboard Rev-C
Many version back (do not recall which) this device worked.
I have listed all I can think of that may help, if I missed something 
please let me know.

Any help will be appreciated, 
amf

D-Link
DWA-160
HW Ver B1
FW Ver 2.00
Ralink
driver: rt2870 
rt2800lib.ko
RT chipset 2860, rev 0103 detected
07d1:3c11


/etc/wpa_supplicant
ctrl_interface=/var/run/wpa_supplicant
fast_reauth=1
ap_scan=1
eapol_version=1
network={
ssid="router ssid"
psk="passwd"
scan_ssid=0
proto=WPA RSN
key_mgmt=WPA-PSK WPA-EAP
pairwise=CCMP TKIP
group=CCMP TKIP
auth_alg=SHARED OPEN
}

also tried with 
key_mgmt=NONE
and the router encryption turned off


/etc/networks/interfaces
auto lo
iface lo inet loopback
auto wlan0
iface wlan0 inet dhcp


*last part of kernel booting*
Starting network...
[3.566223] usb 2-2.3: new high-speed USB device number 3 using ehci-omap
ip: SIOCGIFFLAGS: No such device
ip: SIOCGIFFLAGS: No such device
[3.726135] usb 2-2.3: New USB device found, idVendor=07d1, 
idProduct=3c11
[3.733428] usb 2-2.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[3.741302] usb 2-2.3: Product: 802.11 n WLAN
[3.745941] usb 2-2.3: Manufacturer: Ralink
[3.750366] usb 2-2.3: SerialNumber: 1.0
ip: can't find device 'eth0'
ip: SIOCGIFFLAGS: No such device


*script ran after drivers are loaded*
wpa_supplicant -B -iwlan0 -c/etc/wpa_supplicant.conf -Dwext &&
dhcpcd wlan0 


*output on terminal after running script*

Successfully initialized wpa_supplicant
[   89.307525] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading 
firmware file 'rt2870.bin'
[   89.334045] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware 
detected - version: 0.29
[   89.920074] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
ioctl[SIOCSIWPMKSA]: Invalid argument
ioctl[SIOCSIWMODE]: Invalid argument
ioctl[SIOCGIWRANGE]: Invalid argument
ioctl[SIOCGIWMODE]: Invalid argument
ioctl[SIOCSIWAP]: Invalid argument
ioctl[SIOCSIWESSID]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWENCODEEXT]: Invalid argument
ioctl[SIOCSIWPMKSA]: Invalid argument
wlan0: adding address fe80::af1:9d76:7833:e833
wlan0: waiting for carrier
timed out
dhcpcd exited


*# dmesg | tail*
[   14.738891] usbcore: registered new interface driver rtl8192cu
[   15.126220] usb 2-2.3: reset high-speed USB device number 3 using 
ehci-omap
[   15.258361] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 2860, rev 
0103 detected
[   15.322326] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0002 
detected
[   15.377807] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[   15.384948] usbcore: registered new interface driver rt2800usb
[   16.512756] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading 
firmware file 'rt2870.bin'
[   16.532989] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware 
detected - version: 0.29
[   17.119445] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   26.714233] random: nonblocking pool is initialized


*# dhcpcd --version*
dhcpcd 6.8.1

*# lsmod*
Module  Size  Used byNot tainted
arc41719  2
rt2800usb  15034  0
rt2x00usb  11492  1 rt2800usb
rt2800lib  76924  1 rt2800usb
rt2x00lib  45930  3 rt2800usb,rt2x00usb,rt2800lib
rtl8192cu  98537  0
rtl_usb14724  1 rtl8192cu
rtl8192c_common70336  1 rtl8192cu
rtlwifi   104207  3 rtl8192cu,rtl_usb,rtl8192c_common
mac80211  513955  6 
rt2x00usb,rt2800lib,rt2x00lib,rtl8192cu,rtl_usb,rtlwifi
cfg80211  428348  3 rt2x00lib,rtlwifi,mac80211



-- 
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.
For more options, visit https://groups.google.com/d/optout.