[beagleboard] Gateway problem

[massafrodo]

Hi

I have a BeagleBone Black with a huge Problem

I i flashed the image Debian 9.5 2018-10-07 4GB SD IoT 

 

I have one PC in Network 192.168.144.xxx Gateway 192.168.144.254
The Beaglebone is in network 192.168.143.xxx  Gateway 192.168.143.254

My interfaces file:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo eth0
iface lo inet loopback

# The primary network interface
# auto eth0
iface eth0 inet static
address 192.168.143.207
netmask 255.255.255.0
gateway 192.168.143.254

# Example to keep MAC address between reboots
#hwaddress ether DE:AD:BE:EF:CA:FE

##connman: ethX static config
#connmanctl services
#Using the appropriate ethernet service, tell connman to setup a static IP 
address for that service:
#sudo connmanctl config  --ipv4 manual   
 --nameservers 

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




# Ethernet/RNDIS gadget (g_ether)
# Used by: /opt/scripts/boot/autoconfigure_usb0.sh
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.252
network 192.168.7.0
gateway 192.168.7.1


I can't ping the BeagleBone from the PC. It is possible to ping the Gateway 
in 192.168.143.xxx from PC and Beaglebone.

After booting the BeagleBone,  the "route" command shows:

Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse 
Iface
default 0.0.0.0 0.0.0.0 U 0  00 eth0
default 192.168.143.254 0.0.0.0 UG0  00 eth0
link-local  0.0.0.0 255.255.0.0 U 0  00 eth0
192.168.6.0 0.0.0.0 255.255.255.252 U 0  00 usb1
192.168.7.0 0.0.0.0 255.255.255.252 U 0  00 usb0
192.168.143.0   0.0.0.0 255.255.255.0   U 0  00 eth0

There are two default routes!?!?!?!?!  WHY?

If i restart the network service, the first default route disappears and i 
can successfully ping the Beaglebone from the PC in the 192.168.144 network.
What did i wrong?

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a6096ac8-1396-4433-9239-80e0a1e95135%40googlegroups.com.

[beagleboard] Re: PRU does not start.

[areytim via BeagleBoard]

I'm having the same issue and wondering if this was resolved?  I'm getting 
the exact same error message when trying to start and here is  my tail of 
 dmesg

[   86.179253] pruss 4a30.pruss: creating PRU cores and other child 
platform devices

[   86.211623] remoteproc remoteproc1: 4a334000.pru is available

[   86.211753] pru-rproc 4a334000.pru: PRU rproc node 
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully

[   86.219632] remoteproc remoteproc2: 4a338000.pru is available

[   86.219765] pru-rproc 4a338000.pru: PRU rproc node 
/ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully

[  112.609040] remoteproc remoteproc1: powering up 4a334000.pru

[  112.614874] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  112.614903] remoteproc remoteproc1: request_firmware failed: -2

[  112.624747] remoteproc remoteproc1: Boot failed: -2

[  120.185318] remoteproc remoteproc1: powering up 4a334000.pru

[  120.185412] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  120.185431] remoteproc remoteproc1: request_firmware failed: -2

[  120.197453] remoteproc remoteproc1: Boot failed: -2

[  140.249570] remoteproc remoteproc1: powering up 4a334000.pru

[  140.249661] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  140.249678] remoteproc remoteproc1: request_firmware failed: -2

[  140.262930] remoteproc remoteproc1: Boot failed: -2

[  189.299778] remoteproc remoteproc1: powering up 4a334000.pru

[  189.299866] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  189.299884] remoteproc remoteproc1: request_firmware failed: -2

[  189.311901] remoteproc remoteproc1: Boot failed: -2

[  351.346600] remoteproc remoteproc1: powering up 4a334000.pru

[  351.346699] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  351.346716] remoteproc remoteproc1: request_firmware failed: -2

[  351.357944] remoteproc remoteproc1: Boot failed: -2

[  376.604021] remoteproc remoteproc1: powering up 4a334000.pru

[  376.604110] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  376.604128] remoteproc remoteproc1: request_firmware failed: -2

[  376.615227] remoteproc remoteproc1: Boot failed: -2

[  414.102771] remoteproc remoteproc1: powering up 4a334000.pru

[  414.102862] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  414.102879] remoteproc remoteproc1: request_firmware failed: -2

[  414.113818] remoteproc remoteproc1: Boot failed: -2

[  620.182892] remoteproc remoteproc1: powering up 4a334000.pru

[  620.182982] remoteproc remoteproc1: Direct firmware load for 
am335x-pru0-fw failed with error -2

[  620.183003] remoteproc remoteproc1: request_firmware failed: -2

[  620.193899] remoteproc remoteproc1: Boot failed: -2


Following the setup exactly in Exploring BBB D Molloy chp15

On Monday, March 11, 2019 at 12:35:58 PM UTC-6, din...@gmail.com wrote:
>
> Could you post the output of "dmesg | tail -40" so that we can see the 
> other remoteproc related kernel messages?
>
> Are you by any chance using pru-gcc? If yes, you would need to upgrade 
> your kernel to 4.14.94-ti-r96 . If you are using clpru then you should be 
> fine.
>
> Regards,
> Dimitar
>
> On Sunday, March 10, 2019 at 6:27:40 PM UTC+2, gw wrote:
>>
>> Hello.
>> I need help regarding PRU.
>> I tried to enable the PRU by a command below.
>>
>> *root@beaglebone:/sys/class/remoteproc/remoteproc1# echo 'start' > state  
>>*
>> -bash: echo: write error: No such file or directory
>>
>> But I get above result and PRU does not start.
>> I also tried sudo sh -c "echo 'start' > state" but I got an I/O error.
>>
>> Please help me.
>> Below are related information.
>>
>>
>> *debian@beaglebone:~$ dmesg |grep pru*
>> [   82.512558] pruss 4a30.pruss: creating PRU cores and other child 
>> platform devices
>> [   82.531307] remoteproc remoteproc1: 4a334000.pru is available
>> [   82.531436] pru-rproc 4a334000.pru: PRU rproc node 
>> /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
>> [   82.539513] remoteproc remoteproc2: 4a338000.pru is available
>> [   82.539647] pru-rproc 4a338000.pru: PRU rproc node 
>> /ocp/pruss_soc_bus@4a32600
>> [ 1864.134156] remoteproc remoteproc1: powering up 4a334000.pru
>> [ 1864.134336] remoteproc remoteproc1: Direct firmware load for 
>> am335x-pru0-fw failed with error -2
>>
>> *root@beaglebone:/sys/class/remoteproc/remoteproc1# sudo 
>> /opt/scripts/tools/version.sh*
>> git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
>> eeprom:[A335BNLTBWA51712EW004500]
>> model:[TI_AM335x_BeagleBone_Black_Wireless]
>> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
>> 2018.09-2-g0b54a51eee]:[location: dd MBR]
>> kernel:[4.14.71-ti-r80]
>> nodejs:[v6.14.4]
>> ub

[beagleboard] Error on device overlay?

[Charles]

I am trying to using pins P8_12 and P8_46 to the PRUs R30 register

This would be P8_12 in mode 6, and P8_46 in mode 5 . 

I want to exclusively use these pins by the pru(s).  I modified an example 
dts file, but it wont compile (says syntax error).  I am missing it (the 
error), and hopefully can get a second set of  eyes on it

/*
* Copyright (C) 2012 Texas Instruments Incorporated - http://www.ti.com/
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Purpose License Version 2 as
* published by the Free Software Foundation
*
* Original from: 
github.com/jadonk/validation-scripts/blob/master/test-capemgr/
*
* Modified by Derek Molloy for the example on www.derekmolloy.ie
* that maps GPIO pins for the example
* Modified again by Charles Kerr for his project
*/

/dts-v1/;
/plugin/;

/{
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "DIYBLIGHTS";
version = "00A0";
exclusive-use = "P8.12,P8.46"
fragment@0 {
target = <&am33xx_pinmux>;
__overlay__ {
pinctrl_test: DM_GPIO_Test_Pins {
pinctrl-single,pins = <
0x003 0x06  /* P8_12 GPIO:44 $PINS:12 MODE 6 -pru0 
R30_14 */
0x0A4 0x05  /* P8_46 GPIO:71 $PINS:41 MODE 5 - pru1 
R30_1 */
>;
};
};
};

fragment@1 {
target = <&ocp>;
__overlay__ {
test_helper: helper {
compatible = "bone-pinmux-helper";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_test>;
status = "okay";
};
};
};
};


Any help is appreciated!

Charles

-- 
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/7b2d66bb-72d6-44c5-9a26-21865c0493ce%40googlegroups.com.

[beagleboard] Re: Syntax for dts file error. Trying to make an overlay for connecting to PRU R30 register

[kerrbillpay]

Ok, so I got it working, so will post in case others face the same issue.  
First, the syntax issue was a missing ";" after the exclusive use tag.  
Also, I had some references using the wrong labels.  What wold be great if 
a write up on the current use and sections of the device tree for the 
beaglebone black.  Right now one must be knowledgeable in all things (PRU 
assembly, mapping memory to a arm program to read/write, tools to build the 
PRU, how to activate it, and finally device tree).  Although I know the 
basic concept of the device tree, known what to put for the sections 
(PRUSS, am355x, etc) and the keywords are still very much a mystery.  Hard 
to be knowledgable in all things and keep it a hobby).  Luckily I didn't 
have to disable items (although the next project I will).  Anyway, this 
file appears to have worked:









   /dts-v1/;

/plugin/;



/{

compatible = "ti,beaglebone", "ti,beaglebone-black";

part-number = "DIYBLIGHTS";

version = "00A0";

exclusive-use = "P8.12,P8.46";

fragment@0 {

target = <&am33xx_pinmux>;

__overlay__ {

diyblights: pinmux_pru_pru_pins {

pinctrl-single,pins = <

0x30 0x06  /* P8_12 GPIO:44 $PINS:12 MODE 6 -pru0 
R30_14 */

0xA4 0x05  /* P8_46 GPIO:71 $PINS:41 MODE 5 - pru1 
R30_1 */

>;

};

};

};



fragment@1 {

target = <&ocp>;

__overlay__ {

test_helper: helper {

compatible = "bone-pinmux-helper";

pinctrl-names = "default";

pinctrl-0 = <&diyblights>;

status = "okay";

};

};

};

};








On Saturday, September 14, 2019 at 3:28:05 PM UTC-4, Charles Kerr wrote:
>
> I can't find my old post, so I apologize for any repeat post.
>
> I am trying to allocate two pins (P8_12,P8_46) to PRU0 and PRU1.   So 
> effectively mode 6 and mode 5.  I want to exclusively use these by the 
> pru(s).  Still trying to understand this device tree overlay, but I found 
> an example one and modified it. It gives a syntax error when ti toy to 
> compile it (dtc).  After beating my head against the wall, I am hoping a 
> second set of eyes will be helpful.  Any help one can give on the syntax 
> error (and if the dts file won't accomplish what the desire for these pins).
>
> /*
> * Copyright (C) 2012 Texas Instruments Incorporated - 
> http://www.ti.com/
> *
> * This program is free software; you can redistribute it and/or modify
> * it under the terms of the GNU General Purpose License Version 2 as
> * published by the Free Software Foundation
> *
> * Original from: 
> github.com/jadonk/validation-scripts/blob/master/test-capemgr/
> *
> * Modified by Derek Molloy for the example on www.derekmolloy.ie
> * that maps GPIO pins for the example
> */
>
> /dts-v1/;
> /plugin/;
>
> /{
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part-number = "DIYBLIGHTS";
> version = "00A0";
> exclusive-use = "P8.12,P8.46"
> fragment@0 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> pinctrl_test: DM_GPIO_Test_Pins {
> pinctrl-single,pins = <
> 0x003 0x06  /* P8_12 GPIO:44 $PINS:12 MODE 6 -pru0 
> R30_14 */
> 0x0A4 0x05  /* P8_46 GPIO:71 $PINS:41 MODE 5 - 
> pru1 R30_1 */
> >;
> };
> };
> };
>
> fragment@1 {
> target = <&ocp>;
> __overlay__ {
> test_helper: helper {
> compatible = "bone-pinmux-helper";
> pinctrl-names = "default";
> pinctrl-0 = <&pinctrl_test>;
> status = "okay";
> };
> };
> };
> };
>
>
> Again, thanks ahead for any hep one can offer!
>
> Charles
>

-- 
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/653915c2-666f-40b0-bb21-7d1da706e2b9%40googlegroups.com.

[beagleboard] Programming a C / C++ code to Control LEDS existing on BeagleBoneBlack using BUTTON integrated on the Board

[ghassenjmii]

Hello BBB users. Is there anyone here who developped a C or C++ code which 
make it possible to Control LED using Button integrated both in the board 
through GPIO ? Please help me.

-- 
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/472fe1de-298b-4b7e-b149-4d869a8a50e2%40googlegroups.com.

[beagleboard] BeagleWire compatible???

[wright4j]

Will the BeagleWire be plug and play compatible???

-- 
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/45c4e9a3-3b61-4298-8ea2-07f0c7750b79%40googlegroups.com.

[beagleboard] Re: Windows 10 Bone_D64.exe Failing

[flavioalexandre020]

Tks! Worked for me!!  God Bless you!

Em quinta-feira, 13 de agosto de 2015 00:13:13 UTC-3, mscleavite escreveu:
>
> I have just upgraded to Windows 10 on a machine that I have not previously 
> connected my BBB to.  I had success on other windows 8 machines as well as 
> SSHing using Putty.  I have spent SOME time searching forums and not 
> finding much at all on Windows 10.  During the install of the Bone_D64.exe, 
> the driver the status returned on all the drivers is "Install Failed".  Let 
> the flaming begin.  Or hopefully there is someone out there that has 
> encountered and concurred 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/1bfe291e-8ff0-4f6d-9884-0befb4e4249d%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

['Andy Barbour' via BeagleBoard]

Looking forward to this class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/9b482636-ca6e-404e-bdee-8910aef27abc%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

['Andy Barbour' via BeagleBoard]

Looking forward to the class! Wonder why my last post didn't go through . . 
.

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/45c733af-c456-4afa-aaa1-8448c880e76b%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Wildape]

Looking forward to this class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/bc3a8972-84c5-40ef-a785-179cd8cbcc11%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[cmattox12 . 2]

Looking forward to this class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/686ab990-9abd-4e92-b9a5-04986385fc5b%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Wildape]

Looking forward to this class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/d79742f5-9c4d-4060-9840-11637e2b4555%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Rahul Das]

Looking forward to learning more!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/f46c9ee9-d874-4e18-afc6-e1f752ca35ed%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Rahul Das]

Very excited for this class

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/47c2216f-ab51-4a87-8bce-3984a118dbc2%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Rahul Das]

Very excited for this class

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/17851b76-8849-4145-8b03-f90f97f5dba2%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Dalton Stichtenoth]

Looking Forward to the Class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/4c031b6d-c249-4ccd-8def-d42db94f8a09%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[cmattox12 . 2]

Looking forward to the class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/64da1dc9-c8d3-4d90-80b4-76151c9319e8%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Hannah Woody]

Didn't work the first time, but still looking forward to this class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/c3d1fd98-cd01-46e9-8e66-fd079452f719%40googlegroups.com.

[beagleboard] EMMC to SD backup not workinig

[arunmag]

HI people, 

I have a BBB rev C for my playing around and i forgot the password. I tried 
to use the https://elinux.org/BeagleBone_Black_Extracting_eMMC_contents to 
extract the emmc to sd card and see if i can change the shadow file and 
gain access to my BBB again.  - I just inserted the sd card and it booted 
to it no S2 button press

When i tried to put the SD card. the dd command gave me like 20 byte empty 
gz file. 
I tried to modify the autorun script to print the /dev  to a file and found 
there is no mmcblk1 - Which means emmc is not even detected. 

how i make sure the emmc is detected from the sd card boot and extract the 
emmc content???

Is it something to do with new revision??


help please.. all my work is inside :(((



-- 
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/debd450b-a0f9-4fb9-a865-1feaaaefb4b4%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Hannah Woody]

Looking forward to this class!

On Thursday, September 5, 2019 at 3:16:50 PM UTC-4, Mark A. Yoder wrote:
>
> The purpose of this posting is to announce that I'm once again teaching 
> an Embedded Linux class based on the BeagleBone[1]. This time I'm using
> the  *BeagleBone Black.* 
> I'm teaching as open-source as I can and have have posted many of course 
> materials on eLinux.org [2] and github[3].
>
> I'm always open to ideas on what topics to include in the class and 
> suggestions for interesting course projects.  For example we are starting
> Python this week and hope to be writing simple kernel module 5 weeks from 
> now.  That will be followed by a week of PRU programming.
>
> Class, please respond to this posting.  Others, please welcome my class.
>
> --Mark 
>
> --Prof. Mark A. Yoder 
>   Rose-Hulman Institute of Technology [4] 
>
> [1] http://elinux.org/Embedded_Linux,_Rose-Hulman 
> [2] http://elinux.org/index.php?title=Category:ECE497 
> [3] https://github.com/MarkAYoder/BeagleBoard-exercises 
> [4] http://www.rose-hulman.edu 
>

-- 
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/2debe6fb-7e3d-4192-9099-ac5277e8393e%40googlegroups.com.

[beagleboard] Re: Welcome the Fall 2019 Embedded Linux Class

[Rahul Das]

Looking forward to learning more!
(My earlier response did not show up for some reason so apologies if it 
somehow randomly shows up twice now)

-- 
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/26699441-6df2-4be3-b91f-292af7b35816%40googlegroups.com.

Re: [beagleboard] Re: Can this beaglebone AI run raspbian OS?

[Jason Kridner]

On Tuesday, September 10, 2019 at 1:29:31 PM UTC-4, Josiah Akinloye wrote:
>
> Ok
> So what is the cost of the board
>

FAQ mentions that the price is around US$100.
 

> And can you manufacture based on my requirements??
>

See https://beagleboard.org/support and https://beagleboard.org/resources. 
BeagleBoard.org Foundation does not do customizations, but the open 
hardware design is at https://github.com/beagleboard/beaglebone-ai already 
(and OSHWA certified) and can be customized by developers familiar with the 
AM5729 SoC, such as those listed on the resources page.
 

>
> On Tue, Sep 10, 2019 at 5:27 PM Jason Kridner  wrote:
>
>> On Tuesday, September 10, 2019 at 12:19:35 PM UTC-4, Josiah Akinloye 
>> wrote:
>>>
>>> can the beaglebone AI run raspbian operating system?
>>>
>>
>> What features are you looking for by running Raspbian?
>>
>> You can run Debian.
>>  
>> It is possible to patch a Raspbian image to boot, but many of the custom 
>> aspects of Raspian won't work or won't do anything useful. If there is a 
>> software feature you are looking for that you use in Raspbian today, best 
>> to request that in the Debian images we assemble as a suitable starting 
>> point.
>>
>> -- 
>> 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/0a030485-f048-4745-888c-67aaaec79f3d%40googlegroups.com
>>  
>> 
>> .
>>
> -- 
>
>
>
>
> *Josiah Akinloye+2348135010778ceo at Hubtecs Technological 
> InstituteRobotic and AutomationEgalitarian TranshumanistFuturist"Mindset 
> powered by hard work equals unbeatable Achievement"--OLUWEST*
>

-- 
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/c9b83700-ed45-4ee0-bcd4-0f3d5e69a6d0%40googlegroups.com.

Re: [beagleboard] Re: Can this beaglebone AI run raspbian OS?

[Jason Kridner]

Reading this back encouraged a couple of clarifications

On Tue, Sep 17, 2019 at 8:59 AM Jason Kridner  wrote:

>
>
> On Tuesday, September 10, 2019 at 1:29:31 PM UTC-4, Josiah Akinloye wrote:
>>
>> Ok
>> So what is the cost of the board
>>
>
> FAQ mentions that the price is around US$100.
>

Excluding any applicable tariffs.


>
>
>> And can you manufacture based on my requirements??
>>
>
> See https://beagleboard.org/support and https://beagleboard.org/resources.
> BeagleBoard.org Foundation does not do customizations, but the open
> hardware design is at https://github.com/beagleboard/beaglebone-ai
> already (and OSHWA certified) and can be customized by developers familiar
> with the AM5729 SoC, such as those listed on the resources page.
>


We are open hardware and will make changes to the design that benefit the
developer community. These would strictly be open source updates and with
sufficient demand to justify the board spins/testing.



>
>
>>
>> On Tue, Sep 10, 2019 at 5:27 PM Jason Kridner  wrote:
>>
>>> On Tuesday, September 10, 2019 at 12:19:35 PM UTC-4, Josiah Akinloye
>>> wrote:

 can the beaglebone AI run raspbian operating system?

>>>
>>> What features are you looking for by running Raspbian?
>>>
>>> You can run Debian.
>>>
>>> It is possible to patch a Raspbian image to boot, but many of the custom
>>> aspects of Raspian won't work or won't do anything useful. If there is a
>>> software feature you are looking for that you use in Raspbian today, best
>>> to request that in the Debian images we assemble as a suitable starting
>>> point.
>>>
>>> --
>>> 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/0a030485-f048-4745-888c-67aaaec79f3d%40googlegroups.com
>>> 
>>> .
>>>
>> --
>>
>>
>>
>>
>> *Josiah Akinloye+2348135010778ceo at Hubtecs Technological
>> InstituteRobotic and AutomationEgalitarian TranshumanistFuturist"Mindset
>> powered by hard work equals unbeatable Achievement"--OLUWEST*
>>
> --
> 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/c9b83700-ed45-4ee0-bcd4-0f3d5e69a6d0%40googlegroups.com
> 
> .
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAK8RMs2JEqKGb7beh%3Dn7pY46jkDFvWCTGnwnrS3Pn7J_J1JKmQ%40mail.gmail.com.

[beagleboard] EMMC to SD backup not workinig

[Kim Harry]

Hi
I have done similar on other board. Following steps may helpful
1. Boot from sdcard
2. In shell(uart or ssh terminal) execute lsblk
It will show mmcblk0(maybe flash), mmcblk1(sdcard?)
3. Plug usb thumb-drive and mount it
4. sudo dd if=/dev/{eMMC flash block.  Maybe mmcblk0} xx
Use dd command to extract flash disk to img file.
5. Access img file in other linux pc.
You can use loop0 or img mount in host and can see inside.

Regards

-- 
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/961c2239-1766-42b1-b906-d5b0fc6c5a29%40googlegroups.com.

[beagleboard] Re: Programming a C / C++ code to Control LEDS existing on BeagleBoneBlack using BUTTON integrated on the Board

[TJF]

This example shows how to control a user LED (LED3):

http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/sos_8c_source.html

This example shows how to read the state of a button:

http://users.freebasic-portal.de/tjf/Projekte/libpruio/doc/html/button2_8c_source.html

The only onboard button connected to a GPIO is the boot button, wired to 
P8_43. So you have to adapt #define PIN P8_43. And since the button 
switches GND, you should use a pull-up resistor: if (pruio_gpio_config 
(io,
 
PIN 
,
 
PRUIO_GPIO_IN_1 
))
 
{...

Merge both examples together and off you go.

-- 
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/1c9f62f4-28a6-4987-886a-7a12c6eb86b9%40googlegroups.com.

[beagleboard] Initializing both CS on SPI1 causes data corruption

[bRitch022]

Using two MCP23S17 I/O expanders via SPI1 with CS0 P9.28 and CS1 P9.42. 
I am initializing each chip separately and doing a read immediately after, 
which produces the expected data. However, if I go back to read the first 
chip after initializing the second chip, the data is skewed and doesn't 
read the first chip correctly. This happens even if I swap the order that 
the chips are initialized -- whichever one was initialized first ends up 
with skewed data.

Software or kernel issue?

Here is my code and the output:
https://pastebin.com/L6qJGwPZ


debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
> [sudo] password for debian:
> git:/opt/scripts/:[1aa73453b2c980b75e31e83dab7dd8b6696f10c7]
> eeprom:[A335BNLTEIA04218BBBK0D06]
> model:[TI_AM335x_BeagleBone_Black]
> dogtag:[BeagleBoard.org Debian Image 2018-10-07]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2018.09-2-g0b54a51eee]:[l
> ocation: dd MBR]
> kernel:[4.19.59-ti-rt-r25]
> nodejs:[v6.14.4]
> uboot_overlay_options:[enable_uboot_overlays=1]
>
> uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-SPIDEV1-00A0.dtbo]
> uboot_overlay_options:[disable_uboot_overlay_video=1]
> uboot_overlay_options:[disable_uboot_overlay_audio=1]
> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-19-TI-
>   
>   00A0.dtbo]
> uboot_overlay_options:[enable_uboot_cape_universal=1]
> pkg check: to individually upgrade run: [sudo apt install --only-upgrade 
> ]
> pkg:[bb-cape-overlays]:[4.4.20190812.0-0rcnee0~stretch+20190812]
> pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]
> pkg:[kmod]:[23-2rcnee1~stretch+20171005]
> pkg:[librobotcontrol]:[1.0.3-git20181005.0-0rcnee0~stretch+20181005]
> pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]
> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
> plugdev users systemd-journal i2c 
> bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk
>  weston-launch xenomai]
> cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 
> root=/dev/mmcblk1p1 ro 
> rootfstype=ext4 rootwait coherent_pool=1M net.ifnames=0 quiet]
> dmesg | grep pinctrl-single
> [1.404225] pinctrl-single 44e10800.pinmux: 142 pins, size 568
> dmesg | grep gpio-of-helper
> [1.428047] gpio-of-helper ocp:cape-universal: ready
> END



debian@beaglebone:~/bb.org-overlays/src/arm$ cat BB-SPIDEV1-00A0.dts
/*
 * Copyright (C) 2013 CircuitCo
 *
 * Virtual cape for SPI1 on connector pins P9.29 P9.31 P9.30 P9.28
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License version 2 as
 * published by the Free Software Foundation.
 */
/dts-v1/;
/plugin/;
#include 
#include 
/ {
compatible = "ti,beaglebone", "ti,beaglebone-black", 
"ti,beaglebone-green";
/* identification */
part-number = "BB-SPIDEV1";
version = "00A0";
/* state the resources this cape uses */
exclusive-use =
/* the pin header uses */
"P9.31",/* spi1_sclk */
"P9.29",/* spi1_d0 */
"P9.30",/* spi1_d1 */
"P9.28",/* spi1_cs0 */
"P9.42",/* spi1_cs1 */
/* the hardware ip uses */
"spi1";
/*
 * Helper to show loaded overlays under: 
/proc/device-tree/chosen/overlays/
 */
fragment@0 {
target-path="/";
__overlay__ {
chosen {
overlays {
BB-SPIDEV1-00A0 = __TIMESTAMP__;
};
};
};
};
/*
 * Free up the pins used by the cape from the pinmux helpers.
 */
fragment@1 {
target = <&ocp>;
__overlay__ {
P9_28_pinmux { status = "disabled"; };  /* spi1_cs0 
*/
P9_30_pinmux { status = "disabled"; };  /* spi1_d0 
*/
P9_29_pinmux { status = "disabled"; };  /* spi1_d1 
*/
P9_31_pinmux { status = "disabled"; };  /* 
spi1_sclk */
P9_42_pinmux { status = "disabled"; };  /* spi1_cs1 
*/
};
};
fragment@2 {
target = <&am33xx_pinmux>;
__overlay__ {
/* default state has all gpios released and mode 
set to uart1 */
bb_spi1_pins: pinmux_bb_spi1_pins {
pinctrl-single,pins = <
0x190 0x33  /* 
mcasp0_aclkx.spi1_sclk, INPUT_PULLUP | MODE3 */
  

Re: [beagleboard] Initializing both CS on SPI1 causes data corruption

[Robert Nelson]

On Tue, Sep 17, 2019 at 10:49 AM bRitch022  wrote:
>
> Using two MCP23S17 I/O expanders via SPI1 with CS0 P9.28 and CS1 P9.42.
> I am initializing each chip separately and doing a read immediately after, 
> which produces the expected data. However, if I go back to read the first 
> chip after initializing the second chip, the data is skewed and doesn't read 
> the first chip correctly. This happens even if I swap the order that the 
> chips are initialized -- whichever one was initialized first ends up with 
> skewed data.
>
> Software or kernel issue?

Try again using the MCP23S17 bindings and the pinctrl-mcp23s08 driver:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/pinctrl/pinctrl-mcp23s08.txt

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/CAOCHtYjT-r84ZauHaW9_vx8jjxA_Cp7s77RtAG1nmnRhjBzCLg%40mail.gmail.com.

Re: [beagleboard] Initializing both CS on SPI1 causes data corruption

[Robert Nelson]

On Tue, Sep 17, 2019 at 11:20 AM Bryan Ritchie  wrote:
>
> Robert,
>
> Am I placing a paragraph like this in the SPIDEV1 dts (dtbo) file? Or am I 
> creating a new BB-SPI1-MCP23S17-00A0.dts file?

Sure, that name would be fine, but I would first start with this example:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-SPI0-MCP23S08-00A0.dts

Then change it to SPI1 and tweak the node to match the mcp23s17..

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/CAOCHtYg3VO208OjJ2z4TcUsZ_SbFXK-im4fiM1ZDv5_knZxr4A%40mail.gmail.com.

[beagleboard] Re: Where to order the BeagleBone AI?

[Jason Kridner]

No pre-orders. Orders available soon.

On Tuesday, September 10, 2019 at 12:22:26 PM UTC-4, dee...@gmail.com wrote:
>
> can we preorder?
>
> On Thursday, September 5, 2019 at 1:09:06 AM UTC+2, Jason Kridner wrote:
>>
>> Stay tuned. Did you sign up for the e-mail notification via 
>> https://beagleboard.org/ai ?
>>
>> On Wednesday, September 4, 2019 at 7:02:50 PM UTC-4, someone wrote:
>>>
>>> As Title
>>
>>

-- 
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/f23bd16b-c93c-410f-bea7-e205470f463c%40googlegroups.com.

[beagleboard] Re: Gateway problem

[amf]

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

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

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

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

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

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

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/47d8bf20-9c33-4085-aab8-5a415ddbef32%40googlegroups.com.

Re: [beagleboard] Initializing both CS on SPI1 causes data corruption

[Robert Nelson]

On Tue, Sep 17, 2019 at 12:55 PM Bryan Ritchie  wrote:
>
> Robert,
>
> This caused my spidev1.0 and spidev1.1 to disappear.

Yes, that's good.. you can use the gpiolib/etc instead of hacking thru spidev..

>
> Here's what I compiled:
> /*
>  * Copyright (C) 2015 Robert Nelson 
>  *
>  * This program is free software; you can redistribute it and/or modify
>  * it under the terms of the GNU General Public License version 2 as
>  * published by the Free Software Foundation.
>  */
>
> /dts-v1/;
> /plugin/;
>
> #include 
> #include 
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black", 
> "ti,beaglebone-green";
>
> /* identification */
> part-number = "BB-SPI1-MCP23S17";
> version = "00A0";
>
> /* state the resources this cape uses */
> exclusive-use =
> /* the pin header uses */
> "P9.31",/* spi1_sclk, SPI1_SCLK */
> "P9.29",/* spi1_d0, SPI1_MISO */
> "P9.30",/* spi1_d1, SPI1_MOSI */
> "P9.28",/* spi1_cs0, CS0 */
> "P9.42",/* spi1_cs1, CS1 */
> /* the hardware ip uses */
> "spi1";
>
> /*
>  * Helper to show loaded overlays under: 
> /proc/device-tree/chosen/overlays/
>  */
> fragment@0 {
> target-path="/";
> __overlay__ {
>
> chosen {
> overlays {
> BB-SPI1-MCP23S17-00A0 = __TIMESTAMP__;
> };
> };
> };
> };
>
> /*
>  * Free up the pins used by the cape from the pinmux helpers.
>  */
> fragment@1 {
> target = <&ocp>;
> __overlay__ {
> P9_28_pinmux { status = "disabled"; };  /* spi1_cs0 */
> P9_30_pinmux { status = "disabled"; };  /* spi1_d1 */
> P9_29_pinmux { status = "disabled"; };  /* spi1_d0 */
> P9_31_pinmux { status = "disabled"; };  /* spi1_sclk 
> */
> P9_42_pinmux { status = "disabled"; };  /* spi1_cs1 */
> };
> };
>
> fragment@2 {
> target = <&am33xx_pinmux>;
> __overlay__ {
> bb_spi0_pins: pinmux_bb_spi0_pins {

This label name doesn't match below... (aka: bb_spi1) replace ^ spi0
with spi1...

> pinctrl-single,pins = <
> BONE_P9_31 (PIN_INPUT_PULLUP | 
> MUX_MODE3) /* spi1_sclk.spi1_sclk */
> BONE_P9_29 (PIN_INPUT_PULLUP | 
> MUX_MODE3) /* spi1_d0.spi1_d0 */
> BONE_P9_30 (PIN_OUTPUT_PULLUP | 
> MUX_MODE3) /* spi1_d1.spi1_d1 */
> BONE_P9_28 (PIN_OUTPUT_PULLUP | 
> MUX_MODE3)  /* spi1_cs0.spi1_cs0 */
> BONE_P9_42 (PIN_OUTPUT_PULLUP | 
> MUX_MODE2)  /* spi1_cs1.spi1_cs1 */
> >;
> };
> };
> };
>
> fragment@3 {
> target = <&spi1>;
> __overlay__ {
> #address-cells = <1>;
> #size-cells = <0>;
>
> status = "okay";
> pinctrl-names = "default";
> pinctrl-0 = <&bb_spi1_pins>;
>
> gpiom1: gpio@0 {
> compatible = "microchip,mcp23s17";
> gpio-controller;
> #gpio-cells = <2>;
> microchip,spi-present-mask = <0x01>;
> mcp,spi-present-mask = <0x01>;
> spi-present-mask = <0x01>;
> reg = <0>;
> spi-max-frequency = <100>;
> };
>
> gpiom2: gpio@1 {
> compatible = "microchip,mcp23s17";
> gpio-conroller;

spelling: gpio-controller

> #gpio-cells = <2>;
> microchip,spi-present-mask = <0x01>;
> mcp,spi-present-mask = <0x01>;
> spi-present-mask = <0x01>;
> reg = <1>;
> spi-max-frequency = <100>;
> };
> };
> };
> };


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

Re: [beagleboard] Re: Where to order the BeagleBone AI?

[William Hermans]

price ?


On Tue, Sep 17, 2019 at 8:24 AM Jason Kridner  wrote:

> No pre-orders. Orders available soon.
>
> On Tuesday, September 10, 2019 at 12:22:26 PM UTC-4, dee...@gmail.com
> wrote:
>>
>> can we preorder?
>>
>> On Thursday, September 5, 2019 at 1:09:06 AM UTC+2, Jason Kridner wrote:
>>>
>>> Stay tuned. Did you sign up for the e-mail notification via
>>> https://beagleboard.org/ai ?
>>>
>>> On Wednesday, September 4, 2019 at 7:02:50 PM UTC-4, someone wrote:

 As Title
>>>
>>> --
> 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/f23bd16b-c93c-410f-bea7-e205470f463c%40googlegroups.com
> 
> .
>

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORqrj5-F4Kv8f9nNLDTvXK%3DiM6dCboFFoO%3D%2BHQo3hek6Pg%40mail.gmail.com.

[beagleboard] Indiegogo launched using BeagleBone AI for private, trusted NAS

[Jason Kridner]

This looks interesting to me as it provides a trusted, open-source
software/hardware solution for network-accessible storage:

https://privacysafe.ai/
https://www.indiegogo.com/projects/privacysafe-privacy-by-design/x/7085817#/


-- 
https://beagleboard.org/about

-- 
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/CA%2BT6QPmeZAspxg7i4V1u8a3BgTnjgWFhsauBfyFoB4t6LspK4Q%40mail.gmail.com.

Re: [beagleboard] Re: Where to order the BeagleBone AI?

[Jason Kridner]

Thought I already replied to this, but I don't see it

Price will be around US$100, not including any related tariffs.

You know what, it was on a totally dumb thread name about Raspbian where 
the price question shouldn't have been asked.

On Tuesday, September 17, 2019 at 3:28:27 PM UTC-4, William Hermans wrote:
>
> price ?
>
>
> On Tue, Sep 17, 2019 at 8:24 AM Jason Kridner wrote:
>
>> No pre-orders. Orders available soon.
>>
>> On Tuesday, September 10, 2019 at 12:22:26 PM UTC-4, deeler 
>>  wrote:
>>>
>>> can we preorder?
>>>
>>> On Thursday, September 5, 2019 at 1:09:06 AM UTC+2, Jason Kridner wrote:

 Stay tuned. Did you sign up for the e-mail notification via 
 https://beagleboard.org/ai ?

 On Wednesday, September 4, 2019 at 7:02:50 PM UTC-4, someone wrote:
>
> As Title


>>

-- 
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/0cf281b7-7c3d-4ca6-8f2d-5f330d94d179%40googlegroups.com.