connecting to 192.168.7.2 failing after updating to kernel 4.1.36-bone-rt-r24

[malkowki]

Dear,

after updating my beaglebone REVC board from kernel 4.1.21-bone-rt-r20 to 4.1.36-bone-rt-r24 using Robert Nelson script , I am having issue connecting from  ssh Putty Host Window7 PC  to the board via USB to 192.168.7.2.
Before the update it was working perfectly now it looks like the USB Serial Gadget drivers got corrupted?

Is there a way to restore this?

Thanks for any suggestion.

[Robert Nelson]

Well part of the problem "4.1.21-bone-rt-r20" didn't actually have
"RT" enabled, that first got fixed in "4.1.24-bone-rt-r22" via:

https://github.com/RobertCNelson/bb-kernel/commit/6188fa0514e557f195362481a0d5087c3891f4e6

Otherwise, RT = CONFIG_PREEMPT/CONFIG_PREEMPT_RT_FULL and usb
problem's this isn't really new....

This has always been a known issue, i bet if you swap to the non-rt
version of 4.1.21-bone20 it'll work just fine..

Regards,

--
Robert Nelson
https://rcn-ee.com/

[roberts...@yahoo.com]

--------------------------------------------
On Wed, 12/21/16, Robert Nelson <robert...@gmail.com> wrote:

Subject: Re: [beagleboard] connecting to 192.168.7.2 failing after updating to kernel 4.1.36-bone-rt-r24
To: "Beagle Board" <beagl...@googlegroups.com>
Cc: "Beninio Mbila" <bmb.tec...@gmail.com>
Date: Wednesday, December 21, 2016, 10:00 PM

--
For more options, visit http://beagleboard.org/discuss
---
You received this message
because you are subscribed to the Google Groups
"BeagleBoard" group.
To
unsubscribe from this group and stop receiving emails from
it, send an email to beagleboard...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/CAOCHtYi3ULP%3D22vyMTiEpYi_yro_sOJ4xBBpbRy%2BZsEuRY6ipg%40mail.gmail.com.
For
more options, visit https://groups.google.com/d/optout.
6Carol. Acesta s-a casatorit in 1892 cu principesa Maria de Edinburgh nepoata reginei Victoria a Angliei. La 14 26 martie 1881 Parlamentul a votat transformarea Romaniei in Regat punand inca o data Europa in fata faptului implinit. Romania isi decidea astfel singura soarta in istorie. in 1881 tara noastra intretinea relatii diplomatice cu 18 state ale lumii.

[Robert Nelson]

On Wed, Dec 21, 2016 at 2:18 PM, Beninio Mbila <bmb.tec...@gmail.com> wrote:
>
>
> Hello Robert,
>
> Thanks to highlight this known issue. I had issue in the past with non rt kernel version because the PRU Was not working. Can you confirm that switching to 4.1.21-bone-20 won't affect the PRU driver?

Well, v4.1.x-lts is in maintenance mode now that v4.9.x-lts is out, so
if it worked before it'll probably still work BUT i'm not TESTING
v4.1.x anymore..

Please feel free to update to v4.4.x or v4.9.x..

[Beninio Mbila]

Hi Robert,

Thanks I will try this update, can I still use your update script for this?

[Robert Nelson]

On Wed, Dec 21, 2016 at 2:32 PM, Beninio Mbila <bmb.tec...@gmail.com> wrote:
> Hi Robert,
>
> Thanks I will try this update, can I still use your update script for this?

As Shown:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Kernel_Options

[malkowki]

[malkowki]

Hi Robert,

after having compile the image 4.9.6-bone4 I still cannot ssh to 192.168.1.1 so I have tried to switch back to 4.1.21-bone-rt-r20 by modifying the uEnv.txt and reboot then I get:

Checking if uname_r is set in /boot/uEnv.txt...

gpio: pin 56 (gpio 56) value is 1

Running uname_boot ...

** Invalid partition 2 **

** Invalid partition 3 **

** Invalid partition 4 **

** Invalid partition 5 **

** Invalid partition 6 **

** Invalid partition 7 **

## Error: "bootcmd_nand0" not defined

link up on port 0, speed 100, full duplex

BOOTP broadcast 1

DHCP client bound to address 172.23.16.115 (99 ms)

Using cpsw device

TFTP from server 172.23.20.17; our IP address is 172.23.16.115; sending through gateway 172.23.16.254

Filename '\smsboot\x64\wdsnbp.com'.

Load address: 0x82000000

Loading: * ###

     2.7 MiB/s

done

Bytes transferred = 30832 (7870 hex)

missing environment variable: pxeuuid

Retrieving file: pxelinux.cfg/01-78-a5-04-cc-37-c1

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 172.23.20.17; our IP address is 172.23.16.115; sending through gateway 172.23.16.254

Filename 'pxelinux.cfg/01-78-a5-04-cc-37-c1'.

Load address: 0x80100000

Loading: *

TFTP error: 'Access violation.' (4)

Starting again


Retrieving file: pxelinux.cfg/AC171073

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 172.23.20.17; our IP address is 172.23.16.115; sending through gateway 172.23.16.254

Filename 'pxelinux.cfg/AC171073'.

Load address: 0x80100000

Loading: *

TFTP error: 'Access violation.' (4)

Starting again
Retrieving file: pxelinux.cfg/AC1710

link up on port 0, speed 100, full duplex

Using cpsw device

TFTP from server 172.23.20.17; our IP address is 172.23.16.115; sending through gateway 172.23.16.254

Filename 'pxelinux.cfg/AC1710'.

Load address: 0x80100000

Loading: *

TFTP error: 'Access violation.

Is there a way to solve this ?