[beagleboard] Re: I2C Read with length in the first byte of the transaction

2018-02-15 Thread Andrew P. Lentvorski 
Well, if the SMBus Specification Version 2.0 Section "5.5.7 Block 
write/read" is goofy then, um, okay ...

However, since this appears to be a standard part of SMBus, now I really do 
wish to ask "How do I do this with the Linux I2C drivers?"

-- 
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/a7b322ee-3e44-45b7-a8cd-1477824d6473%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Announcing $25 PocketBeagle

2018-02-15 Thread Graham Haddock 
It works fine on the PocketBeagle running Debian.
You do need to connect it to USB1, which is pinned out on the accessory
connectors, and not USB0, which is on the micro-USB connector.
--- Graham

==

On Thu, Feb 15, 2018 at 7:04 AM,  wrote:

> Hello,
>
> I'm trying to get Internet over USB working on the PocketBeagle with an
> Ubuntu 16.04 host, but without success.
> Has anybody managed to get that working ?
>
> Thanks!
>
> Le mardi 19 décembre 2017 18:15:37 UTC+1, Jason Kridner a écrit :
>>
>>
>>
>> On Tuesday, October 3, 2017 at 10:58:51 PM UTC-4, Graham wrote:
>>>
>>> Andy:
>>>
>>> The following is an outline of what to do to connect a PocketBeagle to
>>> the internet via the USB cable to a Windows 10 desktop which is connected
>>> to the Internet via hardwire Ethernet.
>>>
>>> ~~~
>>> Ethernet over USB Tether Gadget
>>> ~~~
>>>
>>> This is to connect a PocketBeagle to the Internet through the USB
>>> connection to a Windows 10 desktop, which is connected by hardwire Ethernet
>>> to the Internet.
>>>
>>> I used 'Etcher' to load a fresh copy of the latest 'stretch' version of
>>> Debian 9.1 onto the Pocketbone.
>>> bone-debian-9.1-iot-armhf-2017-10-01-4gb.img
>>>
>>> Plug the PocketBeagle into an open USB port on your Windows 10 desktop
>>>
>>> The four LEDs should start blinking, and after about a minute or so, a
>>> new USB serial device should appear in Device Manager\Ports(COM), and a
>>> new Remote NDIS Compatible Device should appear in Device Manager\Network
>>> Adaptors
>>>
>>> Also, a new Ethernet interface will appear in Control Panel\Network and
>>> Internet\Network Connections.
>>> It will be described as "Unidentified Network", Remote NDIS Compatible
>>> Device
>>>
>>> Use Putty to connect to the new COM port
>>> log into the PocketBeagle
>>>
>>> now type
>>> sudo /sbin/route add default gw 192.168.7.1
>>>
>>
>> Instead of doing this, I use 'sudo dhclient usb0' such that it updates
>> the nameservers (/etc/resolv.conf) automatically.
>>
>> For Mac/Linux, I use 'sudo dhclient usb1'.
>>
>>
>>>
>>> Now, on the Windows 10 desktop,
>>> go to and open your primary Ethernet interface:
>>>  Ethernet\Properties\Sharing\
>>> Check the two sharing boxes.
>>> Enter the name of the new NDIS Device interface into the box. [In my
>>> case it was Ethernet 2 ]
>>> Click 'OK' and exit the interface box
>>>
>>> Now open the Unidentified Network\NDIS Device
>>> interface\Properties\Internet Protocol Version 4\Properties
>>> Click 'Use the following IP address'
>>> Enter 192.168.7.1 as the IP address
>>> Enter 255.255.255.0 as the Subnet Mask
>>>
>>> Click 'Use the following DNS server addresses'
>>> Enter 8.8.8.8 as the Preferred DNS server.
>>> Click 'OK' and 'Close' to exit
>>>
>>> Now go to the PocketBeagle command line on Putty
>>> sudo nano /etc/resolv.conf
>>> down-arrow to get past the comment line
>>> enter 'nameserver 8.8.8.8'   [without the quotes]
>>> enter 
>>> enter , then 'Y',  to exit[without the quotes]
>>>
>>> The Ethernet tether gadget should be operational.
>>> To test, type 'ping google.com' in the command line. [without the
>>> quotes]
>>> It should run and see the ping replies.
>>> type  to abort.
>>>
>>> You should now have internet access and can
>>> sudo apt-get update
>>>
>>> The two entries in the PockBeagle are not persistent, so after any
>>> reboot,
>>> you will have to repeat the two entries in the PocketBeagle to get the
>>> internet tether gadget running again.
>>>
>>>
>>> There is more information here ...
>>> https://www.digikey.com/en/maker/blogs/how-to-connect-a-beag
>>> lebone-black-to-the-internet-using-usb/cdf66181b3a5436e9ad730e4ed4cf9ee
>>>
>>> ==
>>>
>>
> --
> 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/JtOGZb-FH2A/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/b1129fa8-22ef-49ba-9237-11c5586ef8a5%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

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

Re: [beagleboard] problem flashing beagle-bone black

2018-02-15 Thread Robert Nelson 
On Thu, Feb 15, 2018 at 2:44 PM,   wrote:
> Ok we will need to purchase cable before we can send you boot log
>
> They have changed the chips for eMMC(U13) and SDRAM(U12). could this be
> causing the problem?

Most likely, and it's probably something we solved a few years ago.

But take a look at your original message, it's lacking lots of
important details, so we can't answer anything, unless you give is
something.

Thus that's why i asked for a boot log..

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

Re: [beagleboard] problem flashing beagle-bone black

2018-02-15 Thread grjorgens 
Ok we will need to purchase cable before we can send you boot log

They have changed the chips for eMMC(U13) and SDRAM(U12). could this be 
causing the problem?


On Thursday, February 15, 2018 at 12:33:16 PM UTC-8, RobertCNelson wrote:
>
> On Thu, Feb 15, 2018 at 2:23 PM,   
> wrote: 
> > can you use usb port(P3)? or is it necessary to use J1 to view boot log? 
>
> Anything dealing with 'bootup', J1 is the only way to grab anything 
> before the kernel loads.. 
>
> 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/28721a09-cf93-42bc-9c05-a3c4e5e42c2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] problem flashing beagle-bone black

2018-02-15 Thread Greg Jorgensen 
 can you use usb port(P3)? or is it necessary to use J1 to view boot log?



On Thu, Feb 15, 2018 at 11:37 AM, Robert Nelson 
wrote:

> On Thu, Feb 15, 2018 at 1:16 PM, grjjl  wrote:
> > We have been using a micro sd to flash a new image to a debian
> beagle-bone
> > black board.(pressing the boot button when power is applied with micro
> sd)
> >
> > we ordered more boards(same supplier same part number) and tried flashing
> > them with the same method. we have been unable to successfully flash any
> of
> > the boards. The user LED's never turn on when we try to flash the board.
> >
> > any suggestions/tips would be helpful.
>
> Please plug in a usb-serial adapter into the J1 header
>
> https://elinux.org/Beagleboard:BeagleBone_Black_Serial
>
> And please attach a boot log of a working and non-working board to the
> list for us to look at..
>
> 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/CAAP3VynW9ymzFgaySz%3DsQSk5WRjTDz7Z2q24ThBDHR3fhfApYg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] problem flashing beagle-bone black

2018-02-15 Thread grjorgens 
can you use usb port(P3)? or is it necessary to use J1 to view boot log?

On Thursday, February 15, 2018 at 11:38:10 AM UTC-8, RobertCNelson wrote:
>
> On Thu, Feb 15, 2018 at 1:16 PM, grjjl  
> wrote: 
> > We have been using a micro sd to flash a new image to a debian 
> beagle-bone 
> > black board.(pressing the boot button when power is applied with micro 
> sd) 
> > 
> > we ordered more boards(same supplier same part number) and tried 
> flashing 
> > them with the same method. we have been unable to successfully flash any 
> of 
> > the boards. The user LED's never turn on when we try to flash the board. 
> > 
> > any suggestions/tips would be helpful. 
>
> Please plug in a usb-serial adapter into the J1 header 
>
> https://elinux.org/Beagleboard:BeagleBone_Black_Serial 
>
> And please attach a boot log of a working and non-working board to the 
> list for us to look at.. 
>
> 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/376b1dbb-e491-4a5f-93ae-e081dec18b49%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 1-Wire Implementation on PocketBeagle

2018-02-15 Thread Robert Nelson 
On Thu, Feb 15, 2018 at 2:12 PM, evilwulfie  wrote:
> I cant help you with a pocket beagle but i can help.
> dont reflash. put a bootable SD card in  boot and mount the emmc
>
> mount -t ext4 /dev/mmcblk1p1 /mnt/emmcext
> cd /mnt/emmcext/boot
>
> comment out the offending line in your uEnv.txt file
>
> umount /mnt/emmcext

No eMMC on the PocketBeagle..

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

Re: [beagleboard] 1-Wire Implementation on PocketBeagle

2018-02-15 Thread Robert Nelson 
On Thu, Feb 15, 2018 at 2:11 PM, Robert Nelson  wrote:
> On Thu, Feb 15, 2018 at 1:48 PM,   wrote:
>> I am trying to implement the 1-Wire protocol to read a DS18B20 temperature
>> sensor on the PocketBeagle. So far I have been able to correctly read the
>> temperature on a BeagleBone Black (BBB) using the following guide:
>>
>> http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/
>>
>> I changed the .dts file below to use the same GPIO port on the BBB (P8.11 -
>> GPIO45) as on the PocketBeagle (P2.33 - GPIO45) on line 19 and added the
>> missing semicolon on line 37. I checked the GPIO offset for both of these
>> pins and they are the same, so it should be the same signal.
>>
>> /*
>> * 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 Public License version 2 as
>> * published by the Free Software Foundation.
>> *
>> * Modified  by Russell Senior from the weather cape's DTS file.
>> * Minor formatting by C W Rose.
>> */
>> /dts-v1/;
>> /plugin/;
>>
>>
>> / {
>> compatible = "ti,beaglebone", "ti,beaglebone-black";
>> part-number = "BB-W1";
>> version = "00A0";
>>
>>
>> exclusive-use = "P8.11"; /*changed to P2.33 for PocketBeagle*/
>>
>>
>> fragment@0 {
>> target = <_pinmux>;
>> __overlay__ {
>>  bb_w1_pins: pinmux_bb_w1_pins {
>>  pinctrl-single,pins =  <0x34 0x37 /* gpmc_ad13.gpio1_13,
>> OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ >;
>>  };
>> };
>> };
>>
>>
>> fragment@1 {
>> target = <>;
>> __overlay__ {
>> onewire@0 {
>> status  = "okay";
>> compatible  = "w1-gpio";
>> pinctrl-names   = "default";
>> pinctrl-0   = <_w1_pins> /*missing semicolon here!*/
>>
>>
>> gpios = < 13 0>;
>> };
>> };
>> };
>> };
>>
>>
>> However, when I try to use the same procedure on the PocketBeagle (which is
>> running Ubuntu), I run into a problem when trying to load the overlay. The
>> guide I have been following uses the capemgr.9 for the BBB, which is not
>> supported by the PocketBeagle. I then tried to load the overlay using the
>> uEnv.txt file to load the overlay (.dcbo file located in /lib/firmware/) at
>> boot. I uncommented the master enable and Overlay 1 lines and replaced the
>> "file" placed holder with the .dcbo file name.
>>
>> After attempting the reboot the PocketBeagle to load the overlay, the
>> PocketBeagle gets stuck during its boot procedure and fails to fully boot
>> and have to reflash the SD card to boot the device; I believe this is due to
>> trying to load the overlay.
>>
>> Therefore I have a few questions:
>>
>> Is there information in the above .dts file that is causing this error?
>> Is changing "P8.11" to "P2.33" supported by the PocketBeagle?
>> Are there any other steps I am missing to load the overlay using uEnv.txt?
>
> Give this a shot:
>
> https://gist.github.com/RobertCNelson/dfd4f707a89b83c9366ecfcdc24321b0
>
> In fragment 0, we drop the cape-universal pinmux for P2_33, this
> free's up the pin for dedicated functions.
>
> In fragment 1, no change
>
> In fragment 2,  -> 

Looking at my old example:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-W1-P9.12-00A0.dts#L41-L55

we'll need a nother change..

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

Re: [beagleboard] 1-Wire Implementation on PocketBeagle

2018-02-15 Thread evilwulfie 
I cant help you with a pocket beagle but i can help.
dont reflash. put a bootable SD card in  boot and mount the emmc

mount -t ext4 /dev/mmcblk1p1 /mnt/emmcext
cd /mnt/emmcext/boot

comment out the offending line in your uEnv.txt file

umount /mnt/emmcext

and reboot

On 2/15/2018 12:48 PM, caleb.c.stew...@gmail.com wrote:
> I am trying to implement the 1-Wire protocol to read a DS18B20
> temperature sensor on the PocketBeagle. So far I have been able to
> correctly read the temperature on a BeagleBone Black (BBB) using the
> following guide:
>
> http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/
>
> I changed the .dts file below to use the same GPIO port on the BBB
> (P8.11 - GPIO45) as on the PocketBeagle (P2.33 - GPIO45) on line 19
> and added the missing semicolon on line 37. I checked the GPIO offset
> for both of these pins and they are the same, so it should be the same
> signal.
>
> |
> /*
> * 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 Public License version 2 as
> * published by the Free Software Foundation.
> *
> * Modified  by Russell Senior from the weather cape's DTS file.
> * Minor formatting by C W Rose.
> */
> /dts-v1/;
> /plugin/;
>
>
> /{
>     compatible ="ti,beaglebone","ti,beaglebone-black";
>     part-number ="BB-W1";
>     version ="00A0";
>
>
>     exclusive-use="P8.11";/*changed to P2.33 for PocketBeagle*/
>
>
>     fragment@0 {
>         target =<_pinmux>;
>         __overlay__ {
>              bb_w1_pins:pinmux_bb_w1_pins {
>                  pinctrl-single,pins = <0x340x37/* gpmc_ad13.gpio1_13,
> OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */>;
>              };
>         };
>     };
>
>
>     fragment@1 {
>         target =<>;
>         __overlay__ {
>             onewire@0 {
>                 status          ="okay";
>                 compatible      ="w1-gpio";
>                 pinctrl-names   ="default";
>                 pinctrl-0      =<_w1_pins>/*missing semicolon here!*/
>
>
>                 gpios =< 130>;
>             };
>         };
>     };
> };
> |
>
>
> However, when I try to use the same procedure on the PocketBeagle
> (which is running Ubuntu), I run into a problem when trying to load
> the overlay. The guide I have been following uses the capemgr.9 for
> the BBB, which is not supported by the PocketBeagle. I then tried to
> load the overlay using the uEnv.txt file to load the overlay (.dcbo
> file located in /lib/firmware/) at boot. I uncommented the master
> enable and Overlay 1 lines and replaced the "file" placed holder with
> the .dcbo file name.
>
> After attempting the reboot the PocketBeagle to load the overlay, the
> PocketBeagle gets stuck during its boot procedure and fails to fully
> boot and have to reflash the SD card to boot the device; I believe
> this is due to trying to load the overlay. 
>
> *Therefore I have a few questions:*
>
>   * Is there information in the above .dts file that is causing this
> error? 
>   * Is changing "P8.11" to "P2.33" supported by the PocketBeagle?
>   * Are there any other steps I am missing to load the overlay using
> uEnv.txt?
>
>
> Any help on this would be greatly appreciated!
> -- 
> 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/9a452247-e7b2-4bb0-80b1-0f83482aee23%40googlegroups.com
> .
> For more options, visit https://groups.google.com/d/optout.

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

Re: [beagleboard] 1-Wire Implementation on PocketBeagle

2018-02-15 Thread Robert Nelson 
On Thu, Feb 15, 2018 at 1:48 PM,   wrote:
> I am trying to implement the 1-Wire protocol to read a DS18B20 temperature
> sensor on the PocketBeagle. So far I have been able to correctly read the
> temperature on a BeagleBone Black (BBB) using the following guide:
>
> http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/
>
> I changed the .dts file below to use the same GPIO port on the BBB (P8.11 -
> GPIO45) as on the PocketBeagle (P2.33 - GPIO45) on line 19 and added the
> missing semicolon on line 37. I checked the GPIO offset for both of these
> pins and they are the same, so it should be the same signal.
>
> /*
> * 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 Public License version 2 as
> * published by the Free Software Foundation.
> *
> * Modified  by Russell Senior from the weather cape's DTS file.
> * Minor formatting by C W Rose.
> */
> /dts-v1/;
> /plugin/;
>
>
> / {
> compatible = "ti,beaglebone", "ti,beaglebone-black";
> part-number = "BB-W1";
> version = "00A0";
>
>
> exclusive-use = "P8.11"; /*changed to P2.33 for PocketBeagle*/
>
>
> fragment@0 {
> target = <_pinmux>;
> __overlay__ {
>  bb_w1_pins: pinmux_bb_w1_pins {
>  pinctrl-single,pins =  <0x34 0x37 /* gpmc_ad13.gpio1_13,
> OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ >;
>  };
> };
> };
>
>
> fragment@1 {
> target = <>;
> __overlay__ {
> onewire@0 {
> status  = "okay";
> compatible  = "w1-gpio";
> pinctrl-names   = "default";
> pinctrl-0   = <_w1_pins> /*missing semicolon here!*/
>
>
> gpios = < 13 0>;
> };
> };
> };
> };
>
>
> However, when I try to use the same procedure on the PocketBeagle (which is
> running Ubuntu), I run into a problem when trying to load the overlay. The
> guide I have been following uses the capemgr.9 for the BBB, which is not
> supported by the PocketBeagle. I then tried to load the overlay using the
> uEnv.txt file to load the overlay (.dcbo file located in /lib/firmware/) at
> boot. I uncommented the master enable and Overlay 1 lines and replaced the
> "file" placed holder with the .dcbo file name.
>
> After attempting the reboot the PocketBeagle to load the overlay, the
> PocketBeagle gets stuck during its boot procedure and fails to fully boot
> and have to reflash the SD card to boot the device; I believe this is due to
> trying to load the overlay.
>
> Therefore I have a few questions:
>
> Is there information in the above .dts file that is causing this error?
> Is changing "P8.11" to "P2.33" supported by the PocketBeagle?
> Are there any other steps I am missing to load the overlay using uEnv.txt?

Give this a shot:

https://gist.github.com/RobertCNelson/dfd4f707a89b83c9366ecfcdc24321b0

In fragment 0, we drop the cape-universal pinmux for P2_33, this
free's up the pin for dedicated functions.

In fragment 1, no change

In fragment 2,  -> 

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

[beagleboard] 1-Wire Implementation on PocketBeagle

2018-02-15 Thread caleb . c . stewart 
I am trying to implement the 1-Wire protocol to read a DS18B20 temperature 
sensor on the PocketBeagle. So far I have been able to correctly read the 
temperature on a BeagleBone Black (BBB) using the following guide:

http://www.bonebrews.com/temperature-monitoring-with-the-ds18b20-on-a-beaglebone-black/

I changed the .dts file below to use the same GPIO port on the BBB (P8.11 - 
GPIO45) as on the PocketBeagle (P2.33 - GPIO45) on line 19 and added the 
missing semicolon on line 37. I checked the GPIO offset for both of these 
pins and they are the same, so it should be the same signal.

/*
* 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 Public License version 2 as
* published by the Free Software Foundation.
* 
* Modified  by Russell Senior from the weather cape's DTS file.
* Minor formatting by C W Rose.
*/
/dts-v1/;
/plugin/;


/ {
compatible = "ti,beaglebone", "ti,beaglebone-black";
part-number = "BB-W1";
version = "00A0";


exclusive-use = "P8.11"; /*changed to P2.33 for PocketBeagle*/


fragment@0 {
target = <_pinmux>;
__overlay__ {
 bb_w1_pins: pinmux_bb_w1_pins {
 pinctrl-single,pins =  <0x34 0x37 /* gpmc_ad13.gpio1_13, 
OMAP_PIN_INPUT_PULLUP | OMAP_MUX_MODE7 - w1-gpio */ >;
 };
};
};


fragment@1 {
target = <>;
__overlay__ {
onewire@0 {
status  = "okay";
compatible  = "w1-gpio";
pinctrl-names   = "default";
pinctrl-0   = <_w1_pins> /*missing semicolon here!*/ 


gpios = < 13 0>;
};
};
};
};


However, when I try to use the same procedure on the PocketBeagle (which is 
running Ubuntu), I run into a problem when trying to load the overlay. The 
guide I have been following uses the capemgr.9 for the BBB, which is not 
supported by the PocketBeagle. I then tried to load the overlay using the 
uEnv.txt file to load the overlay (.dcbo file located in /lib/firmware/) at 
boot. I uncommented the master enable and Overlay 1 lines and replaced the 
"file" placed holder with the .dcbo file name.

After attempting the reboot the PocketBeagle to load the overlay, the 
PocketBeagle gets stuck during its boot procedure and fails to fully boot 
and have to reflash the SD card to boot the device; I believe this is due 
to trying to load the overlay. 

*Therefore I have a few questions:*

   - Is there information in the above .dts file that is causing this 
   error? 
   - Is changing "P8.11" to "P2.33" supported by the PocketBeagle?
   - Are there any other steps I am missing to load the overlay using 
   uEnv.txt?
   

Any help on this would be greatly appreciated!

-- 
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/9a452247-e7b2-4bb0-80b1-0f83482aee23%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Using ROS (rosserial) on PocketBeagle

2018-02-15 Thread Brian Malbec 
I'm brand new to using Ubuntu, PocketBeagles, and ROS (Robotic Operating 
System). My current task is to read Xbox controller data on one 
PocketBeagle and be able to receive it on another PocketBeagle. The 
transmission medium is a pair of XBee S2C's. So far, I have been able to 
use /dev/ttyO4 on both PocketBeagles, and the XBees seem to be able to 
successfully communicate, as well as send Xbox controller data. 

Recently, my team and I discovered a package in ROS called rosserial, which 
claims to be able to send ROS serial messages. What we hope this means is 
that we will be able to send more data to the receiving PocketBeagle (under 
the belief that these ROS messages are smaller in size compared to sending 
raw controller data). Unfortunately, it seems that all of the support for 
this package is for Arduino, with little-to-no support for any other type 
of hardware, specifically embedded Linux. Rosserial also seems to have 
extensions for embeddedlinux and XBee, but nothing seems to be working. Is 
there anyone on this forum that is knowledgeable in ROS (especially 
rosserial) that can assist 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/589d5c3e-0782-4760-8159-a6d7fbf2b5a3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] problem flashing beagle-bone black

2018-02-15 Thread Robert Nelson 
On Thu, Feb 15, 2018 at 1:16 PM, grjjl  wrote:
> We have been using a micro sd to flash a new image to a debian beagle-bone
> black board.(pressing the boot button when power is applied with micro sd)
>
> we ordered more boards(same supplier same part number) and tried flashing
> them with the same method. we have been unable to successfully flash any of
> the boards. The user LED's never turn on when we try to flash the board.
>
> any suggestions/tips would be helpful.

Please plug in a usb-serial adapter into the J1 header

https://elinux.org/Beagleboard:BeagleBone_Black_Serial

And please attach a boot log of a working and non-working board to the
list for us to look at..

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

[beagleboard] problem flashing beagle-bone black

2018-02-15 Thread grjjl 
We have been using a micro sd to flash a new image to a debian beagle-bone 
black board.(pressing the boot button when power is applied with micro sd)

we ordered more boards(same supplier same part number) and tried flashing 
them with the same method. we have been unable to successfully flash any of 
the boards. The user LED's never turn on when we try to flash the board.

any suggestions/tips would be helpful.

 

 

-- 
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/da10c073-99b0-41d9-9621-f68b6aa1734b%40googlegroups.com.
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

2018-02-15 Thread Robert Nelson 
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 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/CAOCHtYhao3AtHyx7O6%2B7evZ8LvU4OAwB1veCEi2v3qkDGgyiSw%40mail.gmail.com.
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

2018-02-15 Thread Robert Nelson 
On Wed, Feb 14, 2018 at 11:33 PM, Luther Goh Lu Feng  wrote:
> I see. I need the serial number of the BBB. Previously I extracted it from
> /sys/devices/platform/bone_capemgr/baseboard/serial-number. Where can I get
> the equivalent now?

sudo hexdump -e '8/1 "%c"' /sys/bus/i2c/devices/0-0050/eeprom -n 28 |
cut -b 5-28

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

[beagleboard] Re: Yocto buil for PocketBeagle

2018-02-15 Thread Jeff Andich 
Don't know if the TI processor SDK 
(http://www.ti.com/tool/PROCESSOR-SDK-AM335X) for the BBB will run on the 
pocket beagle, but last-I checked the  TI processor SDK follows the 
OE/Yocto paradigm.  I apologize for forgetting the differences between 
Yocto and OE. 

The SDK contains canned build scripts and the FS, but then then if you 
follow the TI wiki pages, there's a link to (if you want to develop your 
own filesystem) which then downloads the whole Arago distribution 
associated with that TI SDK version, where you get all of the Yocto layers 
and bitbake.  I tried building it several months ago, and had issues with a 
missing library from git.ti.com.  Plus if you're on a corporate LAN and 
your company firewall doesn't allow git via git://, then you'll have that 
to deal with.

First thing would be to find out of the am335x ti SDK runs on the pocket 
beagle..

If you're interested in pursuing, I could try to fish up some links on how 
to download the associated Arago distribution if you're unable to find 
them..


On Thursday, February 15, 2018 at 7:50:48 AM UTC-6, no...@vytopna.com wrote:
>
> Hello, we are developing custom system on OSD3358 with PocketBeagle as 
> development platform. We need to buld own small linux distribution. We try 
> Yocto for that, but we cannot boot to that image. We try projects with 
> rocko or master release with meta-ti layer and beaglebone as target. Image 
> recipe we try core-image-base. We succes with build and write wic file to 
> micro SD, there are 2 partitions, one FAT16 with MLO and u-boot and another 
> with root filesystem. Whenever put SD card to pocketbeagle and power up it, 
> nothing hapened, only power LED is lighting. Nothing is even on UART0. When 
> we try oficial image it is working.
> We try to write MLO and u-boot RAW to sd card, but nothing hapenes. Does 
> anyone have any experience with yocto and PocketBeagle?
>
> Thank for any advice.
>

-- 
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/adfabd59-3a0a-495b-95ea-3dbac9581da0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Yocto buil for PocketBeagle

2018-02-15 Thread novak 
Hello, we are developing custom system on OSD3358 with PocketBeagle as 
development platform. We need to buld own small linux distribution. We try 
Yocto for that, but we cannot boot to that image. We try projects with 
rocko or master release with meta-ti layer and beaglebone as target. Image 
recipe we try core-image-base. We succes with build and write wic file to 
micro SD, there are 2 partitions, one FAT16 with MLO and u-boot and another 
with root filesystem. Whenever put SD card to pocketbeagle and power up it, 
nothing hapened, only power LED is lighting. Nothing is even on UART0. When 
we try oficial image it is working.
We try to write MLO and u-boot RAW to sd card, but nothing hapenes. Does 
anyone have any experience with yocto and PocketBeagle?

Thank for any advice.

-- 
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/a3f47251-e916-414b-bd92-751c7605741b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.