[beagleboard] Re: How do I detect if I am running off the battery ?

[n ithinu]

I do not know if it is also true for PocketBeagle, but there is a tool 
rc_battery_monitor which shows the voltage at the power supply jack. So you 
may just look into the sources of the tool.

On Thursday, May 9, 2019 at 8:02:31 AM UTC+2, Dave wrote:
>
> I am using and OSD3358 based PocketBeaglish Board. 
>
> I need to figure out if the board is running from external power or the 
> LiPo battery, 
> Is there an easy means of doing so ?
>
> Something in sysfs maybe ?
>

-- 
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/1c0c963c-9c84-41b4-a6cc-350e6be732a5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UARTs only unidirectional, black + robotic cape

[n ithinu]

I am sorry, I typed 'echo" instead of 'cat'.  This works as expected:

cat /boot/vmlinuz-4.14.71-ti-r80 > /dev/ttyS5

-- 
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/3235d61e-965e-46d7-ad3c-25e726c2555c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] UARTs only unidirectional, black + robotic cape

[n ithinu]

I can read from UARTs but I can not write to any. This:

echo /boot/vmlinuz-4.14.71-ti-r80 > /dev/ttyS5

returns immediately for any UART, not even an error message. They can read 
fine, they can not write, any of them.

There is a thread 
https://groups.google.com/forum/#!category-topic/beagleboard/uart/0Yr9ed6PO2o 
about pinmuxing, cape overlays, device trees, bootloaders etc. which try to 
make BB UARTs work. Should I follow it to see, why it does not work also on 
my board?

$ dmesg | grep tty
[0.00] Kernel command line: console=ttyO0,115200n8 
root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
[0.001858] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[1.241161] 44e09000.serial: ttyS0 at MMIO 0x44e09000 (irq = 30, 
base_baud = 300) is a 8250
[2.089133] console [ttyS0] enabled
[2.093844] 48022000.serial: ttyS1 at MMIO 0x48022000 (irq = 31, 
base_baud = 300) is a 8250
[2.103698] 48024000.serial: ttyS2 at MMIO 0x48024000 (irq = 32, 
base_baud = 300) is a 8250
[2.113638] 481a6000.serial: ttyS3 at MMIO 0x481a6000 (irq = 33, 
base_baud = 300) is a 8250
[2.123518] 481a8000.serial: ttyS4 at MMIO 0x481a8000 (irq = 34, 
base_baud = 300) is a 8250
[2.13] 481aa000.serial: ttyS5 at MMIO 0x481aa000 (irq = 35, 
base_baud = 300) is a 8250


-- 
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/b92f073b-df26-4261-9d4c-d74201dd44fd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: beaglebone rc_startup_routine[1278]: timeout reached while waiting for pwm driver

[n ithinu]

I do not have the link anymore. Anyway, it said to get the last version of 
the system on an sd card, but it is not enough as the old bootloader from 
the eMMc would still be used. So it said to desactivate the bootloader

sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k

Possibly it loses the contents of all partitions on the eMMC, I do not know.

If you need the EEPROM and do not want to use the sd card, you should 
instead update the eMMC. I guess you will find links for that.

On Wednesday, May 8, 2019 at 3:27:00 AM UTC+2, layt...@gmail.com wrote:
>
> Thank you! If possible, could you please give me more detailed instruction 
> on how to solve this? Maybe some links would be very helpful!
>
> On Monday, May 6, 2019 at 5:09:27 AM UTC-7, ithinu wrote:
>>
>> It was something like new OS on an sd card, but something outdated in the 
>> booting sequence on the EEPROM and I needed to fill the latter with 
>> zeros... something strange like that if I remember well.
>>
>> On Monday, May 6, 2019 at 1:58:10 PM UTC+2, layt...@gmail.com wrote:
>>>
>>> Hello, I have the same problem here so I cannot run on boot either. Have 
>>> you solved this problem? 
>>> I'm looking forward to hearing from you, thank you!
>>>
>>> On Monday, January 14, 2019 at 5:21:43 AM UTC-8, ith...@gmail.com wrote:
>>>>
>>>> I use 
>>>> http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
>>>>  
>>>> from http://strawsondesign.com/docs/librobotcontrol/flashing.html. I 
>>>> flashed it into the built-in eMMc as the page told that it is better so.
>>>>
>>>> Then I configured librobotcontrol to use rc_balance as told here 
>>>> http://strawsondesign.com/#!edumip-software, which gave an error:
>>>>
>>>> $ systemctl status robotcontrol.service
>>>> ● robotcontrol.service - robotcontrol
>>>>Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; 
>>>> vendor preset: enabled)
>>>>Active: failed (Result: exit-code) since Sun 2018-10-07 16:42:07 
>>>> UTC; 13s ago
>>>>   Process: 1278 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, 
>>>> status=255)
>>>>
>>>> Oct 07 16:42:06 beaglebone systemd[1]: Starting robotcontrol...
>>>> Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: timeout reached 
>>>> while waiting for pwm driver
>>>> Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: TIMEOUT REACHED
>>>> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Control 
>>>> process exited, code=exited status=255
>>>> Oct 07 16:42:07 beaglebone systemd[1]: Failed to start robotcontrol.
>>>> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Unit 
>>>> entered failed state.
>>>> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Failed 
>>>> with result 'exit-code'.
>>>>
>>>> $ uname -a
>>>> Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 
>>>> 2018 armv7l GNU/Linux
>>>>
>>>> I guess the hardware is ok, as I previously used some old image from 
>>>> https://www.hackster.io/edumip/edumip-13a29c and rc_balance was fine.
>>>>
>>>>

-- 
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/80962e54-e028-4b80-ad63-5e5446e3c199%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: beaglebone rc_startup_routine[1278]: timeout reached while waiting for pwm driver

[ithinu]

It was something like new OS on an sd card, but something outdated in the 
booting sequence on the EEPROM and I needed to fill the latter with 
zeros... something strange like that if I remember well.

On Monday, May 6, 2019 at 1:58:10 PM UTC+2, layt...@gmail.com wrote:
>
> Hello, I have the same problem here so I cannot run on boot either. Have 
> you solved this problem? 
> I'm looking forward to hearing from you, thank you!
>
> On Monday, January 14, 2019 at 5:21:43 AM UTC-8, ith...@gmail.com wrote:
>>
>> I use 
>> http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
>>  
>> from http://strawsondesign.com/docs/librobotcontrol/flashing.html. I 
>> flashed it into the built-in eMMc as the page told that it is better so.
>>
>> Then I configured librobotcontrol to use rc_balance as told here 
>> http://strawsondesign.com/#!edumip-software, which gave an error:
>>
>> $ systemctl status robotcontrol.service
>> ● robotcontrol.service - robotcontrol
>>Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; 
>> vendor preset: enabled)
>>Active: failed (Result: exit-code) since Sun 2018-10-07 16:42:07 UTC; 
>> 13s ago
>>   Process: 1278 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, 
>> status=255)
>>
>> Oct 07 16:42:06 beaglebone systemd[1]: Starting robotcontrol...
>> Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: timeout reached 
>> while waiting for pwm driver
>> Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: TIMEOUT REACHED
>> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Control 
>> process exited, code=exited status=255
>> Oct 07 16:42:07 beaglebone systemd[1]: Failed to start robotcontrol.
>> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Unit entered 
>> failed state.
>> Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Failed with 
>> result 'exit-code'.
>>
>> $ uname -a
>> Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 
>> 2018 armv7l GNU/Linux
>>
>> I guess the hardware is ok, as I previously used some old image from 
>> https://www.hackster.io/edumip/edumip-13a29c and rc_balance was fine.
>>
>>

-- 
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/f57e84f9-0701-4511-9431-eea8ff847595%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: cape-powered BB black works, but has no 5V voltage (and no USB)

[ithinu]

When a low-power device is connected, like a mouse, the USB port works. If 
a medium-power device is connected, the port switches off until the next 
reset. 

On Thursday, April 18, 2019 at 5:07:37 PM UTC+2, ith...@gmail.com wrote:
>
> The 5V is there until a device is connected. Then it disappears until the 
> next reset.
>
> On Thursday, April 18, 2019 at 4:48:17 PM UTC+2, ith...@gmail.com wrote:
>>
>> I am sorry for the lack of clarity, it has no 5V only on the usb part, I 
>> guess.
>>
>> On Thursday, April 18, 2019 at 4:46:36 PM UTC+2, ith...@gmail.com wrote:
>>>
>>> My new BB black wireless + cape has no 5V on the USB port. I noticed it 
>>> after connecting a serial-to-usb converter (no light, no /dev/ttyUSB0 etc). 
>>> A voltmeter shows no 5V even on USB socket pins on the USB. Is the board 
>>> decidedly malfunctioning or can it be a software issue?
>>>
>>

-- 
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/3f45457c-2e13-4085-a6d5-f45b7440f2cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: cape-powered BB black works, but has no 5V voltage (and no USB)

[ithinu]

The 5V is there until a device is connected. Then it disappears until the 
next reset.

On Thursday, April 18, 2019 at 4:48:17 PM UTC+2, ith...@gmail.com wrote:
>
> I am sorry for the lack of clarity, it has no 5V only on the usb part, I 
> guess.
>
> On Thursday, April 18, 2019 at 4:46:36 PM UTC+2, ith...@gmail.com wrote:
>>
>> My new BB black wireless + cape has no 5V on the USB port. I noticed it 
>> after connecting a serial-to-usb converter (no light, no /dev/ttyUSB0 etc). 
>> A voltmeter shows no 5V even on USB socket pins on the USB. Is the board 
>> decidedly malfunctioning or can it be a software issue?
>>
>

-- 
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/1b8c27b0-fdf1-4407-832a-6f0b2a737b9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: cape-powered BB black works, but has no 5V voltage (and no USB)

[ithinu]

I am sorry for the lack of clarity, it has no 5V only on the usb part, I 
guess.

On Thursday, April 18, 2019 at 4:46:36 PM UTC+2, ith...@gmail.com wrote:
>
> My new BB black wireless + cape has no 5V on the USB port. I noticed it 
> after connecting a serial-to-usb converter (no light, no /dev/ttyUSB0 etc). 
> A voltmeter shows no 5V even on USB socket pins on the USB. Is the board 
> decidedly malfunctioning or can it be a software issue?
>

-- 
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/144b2b54-7cd6-4732-be81-7473c87c6dda%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] cape-powered BB black works, but has no 5V voltage (and no USB)

[ithinu]

My new BB black wireless + cape has no 5V on the USB port. I noticed it 
after connecting a serial-to-usb converter (no light, no /dev/ttyUSB0 etc). 
A voltmeter shows no 5V even on USB socket pins on the USB. Is the board 
decidedly malfunctioning or can it be a software issue?

-- 
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/aa90da2a-9b7c-469a-b83c-df9032ea5366%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Compatibility BB blue vs Black + robotics cape

[ithinu]

Works after another reboot.


-- 
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/c3d7c901-d2a5-41a7-b102-8714db1ccd89%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Compatibility BB blue vs Black + robotics cape

[ithinu]

I did this:

$ sudo /usr/bin/configure_robotics_dt 
/usr/bin/configure_robotics_dt: line 11: warning: command substitution: 
ignored null byte in input
Using am335x-boneblack-wireless-roboticscape.dtb
making backup copy of /boot/uEnv.txt
Using previously listed kernel 4.14.71-ti-r80
Robotics Cape Device Tree Configured and Installed

Restarted or not, there are errors in example applications like:

ERROR: in init_led, failed to open LED file handle: No such file or 
directory

serial ports do not work, no 6V with rc_test_servos etc.


On Wednesday, April 10, 2019 at 4:16:00 PM UTC+2, RobertCNelson wrote:
>
> On Wed, Apr 10, 2019 at 7:07 AM > wrote: 
> > 
> > Hi. Can I just take an sdcard from bb blue, put it into black + cape and 
> expect it to work? If not, what should I change? 
>
> There is a special dtb you need to load for the black+cape 
> combination, but yes same image will boot.. 
>
> 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/d33cf665-496c-4524-80c4-c59e2c9a766a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: GPIO on robotic cape

[ithinu]

Guessing from this 
https://github.com/StrawsonDesign/Robotics_Cape_Documentation/blob/master/SD-101D_header_pin_table.ods,
 
gpio1[17], gpio3[17] are free. Is it also the case for gpio3[21] if IMU is 
not used? I need 3 x GPIO.




-- 
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/aeaccbae-d8c1-4308-926a-8341d061c5fc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] GPIO on robotic cape

[ithinu]

Hi, on BB blue there were gpio sockets, they do not exists on the robotic 
cape. The cape is not also "thru", i.e. no sockets for another cape. How 
can I use GPIO when the robotic cape is plugged? There is a socket SPI1.1 
with pins SPI11_MOSI, SPI11_MISO, SPI11_SCK, SPI11_SS1, can there be 
reutilised as GPIO? If yes, how to translate their names to values for 
gpio_export etc.?

-- 
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/5cee3548-79bc-4955-9a14-974420ef82eb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Compatibility BB blue vs Black + robotics cape

[ithinu]

Should I just proceed as with a raw BB black, no need to remove some dtd 
special for BB blue?

On Wednesday, April 10, 2019 at 4:16:00 PM UTC+2, RobertCNelson wrote:
>
> On Wed, Apr 10, 2019 at 7:07 AM > wrote: 
> > 
> > Hi. Can I just take an sdcard from bb blue, put it into black + cape and 
> expect it to work? If not, what should I change? 
>
> There is a special dtb you need to load for the black+cape 
> combination, but yes same image will boot.. 
>
> 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/5328d8f0-243e-47b9-b569-6474e9c46c65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Robotic cape pinout

[ithinu]

I can not find it anywhere, search for beaglebone black robotic cape pinout 
gave no results. In case of BB blue, there is one thread with a 
reverse-engineered user-provided pinout, I wonder if ports named the same 
way on Blue have the same pins on the cape?

-- 
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/433c827a-c53a-486c-9e15-530a5c95afe1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] mmc0: tried to reset card, got error -110

[ithinu]

I replaced the card with a new one from another company, and unfortunately 
the problem persists.

On Thursday, April 11, 2019 at 6:15:43 PM UTC+2, RobertCNelson wrote:
>
> On Thu, Apr 11, 2019 at 11:08 AM > wrote: 
> > 
> > I have a new BBB blue. The same card which worked well on the old one 
> now causes, roughly after 10 minutes of working, the error: 
> > 
> > mmc0: tried to reset card, got error -110 
> > 
> > The system becomes read-only, there are i/o errors etc. When fsck -f on 
> another machine, the system has no errors. What can it be? 
>
> errno 110 
> ETIMEDOUT 110 Connection timed out 
>
> -110 is usually a sign it's time to throw the microSD card.. 
>
> 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/2047e21a-b241-406a-be1b-e0f64a1387fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] mmc0: tried to reset card, got error -110

[ithinu]

I replaced the card with a new one of another company, unfortunately the 
problem persists. I guess I will need to return the board.

On Thursday, April 11, 2019 at 6:15:43 PM UTC+2, RobertCNelson wrote:
>
> On Thu, Apr 11, 2019 at 11:08 AM > wrote: 
> > 
> > I have a new BBB blue. The same card which worked well on the old one 
> now causes, roughly after 10 minutes of working, the error: 
> > 
> > mmc0: tried to reset card, got error -110 
> > 
> > The system becomes read-only, there are i/o errors etc. When fsck -f on 
> another machine, the system has no errors. What can it be? 
>
> errno 110 
> ETIMEDOUT 110 Connection timed out 
>
> -110 is usually a sign it's time to throw the microSD card.. 
>
> 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/bc9d0643-ab93-4bab-9fcc-dc9be6905953%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] mmc0: tried to reset card, got error -110

[ithinu]

I have a new BBB blue. The same card which worked well on the old one now 
causes, roughly after 10 minutes of working, the error:

mmc0: tried to reset card, got error -110

The system becomes read-only, there are i/o errors etc. When fsck -f on 
another machine, the system has no errors. What can it be?

-- 
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/64a5560b-5b3c-498d-9f7a-e5acecb97a9d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Compatibility BB blue vs Black + robotics cape

[ithinu]

Hi. Can I just take an sdcard from bb blue, put it into black + cape and 
expect it to work? If not, what should I change?

-- 
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/7f5ee401-5bee-4343-be84-ac33d89286ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Sync with ntp

[ithinu]

Thus, by default BB is expected to synchronize? It it did not do this, this 
may mean that some ports are blocked?

On Thursday, March 21, 2019 at 4:13:56 PM UTC+1, RobertCNelson wrote:
>
> By default we ship with systemd-timesyncd enabled and active..  The 
> ntp package was probally blocked by that.. 
>
> 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/c68f5084-c598-4235-9f87-00ba7f5360bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Sync with ntp

[ithinu]

$ service ntp status
● ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp; generated; vendor preset: enabled)
   Active: active (running) since Thu 2016-11-03 18:16:53 CET; 20min ago
 Docs: man:systemd-sysv-generator(8)
  Process: 547 ExecStart=/etc/init.d/ntp start (code=exited, 
status=0/SUCCESS)
Tasks: 2 (limit: 4915)
   CGroup: /system.slice/ntp.service
   └─647 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 109:116

Nov 03 18:35:29 beaglebone ntpd[647]: Soliciting pool server 94.177.239.114
Nov 03 18:35:30 beaglebone ntpd[647]: Soliciting pool server 94.23.2.80
Nov 03 18:36:26 beaglebone ntpd[647]: Soliciting pool server 163.172.61.210
Nov 03 18:36:29 beaglebone ntpd[647]: Soliciting pool server 51.15.182.163
Nov 03 18:36:33 beaglebone ntpd[647]: Soliciting pool server 194.57.169.1
Nov 03 18:36:34 beaglebone ntpd[647]: Soliciting pool server 195.154.174.209
Nov 03 18:37:30 beaglebone ntpd[647]: Soliciting pool server 37.59.27.22
Nov 03 18:37:36 beaglebone ntpd[647]: Soliciting pool server 151.80.19.218
Nov 03 18:37:38 beaglebone ntpd[647]: Soliciting pool server 95.81.173.155
Nov 03 18:37:38 beaglebone ntpd[647]: Soliciting pool server 185.123.84.51
$ date
Thu Nov  3 18:38:14 CET 2016

-- 
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/9e9f6a5d-32f1-4a2f-b8a1-e62de26b7cb6%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Sync with ntp

[ithinu]

Hi, my Beaglebone Blue does not sync with NTP. I followed the instructions 
at 
https://stackoverflow.com/questions/46148481/set-the-date-in-begalebone-black-using-ntp-debian-8-9
 
but just as in the case of the original poster, the BB does not sync after 
reboot. Can anything be done with that? RPi does sync with NTP 
out-of-the-box on the same Wifi.

-- 
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/230a99b3-f8e1-4504-ad66-26ee4c4db0a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BB blue: make-microSD-flasher-from-eMMC produces a fs with all sort of errors

[ithinu]

I attach a log with the output of 
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh 
and a fragment of output of e2fsck -f /dev/mmcblk0p1.

BBB can boot from it, then it gets slowly worse until halt. Still, BBB 
works normally with its eMMC. One of the reasons might be, that 
/dev/mmcblk0p1 is reported as having 4GB or 16GB, depending on the software.



Unattached inode 793363
Connect to /lost+found? yes

Inode 793363 ref count is 2, should be 1.  Fix? yes

Unattached inode 793364
Connect to /lost+found? yes

Inode 793364 ref count is 2, should be 1.  Fix? yes

Unattached inode 793365
Connect to /lost+found? yes

Inode 793365 ref count is 2, should be 1.  Fix? yes

Unattached inode 793366
Connect to /lost+found? yes

Inode 793366 ref count is 2, should be 1.  Fix? yes

Unattached inode 793367
Connect to /lost+found? yes

Inode 793367 ref count is 2, should be 1.  Fix? yes

Unattached inode 793368
Connect to /lost+found? yes

Inode 793368 ref count is 2, should be 1.  Fix? yes

Unattached inode 793369
Connect to /lost+found? yes

Inode 793369 ref count is 2, should be 1.  Fix? yes

Unattached inode 793370
Connect to /lost+found? yes

Inode 793370 ref count is 2, should be 1.  Fix? yes

Inode 793421 ref count is 1, should be 2.  Fix? yes

Inode 794552 ref count is 6, should be 4.  Fix? yes

Inode 794553 ref count is 6, should be 4.  Fix? yes

Inode 794554 ref count is 6, should be 4.  Fix? yes

Inode 794555 ref count is 6, should be 4.  Fix? yes

Unattached inode 794592
Connect to /lost+found? yes

Inode 794592 ref count is 2, should be 1.  Fix? yes

Unattached inode 794600
Connect to /lost+found? yes

Inode 794600 ref count is 2, should be 1.  Fix? yes

Unattached inode 794601
Connect to /lost+found? yes

Inode 794601 ref count is 2, should be 1.  Fix? yes

Unattached inode 794605
Connect to /lost+found? yes

Inode 794605 ref count is 2, should be 1.  Fix? yes


-- 
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/ef06a8ba-88e7-4e07-9a5b-72e28ef21b8e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
/opt/scripts/tools/eMMC/beaglebone-black-make-microSD-flasher-from-eMMC.sh 


Starting eMMC Flasher from microSD media
Version: [1.20180412: all ssh regneration override...]



Prepare environment for flashing
Starting at Fri Nov  4 11:31:15 UTC 2016

==> sysctl: vm.min_free_kbytes=[2653]
==> sysctl: setting: [sysctl -w vm.min_free_kbytes=16384]
vm.min_free_kbytes = 16384

==> Determining root drive
==> console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
root=/dev/mmcblk1p1 ro rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 
quiet

==> root_drive=[/dev/mmcblk1p1]
> Root drive identified at /dev/mmcblk1p1
==> Determining boot drive
==> Figuring out Source and Destination devices
> Source identified: [/dev/mmcblk1]
> Destination identified: [/dev/mmcblk0]
> Unmounting auto-mounted partitions
==> Figuring out machine
> Machine is TI_AM335x_BeagleBone_Blue
> Machine is compatible with BeagleBone Black

5 4 3 2 1 


Checking running system
==> Copying: [/dev/mmcblk1] -> [/dev/mmcblk0]
==> lsblk:

NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
mmcblk0  179:00 14.9G  0 disk 
└─mmcblk0p1  179:10 14.9G  0 part 
mmcblk1  179:80  3.6G  0 disk 
└─mmcblk1p1  179:90  3.6G  0 part /
mmcblk1boot0 179:16   04M  1 disk 
mmcblk1boot1 179:24   04M  1 disk 
mmcblk1rpmb  179:32   04M  0 disk 

==> df -h | grep rootfs:

==> updating: /boot/initrd.img-4.14.71-ti-r80
update-initramfs: Generating /boot/initrd.img-4.14.71-ti-r80
WARNING: Setting CRYPTSETUP in /etc/initramfs-tools/initramfs.conf is 
deprecated and will stop working in the future. Use 
/etc/cryptsetup-initramfs/conf-hook instead.
cryptsetup: WARNING: failed to detect canonical device of /dev/mmcblk1p1
cryptsetup: WARNING: could not determine root device from /etc/fstab
==> Giving you time to check...
10 9 8 7 6 5 4 3 2 1 
=

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

Possibly, I do not know a lot about it. At the beginning of the file, there 
is "# Generated by Connection Manager" though.


On Monday, February 18, 2019 at 1:35:05 PM UTC+1, ith...@gmail.com wrote:
>
> So it is like that: even if I put nameservers 10.42.0.1 or 8.8.8.8, 
> whatever, into connmanctl config and asking it then shows that exact IP as 
> the DNS server, what is put into resolv.conf is some three values which 
> look like IP6 adresses, I have no idea what they mean. Anyway, DNS is not 
> working with them and I need to replace everything in resolv.conf with 
> nameserver 10.42.0.1 after every rewrite of the file by connmanctl, then it 
> works fine.
>
>
> On Wednesday, February 13, 2019 at 7:36:37 PM UTC+1, ith...@gmail.com 
> wrote:
>>
>> Strangely the hotspot was set as DNS before, but it did not work back 
>> then.
>>
>> Thank you all for your support.
>>
>> .On Wednesday, February 13, 2019 at 6:09:32 PM UTC+1, Sicelo Mhlongo 
>> wrote:
>>>
>>> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote: 
>>> > Is there a way of just replacing connmanm with wpa_supplicant using 
>>> apt_get? 
>>> > 
>>>
>>> Yes there is. Note that there is nothing wrong with connman. You can 
>>> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli. 
>>>
>>> One more thing, connmanctl can connect to an Enterprise network. You 
>>> need to prepare the corresponding file, just like you will need to with 
>>> wpa_supplicant 
>>>
>>>

-- 
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/7e1ec7fa-3371-44c0-aa79-435ae87c4a45%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

So it is like that: even if I put nameservers 10.42.0.1 or 8.8.8.8, 
whatever, into connmanctl config and asking it then shows that exact IP as 
the DNS server, what is put into resolv.conf is some three values which 
look like IP6 adresses, I have no idea what they mean. Anyway, DNS is not 
working with them and I need to replace everything in resolv.conf with 
nameserver 10.42.0.1 after every rewrite of the file by connmanctl, then it 
works fine.


On Wednesday, February 13, 2019 at 7:36:37 PM UTC+1, ith...@gmail.com wrote:
>
> Strangely the hotspot was set as DNS before, but it did not work back then.
>
> Thank you all for your support.
>
> .On Wednesday, February 13, 2019 at 6:09:32 PM UTC+1, Sicelo Mhlongo wrote:
>>
>> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote: 
>> > Is there a way of just replacing connmanm with wpa_supplicant using 
>> apt_get? 
>> > 
>>
>> Yes there is. Note that there is nothing wrong with connman. You can 
>> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli. 
>>
>> One more thing, connmanctl can connect to an Enterprise network. You 
>> need to prepare the corresponding file, just like you will need to with 
>> wpa_supplicant 
>>
>>

-- 
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/ed1f82b7-7cc9-4a64-8126-66c486345e71%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

Strangely the hotspot was set as DNS before, but it did not work back then.

Thank you all for your support.

.On Wednesday, February 13, 2019 at 6:09:32 PM UTC+1, Sicelo Mhlongo wrote:
>
> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com  
> wrote: 
> > Is there a way of just replacing connmanm with wpa_supplicant using 
> apt_get? 
> > 
>
> Yes there is. Note that there is nothing wrong with connman. You can 
> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli. 
>
> One more thing, connmanctl can connect to an Enterprise network. You 
> need to prepare the corresponding file, just like you will need to with 
> wpa_supplicant 
>
>

-- 
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/6d81409a-96e2-4242-85fc-13a8ab8dee05%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[Ithinu]

I manually removed everything from /etc/resolv.conf and put there only ip
of the laptop's hotspot. Fortunately a direct connection to the laptop is
enough and even better for now than that to the enterprise wifi.


On Wed, Feb 13, 2019 at 6:42 PM Ithinu  wrote:

> > Yes there is. Note that there is nothing wrong with connman.
> > One more thing, connmanctl can connect to an Enterprise network. You
> > need to prepare the corresponding file, just like you will need to with
> > wpa_supplicant
>
> I did. Then I used a standard sequence of operations from the tutorial and
> in this particular network it showed "bad parameter" or whatever, without a
> slightest explanation, where the problem is. But given that you find
> nothing wrong with connman, you likely also find nothing wrong with its
> error reporting.
>
>
>
> On Wed, Feb 13, 2019 at 6:09 PM Sicelo  wrote:
>
>> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote:
>> > Is there a way of just replacing connmanm with wpa_supplicant using
>> apt_get?
>> >
>>
>> Yes there is. Note that there is nothing wrong with connman. You can
>> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli.
>>
>> One more thing, connmanctl can connect to an Enterprise network. You
>> need to prepare the corresponding file, just like you will need to with
>> wpa_supplicant
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/oUorVdn8mEw/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/beagleboard/20190213170912.GA11879%40Nokia-N900
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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/CANA2BUVHyfQj%2B5maC5QWCj%3DRx9HLPeE9Kkfv_%3Dbmxr0E%3D6m%2BYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[Ithinu]

> Yes there is. Note that there is nothing wrong with connman.
> One more thing, connmanctl can connect to an Enterprise network. You
> need to prepare the corresponding file, just like you will need to with
> wpa_supplicant

I did. Then I used a standard sequence of operations from the tutorial and
in this particular network it showed "bad parameter" or whatever, without a
slightest explanation, where the problem is. But given that you find
nothing wrong with connman, you likely also find nothing wrong with its
error reporting.



On Wed, Feb 13, 2019 at 6:09 PM Sicelo  wrote:

> On Wed, Feb 13, 2019 at 09:01:36AM -0800, ith...@gmail.com wrote:
> > Is there a way of just replacing connmanm with wpa_supplicant using
> apt_get?
> >
>
> Yes there is. Note that there is nothing wrong with connman. You can
> learn it, like you learned any other tool, e.g. wpa_supplicant, nmcli.
>
> One more thing, connmanctl can connect to an Enterprise network. You
> need to prepare the corresponding file, just like you will need to with
> wpa_supplicant
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/oUorVdn8mEw/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/beagleboard/20190213170912.GA11879%40Nokia-N900
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

[beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

Is there a way of just replacing connmanm with wpa_supplicant using apt_get?


On Monday, February 11, 2019 at 6:18:56 PM UTC+1, ith...@gmail.com wrote:
>
> I use Beaglebone Blue which has no Ethernet port. Yes, internet sharing 
> has many variables, but hotspots often work and if BBB had a typical Wifi 
> manager, there would likely be no issue from the start. There are no tools 
> like telnet or nmcli installed on it. For now, I will try port tunneling 
> via SSH. Thanks Tarmo for your help.
>
>
> On Monday, February 11, 2019 at 5:44:48 PM UTC+1, Tarmo Kuuse wrote:
>
>> On Monday, 11 February 2019 18:03:01 UTC+2, ith...@gmail.com wrote:
>>>
>>> Hello Tarmo. Thanks for your help,  host google.com 8.8.8.8 gives
>>> ;; connection timed out; no servers could be reached
>>>
>>> I have lost too much time an attempt to have a working network 
>>> connection on BB.
>>>
>>> Firstly, via USB, a known problem. With Linux, it never worked like a 
>>> normal network.
>>> Then, an adapter Ethernet-USB. BB recognized it in maybe 80%, then 20% 
>>> of times, then never. My laptop recognizes it always until now.
>>> Then, connmanctl. I have never seen this application before, in any 
>>> case, no way of connecting it to a given enterprise Wifi, and its error 
>>> reporting was like "invalid parameter" to its internal command with no 
>>> parameters. Sure, a more typical Wifi and it would work.
>>> So I decided to connect BB to my laptop working as a hotspot. It accepts 
>>> specific ports, SSH for example, DNS it seems no way.
>>>
>>> With RPi, it just works. Cable, Wifi, in different places and networks, 
>>> it just works. BB, no way.
>>>
>>
>> I'm sorry to hear about your USB-Ethernet adapter dying. I have used a 
>> couple of different USB-Ethernet adapters on my Beaglebone-derived device - 
>> some are very stable and some drop out after a few hours or days, but a 
>> reset always brings them back online. Perhaps you should get a different 
>> one. BTW, I'm a little confused - if you have a BeagleBone Black (as the 
>> topic states), why can't you use the built-in Ethernet port?
>>
>> Anyway, Internet connection sharing is a fragile operation as there are 
>> many things which need to go right for it to work. If your ping and ssh go 
>> through but DNS doesn't, it might be that TCP and ICMP work, but UDP 
>> doesn't. You can do some experiments using simple tools like telnet and 
>> netcat, but this doesn't really concern the BeagleBone any more.
>>
>> --
>> Kind regards,
>> Tarmo
>>
>

-- 
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/9b49a4c8-293e-4435-90c8-4fcbbe49c139%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

I use Beaglebone Blue which has no Ethernet port. Yes, internet sharing has 
many variables, but hotspots often work and if BBB had a typical Wifi 
manager, there would likely be no issue from the start. There are no tools 
like telnet or nmcli installed on it. For now, I will try port tunneling 
via SSH. Thanks Tarmo for your help.


On Monday, February 11, 2019 at 5:44:48 PM UTC+1, Tarmo Kuuse wrote:

> On Monday, 11 February 2019 18:03:01 UTC+2, ith...@gmail.com wrote:
>>
>> Hello Tarmo. Thanks for your help,  host google.com 8.8.8.8 gives
>> ;; connection timed out; no servers could be reached
>>
>> I have lost too much time an attempt to have a working network connection 
>> on BB.
>>
>> Firstly, via USB, a known problem. With Linux, it never worked like a 
>> normal network.
>> Then, an adapter Ethernet-USB. BB recognized it in maybe 80%, then 20% of 
>> times, then never. My laptop recognizes it always until now.
>> Then, connmanctl. I have never seen this application before, in any case, 
>> no way of connecting it to a given enterprise Wifi, and its error reporting 
>> was like "invalid parameter" to its internal command with no parameters. 
>> Sure, a more typical Wifi and it would work.
>> So I decided to connect BB to my laptop working as a hotspot. It accepts 
>> specific ports, SSH for example, DNS it seems no way.
>>
>> With RPi, it just works. Cable, Wifi, in different places and networks, 
>> it just works. BB, no way.
>>
>
> I'm sorry to hear about your USB-Ethernet adapter dying. I have used a 
> couple of different USB-Ethernet adapters on my Beaglebone-derived device - 
> some are very stable and some drop out after a few hours or days, but a 
> reset always brings them back online. Perhaps you should get a different 
> one. BTW, I'm a little confused - if you have a BeagleBone Black (as the 
> topic states), why can't you use the built-in Ethernet port?
>
> Anyway, Internet connection sharing is a fragile operation as there are 
> many things which need to go right for it to work. If your ping and ssh go 
> through but DNS doesn't, it might be that TCP and ICMP work, but UDP 
> doesn't. You can do some experiments using simple tools like telnet and 
> netcat, but this doesn't really concern the BeagleBone any more.
>
> --
> Kind regards,
> Tarmo
>

-- 
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/15172b9b-4890-450c-b2b8-86a6af5672cd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

Hello Tarmo. Thanks for your help,  host google.com 8.8.8.8 gives
;; connection timed out; no servers could be reached

I have lost too much time an attempt to have a working network connection 
on BB.

Firstly, via USB, a known problem. With Linux, it never worked like a 
normal network.
Then, an adapter Ethernet-USB. BB recognized it in maybe 80%, then 20% of 
times, then never. My laptop recognizes it always until now.
Then, connmanctl. I have never seen this application before, in any case, 
no way of connecting it to a given enterprise Wifi, and its error reporting 
was like "invalid parameter" to its internal command with no parameters. 
Sure, a more typical Wifi and it would work.
So I decided to connect BB to my laptop working as a hotspot. It accepts 
specific ports, SSH for example, DNS it seems no way.

With RPi, it just works. Cable, Wifi, in different places and networks, it 
just works. BB, no way.


On Monday, February 11, 2019 at 4:40:17 PM UTC+1, Tarmo Kuuse wrote:
>
> On Monday, 11 February 2019 16:28:55 UTC+2, ith...@gmail.com wrote:
>>
>> In /etc/resolv.conf there is a line nameserver 8.8.8.8
>>
>> I am sorry, there is Debian on BB and not Ubuntu, this may explain the 
>> missing tools.
>>
>
> I'd recommend debugging DNS connectivity using the low-level "host" 
> command. It ignores the system's DNS client configuration. For example, the 
> following command queries the name "google.com" from DNS server 8.8.8.8:
>
> $ host google.com 8.8.8.8
>
> I would firstly try the DNS servers provided by my Internet Service 
> Provider. Anyway, if "host" resolves names and the system's DNS client 
> doesn't, then you have a lead. If neither option resolves names, your 
> Internet connection is broken.
>
> --
> Kind regards,
> Tarmo
>

-- 
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/ede453c6-c140-4a14-ae31-2fc4fd40ecea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

In /etc/resolv.conf there is a line nameserver 8.8.8.8

I am sorry, there is Debian on BB and not Ubuntu, this may explain the 
missing tools.

-- 
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/a58a9cf2-63c1-4aee-bd64-35c1554cf9e7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Why dns is not working in this BBB -> laptop hotspot configuration

[ithinu]

So there is connmanctl. And a new problem: no dns. It was once, no more. I 
can not test it, because all these usable little tools normally found in 
ubuntu like nmcli have been removed from BB. Anyone could help?

##connman: WiFi
#
#connmanctl
#connmanctl> tether wifi off
#connmanctl> enable wifi
#connmanctl> scan wifi
#connmanctl> services
#connmanctl> agent on
#connmanctl> connect wifi_*_managed_psk
#connmanctl> config wifi_e0e5ff8b8b94_671272_managed_psk nameservers 8.8.8.8
#connmanctl> quit

  Type = wifi
  Security = [ psk, wps ]
  State = ready
  Strength = 89
  Favorite = True
  Immutable = False
  AutoConnect = True
  Name = art
  Ethernet = [ Method=auto, Interface=wlan0, Address=E0:E5:CF:8B:9B:96, 
MTU=1500 ]
  IPv4 = [ Method=dhcp, Address=10.42.0.90, Netmask=255.255.255.0, 
Gateway=10.42.0.1 ]
  IPv4.Configuration = [ Method=dhcp ]
  IPv6 = [  ]
  IPv6.Configuration = [ Method=auto, Privacy=disabled ]
  Nameservers = [ 8.8.8.8 ]
  Nameservers.Configuration = [ 8.8.8.8 ]
  Timeservers = [ 10.42.0.1 ]
  Timeservers.Configuration = [  ]
  Domains = [  ]
  Domains.Configuration = [  ]
  Proxy = [ Method=direct ]# ping 8.8.8.8
  Proxy.Configuration = [  ]
  Provider = [  ]

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=121 time=3.79 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=121 time=4.92 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=121 time=4.65 ms

$ ping google.com
ping: google.com: Temporary failure in name resolution

-- 
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/9d79a5db-90c1-4916-b5a5-4d36cebe7391%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Wifi 5 GHz

[ithinu]

Hi, is BB wifi dual-band?

-- 
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/a7e2d2dd-f645-4336-9ea3-d5b02cd634f8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBlue depleted its battery below the critical level?

[ithinu]

Hello,

My Beaglebone blue switched suddenly off. I connected it to a charger and 
ran rc_battery_monitor. It has shown cell voltage 3.28V, which seems to be 
below any critical level? Is it unsafe to the battery? If yes, why had not 
the BBlue switched itself off earlier?

-- 
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/4d0b857e-5a8a-477e-b623-e5ee911d3485%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to connect Beagleboard to Wifi as a client

[ithinu]

After a system restart, connmanctl now shows the wifi networks.

So to sum it up, if you want a wireless bidirectional connection with 
beaglebone independent from any local wifi, make your laptop a hotspot, 
make Beaglebone a client, but via connmanctl and not using the other 
methods, which did not seem to work any more. Then arp -a and you can 
connect via ssh to the ip number shown there. And it survives reboots.

-- 
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/42425750-de63-4621-a716-99286e223c9b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to connect Beagleboard to Wifi as a client

[ithinu]

There is also something called connmanctl, but it does not work like 
expected...

# connmanctl
connmanctl> tether wifi off
Error disabling wifi tethering: Already disabled
connmanctl> enable wifi
Error wifi: Already enabled
connmanctl> scan wifi
Scan completed for wifi
connmanctl> agent on
Agent registered
connmanctl> services

connmanctl> agent on
Agent already registered
connmanctl> 
connmanctl> services

And Beaglebone still is visible as a hotspot.

-- 
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/6b79fece-1a56-40e3-90ff-ed6301199b15%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to connect Beagleboard to Wifi as a client

[ithinu]

Hi,

Connecting to Beagleboard configured as a hotspot does not work 
*bidirectionally*. I can ssh to it, but there is not internet on the 
Beaglebone. I tried "shared to other computers", it does not work. Someone 
here proposed to use an Ethernet adapter. Thanks it worked, but I need 
wireless. I would thus want to try Beaglebone as a Wifi client, my laptop 
as a hotspot.

So I tried this 
https://stackoverflow.com/questions/51837774/how-to-auto-connect-wifi-on-beaglebone-custom-linux

$ sudo /etc/init.d/networking restart
$ systemctl status networking.service
● networking.service - Raise network interfaces
   Loaded: loaded (/lib/systemd/system/networking.service; enabled; vendor 
preset: enabled)
   Active: active (exited) since Thu 2016-11-03 18:02:05 UTC; 1min 1s ago
 Docs: man:interfaces(5)
  Process: 2379 ExecStop=/sbin/ifdown -a --read-environment --exclude=lo 
(code=exited, status=0/SUCCESS)
  Process: 2428 ExecStart=/sbin/ifup -a --read-environment (code=exited, 
status=0/SUCCESS)
  Process: 2424 ExecStartPre=/bin/sh -c [ "$CONFIGURE_INTERFACES" != "no" ] 
&& [ -n "$(ifquery --read-environment --list --exclude=lo)" ] && udevadm 
settle (code=exited, sta
 Main PID: 2428 (code=exited, status=0/SUCCESS)

Nov 03 18:02:04 beaglebone systemd[1]: Starting Raise network interfaces...
Nov 03 18:02:05 beaglebone systemd[1]: Started Raise network interfaces.

Does not work. Beaglebone is still a hotspot, ignores the content of 
wpa_supplicant.conf and /etc/network/interfaces. Interesingly, so slightest 
warning or error message on restart.

Please help me. I guess that I should somehow switch off the hotspot on 
Beaglebone, but the docs which I browsed silent on this.


-- 
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/62a8af6c-dd0f-4e13-a1b3-883afd65f544%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: beaglebone rc_startup_routine[1278]: timeout reached while waiting for pwm driver

[ithinu]

$ rc_test_drivers

Kernel: 4.14.71-ti-r80
BeagleBoard.org Debian Image 2018-10-07
Debian: 9.5

PASSED: gpio 0
PASSED: gpio 1
PASSED: gpio 2
PASSED: gpio 3
PASSED: pwm0
PASSED: pwm1
PASSED: pwm2
PASSED: eqep0
PASSED: eqep1
PASSED: eqep2
PASSED: pru-rproc
PASSED: uart1
PASSED: uart2
PASSED: uart4
PASSED: uart5
PASSED: i2c1
PASSED: i2c2
PASSED: spi
PASSED: LED
PASSED: ADC iio

Currently running on a:
MODEL_BB_BLUE
Robot Control library Version:
1.0.3

-- 
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/7fcdfdb3-0188-4dee-88a0-d8770160ad80%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] beaglebone rc_startup_routine[1278]: timeout reached while waiting for pwm driver

[ithinu]

I use 
http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
 
from http://strawsondesign.com/docs/librobotcontrol/flashing.html. I 
flashed it into the built-in eMMc as the page told that it is better so.

Then I configured librobotcontrol to use rc_balance as told here 
http://strawsondesign.com/#!edumip-software, which gave an error:

$ systemctl status robotcontrol.service
● robotcontrol.service - robotcontrol
   Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-10-07 16:42:07 UTC; 
13s ago
  Process: 1278 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, 
status=255)

Oct 07 16:42:06 beaglebone systemd[1]: Starting robotcontrol...
Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: timeout reached while 
waiting for pwm driver
Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: TIMEOUT REACHED
Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Control 
process exited, code=exited status=255
Oct 07 16:42:07 beaglebone systemd[1]: Failed to start robotcontrol.
Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Unit entered 
failed state.
Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Failed with 
result 'exit-code'.

$ uname -a
Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 2018 
armv7l GNU/Linux

I guess the hardware is ok, as I previously used some old image from 
https://www.hackster.io/edumip/edumip-13a29c and rc_balance was fine.

-- 
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/a6b31f68-4a7b-4c94-b1b0-d7155ac71070%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RoboticsCape Error: "timeout reached while waiting for gpio driver"

[ithinu]

I have the same problem. I use 
http://strawsondesign.com/docs/images/BBB-blank-debian-9.5-iot-armhf-2018-10-07-4gb.img.xz
 
from http://strawsondesign.com/docs/librobotcontrol/flashing.html. I 
flashed it into the built-in eMMc as the page told that it is better so.

Then I configured librobotcontrol to use rc_balance as told here 
http://strawsondesign.com/#!edumip-software, which gave an error:

$ systemctl status robotcontrol.service
● robotcontrol.service - robotcontrol
   Loaded: loaded (/lib/systemd/system/robotcontrol.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2018-10-07 16:42:07 UTC; 
13s ago
  Process: 1278 ExecStartPre=/usr/bin/rc_startup_routine (code=exited, 
status=255)

Oct 07 16:42:06 beaglebone systemd[1]: Starting robotcontrol...
Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: timeout reached while 
waiting for pwm driver
Oct 07 16:42:07 beaglebone rc_startup_routine[1278]: TIMEOUT REACHED
Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Control 
process exited, code=exited status=255
Oct 07 16:42:07 beaglebone systemd[1]: Failed to start robotcontrol.
Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Unit entered 
failed state.
Oct 07 16:42:07 beaglebone systemd[1]: robotcontrol.service: Failed with 
result 'exit-code'.


Following Robert's advice, despite that the kernel is already 4.14:

$ uname -a
Linux beaglebone 4.14.71-ti-r80 #1 SMP PREEMPT Fri Oct 5 23:50:11 UTC 2018 
armv7l GNU/Linux
$ sudo ./update_kernel.sh --ti-channel --lts-4_14
info: checking archive
ERROR: The certificate of ‘rcn-ee.com’ is not trusted.
ERROR: The certificate of ‘rcn-ee.com’ is not yet activated.
The certificate has not yet been activated

I guess the hardware is ok, as I previously used some old image from 
https://www.hackster.io/edumip/edumip-13a29c and rc_balance was fine.

-- 
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/0ea51a55-2a22-4b27-ae38-a5a77ff68829%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Are PRUs really deterministic, and well documented, ant not obsolete...

[ithinu]

So it means that I can do no-jitter bit banging if only one PRU accesses 
the GPIO, and if the unit does not use any shared resources? That would be 
great.

On Tuesday, January 8, 2019 at 10:43:36 PM UTC+1, Charles Steinkuehler 
wrote:
>
> The PRUs are mostly deterministic when accessing resources within the 
> local PRU-ICSS block.  The "mostly" comes from potential contentions 
> if you have both PRU cores accessing the same resource (eg: PRU0 and 
> PRU1 both trying to access the local UART) in which case one of the 
> PRU cores will stall briefly. 
>
> The PRUs are less deterministic when accessing resources outside the 
> PRI-ICSS block (eg: SDRAM or GPIO registers) where the transaction is 
> subject to synchronization delays, bus congestion on the L3/L4 
> interconnect, etc. 
>
> On 1/8/2019 6:48 AM, daveyj...@gmail.com  wrote: 
> > Hi, I have read this nice ad for PRUs 
> > http://www.staroceans.org/documents/TI-sdk/spry264.pdf which states how 
> > deterministic the PRUs are, 
> > 
> > "*each PRU has its own single-cycle I/O*" etc. Then I wanted details... 
> > 
> > http://processors.wiki.ti.com/index.php/Programmable_Realtime_Unit 
> "Content 
> > is* no longer maintained and is being kept for reference only!* " 
> > 
> > http://processors.wiki.ti.com/index.php/PRU-ICSS "Please note as of 
> > Wednesday, August 15th, 2018 this wiki *has been set to read only*." 
> > 
> > http://processors.wiki.ti.com/index.php/PRU_Read_Latencies "The PRU 
> write 
> > instruction is a fire-and-forget command that executes in *~*1 cycle" 
> > 
> > *that tilde...* 
> > 
> > 
> > "The read latency values at the following links are *considered* 
> > "best-case," accounting for the 2 cycle instruction and interconnect 
> > introduced *latency*". 
> > 
> > *best case* 
> > 
> > Possibly, there is some doc which states min/max execution times? 
> > Deterministic or not? etc, etc. 
> > *Not found. Just not found.* 
> > 
> > --- 
> > 
> > I do not want to be pessimistic but neither I want to 
> reverse-engineer 
> > these "deteministic" units, that do not really look that-deterministic. 
> And 
> > that docs obsolete or missing??? What is it all about? 
> > 
> > 
> > 
> > 
>
>
> -- 
> Charles Steinkuehler 
> cha...@steinkuehler.net  
>

-- 
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/8e0256f6-38cf-44b6-8456-9750ad0a95c8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to connect Beaglebone blue to *any* network, except a simple Wifi

[ithinu]

Hi Tarmo, yes one of these pages with instructions also informed that 
network-over-usb it is a non-recommended struggle, which may not even 
survive a reboot.

Thanks for informing me that a USB-Ethernet dongle will work though, I did 
not know that.

On Monday, January 7, 2019 at 5:37:02 PM UTC+1, Tarmo Kuuse wrote:

> Hi!
>
> On Monday, 7 January 2019 18:17:01 UTC+2, ith...@gmail.com wrote:
>>
>> Firstly, via USB. I set a gateway on Beaglebone, but the desktop (host 
>> Ubuntu) does not care. There are some instructions on the internet, 
>> followed by "if does not work add use echo 1 > 
>> /proc/sys/net/ipv4/ip_forward, a thing with iptables, whatever", it all did 
>> not work, ping 8.8.8.8 on the bone does not work. Someone told that you 
>> need to put the respective interface to a "trusted zone". I do not know 
>> where I can found that zone. To add a VPN connection. "Add a VPN 
>> connection" is grayed on my system.
>>
>> I did not want to touch wifi, because I would prefer beaglebone to be a 
>> hotspot, but if it did not work with the cable...
>>
>> Firstly, there is "connman", to make it easier. I tried connman, but the 
>> wifi network is enterprise tunneled double-authentication etc, connman just 
>> prints "invalid arguments" when I try to connect. There is some 
>> wpa-supplicant-like configuration file, added it as instructed, but no 
>> effect, all I see is still "invalid arguments". No detailed error, no 
>> problematic file, no problematic line, no list of these arguments, nothing, 
>> just "invalid arguments".
>>
>> Lastly, there is wpa-supplicant itself. I made a respective file, but it 
>> all starts and stops with
>>
>> $  wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0
>> Successfully initialized wpa_supplicant
>> Could not read interface p2p-dev-wlan0 flags: No such device
>> nl80211: Could not set interface 'p2p-dev-wlan0' UP
>> nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
>> p2p-dev-wlan0: Failed to initialize driver interface
>> P2P: Failed to enable P2P Device interface
>>
>> There is nothing about p2p-dev-wlan0, whatever it is, in 
>> wpa_supplicant.conf
>>
>> Could you please help me? I had never problems with RPi, with BBone 
>> Black, but Blue, no idea. I am not a network expert and I do not want to be 
>> one. I just want to apt update etc. Thanks.
>>
>
> Are you trying to connect a Beaglebone to Internet using an USB connection 
> to your PC? It's going to be a struggle, especially if you don't want to 
> dive into networking details.
>
> I suggest buying a cheap USB-Ethernet adapter and connecting your 
> Beaglebone to local LAN using that. It usually works just like that. 
> Something like this:
>
> http://www.logilink.eu/Produkte_LogiLink/Aktive_Netzwerkkomponenten/Fast_Ethernet/USB_2_0_to_Fast_Ethernet_RJ45_Adapter_UA0144B.htm
>
> --
> Kind regards,
> Tarmo Kuuse
>

-- 
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/8756ddc2-78be-4db8-aa48-24540354f27b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to connect Beaglebone blue to *any* network, except a simple Wifi

[ithinu]

Thanks Robert, I know. I have created that file. It is something like 
wpa-supplicant.conf, but different. Connman did not react to that file, or 
at least all that it prints is still "invalid arguments", as in the case 
when the file did not exist.

-- 
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/9a9b1dac-b94c-422a-81d1-7604be0c046b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to connect Beaglebone blue to *any* network, except a simple Wifi

[ithinu]

Firstly, via USB. I set a gateway on Beaglebone, but the desktop (host 
Ubuntu) does not care. There are some instructions on the internet, 
followed by "if does not work add use echo 1 > 
/proc/sys/net/ipv4/ip_forward, a thing with iptables, whatever", it all did 
not work, ping 8.8.8.8 on the bone does not work. Someone told that you 
need to put the respective interface to a "trusted zone". I do not know 
where I can found that zone. To add a VPN connection. "Add a VPN 
connection" is grayed on my system.

I did not want to touch wifi, because I would prefer beaglebone to be a 
hotspot, but if it did not work with the cable...

Firstly, there is "connman", to make it easier. I tried connman, but the 
wifi network is enterprise tunneled double-authentication etc, connman just 
prints "invalid arguments" when I try to connect. There is some 
wpa-supplicant-like configuration file, added it as instructed, but no 
effect, all I see is still "invalid arguments". No detailed error, no 
problematic file, no problematic line, no list of these arguments, nothing, 
just "invalid arguments".

Lastly, there is wpa-supplicant itself. I made a respective file, but it 
all starts and stops with

$  wpa_supplicant -c /etc/wpa_supplicant/wpa_supplicant.conf -i wlan0
Successfully initialized wpa_supplicant
Could not read interface p2p-dev-wlan0 flags: No such device
nl80211: Could not set interface 'p2p-dev-wlan0' UP
nl80211: deinit ifname=p2p-dev-wlan0 disabled_11b_rates=0
p2p-dev-wlan0: Failed to initialize driver interface
P2P: Failed to enable P2P Device interface

There is nothing about p2p-dev-wlan0, whatever it is, in wpa_supplicant.conf

Could you please help me? I had never problems with RPi, with BBone Black, 
but Blue, no idea. I am not a network expert and I do not want to be one. I 
just want to apt update etc. 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/f226d959-6ce6-4372-abe4-e0a59505a31d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Reboot instead of shutdown

[ithinu]

On Thu, Apr 27, 2017 at 7:26 PM, William Hermans  wrote:

> It's meant to impress on the point that the hardware was designed with 
> cost in mind, and that the software for this hardware is provided free of 
> charge.
>

I realize that. This is why I suggested a solution which a knowledgeable 
person might possibly write in few minutes (adding an option to a script?) 
and not for example a board modification, which would add to effort and 
cost.
 

> I am sure there is someone out in the world that would be happy to make 
> these changes for you, if you're willing to pay their fee.
>

Very likely, but this is about a third time when I write in this thread 
that I found a solution for myself (unplug an USB cable). Otherwise, I 
would add some statement to one of the shutdown script, but given how the 
Linux startup system is complex today, I doubt the fast fix would be on par 
with that made by a Linux professional. Or that the additional possibility 
would become a part of your FAQ etc.
 

>
> But I can sympathize, I understand where you're coming from. I've had to 
> make software changes myself for various things I needed built into the 
> system. Granted, I never needed this specific functionality myself, as I 
> said in my previous post, we do not use our own boards in this specific 
> manner. You may have to end up adapting your usage, or the software to 
> conform to your own specific needs. But that's often how the open source 
> world works. 
>

Sometimes (very often?) users report an issue to help the developers, and 
not to demand anything from them.

They do this e.g. out of gratitude.

-- 
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/9e0707a6-233e-4876-9528-1813c317a902%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Reboot instead of shutdown

[ithinu]

Perhaps a work-around would be to provide a software possibility of 
freezing the unit after the kernel is down. Handy for someone who has a 
power-hungry cape requiring a power supply, no Ethernet and would like to 
safely replace the sd card. If it were possible to detect, that the unit is 
going to reboot anyway, the freeze could even be chosen automatically if a 
shutdown is requested.

On Thursday, April 27, 2017 at 6:41:17 PM UTC+2, William Hermans wrote:
>
> By the way those changes which I mentioned for the USB OTG port are made 
> through device tree configurations. I think in the main board file, but 
> that problem has been corrected so long ago, I do not remember exactly how.
>
> Here, we do not connect to our boards in this manner, ever.I have one 
> beaglebone black that I do power over that USB port here, but never with a 
> barrel jack, or through the P9 header at the same time. We have a few capes 
> we're working on, with different beaglebone greens. These are all powered 
> through the P9 header, but communication is made through ethernet on those 
> boards. Well actually, all the boards we have in our "lab" are connected 
> via ethernet for communications.
>
> On Thu, Apr 27, 2017 at 9:34 AM, William Hermans  > wrote:
>
>>
>>
>> On Thu, Apr 27, 2017 at 1:27 AM, ithinu 
>> > wrote:
>>
>>> > Short story, you're using a powered hub, and you need to keep that hub 
>>> from sending power back into the host.
>>>
>>> No, the hub is not powered. Also, as I said, the problem exists only 
>>> with the combination power supply/usb connection, which I rarely need. But 
>>> it still can be a problem of someone else.
>>>
>>> So, I would guess, it is more of checking the issue by the board 
>>> constructors before the next rev of BeagleBone. Especially that someone in 
>>> the other thread reports that the problem is spotty. With an oscilloscope, 
>>> power supplies of different power, capes or not, USB cables of different 
>>> length etc., until the cause is apparent. Or just don't care :)
>>>
>>> In any case, I can be of help, for example I can check if the problem 
>>> persists with the board connected directly to a PC.
>>>
>>
>> The issue in the post you linked to has to be different. Unless you've 
>> gone and reconfigured the USB OTG port, though software, which is possible. 
>> So while the problem Harvey was talking about in that post *could* be 
>> corrected through hardware changes. Making those changes would be less than 
>> ideal. As it would reduce the flexibility of the USB mini connector. There 
>> are two or possibly three different modes the USB mini connector could be 
>> configured into through software.
>>
>
>

-- 
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/9580793f-c85c-4827-a6c2-5e9ad9336893%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Reboot instead of shutdown

[ithinu]

> Short story, you're using a powered hub, and you need to keep that hub 
from sending power back into the host.

No, the hub is not powered. Also, as I said, the problem exists only with 
the combination power supply/usb connection, which I rarely need. But it 
still can be a problem of someone else.

So, I would guess, it is more of checking the issue by the board 
constructors before the next rev of BeagleBone. Especially that someone in 
the other thread reports that the problem is spotty. With an oscilloscope, 
power supplies of different power, capes or not, USB cables of different 
length etc., until the cause is apparent. Or just don't care :)

In any case, I can be of help, for example I can check if the problem 
persists with the board connected directly to a PC.



-- 
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/8001ad66-27be-410a-b238-e5a760628cfd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Reboot instead of shutdown

[ithinu]

The board is connected to a 5V power supply, to a USB hub and via Ethernet 
to a router. It has no capes.

uname -a
Linux beaglebone 4.4.39-ti-r75 #1 SMP Thu Dec 15 22:16:11 UTC 2016 armv7l 
GNU/Linux

The command

  sudo systemctl poweroff

reboots it just like 

  shutdown -P now

However, if the board is disconnected from the USB hub (still connected to 
the power supply), both of the above commands shut the unit down as 
expected. I checked this several times: connecting even a running unit to 
USB makes it unable to shutdown. However, if powered from USB (power supply 
disconnected) the board shuts down again without a problem.

I tested this several times and it seems, that the only combination where 
the board can not shut down is when connected to both the power supply and 
USB at once. Which is ok as of me, as I do not need the USB connection any 
more.

There is an old thread (the kernel must obviously have been different) 
where a similar problem is reported by several people: 
https://groups.google.com/forum/#!msg/beagleboard/qw5zlS4F4p4/chu0J3VXKgAJ


On Wednesday, April 26, 2017 at 4:45:41 AM UTC+2, Graham wrote:
>
> What OS/kernel is ithinu running?
>
> "shutdown -P now" works on all my BBB/BBG boards.
>
> But, I run from external +5V, without anything on the battery connections.
>
> --- Graham
>
> ==
>
>
>> I usually tell everyone to use:
>>
>> sudo systemctl poweroff
>>
>> as systemd knows how to tell the external tps65217 to cut power.
>>
>> looking at the syslog, i don't remember any issues with 4.4.39-ti-r75,
>> and looking at the git log i don't see any poweroff regressions
>> mentioned..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to a topic in the 
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit 
>> https://groups.google.com/d/topic/beagleboard/9VdtZKf3Dz0/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to 
>> beagleboard...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgHtwySLzoGJOdRLwGKm34kPxxwz6GBj5BFwWYUUtbR9g%40mail.gmail.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/b71765fd-1179-4c6d-911b-8969233bc7b9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Reboot instead of shutdown

[ithinu]

shutdown -P now does the same as shutdown -h now: reboots the board. So I 
still do not know a way of shutting it down.

I attach the relevant part of syslog.


On Sunday, April 23, 2017 at 3:04:21 AM UTC+2, Graham wrote:
>
>
> shutdown -P now
>
> --- Graham
>
> ==
>
> On Saturday, April 22, 2017 at 6:57:45 PM UTC-5, ithinu wrote:
>>
>> I want to shutdown the board in order to have the sdcard in a consistent 
>> state.
>>
>>   shutdown -h now
>>
>> reboots instead. There is a discussion about this 
>> https://groups.google.com/d/msg/beagleboard/qw5zlS4F4p4/chu0J3VXKgAJ but 
>> I do not get the conclusion.
>>
>> Is it possible to shutdown the board, if powered externally, without 
>> ahardware modification?
>>
>>

-- 
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/73e3e676-12e5-4c84-9ba7-1afd40f4afb8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


syslog
Description: Binary data

[beagleboard] How to shutdown?

[ithinu]

I would like to shutdown, so that the sdcard is in a consistent state:

 shutdown -h now

The board always restarts instead. There is a discussion about this 
https://groups.google.com/d/msg/beagleboard/qw5zlS4F4p4/chu0J3VXKgAJ but I 
do not quite get the conclusion. Is it that I can not shutdown the system 
if there is a power supply without some soldering?

-- 
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/78d1b95e-efa8-40e8-acda-3a17c018e878%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Reboot instead of shutdown

[ithinu]

I want to shutdown the board in order to have the sdcard in a consistent 
state.

  shutdown -h now

reboots instead. There is a discussion about this 
https://groups.google.com/d/msg/beagleboard/qw5zlS4F4p4/chu0J3VXKgAJ but I 
do not get the conclusion.

Is it possible to shutdown the board, if powered externally, without 
ahardware modification?

-- 
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/ebc8ae1f-4b88-48c9-b8a0-1d2ef17174e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Pin numbering in pinmux-pins

[Ithinu]

Is it also that P8_12 is the 12th pin in the socket 9? It seems that there
is 0x30 mentioned in the case of both.​

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

Re: [beagleboard] Pin numbering in pinmux-pins

[Ithinu]

Hi saumitra, thanks for your help but I still do not know how to relate the
numbers in question 0, 1, 2, 3, 4, 5, 6, 7, 32, 33, 38 to 22, 23, 24, 5, 4,
3, 6, 25, 20, 21.

> ( GPIO1_28 - 1*32 + 28 ) is the GPIO60 ( not PIN60 ). If we search for
the
> same offset (0x078) we see that pin 30 is 30 HEX

There is thus 1_28, 60, 0x78, 30 and a two-character chip pin name. How is
0x78 related to 60? Why 0x078 is "the same offset"? Comparing to what?


On Mon, Dec 26, 2016 at 6:37 AM, saumitra kapoor  wrote:

> Hi,
>
> Yes you are right. Some important points to consider for this numbering :
>
>- The pin number is the $PINS value and should not be confused with
>the GPIO.
>- Let us take an example of P8_12 ( $PINS value 12 ) in mode 0x27  (
>Input Mode7 Pull Down ). Viewing this pins file helps in the corresponding
>readings.
>- You can see that pin 0 is allocated to eMMC. Moreover, you can query
>the value at the memory address. P8_12 is mapped at the memory address
>44e10830.
>- "cat pingroups" will show you the registered pin groups.
>
> root@beaglebone:/sys/kernel/debug/pinctrl/44e10800.pinmux# cat pins |more
> registered pins: 142
> pin 0 (44e10800) 0031 pinctrl-single
> pin 1 (44e10804) 0031 pinctrl-single
> pin 2 (44e10808) 0031 pinctrl-single
> pin 3 (44e1080c) 0031 pinctrl-single
> pin 4 (44e10810) 0031 pinctrl-single
> pin 5 (44e10814) 0031 pinctrl-single
> pin 6 (44e10818) 0031 pinctrl-single
> pin 7 (44e1081c) 0031 pinctrl-single
> pin 8 (44e10820) 0027 pinctrl-single
> pin 9 (44e10824) 0027 pinctrl-single
> pin 10 (44e10828) 0027 pinctrl-single
> pin 11 (44e1082c) 0027 pinctrl-single
> pin 12 (44e10830) 0027 pinctrl-single
> 
>
> The pin 12 on the P9 header ( GPIO1_28 - 1*32 + 28 ) is the GPIO60 ( not
> PIN60 ). If we search for the same offset (0x078) we see that pin 30 is 30
> HEX ( 11 in binary ) which relates to GPIO pin configuration settings (
> mmode , puden ,  etc).
>
> Hope it helps. Please correct me if I'm wrong.
>
>
> On Sun, Dec 25, 2016 at 3:35 PM,  wrote:
>
>> Hello, how are pin numbers in 
>> /sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins
>> related to any other numbering? (connectors or chip pins)
>>
>> For example, there are 11 eMMC pins listed in that file:
>>
>> pin 0 (44e10800.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 1 (44e10804.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 2 (44e10808.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 3 (44e1080c.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 4 (44e10810.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 5 (44e10814.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 6 (44e10818.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 7 (44e1081c.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 32 (44e10880.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 33 (44e10884.0): 481d8000.mmc (GPIO UNCLAIMED) function
>> pinmux_emmc_pins group pinmux_emmc_pins
>> pin 88 (44e10960.0): 4806.mmc (GPIO UNCLAIMED) function
>> pinmux_mmc1_pins group pinmux_mmc1_pins
>>
>> I would like to relate them to the 10 eMMC pins in the Reference Manual:
>>
>> 22 V8 MMC1_DAT5
>> 23 U8 MMC1_DAT4
>> 24 V7 MMC1_DAT1
>> 5 R8 MMC1_DAT2
>> 4 T9 MMC1_DAT7
>> 3 R9 MMC1_DAT6
>> 6 T8 MMC1_DAT3
>> 25 U7 MMC1_DAT0
>> 20 V9 MMC1_CMD
>> 21 U9 MMC1_CLK
>>
>> --
>> 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/ms
>> gid/beagleboard/c93f7ef8-df5f-46f7-85d7-aa90aefd7981%40googlegroups.com
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
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/CANA2BUUeefE4KPq6vUD7gfQG3yAHfBbRaJcXWj8d%3DAgQMLZ1hw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Pin numbering in pinmux-pins

[ithinu]

Hello, how are pin numbers in 
/sys/kernel/debug/pinctrl/44e10800.pinmux/pinmux-pins related to any other 
numbering? (connectors or chip pins)

For example, there are 11 eMMC pins listed in that file:

pin 0 (44e10800.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 1 (44e10804.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 2 (44e10808.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 3 (44e1080c.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 4 (44e10810.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 5 (44e10814.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 6 (44e10818.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 7 (44e1081c.0): 481d8000.mmc (GPIO UNCLAIMED) function pinmux_emmc_pins 
group pinmux_emmc_pins
pin 32 (44e10880.0): 481d8000.mmc (GPIO UNCLAIMED) function 
pinmux_emmc_pins group pinmux_emmc_pins
pin 33 (44e10884.0): 481d8000.mmc (GPIO UNCLAIMED) function 
pinmux_emmc_pins group pinmux_emmc_pins
pin 88 (44e10960.0): 4806.mmc (GPIO UNCLAIMED) function 
pinmux_mmc1_pins group pinmux_mmc1_pins

I would like to relate them to the 10 eMMC pins in the Reference Manual:

22 V8 MMC1_DAT5
23 U8 MMC1_DAT4
24 V7 MMC1_DAT1
5 R8 MMC1_DAT2
4 T9 MMC1_DAT7
3 R9 MMC1_DAT6
6 T8 MMC1_DAT3
25 U7 MMC1_DAT0
20 V9 MMC1_CMD
21 U9 MMC1_CLK

-- 
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/c93f7ef8-df5f-46f7-85d7-aa90aefd7981%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to enable bash history?

[ithinu]

Add to .bashrc

PROMPT_COMMAND="history -a"
shopt -s histappend


-- 
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/e87af9c5-0e75-4ca5-aea7-c6bdc65d2e5a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] How to enable bash history?

[ithinu]

In principle, everything looks ok:

# set -o | grep history
history on
#  echo $HISTFILE
/root/.bash_history
# echo $HISTSIZE
500
# echo $HISTFILESIZE
500

But .bash_history is empty and the history is lost between sessions.

-- 
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/4fd53dba-e058-426e-8bbf-b01a45311247%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] USB over Ethernet does not work, only USB mass device

[Ithinu]

Ok, I found the docs and the new Debian works fine with the cape. Thanks!

On Sat, Dec 24, 2016 at 5:27 PM, Artur Rataj  wrote:

> Ok, I found the docs and the new Debian works fine with the cape. Thanks!
>
> On Sat, Dec 24, 2016 at 3:21 PM,  wrote:
>
>> I would guess trhat it is like that: I should reflash the eMMC with
>> eMMC/HDMI enabled. Then, as rootfs being an image is readonly, I should
>> download the non-flashing version and boot from it if I want to use the lcd
>> card. HDMI/eMMC should be disabled but only on the card. What is the exact
>> purpose of the boot button if Beagleboard can boots from the card even if
>> the button is not pressed?
>>
>>
>> On Saturday, December 24, 2016 at 2:51:07 PM UTC+1, ith...@gmail.com
>> wrote:
>>>
>>> "Yet, the card"
>>>
>>> On Saturday, December 24, 2016 at 2:49:40 PM UTC+1, ith...@gmail.com
>>> wrote:

 I flashed the new image and the board started to work correctly, both
 mass device and Ethernet over USB. However, after disabling HDMI and eMMc
 as you suggested, none of these two shows up, as if the board weren't
 connected at all.

 Is it that "disable eMMC" disables eMMC completely, so that not it does
 not work as a boot partition? Should I thus always boot from the card if I
 want to use the cape? Yes, the card keeps reflashing eMMC. rootfs mounts
 readonly to PC sot
 that I can not disable the reflashing. What should I do?

 On Saturday, December 24, 2016 at 2:03:25 AM UTC+1, RobertCNelson wrote:
>
> On Fri, Dec 23, 2016 at 5:33 PM,   wrote:
> > Thanks Robert for fixing this. However, I use this lcd cape:
> >
> > http://pl.farnell.com/element14/bb-cape-disp-ct43/display-bo
> ard-tft-lcd-beaglebone/dp/2526164
> >
> > for which I need "temporarily" a custom image:
> > https://www.element14.com/community/docs/DOC-81966
> >
> > "The intention is to provision and release an official
> beagleboard.org
> > supported firmware image that will be posted
> > to beagleboard.org’s firmware images page"
> >
> > which also does not bring usb0.
> >
> > I wonder if the image which you linked might already support the
> cape? I
> > think that I will just flash that image and not use
> > the lcd for now.
>
> Oh that lcd/board combination is supported, with a couple small
> tweaks..
>
> Grab the lxqt-4gb image, and boot..
>
> Login and change:
>
> /boot/uEnv.txt
>
> dtb=am335x-boneblack-overlay.dtb
>
> and also run:
>
> sudo apt update ; sudo apt upgrade
>
> as another user just solved the lightdm startup issue today, so that
> was just pushed to the repo..
>
> (this sunday's snapshot will have that package updated by default)
>
> and we are a few weeks away from making that cape work out of the box
> (all lcd3/lcd4/lcd7 capes)
>
> 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/CANA2BUU1wPvtZdkZGrnUmuQiiW2wob-RWu6es7H64tjbAmYNSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] USB over Ethernet does not work, only USB mass device

[ithinu]

I would guess trhat it is like that: I should reflash the eMMC with 
eMMC/HDMI enabled. Then, as rootfs being an image is readonly, I should 
download the non-flashing version and boot from it if I want to use the lcd 
card. HDMI/eMMC should be disabled but only on the card. What is the exact 
purpose of the boot button if Beagleboard can boots from the card even if 
the button is not pressed?

On Saturday, December 24, 2016 at 2:51:07 PM UTC+1, ith...@gmail.com wrote:
>
> "Yet, the card"
>
> On Saturday, December 24, 2016 at 2:49:40 PM UTC+1, ith...@gmail.com 
> wrote:
>>
>> I flashed the new image and the board started to work correctly, both 
>> mass device and Ethernet over USB. However, after disabling HDMI and eMMc 
>> as you suggested, none of these two shows up, as if the board weren't 
>> connected at all.
>>
>> Is it that "disable eMMC" disables eMMC completely, so that not it does 
>> not work as a boot partition? Should I thus always boot from the card if I 
>> want to use the cape? Yes, the card keeps reflashing eMMC. rootfs mounts 
>> readonly to PC sot
>> that I can not disable the reflashing. What should I do?
>>
>> On Saturday, December 24, 2016 at 2:03:25 AM UTC+1, RobertCNelson wrote:
>>>
>>> On Fri, Dec 23, 2016 at 5:33 PM,   wrote: 
>>> > Thanks Robert for fixing this. However, I use this lcd cape: 
>>> > 
>>> > 
>>> http://pl.farnell.com/element14/bb-cape-disp-ct43/display-board-tft-lcd-beaglebone/dp/2526164
>>>  
>>> > 
>>> > for which I need "temporarily" a custom image: 
>>> > https://www.element14.com/community/docs/DOC-81966 
>>> > 
>>> > "The intention is to provision and release an official beagleboard.org 
>>> > supported firmware image that will be posted 
>>> > to beagleboard.org’s firmware images page" 
>>> > 
>>> > which also does not bring usb0. 
>>> > 
>>> > I wonder if the image which you linked might already support the cape? 
>>> I 
>>> > think that I will just flash that image and not use 
>>> > the lcd for now. 
>>>
>>> Oh that lcd/board combination is supported, with a couple small tweaks.. 
>>>
>>> Grab the lxqt-4gb image, and boot.. 
>>>
>>> Login and change: 
>>>
>>> /boot/uEnv.txt 
>>>
>>> dtb=am335x-boneblack-overlay.dtb 
>>>
>>> and also run: 
>>>
>>> sudo apt update ; sudo apt upgrade 
>>>
>>> as another user just solved the lightdm startup issue today, so that 
>>> was just pushed to the repo.. 
>>>
>>> (this sunday's snapshot will have that package updated by default) 
>>>
>>> and we are a few weeks away from making that cape work out of the box 
>>> (all lcd3/lcd4/lcd7 capes) 
>>>
>>> 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/86b957ee-e6ff-436c-b33b-5311c7de3241%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] USB over Ethernet does not work, only USB mass device

[ithinu]

"Yet, the card"

On Saturday, December 24, 2016 at 2:49:40 PM UTC+1, ith...@gmail.com wrote:
>
> I flashed the new image and the board started to work correctly, both mass 
> device and Ethernet over USB. However, after disabling HDMI and eMMc as you 
> suggested, none of these two shows up, as if the board weren't connected at 
> all.
>
> Is it that "disable eMMC" disables eMMC completely, so that not it does 
> not work as a boot partition? Should I thus always boot from the card if I 
> want to use the cape? Yes, the card keeps reflashing eMMC. rootfs mounts 
> readonly to PC sot
> that I can not disable the reflashing. What should I do?
>
> On Saturday, December 24, 2016 at 2:03:25 AM UTC+1, RobertCNelson wrote:
>>
>> On Fri, Dec 23, 2016 at 5:33 PM,   wrote: 
>> > Thanks Robert for fixing this. However, I use this lcd cape: 
>> > 
>> > 
>> http://pl.farnell.com/element14/bb-cape-disp-ct43/display-board-tft-lcd-beaglebone/dp/2526164
>>  
>> > 
>> > for which I need "temporarily" a custom image: 
>> > https://www.element14.com/community/docs/DOC-81966 
>> > 
>> > "The intention is to provision and release an official beagleboard.org 
>> > supported firmware image that will be posted 
>> > to beagleboard.org’s firmware images page" 
>> > 
>> > which also does not bring usb0. 
>> > 
>> > I wonder if the image which you linked might already support the cape? 
>> I 
>> > think that I will just flash that image and not use 
>> > the lcd for now. 
>>
>> Oh that lcd/board combination is supported, with a couple small tweaks.. 
>>
>> Grab the lxqt-4gb image, and boot.. 
>>
>> Login and change: 
>>
>> /boot/uEnv.txt 
>>
>> dtb=am335x-boneblack-overlay.dtb 
>>
>> and also run: 
>>
>> sudo apt update ; sudo apt upgrade 
>>
>> as another user just solved the lightdm startup issue today, so that 
>> was just pushed to the repo.. 
>>
>> (this sunday's snapshot will have that package updated by default) 
>>
>> and we are a few weeks away from making that cape work out of the box 
>> (all lcd3/lcd4/lcd7 capes) 
>>
>> 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/7848e97a-10f0-475a-876f-fbfe5b930552%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] USB over Ethernet does not work, only USB mass device

[ithinu]

I flashed the new image and the board started to work correctly, both mass 
device and Ethernet over USB. However, after disabling HDMI and eMMc as you 
suggested, none of these two shows up, as if the board weren't connected at 
all.

Is it that "disable eMMC" disables eMMC completely, so that not it does not 
work as a boot partition? Should I thus always boot from the card if I want 
to use the cape? Yes, the card keeps reflashing eMMC. rootfs mounts 
readonly to PC sot
that I can not disable the reflashing. What should I do?

On Saturday, December 24, 2016 at 2:03:25 AM UTC+1, RobertCNelson wrote:
>
> On Fri, Dec 23, 2016 at 5:33 PM,  > wrote: 
> > Thanks Robert for fixing this. However, I use this lcd cape: 
> > 
> > 
> http://pl.farnell.com/element14/bb-cape-disp-ct43/display-board-tft-lcd-beaglebone/dp/2526164
>  
> > 
> > for which I need "temporarily" a custom image: 
> > https://www.element14.com/community/docs/DOC-81966 
> > 
> > "The intention is to provision and release an official beagleboard.org 
> > supported firmware image that will be posted 
> > to beagleboard.org’s firmware images page" 
> > 
> > which also does not bring usb0. 
> > 
> > I wonder if the image which you linked might already support the cape? I 
> > think that I will just flash that image and not use 
> > the lcd for now. 
>
> Oh that lcd/board combination is supported, with a couple small tweaks.. 
>
> Grab the lxqt-4gb image, and boot.. 
>
> Login and change: 
>
> /boot/uEnv.txt 
>
> dtb=am335x-boneblack-overlay.dtb 
>
> and also run: 
>
> sudo apt update ; sudo apt upgrade 
>
> as another user just solved the lightdm startup issue today, so that 
> was just pushed to the repo.. 
>
> (this sunday's snapshot will have that package updated by default) 
>
> and we are a few weeks away from making that cape work out of the box 
> (all lcd3/lcd4/lcd7 capes) 
>
> 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/b56203b9-c8f5-4e26-9442-c5de442ad9e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] USB over Ethernet does not work, only USB mass device

[ithinu]

Thanks Robert for fixing this. However, I use this lcd cape:

http://pl.farnell.com/element14/bb-cape-disp-ct43/display-board-tft-lcd-beaglebone/dp/2526164

for which I need "temporarily" a custom image: 
https://www.element14.com/community/docs/DOC-81966

"The intention is to provision and release an official beagleboard.org 
supported firmware image that will be posted
to beagleboard.org’s firmware images page"

which also does not bring usb0.

I wonder if the image which you linked might already support the cape? I 
think that I will just flash that image and not use
the lcd for now.


On Friday, December 23, 2016 at 11:59:22 PM UTC+1, RobertCNelson wrote:
>
> On Fri, Dec 23, 2016 at 4:55 PM,  > wrote: 
> > Hi, I have pluggeg in a new BB Black to Linux Mint, once LM 18.1, now 
> some 
> > older version, but the results are similar. The mass device connects 
> > instantly, the leds blink, but there is nothing at 192.168.7.2. I attach 
> > ifconfig, then syslog. 
> > 
> > Du you know what might be the problem? 
>
> Please reflash 
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_lxqt 
>
> There was an issue with usb0 that i had solved last week.. (race 
> condition during the setup of wlan0) 
>
> 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/bdf1fc33-a70f-4713-8deb-815c711c007e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] USB over Ethernet does not work, only USB mass device

[ithinu]

Hi, I have pluggeg in a new BB Black to Linux Mint, once LM 18.1, now some 
older version, but the results are similar. The mass device connects 
instantly, the leds blink, but there is nothing at 192.168.7.2. I attach 
ifconfig, then syslog.

Du you know what might be the problem?

eth0  Link encap:Ethernet  HWaddr 00:19:99:e8:64:40  
  inet addr:192.168.100.4  Bcast:192.168.100.255  Mask:255.255.255.0
  inet6 addr: fe80::219:99ff:fee8:6440/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:2098119 errors:0 dropped:0 overruns:0 frame:0
  TX packets:1165704 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:2883043840 (2.8 GB)  TX bytes:87011521 (87.0 MB)

eth1  Link encap:Ethernet  HWaddr 60:64:05:fe:ff:6b  
  inet6 addr: fe80::6264:5ff:fefe:ff6b/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:46 errors:3 dropped:0 overruns:0 frame:3
  TX packets:187 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:10507 (10.5 KB)  TX bytes:45720 (45.7 KB)

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:2842 errors:0 dropped:0 overruns:0 frame:0
  TX packets:2842 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:0 

Dec 23 23:48:19 nebula kernel: [1.187206] usb 2-1.1: new high-speed USB 
device number 37 using ehci-pci
Dec 23 23:48:19 nebula kernel: [1.280513] usb 2-1.1: New USB device 
found, idVendor=1d6b, idProduct=0104
Dec 23 23:48:19 nebula kernel: [1.280518] usb 2-1.1: New USB device 
strings: Mfr=3, Product=4, SerialNumber=5
Dec 23 23:48:19 nebula kernel: [1.280521] usb 2-1.1: Product: 
BeagleBoneBlack
Dec 23 23:48:19 nebula kernel: [1.280523] usb 2-1.1: Manufacturer: 
Circuitco
Dec 23 23:48:19 nebula kernel: [1.280525] usb 2-1.1: SerialNumber: 
A0-4816BBBK2EBD
Dec 23 23:48:19 nebula kernel: [1.283290] rndis_host 2-1.1:1.0 eth1: 
register 'rndis_host' at usb-:00:1d.0-1.1, RNDIS device, 
60:64:05:fe:ff:6b
Dec 23 23:48:19 nebula kernel: [1.283774] cdc_acm 2-1.1:1.2: This 
device cannot do calls on its own. It is not a modem.
Dec 23 23:48:19 nebula kernel: [1.283824] cdc_acm 2-1.1:1.2: ttyACM0: 
USB ACM device
Dec 23 23:48:19 nebula kernel: [1.284525] usb-storage 2-1.1:1.4: USB 
Mass Storage device detected
Dec 23 23:48:19 nebula kernel: [1.284720] scsi21 : usb-storage 2-1.1:1.4
Dec 23 23:48:19 nebula mtp-probe: checking bus 2, device 37: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1"
Dec 23 23:48:19 nebula mtp-probe: bus: 2, device: 37 was not an MTP device
Dec 23 23:48:19 nebula NetworkManager[2704]:  failed to allocate link 
cache: (-12) Object not found
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): carrier is OFF
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): new Ethernet 
device (driver: 'rndis_host' ifindex: 20)
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): exported as 
/org/freedesktop/NetworkManager/Devices/17
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): device state 
change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): bringing up 
device.
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): carrier now ON 
(device state 20)
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): preparing 
device.
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): deactivating 
device (reason 'managed') [2]
Dec 23 23:48:19 nebula NetworkManager[2704]:  Added default wired 
connection 'Wired connection 1' for 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/net/eth1
Dec 23 23:48:19 nebula NetworkManager[2704]:SCPlugin-Ifupdown: devices 
added (path: 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/net/eth1, 
iface: eth1)
Dec 23 23:48:19 nebula NetworkManager[2704]:SCPlugin-Ifupdown: device 
added (path: 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/net/eth1, 
iface: eth1): no ifupdown configuration found.
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): device state 
change: unavailable -> disconnected (reason 'none') [20 30 0]
Dec 23 23:48:19 nebula NetworkManager[2704]:  Auto-activating 
connection 'Wired connection 1'.
Dec 23 23:48:19 nebula NetworkManager[2704]:  Activation (eth1) 
starting connection 'Wired connection 1'
Dec 23 23:48:19 nebula NetworkManager[2704]:  (eth1): device state 
change: disconnected -> prepare (reason 'none') [30 40 0]
Dec 23 23:48:19 nebula NetworkManager[2704]:  Activation (eth1) Stage 
1 of 5 (Device Prepare) scheduled...
Dec 23 23:48:19 nebula NetworkManager[2704]:  Activation (eth1) Stage 
1 of 5 (Device Prepare) started...
Dec 23 23:48:19 nebula NetworkManager[2704]:  A

[beagleboard] No USB over Ethernet, only USB mass device

[ithinu]

Hi, I plugged in a new BB to Linux Mint 18.1, the problem as in topic.

I attach the syslog. Any ideas?


Dec 23 19:12:10 mint kernel: [ 1390.005861] usb 2-1.6: new high-speed USB 
device number 13 using ehci-pci
Dec 23 19:12:10 mint kernel: [ 1390.099150] usb 2-1.6: New USB device 
found, idVendor=1d6b, idProduct=0104
Dec 23 19:12:10 mint kernel: [ 1390.099154] usb 2-1.6: New USB device 
strings: Mfr=2, Product=3, SerialNumber=4
Dec 23 19:12:10 mint kernel: [ 1390.099156] usb 2-1.6: Product: 
BeagleBoneBlack
Dec 23 19:12:10 mint kernel: [ 1390.099158] usb 2-1.6: Manufacturer: 
Circuitco
Dec 23 19:12:10 mint kernel: [ 1390.099160] usb 2-1.6: SerialNumber: 
A0-4816BBBK2EBD
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1239] device 
(eth0): failed to find device 5 'eth0' with udev
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1251] 
manager: (eth0): new Ethernet device 
(/org/freedesktop/NetworkManager/Devices/4)
Dec 23 19:12:10 mint kernel: [ 1390.102922] rndis_host 2-1.6:1.0 eth0: 
register 'rndis_host' at usb-:00:1d.0-1.6, RNDIS device, 
60:64:05:fe:ff:6b
Dec 23 19:12:10 mint kernel: [ 1390.103446] cdc_acm 2-1.6:1.2: ttyACM0: USB 
ACM device
Dec 23 19:12:10 mint kernel: [ 1390.103993] usb-storage 2-1.6:1.4: USB Mass 
Storage device detected
Dec 23 19:12:10 mint kernel: [ 1390.104108] scsi host8: usb-storage 
2-1.6:1.4
Dec 23 19:12:10 mint mtp-probe: checking bus 2, device 13: 
"/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6"
Dec 23 19:12:10 mint mtp-probe: bus: 2, device: 13 was not an MTP device
Dec 23 19:12:10 mint kernel: [ 1390.116570] rndis_host 2-1.6:1.0 
enx606405feff6b: renamed from eth0
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1586] device 
(eth0): interface index 5 renamed iface from 'eth0' to 'enx606405feff6b'
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1629] 
devices added (path: 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/net/enx606405feff6b,
 
iface: enx606405feff6b)
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1630] device 
added (path: 
/sys/devices/pci:00/:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/net/enx606405feff6b,
 
iface: enx606405feff6b): no ifupdown configuration found.
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1634] device 
(enx606405feff6b): state change: unmanaged -> unavailable (reason 
'managed') [10 20 2]
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1639] device 
(enx606405feff6b): link connected
Dec 23 19:12:10 mint kernel: [ 1390.143135] IPv6: ADDRCONF(NETDEV_UP): 
enx606405feff6b: link is not ready
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1652] 
keyfile: add connection in-memory 
(b658715f-b7f9-3986-a744-cfbba6bd59be,"Wired connection 1")
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1656] 
settings: (enx606405feff6b): created default wired connection 'Wired 
connection 1'
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1672] device 
(enx606405feff6b): state change: unavailable -> disconnected (reason 
'none') [20 30 0]
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1678] 
policy: auto-activating connection 'Wired connection 1'
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1686] device 
(enx606405feff6b): Activation: starting connection 'Wired connection 1' 
(b658715f-b7f9-3986-a744-cfbba6bd59be)
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1687] device 
(enx606405feff6b): state change: disconnected -> prepare (reason 'none') 
[30 40 0]
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1690] device 
(enx606405feff6b): state change: prepare -> config (reason 'none') [40 50 0]
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1692] device 
(enx606405feff6b): state change: config -> ip-config (reason 'none') [50 70 
0]
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1695] dhcp4 
(enx606405feff6b): activation: beginning transaction (timeout in 45 seconds)
Dec 23 19:12:10 mint NetworkManager[1552]:   [1482520330.1706] dhcp4 
(enx606405feff6b): dhclient started with pid 4939
Dec 23 19:12:10 mint dhclient[4939]: DHCPREQUEST of 192.168.7.1 on 
enx606405feff6b to 255.255.255.255 port 67 (xid=0x4c673499)
Dec 23 19:12:10 mint colord-sane: [bjnp] create_broadcast_socket: ERROR - 
bind socket to local address failed - Cannot assign requested address
Dec 23 19:12:11 mint kernel: [ 1391.102720] scsi 8:0:0:0: Direct-Access 
LinuxFile-CD Gadget   0308 PQ: 0 ANSI: 2
Dec 23 19:12:11 mint kernel: [ 1391.103047] sd 8:0:0:0: Attached scsi 
generic sg7 type 0
Dec 23 19:12:11 mint kernel: [ 1391.104223] sd 8:0:0:0: [sdg] 196608 
512-byte logical blocks: (101 MB/96.0 MiB)
Dec 23 19:12:11 mint kernel: [ 1391.104942] sd 8:0:0:0: [sdg] Write Protect 
is off
Dec 23 19:12:11 mint kernel: [ 1391.104946] sd 8:0:0:0: [sdg] Mode Sense: 
0f 00 00 00
Dec 23 19:12:11 mint kernel: [ 1391.105580] sd 8:0:0:0: [sdg] Write cache: 
enabled, read cache: enabled, doesn't support DPO or FUA
Dec 23 19:12:1