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

GoogleGroups
1

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.

2

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,

3

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

Regards,

4

Hi Robert,

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

5

As Shown:

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

Regards,

7

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 ?