date:20180218

Re: [beagleboard] baseboard folder disappears in bone_capemgr after kernel upgrade to latest 4.4 kernel

2018-02-18 Thread 'Luther Goh Lu Feng' via BeagleBoard

 When available, the contents of 
`/sys/devices/platform/bone_capemgr/baseboard/serial-number` and 
`/sys/bus/i2c/devices/0-0050/eeprom` differ. Are they expected to be the same 
or are they 2 different type of serial numbers altogether? And are both unique? 
Thanks!

--Luther
On Friday, February 16, 2018, 2:15:30 AM GMT+8, Robert Nelson 
 wrote:  
 
 On Wed, Feb 14, 2018 at 11:35 PM, Luther Goh Lu Feng  wrote:
> I would also like to know when the U-boot overlays changed from being
> inactive to being active. Is it specifically during the reboot into the new
> kernel?

well between r93 -> r146..

https://github.com/RobertCNelson/ti-linux-kernel-dev/commits/ti-linux-4.4.y

r93: Mar 16, 2017
r146: Feb 2, 2018

So i'd say mid summer of 2017..

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/rtB2f4Aqd-Q/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/CAOCHtYhao3AtHyx7O6%2B7evZ8LvU4OAwB1veCEi2v3qkDGgyiSw%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/370050950.1108776.1519009270202%40mail.yahoo.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: bbgw wlan0 users

2018-02-18 Thread migue . fonseca

This actually solved my problem, now it is working just perfect!!. Please 
see this post: 

So on the BeagleBone Family, we use an eeprom id to detect what board you 
have.  In your case, the board eeprom got mis-written too.

Which is easy to fix, near the 5Volt header there are 4 copper holes (TP2 
-> TP5) that's for a LiPo battery, next to that is IC4, followed by TP1.

TP1: is write protect pin for the i2c eeprom.  To allow us to write a 
correct ID, we need to GND that pin (TP1)

On the P9 header:

http://beagleboard.org/static/images/cape-headers.png

Pin's 1 & 2 are GND, connect either P9.1/P9.2 to TP1 with a short piece of 
wire.  Then you can exicute


*sudo dd 
if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom*

El domingo, 18 de febrero de 2018, 13:36:50 (UTC-6), sbsa...@gmail.com 
escribió:
>
> Did anyone get this going?  Honestly, I have spent a few hours and the 
> image for the BBBW bone-debian-9.3-lxqt-armhf-2018-01-28-4gb.img also gives 
> the same error:
>
> Method "SetProperty" with signature "sv" on interface 
> "net.connman.Technology" doesn't exist
>
> With the word wireless in it, I feel it would be easier to get it going? :(
>
> On Monday, May 29, 2017 at 12:24:26 PM UTC-4, RobertCNelson wrote:
>>
>>
>>
>> On Mon, May 29, 2017 at 12:02 AM, Migue Fonseca  
>> wrote:
>>
>>> Hey my friend, thanks for your quick reply. I retested everything with 
>>> the new image, same result:
>>> [image: Imágenes integradas 1]
>>>
>>> Could this be a driver issue? Let me know what you think.
>>>
>>
>> Please run version.sh:
>>
>> debian@test-bbbw-11:/opt/scripts/tools$ sudo ./version.sh
>> git:/opt/scripts/:[0e222d4aeb4f1c06dcdd025e0b1e1835404e1551]
>> eeprom:[A335BNLTBWA0*]
>> dogtag:[BeagleBoard.org Debian Image 2016-10-23]
>> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
>> 2017.05-2-g962663a0e0]
>> kernel:[4.4.62-ti-rt-r105]
>> nodejs:[v0.12.18]
>>
>> 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/504fb711-070a-4e38-824c-c2c467f49a95%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBW WiFi does not work after eprom flash

2018-02-18 Thread sbsaylors

So from a fresh BBBW image, you just type:
dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom?

Did you also have to do the GND TP1?  (<- I have no idea what this is or 
how to do it?) :)

On Sunday, February 18, 2018 at 3:37:56 PM UTC-5, Stephen Mansfield wrote:
>
> Ok, the error was that it was one line as RobertNielson pointed out.
>
> dd 
> if=/opt/scripts/device/bone/bbbw-eeprom.dumpof=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom
>
> After I did this, connmanctl worked fine and the wifi works fine.
>
> Thanks a bunch
>
>
> On Sunday, February 18, 2018 at 1:29:47 PM UTC-5, Stephen Mansfield wrote:
>>
>> Hello,
>>
>> I received my BBBW the other day.  Everything worked fine including the 
>> wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3 
>> 2018-01-28 SD LXQT and the wireless no longer works.  When I type 
>> root@beaglebone:/# connmanctl and then type > scan wifi it get the 
>> following error, "Error /net/connman/technology/wifi: Method "Scan" with 
>> signature "" on interface "net.connman.Technology" doesn't exist".  When I 
>> type ifconfig I get, 
>>
>> root@beaglebone:/# ifconfig
>> eth0: flags=-28669  mtu 1500
>> ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet)
>> RX packets 0  bytes 0 (0.0 B)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 0  bytes 0 (0.0 B)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> device interrupt 181
>>
>> lo: flags=73  mtu 65536
>> inet 127.0.0.1  netmask 255.0.0.0
>> inet6 ::1  prefixlen 128  scopeid 0x10
>> loop  txqueuelen 1  (Local Loopback)
>> RX packets 2720  bytes 184480 (180.1 KiB)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 2720  bytes 184480 (180.1 KiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> usb0: flags=4163  mtu 1500
>> inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
>> inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 0x20
>> ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet)
>> RX packets 807  bytes 126314 (123.3 KiB)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 190  bytes 36851 (35.9 KiB)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> usb1: flags=4099  mtu 1500
>> inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
>> ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet)
>> RX packets 0  bytes 0 (0.0 B)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 0  bytes 0 (0.0 B)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>>
>> root@beaglebone:/#
>>
>> I see no wlan.  There is a previous post that descripibes grounding TP1.  
>> I did the following
>>
>> GND TP1 then run as root: 
>>
>> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
>> of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 
>>
>> I rebooted but still no wifi.  Just to be sure, I am using a Beaglebone 
>> Black Wireless.  Any thoughts?
>>
>

-- 
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/40979a15-3a6e-4387-a894-f84febf22365%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBW WiFi does not work after eprom flash

2018-02-18 Thread sbsaylors



On Sunday, February 18, 2018 at 1:29:47 PM UTC-5, Stephen Mansfield wrote:
>
> Hello,
>
> I received my BBBW the other day.  Everything worked fine including the 
> wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3 
> 2018-01-28 SD LXQT and the wireless no longer works.  When I type 
> root@beaglebone:/# connmanctl and then type > scan wifi it get the 
> following error, "Error /net/connman/technology/wifi: Method "Scan" with 
> signature "" on interface "net.connman.Technology" doesn't exist".  When I 
> type ifconfig I get, 
>
> root@beaglebone:/# ifconfig
> eth0: flags=-28669  mtu 1500
> ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 181
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 2720  bytes 184480 (180.1 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 2720  bytes 184480 (180.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb0: flags=4163  mtu 1500
> inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
> inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 0x20
> ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet)
> RX packets 807  bytes 126314 (123.3 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 190  bytes 36851 (35.9 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb1: flags=4099  mtu 1500
> inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
> ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> root@beaglebone:/#
>
> I see no wlan.  There is a previous post that descripibes grounding TP1.  
> I did the following
>
> GND TP1 then run as root: 
>
> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
> of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 
>
> I rebooted but still no wifi.  Just to be sure, I am using a Beaglebone 
> Black Wireless.  Any thoughts?
>

-- 
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/390d4037-476a-449b-802b-ef783b03cbf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBBW WiFi does not work after eprom flash

2018-02-18 Thread sbsaylors

Hello Robert, I know you have a wealth of knowledge on this. I know you 
have give each piece of that to different folks. I have spent at least 5 
hours today and many others over the last week since buying the BBBW to get 
wifi going. Mind you, I truly am not a complete noobie here. But it would 
be amazing if someone. Anyone could put a simple 1 page with screenshots of 
how to get the BBBW with the current image to work? 

On Sunday, February 18, 2018 at 2:02:52 PM UTC-5, RobertCNelson wrote:
>
> On Sun, Feb 18, 2018 at 12:00 PM, Stephen Mansfield 
>  wrote: 
> > Hello, 
> > 
> > I received my BBBW the other day.  Everything worked fine including the 
> > wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3 
> > 2018-01-28 SD LXQT and the wireless no longer works.  When I type 
> > root@beaglebone:/# connmanctl and then type > scan wifi it get the 
> following 
> > error, "Error /net/connman/technology/wifi: Method "Scan" with signature 
> "" 
> > on interface "net.connman.Technology" doesn't exist".  When I type 
> ifconfig 
> > I get, 
> > 
> > root@beaglebone:/# ifconfig 
> > eth0: flags=-28669  mtu 1500 
> > ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet) 
> > RX packets 0  bytes 0 (0.0 B) 
> > RX errors 0  dropped 0  overruns 0  frame 0 
> > TX packets 0  bytes 0 (0.0 B) 
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
> > device interrupt 181 
> > 
> > lo: flags=73  mtu 65536 
> > inet 127.0.0.1  netmask 255.0.0.0 
> > inet6 ::1  prefixlen 128  scopeid 0x10 
> > loop  txqueuelen 1  (Local Loopback) 
> > RX packets 2720  bytes 184480 (180.1 KiB) 
> > RX errors 0  dropped 0  overruns 0  frame 0 
> > TX packets 2720  bytes 184480 (180.1 KiB) 
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
> > 
> > usb0: flags=4163  mtu 1500 
> > inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3 
> > inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 
> 0x20 
> > ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet) 
> > RX packets 807  bytes 126314 (123.3 KiB) 
> > RX errors 0  dropped 0  overruns 0  frame 0 
> > TX packets 190  bytes 36851 (35.9 KiB) 
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
> > 
> > usb1: flags=4099  mtu 1500 
> > inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3 
> > ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet) 
> > RX packets 0  bytes 0 (0.0 B) 
> > RX errors 0  dropped 0  overruns 0  frame 0 
> > TX packets 0  bytes 0 (0.0 B) 
> > TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0 
> > 
> > root@beaglebone:/# 
> > 
> > I see no wlan.  There is a previous post that descripibes grounding TP1. 
>  I 
> > did the following 
> > 
> > GND TP1 then run as root: 
> > 
> > dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
> > of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 
>
> This is "one" line.. ^ 
>
> You can also run: 
>
> sudo /opt/scripts/tools/version.sh | grep eeprom 
>
> to verify it programmed. 
>
> 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/fe5751be-6fea-4c21-9a8f-829df8a237f9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBW WiFi does not work after eprom flash

2018-02-18 Thread Stephen Mansfield

Ok, the error was that it was one line as RobertNielson pointed out.

dd 
if=/opt/scripts/device/bone/bbbw-eeprom.dumpof=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom

After I did this, connmanctl worked fine and the wifi works fine.

Thanks a bunch


On Sunday, February 18, 2018 at 1:29:47 PM UTC-5, Stephen Mansfield wrote:
>
> Hello,
>
> I received my BBBW the other day.  Everything worked fine including the 
> wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3 
> 2018-01-28 SD LXQT and the wireless no longer works.  When I type 
> root@beaglebone:/# connmanctl and then type > scan wifi it get the 
> following error, "Error /net/connman/technology/wifi: Method "Scan" with 
> signature "" on interface "net.connman.Technology" doesn't exist".  When I 
> type ifconfig I get, 
>
> root@beaglebone:/# ifconfig
> eth0: flags=-28669  mtu 1500
> ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 181
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 2720  bytes 184480 (180.1 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 2720  bytes 184480 (180.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb0: flags=4163  mtu 1500
> inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
> inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 0x20
> ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet)
> RX packets 807  bytes 126314 (123.3 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 190  bytes 36851 (35.9 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb1: flags=4099  mtu 1500
> inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
> ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> root@beaglebone:/#
>
> I see no wlan.  There is a previous post that descripibes grounding TP1.  
> I did the following
>
> GND TP1 then run as root: 
>
> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
> of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 
>
> I rebooted but still no wifi.  Just to be sure, I am using a Beaglebone 
> Black Wireless.  Any thoughts?
>

-- 
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/d0b0fa18-57aa-4bae-8d08-d6f0e7562121%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] AWS IOT C++

2018-02-18 Thread Hemant Kapoor

Thanks, 

Will have a look

-- 
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/e48a97e7-d404-4fca-b61e-c471cb9ff85c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] AWS IOT C++

2018-02-18 Thread Robert Nelson

On Sun, Feb 18, 2018 at 1:04 PM, Hemant Kapoor  wrote:
> Hello All,
>
> I have a c++ program running on beaglebone black which reads temperature
> from MCP9808 IC via i2c protocol.
>
> For this I have created a thing in AWS IOT and want to update it via MQTT...
> All this needs to be done in C++
>
> This is the plan and have no idea how to do this...
>
> Has any one done something similar to could guide me as how this could be
> acheived.

Have you tried googling: "python mqtt mcp9808"  look at the first hit..

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

Re: [beagleboard] Re: bbgw wlan0 users

2018-02-18 Thread sbsaylors

Did anyone get this going?  Honestly, I have spent a few hours and the 
image for the BBBW bone-debian-9.3-lxqt-armhf-2018-01-28-4gb.img also gives 
the same error:

Method "SetProperty" with signature "sv" on interface 
"net.connman.Technology" doesn't exist

With the word wireless in it, I feel it would be easier to get it going? :(

On Monday, May 29, 2017 at 12:24:26 PM UTC-4, RobertCNelson wrote:
>
>
>
> On Mon, May 29, 2017 at 12:02 AM, Migue Fonseca  > wrote:
>
>> Hey my friend, thanks for your quick reply. I retested everything with 
>> the new image, same result:
>> [image: Imágenes integradas 1]
>>
>> Could this be a driver issue? Let me know what you think.
>>
>
> Please run version.sh:
>
> debian@test-bbbw-11:/opt/scripts/tools$ sudo ./version.sh
> git:/opt/scripts/:[0e222d4aeb4f1c06dcdd025e0b1e1835404e1551]
> eeprom:[A335BNLTBWA0*]
> dogtag:[BeagleBoard.org Debian Image 2016-10-23]
> bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 
> 2017.05-2-g962663a0e0]
> kernel:[4.4.62-ti-rt-r105]
> nodejs:[v0.12.18]
>
> 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/fd13412b-8677-43c8-b50f-fb92d88e1264%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: getting started with beaglebone black

2018-02-18 Thread Hemant Kapoor

Hello Arun, 

Congratulations on buying your first BBB :)

I am also a beginner but will try to share my experience so far: 

1.Having worked mostly in c/c++ and assembly,is it a good idea to stick to 
the same languages or i am better off programming in a different language 
like python,Java etc?
HK: If planning to run debain OS and good knowledge in C,C++, I would 
suggest to stick with the same.
Coming from same bare metal background, It was important for me to have a 
paradigm shift to work on a fully matured embedded OS.  All you can do with 
bare metal can be done with OS but in a different way.
Having said that, I would suggest that a strong background with Linux 
fundamentals. 

2.How easy it it to intergrate the software to access the hardware,i mean 
are most of the drivers already written and are they easily avalable?I plan 
to intergrate an two slave MCUs via SPI,and some sensors via I2C bus.
HK: Once you have mastered Linux internals a quick google search will be 
help you a long way. 
I have recently written a hobby program to interact with a temprature 
sensor using I2C protocol, it is very basic but you can have a look to get 
an idea of programming involved.
https://github.com/hemantkapoor/temperatureSensor

3.Is it possible to use the PRUs of the Sitara controller as a parallel 
port for some high speed data transfer?like getting data from a fast ADC or 
writing to a DAC?
HK: Yes there is a way but I haven't explored it myself.

Also interface a 20x4 LCD display via the GPIO ports.
HK: With Linux chances are you already will have a driver for this and you 
can create custom Linux kernel to include the driver. And interfacing with 
LCD will be a simple matter of opening a file and writing to it...

Remember with Linux everything thins is a file...

This is just a beginner sharing his expirience, I am sure there are experts 
in this forum who are very helpful and could guide you for specific issues.

On Friday, 9 February 2018 08:53:43 UTC, Arun Kumar wrote:
>
> Hello BB experts,
>
> I recently purchased my first Beaglebone Black and cant wait to get 
> started.
> Have mostly worked on bare-metal microcontroller projects mostly involving 
> close loop motor control applications.I would like to step into the world 
> of operating systems(especially Linux) and decided that i would use the 
> beagle bone black as the starting platform.
> My ultimate aim is to develop an On-grid/Grid tied inverter using the 
> Beaglebone black.
>
> I have a couple of questions and would be gratefull if someone points me 
> in the right direction.
> 1.Having worked mostly in c/c++ and assembly,is it a good idea to stick to 
> the same languages or i am better off programming in a different language 
> like python,Java etc?
> 2.How easy it it to intergrate the software to access the hardware,i mean 
> are most of the drivers already written and are they easily avalable?I plan 
> to intergrate an two slave MCUs via SPI,and some sensors via I2C bus.
> 3.Is it possible to use the PRUs of the Sitara controller as a parallel 
> port for some high speed data transfer?like getting data from a fast ADC or 
> writing to a DAC?
> Also interface a 20x4 LCD display via the GPIO ports.
>
> I would like some starting directions as to how to proceed with the above 
> with the BBB.
> I fould some tutorials on using the beagle bone black here 
> .
>
> Many thank,
> Arun
>
>
>
>

-- 
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/260fcc12-2ac3-4d37-baa8-93f04e4b0d5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] AWS IOT C++

2018-02-18 Thread Hemant Kapoor

Hello All, 

I have a c++ program running on beaglebone black which reads temperature 
from MCP9808 IC via i2c protocol.

For this I have created a thing in AWS IOT and want to update it via 
MQTT... All this needs to be done in C++

This is the plan and have no idea how to do this... 

Has any one done something similar to could guide me as how this could be 
acheived.

Regards, 
Hemant Kapoor

-- 
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/afa51942-0df9-4679-adb7-6e874313f69b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBBW WiFi does not work after eprom flash

2018-02-18 Thread Robert Nelson

On Sun, Feb 18, 2018 at 12:00 PM, Stephen Mansfield
 wrote:
> Hello,
>
> I received my BBBW the other day.  Everything worked fine including the
> wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3
> 2018-01-28 SD LXQT and the wireless no longer works.  When I type
> root@beaglebone:/# connmanctl and then type > scan wifi it get the following
> error, "Error /net/connman/technology/wifi: Method "Scan" with signature ""
> on interface "net.connman.Technology" doesn't exist".  When I type ifconfig
> I get,
>
> root@beaglebone:/# ifconfig
> eth0: flags=-28669  mtu 1500
> ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 181
>
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Local Loopback)
> RX packets 2720  bytes 184480 (180.1 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 2720  bytes 184480 (180.1 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb0: flags=4163  mtu 1500
> inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
> inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 0x20
> ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet)
> RX packets 807  bytes 126314 (123.3 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 190  bytes 36851 (35.9 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> usb1: flags=4099  mtu 1500
> inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
> ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet)
> RX packets 0  bytes 0 (0.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> root@beaglebone:/#
>
> I see no wlan.  There is a previous post that descripibes grounding TP1.  I
> did the following
>
> GND TP1 then run as root:
>
> dd if=/opt/scripts/device/bone/bbbw-eeprom.dump
> of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom

This is "one" line.. ^

You can also run:

sudo /opt/scripts/tools/version.sh | grep eeprom

to verify it programmed.

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

[beagleboard] BBBW WiFi no longer works after latest eprom update

2018-02-18 Thread stephen . k . mansfield


Hello,

I received my BBBW the other day.  Everything worked fine including the 
wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3 
2018-01-28 SD LXQT and the wireless no longer works.  When I type 
root@beaglebone:/# connmanctl and then type > scan wifi it get the 
following error, "Error /net/connman/technology/wifi: Method "Scan" with 
signature "" on interface "net.connman.Technology" doesn't exist".  When I 
type ifconfig I get, 

root@beaglebone:/# ifconfig
eth0: flags=-28669  mtu 1500
ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 181

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Local Loopback)
RX packets 2720  bytes 184480 (180.1 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2720  bytes 184480 (180.1 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163  mtu 1500
inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 0x20
ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet)
RX packets 807  bytes 126314 (123.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 190  bytes 36851 (35.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4099  mtu 1500
inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@beaglebone:/#

I see no wlan.  There is a previous post that descripibes grounding TP1.  I 
did the following

GND TP1 then run as root: 

dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 

I rebooted but still no wifi.  Just to be sure, I am using a Beaglebone 
Black Wireless.  Any thoughts?

-- 
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/632d270c-7bca-43af-b03a-4c7c3f2fad87%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBBW WiFi does not work after eprom flash

2018-02-18 Thread Stephen Mansfield

Hello,

I received my BBBW the other day.  Everything worked fine including the 
wireless.  I updated it with the latest Stretch LXQT image -- Debian 9.3 
2018-01-28 SD LXQT and the wireless no longer works.  When I type 
root@beaglebone:/# connmanctl and then type > scan wifi it get the 
following error, "Error /net/connman/technology/wifi: Method "Scan" with 
signature "" on interface "net.connman.Technology" doesn't exist".  When I 
type ifconfig I get, 

root@beaglebone:/# ifconfig
eth0: flags=-28669  mtu 1500
ether 50:65:83:d9:82:98  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 181

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Local Loopback)
RX packets 2720  bytes 184480 (180.1 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2720  bytes 184480 (180.1 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb0: flags=4163  mtu 1500
inet 192.168.7.2  netmask 255.255.255.252  broadcast 192.168.7.3
inet6 fe80::5265:83ff:fed9:829a  prefixlen 64  scopeid 0x20
ether 50:65:83:d9:82:9a  txqueuelen 1000  (Ethernet)
RX packets 807  bytes 126314 (123.3 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 190  bytes 36851 (35.9 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

usb1: flags=4099  mtu 1500
inet 192.168.6.2  netmask 255.255.255.252  broadcast 192.168.6.3
ether 50:65:83:d9:82:9d  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@beaglebone:/#

I see no wlan.  There is a previous post that descripibes grounding TP1.  I 
did the following

GND TP1 then run as root: 

dd if=/opt/scripts/device/bone/bbbw-eeprom.dump 
of=/sys/devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050/eeprom 

I rebooted but still no wifi.  Just to be sure, I am using a Beaglebone 
Black Wireless.  Any thoughts?

-- 
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/825d8796-a805-4cec-bcf3-4dc95fe5d175%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Why information from 'md' and 'imi' commands is different?

2018-02-18 Thread Vasyl Yosypenko

Why when used cmd 'md' Load address is 00800080, but when cmd 'imi' - 
> 80008000 ?





-- 
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/4ed948eb-ce76-4354-95ab-b38052f0c7e0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Why information from 'md' and 'imi' commands is different?

2018-02-18 Thread v . v . yosypenko



Why when used cmd 'md' Load address is 00800080, but when cmd 'imi' - 
> 80008000 ?



-- 
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/f1553ad4-0aa1-4804-b07f-e576b3441212%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Can one check for Rev B or Rev C in software?

2018-02-18 Thread Chris Green

On Sat, Feb 17, 2018 at 11:09:25AM -0600, Robert Nelson wrote:
> On Sat, Feb 17, 2018 at 10:49 AM, Chris Green  wrote:
> > I have a remote BBB and I want to check whether it is Rev B or Rev C,
> > how can I do this using just command line software (I only have ssh
> > access to it).
> 
> debian@test-bbb-2:~$ sudo /opt/scripts/tools/version.sh | grep eeprom
> 
My remote BBB is too old to have that!

I tried copying the version.sh script but it produced no output, so I
dug further and just ran the code for the eeprom output, it gives:

eeprom:[A335BNLT00A55004BBBK0340]

So presumably that makes it revision A5, very ancient by BBB
standards. As it reports 4Gb of memory I assume I must be running from
microSD as the EMMC would be 2Gb.

-- 
Chris Green

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

Re: [beagleboard] baseboard folder disappears in bone_capemgr after kernel upgrade to latest 4.4 kernel

Re: [beagleboard] Re: bbgw wlan0 users

[beagleboard] Re: BBBW WiFi does not work after eprom flash

[beagleboard] Re: BBBW WiFi does not work after eprom flash

Re: [beagleboard] BBBW WiFi does not work after eprom flash

[beagleboard] Re: BBBW WiFi does not work after eprom flash

Re: [beagleboard] AWS IOT C++

Re: [beagleboard] AWS IOT C++

Re: [beagleboard] Re: bbgw wlan0 users

[beagleboard] Re: getting started with beaglebone black

[beagleboard] AWS IOT C++

Re: [beagleboard] BBBW WiFi does not work after eprom flash

[beagleboard] BBBW WiFi no longer works after latest eprom update

[beagleboard] BBBW WiFi does not work after eprom flash

[beagleboard] Why information from 'md' and 'imi' commands is different?

[beagleboard] Why information from 'md' and 'imi' commands is different?

Re: [beagleboard] Can one check for Rev B or Rev C in software?

17 matches

Site Navigation

Mail list logo

Footer information