[beagleboard] Re: I2C SCL Voltage level too low?

[yassyass]

With the 1k resistors improvement is evident in terms of voltage level for 
the high signal.




However the rise time still seems to be slow and I2C device is still not 
responding to commands. 






I will try and increase the resistance to 3k3 as advised by John and will 
report back with results.

-- 
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/355482bc-9893-446d-8d2e-a118f8110dd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] I2C SCL Voltage level too low?

[yassyass]

I only managed to get hold of a couple 1k resistors and wired them up to 
the 3v3 rail and got improvements. I am going to assume the internal 
pullups on the I2C device were not enabled. 




 

On Thursday, April 5, 2018 at 5:22:35 PM UTC+12, john3909 wrote:
>
> You mean decrease the resistor values. Don’t rely on the internal pull up 
> resistors. 4K7 should be OK, but try 3K3 to see if the signals look better. 
>
> Regards,
> John
>
>
>
>
>
> On Apr 4, 2018, at 10:06 PM, yassyass  
> wrote:
>
> Thanks Wulf, I will attempt to increase the resistor values and get back 
> with results.
>
>
> -- 
> For more options, visit http://beagleboard.org/discuss
> --- 
> You received this message because you are subscribed to the Google Groups 
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to beagleboard...@googlegroups.com .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/beagleboard/893c8ea1-b87c-4331-94fe-0be41e89e962%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/41abbc70-8bd1-47da-8958-02b563450ab5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] I2C SCL Voltage level too low?

[John Syne]

You mean decrease the resistor values. Don’t rely on the internal pull up 
resistors. 4K7 should be OK, but try 3K3 to see if the signals look better. 

Regards,
John





> On Apr 4, 2018, at 10:06 PM, yassyass  wrote:
> 
> Thanks Wulf, I will attempt to increase the resistor values and get back with 
> results.
> 
> 
> -- 
> 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/893c8ea1-b87c-4331-94fe-0be41e89e962%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/E178BD24-10B7-4FD9-918D-BE5F873C5FA2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] I2C SCL Voltage level too low?

[yassyass]

Thanks Wulf, I will attempt to increase the resistor values and get back 
with results.

-- 
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/893c8ea1-b87c-4331-94fe-0be41e89e962%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] I2C SCL Voltage level too low?

[evilwulfie]

I use 5.6k resistors. I think what your seeing is a slow scope.

On 4/4/2018 9:50 PM, yassyass wrote:
> Wrote a python script using SMBus to write to a slave I2C device. The
> slave is detectable with i2cdetect which results in the following output
>
> debian@beaglebone:~$ i2cdetect -y -r 2
>
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
>
> 00:          -- -- -- -- -- -- -- -- -- -- -- -- -- 
>
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>
> 30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>
> 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>
> 50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 
>
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 
>
> 70: -- -- -- -- -- -- -- --    
>
>
> The slave device would not respond to commands and upon inspecting it
> with a scope the voltage signal is appearing lower than the high
> threshold and has a very high time constant it seems. 
>
>
> The slave device has its own internal pull-up resistors of two 4.7k
> resistors one on each of the buses to the 3V supply on the BBB.
>
>
> The frequency of the bus is set to 400kHz on i2c-2. The BBB is being
> powered by USB only. 
>
>
> The following images are of the SCL bus
>
>
> 
>
> 
>
> Could the issue be that the pull up resistors are too high? Does the
> BBB require more power via an external source?
>
>
>
> -- 
> 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/5f323c46-4809-4f8f-aeb8-cb390d3288c9%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/de8a16a1-a9d0-87ae-a6fc-e2c57c1ed3ed%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] I2C SCL Voltage level too low?

[yassyass]

Wrote a python script using SMBus to write to a slave I2C device. The slave 
is detectable with i2cdetect which results in the following output

debian@beaglebone:~$ i2cdetect -y -r 2

 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f

00:  -- -- -- -- -- -- -- -- -- -- -- -- -- 

10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

30: 30 -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

50: -- -- -- -- UU UU UU UU -- -- -- -- -- -- -- -- 

60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 

70: -- -- -- -- -- -- -- --


The slave device would not respond to commands and upon inspecting it with 
a scope the voltage signal is appearing lower than the high threshold and 
has a very high time constant it seems. 


The slave device has its own internal pull-up resistors of two 4.7k 
resistors one on each of the buses to the 3V supply on the BBB.


The frequency of the bus is set to 400kHz on i2c-2. The BBB is being 
powered by USB only. 


The following images are of the SCL bus






Could the issue be that the pull up resistors are too high? Does the BBB 
require more power via an external source?



-- 
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/5f323c46-4809-4f8f-aeb8-cb390d3288c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: USB keyboard and mouse not working with yocto?

[hsinggloria]

Hi, I have the same issue with my build, but I don't have the meta-ti 
layer... 

On Thursday, August 27, 2015 at 8:46:52 AM UTC-7, hwha...@gmail.com wrote:
>
> Traced the issue down to something in the meta-ti layer. Google was able 
> to find this thread 
> 
> .
> The meta-ti layer doesn't include kernel modules in the root image but the 
> default meta-yocto-bsp does. The solution is to add 
> MACHINE_EXTRA_RRECOMMENDS = " kernel-modules" 
> to the beaglebone.conf or ti33xx.inc file in the meta-ti layer.
>
> On Tuesday, August 25, 2015 at 8:40:02 PM UTC-7, Jonathan Campbell wrote:
>>
>> On a BBB rev B, I've tried clean builds of yocto 1.8 (Fido) and 1.7 
>> (Dizzy) with the matching meta-ti layer. When building the standard 
>> core-image-sato, I never get a simple USB mouse and keyboard to work.
>> I know the BBB HW works as the keyboard, mouse, and usb hub work just 
>> fine with the latest Debian image (2015-03-01).
>> I've tried several kernel versions (including 3.14, and 4.1) and several 
>> different combos of having things plugged into the BBB upon power up.
>>
>> Has anyone else had this issue? Mr. Google wasn't of much help for me 
>> with this issue. Any pointers or debugging methods would be 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/99035f65-8292-400e-992e-10f75670a093%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] enc28J60 support for BBB

[drh8712]

I need to implement a second ethernet port on a BBB running 
4.4.115-bone21.  I am using a enc28J60 board interfaced to SP1.  We 
combined dts source from BB-SPIDEV1.dts and PB-SPI1-ETH-CLICK.dts and 
created enc28j60-00A0.dts:

Everything works as expected and we can use both ports:  
The content of /etc/udev/rules.d/70-persistent-net.rules

is as follows:

# Auto generated by RootStock-NG: setup_sdcard.sh
# udevadm info -q all -p /sys/class/net/eth0 --attribute-walk

# BeagleBone: net device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="cpsw", ATTR{type}=="1", 
NAME="eth1"

BeagleBone: net enc28j80 device ()
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="enc28j60", ATTR{type}=="1", 
NAME="eth0"

our issue is during a bootup sequence we are getting about a 90 second 
delay after about 5.5 seconds. I have attached the appropriate portion of 
the dmesg output:

4.318705] random: udevadm: uninitialized urandom read (16 bytes read, 9 
bits of entropy available)
[4.319277] random: udevadm: uninitialized urandom read (16 bytes read, 
9 bits of entropy available)
[4.319786] random: udevadm: uninitialized urandom read (16 bytes read, 
9 bits of entropy available)
[5.483137] cpsw 4a10.ethernet rename3: renamed from eth1
[   96.473474] EXT4-fs (mmcblk1p1): mounted filesystem with ordered data 
mode. Opts: (null)
[   96.658743] random: nonblocking pool is initialized
[   96.883412] systemd[1]: RTC configured in localtime, applying delta of 
-360 minutes to system time.

The content of /etc/network/interfaces is also attached:

# 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
iface lo inet loopback

# The primary network interface
auto eth0
allow-hotplug eth0
iface eth0 inet static
   address 172.20.23.110
   netmask 255.255.252.0
   gateway 172.20.23.1
#   post-up route add -net 172.20.23.0 netmask 255.255.255.0 gw 
172.20.23.138 dev eth0
#   post-down route del default gw 172.20.23.1


auto eth1
allow-hotplug eth1
iface eth1 inet static
   address 172.20.23.111
   netmask 255.255.252.0
   gateway 172.20.23.1
#   post-up route add -net 172.20.23.0 netmask 255.255.255.0 gw 
172.20.23.138 dev eth0
#   post-down route del default gw 172.20.23.1

I do not know what could be causing the the BBB ethernet port to be 
renamed.  This does not occur when the enc28J60 board is removed.  

This delay appears as if the BBB ethernet port is waiting for a DHCP server 
to respond.  But why would it behavior this way only when the enc28J60 is 
present?

Any help 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/b4b9d074-e004-4f95-91cc-0b748dbf5efc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: How to wire up and configure an i2c device on Beaglebone

[yassyass]

I would like to ask the same question that klemenz is asking. Does cloud9 
provide a framework to run i2c slaves with js or python?

On Wednesday, March 7, 2012 at 10:44:32 PM UTC+13, klemenz...@gmail.com 
wrote:
>
> Hi Dan,
>
> Is there an i2c support within cloud9ide environment or more precisely 
> within bonescript custom .js?
>
> thanks
>
> Dne sobota, 31. december 2011 22:07:43 UTC+1 je oseba Dan napisala:
>>
>> Stan, 
>> Thanks for the info.  I was able to get i2cdetect to work with a 3.3V 
>> device, and will give the level shifter a shot (when I have one) for 
>> the 5V device. 
>> Poking around further, I'm guessing the /sys/class/i2c-adapter 
>> approach mentioned in my question #4 works only if there is a kernel 
>> module for the device.  For example, there is a kernel-module-bmp085 
>> for the BMP085 barometric sensor. 
>> For everything else, there is the i2cget and i2cset approach that you 
>> recommended. 
>> Thanks, 
>> Dan. 
>> On Dec 30, 9:55 pm, Stan Seibert  wrote: 
>> > On Dec 30, 4:50 pm, Dan  wrote: 
>> > 
>> > > 1. Should the pullup resistors always be connected to 3.3V (as 
>> opposed 
>> > > to some other voltage) on the Beaglebone?  I used 5K resistors - is 
>> > > that close enough? (the SRM says 5.5K). 
>> > 
>> > 5k resistors should be fine (I used 4.7k with my device), and since 
>> > the I/O voltage on the board is 3.3V, you should only connect the pull- 
>> > ups to that.  (Pin 3 or 4 on P9) 
>> > 
>> > > 2. Are pins 19 and 20 connected to i2c2 or i2c3?  The SRM manual says 
>> > > i2c2, but based on the results of i2cdetect and other posts I think 
>> > > it's i2c3.  Is there an i2c2 on the Beaglebone? 
>> > 
>> > The numbering in the OS seems to be different than the numbering in 
>> > the SRM.  Pins 19 and 20 are on i2c2 in the hardware numbering scheme, 
>> > but in Linux, the device name is /dev/i2c-3. 
>> > 
>> > > 3. Should i2cdetect automatically find thei2cdevice at the correct 
>> > > address if everything is hooked up correctly? 
>> > 
>> > That depends on your device and whether it will respond to the read 
>> > probes that i2cdetect uses, but in general, yes. 
>> > 
>> > > 4. Do I always need to enter a command similar to the one in Koen's 
>> > > article: "echo bmp085 0x77 > /sys/class/i2c-adapter/i2c-3/ 
>> > > new_device"?  Is the "bmp085" part just a label that I choose, or 
>> does 
>> > > it need to precisely match some setting in the device? 
>> > 
>> > I just interact with my device using the i2cget and i2cset command 
>> > line tools, following the data sheet for my device to know what data 
>> > addresses on the device to set and get. 
>> > 
>> > > 5.Is a 5V device like theBlinkMsupported by the BeagleboneI2C?  If 
>> > > so, is the process for configuring it any different from the process 
>> > > described in Koen's blog post?  (This is the device I tried to get 
>> > > working, and I'm guessing it's not supported). 
>> > 
>> > I've never tried using a 3.3V master and a 5VI2Cdevice, but I have 
>> > used this level shifter for the other direction with an Arduino (5V 
>> > master and 3.3V device): 
>> > 
>> > http://www.sparkfun.com/products/8745 
>> > 
>> > (The description and comments were kind of confusing for this board. 
>> > I used the TX on channel 1 and 2 for theI2CSDA and SCL.)
>
>

-- 
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/4ed9a05f-3c26-4a9f-8894-a1690b735de1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] CANBUS

[Robert Nelson]

On Wed, Apr 4, 2018 at 2:31 PM,   wrote:
> Hi every one.
>
> I have a problem enabling the CAN BUS pins, I am following the instruccion
> of a tutorial, but in a part of this I have to check the file "SLOTS".
>
>
>  cat: '/sys/devices/platform/bone_capemgr/*slots': No such file or directory
>
> I don't know what I have to do.

Please run:

sudo /opt/scripts/tools/version.sh

and we will walk you thru it..

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/CAOCHtYhfJN%3DaPdF%2B6yGaAMuEvb-V6tGpS5UOKGHqaha%2BgTW1VQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] CANBUS

[alberto . caraveo23]

Hi every one.

I have a problem enabling the CAN BUS pins, I am following the instruccion 
of a tutorial, but in a part of this I have to check the file "SLOTS".


 cat: '/sys/devices/platform/bone_capemgr/*slots': No such file or directory

I don't know what I have to do.

Thanks

-- 
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/6c345cf6-3504-4339-b344-1395d5f07bcf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] I *still* can't get Debian 9 onto my BBB

[Robert Nelson]

On Wed, Apr 4, 2018 at 2:52 PM, Chris Green  wrote:
> Well I'm back at home off my boat now and I didn't manage to get
> Debian 9 onto my BBB there, it's still running Debian 7.
>
> I still have remote access to the BBB from here at home so, if anyone
> wants to help and needs answers to questions I can go and take a look.
>
> The Debian 9 image I was trying was this one (expanded of course) :-
>
> bone-debian-9.3-iot-armhf-2018-01-28-4gb.img.xz
>
>
> As noted in my previous postings here this image successfully
> self-installed automatically on another (I thought older) Debian 7 BBB
> that I had.
>
> When inserted in the BBB I want to update it did nothing on rebooting.
> I also tried powering up with the 'boot' button held down but that did
> no good either, it simply did nothing.
>
> I tried running the script:-
>
> /opt/scripts/tools/beaglebone-black-eMMC-flasher.sh
>
> and that didn't work either (as reported above in an earlier posting),
> it seems to have done something to the microSD which had Debian 9 on
> it too.
>
>
> So, how on earth am I going to get Debian 9 onto my BBB?  Surely there
> must be a reliable way to do this, especially as I have a running
> Debian system on it.  Is there a script I can get which can install an
> OS from an image on a microSD?  I'd really be happiest with a
> script/program I can load and run on my existing system rather than
> some sort of automatic load which requires a combination of buttons
> pressed and power-up sequences.
>
> What I need (help/information) is:-
>
> What Debian 9 image to use (minimal non-GUI system)
>
> How to write it to the microSD card (on a Linux system)
>
> A script to run that will install it on the eMMC.

With: bone-debian-9.3-iot-armhf-2018-01-28-4gb.img.xz booted on the microSD

Run:

sudo /opt/scripts/tools/eMMC/init-eMMC-flasher-v3.sh

It should "work", but there is a good reason we moved to flashing the
eMMC in single user mode...

So IF it fails, follow the standard eMMC flashing directions here:

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Flashing_eMMC

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

[beagleboard] Re: How to Autorun application at the start up in BeagleBone

[Chris Green]

santosh.aiw...@devtechm2m.com wrote:
> [-- multipart/alternative, encoding 7bit, 51 lines --]
> 
> [-- text/plain, encoding 7bit, charset: UTF-8, 16 lines --]
> 
> 
> 
>  I am using BBB with latest debian version 9.2.I want Autorun application 
> at the start up.
> firstly i am trying to crontab & systemd service it's working but not 
> showing debugged data on serial debug.  
> 
>  
> 
A basic method I use is to run things from /etc/rc.local.  Any program
called from /etc/rc.local will get run at system startup.

-- 
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/n6nfpe-u3n.ln1%40esprimo.zbmc.eu.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] I *still* can't get Debian 9 onto my BBB

[Chris Green]

Well I'm back at home off my boat now and I didn't manage to get
Debian 9 onto my BBB there, it's still running Debian 7.

I still have remote access to the BBB from here at home so, if anyone
wants to help and needs answers to questions I can go and take a look.

The Debian 9 image I was trying was this one (expanded of course) :-

bone-debian-9.3-iot-armhf-2018-01-28-4gb.img.xz


As noted in my previous postings here this image successfully
self-installed automatically on another (I thought older) Debian 7 BBB
that I had.

When inserted in the BBB I want to update it did nothing on rebooting.
I also tried powering up with the 'boot' button held down but that did
no good either, it simply did nothing.

I tried running the script:-

/opt/scripts/tools/beaglebone-black-eMMC-flasher.sh

and that didn't work either (as reported above in an earlier posting),
it seems to have done something to the microSD which had Debian 9 on
it too.


So, how on earth am I going to get Debian 9 onto my BBB?  Surely there
must be a reliable way to do this, especially as I have a running
Debian system on it.  Is there a script I can get which can install an
OS from an image on a microSD?  I'd really be happiest with a
script/program I can load and run on my existing system rather than
some sort of automatic load which requires a combination of buttons
pressed and power-up sequences.

What I need (help/information) is:-

What Debian 9 image to use (minimal non-GUI system)

How to write it to the microSD card (on a Linux system)

A script to run that will install it on the eMMC.

-- 
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/i1nfpe-u3n.ln1%40esprimo.zbmc.eu.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] RE: CE Certification for BB Black

[Gerald Coley]

Just glad it was stil there and had not been moved.

Gerald


From: Gary Beaver [mailto:gary.bea...@ghielectronics.com]
Sent: Wednesday, April 4, 2018 1:29 PM
To: Gerald Coley ; beagleboard@googlegroups.com; 
disc...@beagleboard.org
Cc: jkrid...@beagleboard.org
Subject: RE: CE Certification for BB Black

Thanks Gerald!

Regards,
Gary Beaver
Director of Operations
GHI Electronics, LLC
Where Hardware Meets Software
501 E. Whitcomb Ave
Madison Heights, MI  48071, USA
TEL: +1 (248) 397-8856
FAX: +1 (248) 397-8890
WEB: www.ghielectronics.com

Disclaimer: The information transmitted and any attachments are intended only 
for the person or entity
to which it is addressed and may contain confidential and/or privileged 
material. Any review, re-transmission,
dissemination or other use of, or taking of any action in reliance upon this 
information by persons or entities
other than the intended recipient is prohibited. If you are not the intended 
recipient and received this in
error, please contact the sender and delete the material from your system.

From: Gerald Coley >
Sent: Wednesday, April 4, 2018 2:25 PM
To: beagleboard@googlegroups.com; 
disc...@beagleboard.org
Cc: jkrid...@beagleboard.org; Gary Beaver 
>
Subject: RE: CE Certification for BB Black

Same place it has always been.

https://www.elinux.org/Beagleboard:BeagleBoneBlack#Regulatory_Compliance_Documents

Gerald

From: beagleboard@googlegroups.com 
[mailto:beagleboard@googlegroups.com] On Behalf Of Ashley Marinez
Sent: Wednesday, April 4, 2018 10:36 AM
To: disc...@beagleboard.org
Cc: jkrid...@beagleboard.org; Gary Beaver 
>
Subject: [beagleboard] CE Certification for BB Black

Hello,

May I please attain the CE Certification for the BeagleBone Black (p/n: 
BBB01-SC-505)?

Thank you,

Ashley Marinez | Product Specialist
MOUSER ELECTRONICS a TTI - Berkshire Hathaway Company
817-804-3704 Direct | www.mouser.com
The Newest Products for Your Newest Designs®

--
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/4d0f13b0790c4e26aed76c726320e133%40mouser.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/25a2ee3fa88248f1903abfad1ce19bde%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] RE: CE Certification for BB Black

[Gary Beaver]

Thanks Gerald!

Regards,
Gary Beaver
Director of Operations
GHI Electronics, LLC
Where Hardware Meets Software
501 E. Whitcomb Ave
Madison Heights, MI  48071, USA
TEL: +1 (248) 397-8856
FAX: +1 (248) 397-8890
WEB: www.ghielectronics.com

Disclaimer: The information transmitted and any attachments are intended only 
for the person or entity
to which it is addressed and may contain confidential and/or privileged 
material. Any review, re-transmission,
dissemination or other use of, or taking of any action in reliance upon this 
information by persons or entities
other than the intended recipient is prohibited. If you are not the intended 
recipient and received this in
error, please contact the sender and delete the material from your system.

From: Gerald Coley 
Sent: Wednesday, April 4, 2018 2:25 PM
To: beagleboard@googlegroups.com; disc...@beagleboard.org
Cc: jkrid...@beagleboard.org; Gary Beaver 
Subject: RE: CE Certification for BB Black

Same place it has always been.

https://www.elinux.org/Beagleboard:BeagleBoneBlack#Regulatory_Compliance_Documents

Gerald

From: beagleboard@googlegroups.com 
[mailto:beagleboard@googlegroups.com] On Behalf Of Ashley Marinez
Sent: Wednesday, April 4, 2018 10:36 AM
To: disc...@beagleboard.org
Cc: jkrid...@beagleboard.org; Gary Beaver 
>
Subject: [beagleboard] CE Certification for BB Black

Hello,

May I please attain the CE Certification for the BeagleBone Black (p/n: 
BBB01-SC-505)?

Thank you,

Ashley Marinez | Product Specialist
MOUSER ELECTRONICS a TTI - Berkshire Hathaway Company
817-804-3704 Direct | www.mouser.com
The Newest Products for Your Newest Designs®

--
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/4d0f13b0790c4e26aed76c726320e133%40mouser.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/DM6PR13MB2457A8400D15C74822BC6CE286A40%40DM6PR13MB2457.namprd13.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] RE: CE Certification for BB Black

[Gerald Coley]

Same place it has always been.

https://www.elinux.org/Beagleboard:BeagleBoneBlack#Regulatory_Compliance_Documents

Gerald

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Ashley Marinez
Sent: Wednesday, April 4, 2018 10:36 AM
To: disc...@beagleboard.org
Cc: jkrid...@beagleboard.org; Gary Beaver 
Subject: [beagleboard] CE Certification for BB Black

Hello,

May I please attain the CE Certification for the BeagleBone Black (p/n: 
BBB01-SC-505)?

Thank you,

Ashley Marinez | Product Specialist
MOUSER ELECTRONICS a TTI - Berkshire Hathaway Company
817-804-3704 Direct | www.mouser.com
The Newest Products for Your Newest Designs®

--
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/4d0f13b0790c4e26aed76c726320e133%40mouser.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/e912a06a959e47f782dc6ff2f1a2042c%40winhexbeus11.winus.mail.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] CE Certification for BB Black

[Ashley Marinez]

Hello,

May I please attain the CE Certification for the BeagleBone Black (p/n: 
BBB01-SC-505)?

Thank you,

Ashley Marinez | Product Specialist
MOUSER ELECTRONICS a TTI - Berkshire Hathaway Company
817-804-3704 Direct | www.mouser.com
The Newest Products for Your Newest Designs(r)

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

Re: [beagleboard] can't enable PRU with kernel 4.4.113-ti-r145

[Robert Nelson]

On Wed, Apr 4, 2018 at 12:35 PM, Sebastián Sáez  wrote:
> Thanks Robert for the script.
>
> If wifi is in 1-bit mode, does it affect its operation ?.

In theory it's be 25% as fast...

> I've already had problems with wifi and the beaglebone green wireless
> seeedstudio, I do not want to get worse.

Grab a newer image, it took a while to figure out all the bugs in the
bbgw hardware design..

> I think it's best to modify the 433 mhz tutorial script to use another PRU
> pin.

I would..

> In the tutorial (step 3) this is installed, will it be necessary?
> git: //github.com/beagleboard/am335x_pru_package

follow the tutorial...


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/CAOCHtYiXpZJhXxguh%3Dt0R6OyaeGqF02OmXw8fuLnUNL%2Bk%2BUg0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] can't enable PRU with kernel 4.4.113-ti-r145

[Sebastián Sáez]

Thanks Robert for the script.

If wifi is in 1-bit mode, does it affect its operation ?.
I've already had problems with wifi and the beaglebone green wireless 
seeedstudio, I do not want to get worse.

I think it's best to modify the 433 mhz tutorial script to use another PRU 
pin.

In the tutorial (step 3) this is installed, will it be necessary?
git: //github.com/beagleboard/am335x_pru_package



On Wednesday, April 4, 2018 at 2:17:17 PM UTC-3, RobertCNelson wrote:
>
> On Wed, Apr 4, 2018 at 12:13 PM, Robert Nelson  > wrote: 
> > On Wed, Apr 4, 2018 at 12:02 PM, Robert Nelson  > wrote: 
> >> On Wed, Apr 4, 2018 at 9:46 AM, Sebastián Sáez  > wrote: 
> >>> now config-pin p9.25 pruout it's working now but I need to use p8.11 
> as PRU 
> >>> 
>  root@beaglebone:~/rfsend# cat 
>  /sys/devices/platform/ocp/ocp\:P9_25_pinmux/state 
>  pruout 
> >>> 
> >>> 
> >>> how I can use p8.11 as PRU ? 
> >>> 
> >>> List of avaliable pins 
> >>> 
>  root@beaglebone:~/rfsend# cat /sys/devices/platform/ocp/ocp\: 
>  ocp:cape-universal/   ocp:P8_35_pinmux/ ocp:P9_16_pinmux/ 
>  ocp:l4_wkup@44c0/ ocp:P8_36_pinmux/ ocp:P9_17_pinmux/ 
>  ocp:P8_07_pinmux/ ocp:P8_37_pinmux/ ocp:P9_18_pinmux/ 
>  ocp:P8_08_pinmux/ ocp:P8_38_pinmux/ ocp:P9_19_pinmux/ 
>  ocp:P8_09_pinmux/ ocp:P8_39_pinmux/ ocp:P9_20_pinmux/ 
>  ocp:P8_10_pinmux/ ocp:P8_40_pinmux/ ocp:P9_21_pinmux/ 
>  ocp:P8_13_pinmux/ ocp:P8_41_pinmux/ ocp:P9_22_pinmux/ 
>  ocp:P8_19_pinmux/ ocp:P8_42_pinmux/ ocp:P9_23_pinmux/ 
>  ocp:P8_27_pinmux/ ocp:P8_43_pinmux/ ocp:P9_24_pinmux/ 
>  ocp:P8_28_pinmux/ ocp:P8_44_pinmux/ ocp:P9_25_pinmux/ 
>  ocp:P8_29_pinmux/ ocp:P8_45_pinmux/ ocp:P9_26_pinmux/ 
>  ocp:P8_30_pinmux/ ocp:P8_46_pinmux/ ocp:P9_27_pinmux/ 
>  ocp:P8_31_pinmux/ ocp:P9_11_pinmux/ ocp:P9_41_pinmux/ 
>  ocp:P8_32_pinmux/ ocp:P9_13_pinmux/ ocp:P9_42_pinmux/ 
>  ocp:P8_33_pinmux/ ocp:P9_14_pinmux/ ocp:P9_91_pinmux/ 
> >> 
> >> Okay firgured this out, you have the 
> >> "model:[TI_AM335x_BeagleBone_Green_Wireless]" 
> >> 
> >> You'll need to make a choice: 
> >> 
> >> PRU or WIFI... 
> >> 
> >> P8.11 is gpmc_ad13.mmc2_dat1 
> >> 
> >> 
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BBGW-WL1835-00A0.dts#L25
>  
> >> 
> >> You can kill wifi via: 
> >> 
> >> disable_uboot_overlay_wireless=1 
> >> 
> >> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
> > 
> > Correction, here's a hack (1), we can stick the wl18xx into 1 bit mode: 
> > 
> > debian@test-bbb-2:~$ cd /opt/source/bb.org-overlays/ 
> > debian@test-bbb-2:/opt/source/bb.org-overlays$ git pull 
> > debian@test-bbb-2:/opt/source/bb.org-overlays$ cp 
> > src/arm/BB-BBGW-WL1835-1BIT-00A0.dts src/arm/BB-BBGW-WL1835-00A0.dts 
> > debian@test-bbb-2:/opt/source/bb.org-overlays$ make 
> > debian@test-bbb-2:/opt/source/bb.org-overlays$ sudo make install 
> > 
> > 1: 
> https://github.com/beagleboard/bb.org-overlays/commit/093227e24835b73d95090fa4d0c17ea13ae322db
>  
>
> NM, this "BB-BBGW-WL1835-1BIT-00A0.d hack" will only work with 
> v4.16.0, which should be out in a few days.. 
>
> 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/db725572-9f2d-4e87-bbd2-48c37157f641%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] can't enable PRU with kernel 4.4.113-ti-r145

[Robert Nelson]

On Wed, Apr 4, 2018 at 12:13 PM, Robert Nelson  wrote:
> On Wed, Apr 4, 2018 at 12:02 PM, Robert Nelson  
> wrote:
>> On Wed, Apr 4, 2018 at 9:46 AM, Sebastián Sáez  wrote:
>>> now config-pin p9.25 pruout it's working now but I need to use p8.11 as PRU
>>>
 root@beaglebone:~/rfsend# cat
 /sys/devices/platform/ocp/ocp\:P9_25_pinmux/state
 pruout
>>>
>>>
>>> how I can use p8.11 as PRU ?
>>>
>>> List of avaliable pins
>>>
 root@beaglebone:~/rfsend# cat /sys/devices/platform/ocp/ocp\:
 ocp:cape-universal/   ocp:P8_35_pinmux/ ocp:P9_16_pinmux/
 ocp:l4_wkup@44c0/ ocp:P8_36_pinmux/ ocp:P9_17_pinmux/
 ocp:P8_07_pinmux/ ocp:P8_37_pinmux/ ocp:P9_18_pinmux/
 ocp:P8_08_pinmux/ ocp:P8_38_pinmux/ ocp:P9_19_pinmux/
 ocp:P8_09_pinmux/ ocp:P8_39_pinmux/ ocp:P9_20_pinmux/
 ocp:P8_10_pinmux/ ocp:P8_40_pinmux/ ocp:P9_21_pinmux/
 ocp:P8_13_pinmux/ ocp:P8_41_pinmux/ ocp:P9_22_pinmux/
 ocp:P8_19_pinmux/ ocp:P8_42_pinmux/ ocp:P9_23_pinmux/
 ocp:P8_27_pinmux/ ocp:P8_43_pinmux/ ocp:P9_24_pinmux/
 ocp:P8_28_pinmux/ ocp:P8_44_pinmux/ ocp:P9_25_pinmux/
 ocp:P8_29_pinmux/ ocp:P8_45_pinmux/ ocp:P9_26_pinmux/
 ocp:P8_30_pinmux/ ocp:P8_46_pinmux/ ocp:P9_27_pinmux/
 ocp:P8_31_pinmux/ ocp:P9_11_pinmux/ ocp:P9_41_pinmux/
 ocp:P8_32_pinmux/ ocp:P9_13_pinmux/ ocp:P9_42_pinmux/
 ocp:P8_33_pinmux/ ocp:P9_14_pinmux/ ocp:P9_91_pinmux/
>>
>> Okay firgured this out, you have the
>> "model:[TI_AM335x_BeagleBone_Green_Wireless]"
>>
>> You'll need to make a choice:
>>
>> PRU or WIFI...
>>
>> P8.11 is gpmc_ad13.mmc2_dat1
>>
>> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BBGW-WL1835-00A0.dts#L25
>>
>> You can kill wifi via:
>>
>> disable_uboot_overlay_wireless=1
>>
>> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
>
> Correction, here's a hack (1), we can stick the wl18xx into 1 bit mode:
>
> debian@test-bbb-2:~$ cd /opt/source/bb.org-overlays/
> debian@test-bbb-2:/opt/source/bb.org-overlays$ git pull
> debian@test-bbb-2:/opt/source/bb.org-overlays$ cp
> src/arm/BB-BBGW-WL1835-1BIT-00A0.dts src/arm/BB-BBGW-WL1835-00A0.dts
> debian@test-bbb-2:/opt/source/bb.org-overlays$ make
> debian@test-bbb-2:/opt/source/bb.org-overlays$ sudo make install
>
> 1: 
> https://github.com/beagleboard/bb.org-overlays/commit/093227e24835b73d95090fa4d0c17ea13ae322db

NM, this "BB-BBGW-WL1835-1BIT-00A0.d hack" will only work with
v4.16.0, which should be out in a few days..

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

Re: [beagleboard] can't enable PRU with kernel 4.4.113-ti-r145

[Robert Nelson]

On Wed, Apr 4, 2018 at 12:02 PM, Robert Nelson  wrote:
> On Wed, Apr 4, 2018 at 9:46 AM, Sebastián Sáez  wrote:
>> now config-pin p9.25 pruout it's working now but I need to use p8.11 as PRU
>>
>>> root@beaglebone:~/rfsend# cat
>>> /sys/devices/platform/ocp/ocp\:P9_25_pinmux/state
>>> pruout
>>
>>
>> how I can use p8.11 as PRU ?
>>
>> List of avaliable pins
>>
>>> root@beaglebone:~/rfsend# cat /sys/devices/platform/ocp/ocp\:
>>> ocp:cape-universal/   ocp:P8_35_pinmux/ ocp:P9_16_pinmux/
>>> ocp:l4_wkup@44c0/ ocp:P8_36_pinmux/ ocp:P9_17_pinmux/
>>> ocp:P8_07_pinmux/ ocp:P8_37_pinmux/ ocp:P9_18_pinmux/
>>> ocp:P8_08_pinmux/ ocp:P8_38_pinmux/ ocp:P9_19_pinmux/
>>> ocp:P8_09_pinmux/ ocp:P8_39_pinmux/ ocp:P9_20_pinmux/
>>> ocp:P8_10_pinmux/ ocp:P8_40_pinmux/ ocp:P9_21_pinmux/
>>> ocp:P8_13_pinmux/ ocp:P8_41_pinmux/ ocp:P9_22_pinmux/
>>> ocp:P8_19_pinmux/ ocp:P8_42_pinmux/ ocp:P9_23_pinmux/
>>> ocp:P8_27_pinmux/ ocp:P8_43_pinmux/ ocp:P9_24_pinmux/
>>> ocp:P8_28_pinmux/ ocp:P8_44_pinmux/ ocp:P9_25_pinmux/
>>> ocp:P8_29_pinmux/ ocp:P8_45_pinmux/ ocp:P9_26_pinmux/
>>> ocp:P8_30_pinmux/ ocp:P8_46_pinmux/ ocp:P9_27_pinmux/
>>> ocp:P8_31_pinmux/ ocp:P9_11_pinmux/ ocp:P9_41_pinmux/
>>> ocp:P8_32_pinmux/ ocp:P9_13_pinmux/ ocp:P9_42_pinmux/
>>> ocp:P8_33_pinmux/ ocp:P9_14_pinmux/ ocp:P9_91_pinmux/
>
> Okay firgured this out, you have the
> "model:[TI_AM335x_BeagleBone_Green_Wireless]"
>
> You'll need to make a choice:
>
> PRU or WIFI...
>
> P8.11 is gpmc_ad13.mmc2_dat1
>
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BBGW-WL1835-00A0.dts#L25
>
> You can kill wifi via:
>
> disable_uboot_overlay_wireless=1
>
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

Correction, here's a hack (1), we can stick the wl18xx into 1 bit mode:

debian@test-bbb-2:~$ cd /opt/source/bb.org-overlays/
debian@test-bbb-2:/opt/source/bb.org-overlays$ git pull
debian@test-bbb-2:/opt/source/bb.org-overlays$ cp
src/arm/BB-BBGW-WL1835-1BIT-00A0.dts src/arm/BB-BBGW-WL1835-00A0.dts
debian@test-bbb-2:/opt/source/bb.org-overlays$ make
debian@test-bbb-2:/opt/source/bb.org-overlays$ sudo make install


1: 
https://github.com/beagleboard/bb.org-overlays/commit/093227e24835b73d95090fa4d0c17ea13ae322db

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/CAOCHtYgTM%2BJ2M%3DY2VRAHV8kJeUN-KpG49COE1cdijny5fy1kLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] can't enable PRU with kernel 4.4.113-ti-r145

[Robert Nelson]

On Wed, Apr 4, 2018 at 9:46 AM, Sebastián Sáez  wrote:
> now config-pin p9.25 pruout it's working now but I need to use p8.11 as PRU
>
>> root@beaglebone:~/rfsend# cat
>> /sys/devices/platform/ocp/ocp\:P9_25_pinmux/state
>> pruout
>
>
> how I can use p8.11 as PRU ?
>
> List of avaliable pins
>
>> root@beaglebone:~/rfsend# cat /sys/devices/platform/ocp/ocp\:
>> ocp:cape-universal/   ocp:P8_35_pinmux/ ocp:P9_16_pinmux/
>> ocp:l4_wkup@44c0/ ocp:P8_36_pinmux/ ocp:P9_17_pinmux/
>> ocp:P8_07_pinmux/ ocp:P8_37_pinmux/ ocp:P9_18_pinmux/
>> ocp:P8_08_pinmux/ ocp:P8_38_pinmux/ ocp:P9_19_pinmux/
>> ocp:P8_09_pinmux/ ocp:P8_39_pinmux/ ocp:P9_20_pinmux/
>> ocp:P8_10_pinmux/ ocp:P8_40_pinmux/ ocp:P9_21_pinmux/
>> ocp:P8_13_pinmux/ ocp:P8_41_pinmux/ ocp:P9_22_pinmux/
>> ocp:P8_19_pinmux/ ocp:P8_42_pinmux/ ocp:P9_23_pinmux/
>> ocp:P8_27_pinmux/ ocp:P8_43_pinmux/ ocp:P9_24_pinmux/
>> ocp:P8_28_pinmux/ ocp:P8_44_pinmux/ ocp:P9_25_pinmux/
>> ocp:P8_29_pinmux/ ocp:P8_45_pinmux/ ocp:P9_26_pinmux/
>> ocp:P8_30_pinmux/ ocp:P8_46_pinmux/ ocp:P9_27_pinmux/
>> ocp:P8_31_pinmux/ ocp:P9_11_pinmux/ ocp:P9_41_pinmux/
>> ocp:P8_32_pinmux/ ocp:P9_13_pinmux/ ocp:P9_42_pinmux/
>> ocp:P8_33_pinmux/ ocp:P9_14_pinmux/ ocp:P9_91_pinmux/

Okay firgured this out, you have the
"model:[TI_AM335x_BeagleBone_Green_Wireless]"

You'll need to make a choice:

PRU or WIFI...

P8.11 is gpmc_ad13.mmc2_dat1

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-BBGW-WL1835-00A0.dts#L25

You can kill wifi via:

disable_uboot_overlay_wireless=1

https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

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/CAOCHtYhU2QnnO_vR-rDbOMU2%2BS3Cb__4%3DSdTV7tAE1JU3FsQcQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: SD card errors on hard reboot

[evilwulfie]

you cannot just do a hard shutdown you must use a shutdown now command
you always risk file system corruption if you do not

On 4/4/2018 8:24 AM, Tarmo Kuuse wrote:
> On Monday, 19 March 2018 23:55:04 UTC+2, Troy Weber wrote:
>
> Hello!
>
> I have an application running on the Beaglebone Black. It runs
> from the eMMC because we need to mount a blank SD card and
> occasionally store data or video on the external SD card. Here are
> some details to jog ideas:
>
>   * using a Bealgebone black
>   * connected to a powered hub and running 2 led strips and 1 camera
>   * made a custom cape/shield that allows us to interface with
>   o an RGB button
>   o a 16x2 char lcd
>   o an optically isolated relay module
>   * the relay module runs a solenoid circuit (in which I'm
> currently debugging the need for a flyback diode)
>   * the SD card is mounted using */etc/fstab* with the line
> */dev/mmcblk0p1 /media/sd auto
> auto,nofail,user,dmask=022,fmask=111 0 0*
>   * SD cards are inexpensive and found
> here: 
> https://www.amazon.com/gp/product/B00WUCNGVQ/ref=oh_aui_search_detailpage?ie=UTF8=1
> 
> 
>
> My application is writing files to the SD card only on certain
> occasions during which the Beaglebone will not be hard-rebooted.
> However, it will be hard-rebooted (and the application started by
> systemd on next boot) as a means of shutting it down.
>
> The problem is that I've recently began to discover issues with
> the blank SD card on next boot after a hard reboot. For a short
> time I can *touch* and write *vim* files on the card just fine.
> Once I start up the node.js program, part way through it complains
> about the SD card being read-only. From then on I cannot
> *touch* or *vim* files anymore. So I reformat the card and copy
> the configuration files back on. I've noticed that one of my
> configuration files is chopped short.
>
> Here are some things I've tried and intend to try:
>
>   * have tried
>   o removing the power to the hub which seemed to be
> back-powering the BBB (still fails on reboot)
>   o stopping the program that writes files entirely (still
> fails on reboot)
>   * intend to try
>   o writing the configuration files elsewhere (on the eMMC for
> example)
>   o better SD cards
>
> In the meantime, any ideas?
>
>
> What's the file system on the SD card? FAT? ext4?
>
> --
> Tarmo
> -- 
> 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/ea6a9f55-220d-40c0-8781-5dfffee87178%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/46947563-9e92-ca7e-a0ce-094b6e449db2%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: SD card errors on hard reboot

[Tarmo Kuuse]

On Monday, 19 March 2018 23:55:04 UTC+2, Troy Weber wrote:
>
> Hello!
>
> I have an application running on the Beaglebone Black. It runs from the 
> eMMC because we need to mount a blank SD card and occasionally store data 
> or video on the external SD card. Here are some details to jog ideas:
>
>- using a Bealgebone black
>- connected to a powered hub and running 2 led strips and 1 camera
>- made a custom cape/shield that allows us to interface with
>   - an RGB button
>   - a 16x2 char lcd
>   - an optically isolated relay module
>- the relay module runs a solenoid circuit (in which I'm currently 
>debugging the need for a flyback diode)
>- the SD card is mounted using */etc/fstab* with the line */dev/mmcblk0p1 
>/media/sd auto auto,nofail,user,dmask=022,fmask=111 0 0*
>- SD cards are inexpensive and found here: 
>
> https://www.amazon.com/gp/product/B00WUCNGVQ/ref=oh_aui_search_detailpage?ie=UTF8=1
>
> My application is writing files to the SD card only on certain occasions 
> during which the Beaglebone will not be hard-rebooted. However, it will be 
> hard-rebooted (and the application started by systemd on next boot) as a 
> means of shutting it down.
>
> The problem is that I've recently began to discover issues with the blank 
> SD card on next boot after a hard reboot. For a short time I can *touch* 
> and write *vim* files on the card just fine. Once I start up the node.js 
> program, part way through it complains about the SD card being read-only. 
> From then on I cannot *touch* or *vim* files anymore. So I reformat the 
> card and copy the configuration files back on. I've noticed that one of my 
> configuration files is chopped short.
>
> Here are some things I've tried and intend to try:
>
>- have tried
>   - removing the power to the hub which seemed to be back-powering 
>   the BBB (still fails on reboot)
>   - stopping the program that writes files entirely (still fails on 
>   reboot)
>- intend to try
>   - writing the configuration files elsewhere (on the eMMC for 
>   example)
>   - better SD cards
>
> In the meantime, any ideas?
>

What's the file system on the SD card? FAT? ext4?

--
Tarmo

-- 
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/ea6a9f55-220d-40c0-8781-5dfffee87178%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: I2C process call

[Graham]

Zeegee:

There is nothing at the hardware level that is uniquely required by the 
"Process Call" transaction.

You might have to hack into the low level I2C driver to implement it.

It looks like a simple 2 byte write followed by a restart and a two byte 
read in a single transaction.

Most I2C chips would properly respond to a 2 byte write transaction, 
followed by a two byte read transaction, which could be implemented, if you 
can stand the extra overhead of two shorter transactions.


I would recommend migrating off of Angstrom, if you can, since I don't 
think it is supported any longer on the BBB.

--- Graham

==




On Wednesday, April 4, 2018 at 2:05:03 AM UTC-5, ZG wrote:
>
> Hi All,
>
> I am using a beaglebone black and a custom board based off it.
>
> On the BBB, I am running Debian Linux 7 (Linux 3.8-13)
>
> On the custom board, I am running Angstrom distribution.
>
>
> On both boards, when I run *i2cdetect -F 2*, they give the same results, 
> as below:
>
> Functionalities implemented by /dev/i2c-2:
>
> I2C  yes
>
> SMBus Quick Command  no
>
> SMBus Send Byte  yes
>
> SMBus Receive Byte   yes
>
> SMBus Write Byte yes
>
> SMBus Read Byte  yes
>
> SMBus Write Word yes
>
> SMBus Read Word  yes
>
> SMBus Process Call   yes
>
> SMBus Block Writeyes
>
> SMBus Block Read no
>
> SMBus Block Process Call no
>
> SMBus PECyes
>
> I2C Block Write  yes
>
> I2C Block Read   yes
>
>  
>
> I REALLY need to use the PROCESS_CALL functionality of the I2C.
>
>
> The question is: does the PROCESS_CALL functionality rely on the hardware? 
>
> if it is just software, any patches or drivers I could use so I could 
> support it on my hardware? 
>
> I have searched the web with regard to this, but have not found any 
> answers.
>
> I am hoping this community would be able to help.
>
>
> Thanks in advance,
>
> Zeegee
>

-- 
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/5ed9a80d-3596-4678-9eaf-ae48545933e9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] can't enable PRU with kernel 4.4.113-ti-r145

[Sebastián Sáez]

now config-pin p9.25 pruout it's working now but I need to use p8.11 as PRU

root@beaglebone:~/rfsend# cat 
> /sys/devices/platform/ocp/ocp\:P9_25_pinmux/state
> pruout


how I can use p8.11 as PRU ?

List of avaliable pins

root@beaglebone:~/rfsend# cat /sys/devices/platform/ocp/ocp\:
> ocp:cape-universal/   ocp:P8_35_pinmux/ ocp:P9_16_pinmux/
> ocp:l4_wkup@44c0/ ocp:P8_36_pinmux/ ocp:P9_17_pinmux/
> ocp:P8_07_pinmux/ ocp:P8_37_pinmux/ ocp:P9_18_pinmux/
> ocp:P8_08_pinmux/ ocp:P8_38_pinmux/ ocp:P9_19_pinmux/
> ocp:P8_09_pinmux/ ocp:P8_39_pinmux/ ocp:P9_20_pinmux/
> ocp:P8_10_pinmux/ ocp:P8_40_pinmux/ ocp:P9_21_pinmux/
> ocp:P8_13_pinmux/ ocp:P8_41_pinmux/ ocp:P9_22_pinmux/
> ocp:P8_19_pinmux/ ocp:P8_42_pinmux/ ocp:P9_23_pinmux/
> ocp:P8_27_pinmux/ ocp:P8_43_pinmux/ ocp:P9_24_pinmux/
> ocp:P8_28_pinmux/ ocp:P8_44_pinmux/ ocp:P9_25_pinmux/
> ocp:P8_29_pinmux/ ocp:P8_45_pinmux/ ocp:P9_26_pinmux/
> ocp:P8_30_pinmux/ ocp:P8_46_pinmux/ ocp:P9_27_pinmux/
> ocp:P8_31_pinmux/ ocp:P9_11_pinmux/ ocp:P9_41_pinmux/
> ocp:P8_32_pinmux/ ocp:P9_13_pinmux/ ocp:P9_42_pinmux/
> ocp:P8_33_pinmux/ ocp:P9_14_pinmux/ ocp:P9_91_pinmux/




On Tuesday, April 3, 2018 at 8:38:22 PM UTC-3, Sebastián Sáez wrote:
>
> I burn a new microSD card with the same image and now the linux it's boot
>>
>> bone-debian-8.10-seeed-iot-armhf-2018-02-01-4gb.img
>
>
> Try again and now this is the otuput
>  
>
>> config-pin p8.11 pruout
>
> P8_11 pinmux file not found!
>> bash: /sys/devices/platform/ocp/ocp*P8_11_pinmux/state: No such file or 
>> directory
>> Cannot write pinmux file: /sys/devices/platform/ocp/ocp*P8_11_pinmux/state
>
>
> here the new sytem info
>
> sudo /opt/scripts/tools/version.sh
>> git:/opt/scripts/:[ad016da40de5805f1a6f981cbb6c454b1a7f244b]
>> eeprom:[A335BNLTGW1ABBGW16050761]
>> model:[TI_AM335x_BeagleBone_Green_Wireless]
>> dogtag:[BeagleBoard.org Debian Image 2018-02-01]
>> bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 
>> 2018.01-2-g9aa111a004]
>> kernel:[4.4.113-ti-r145]
>> nodejs:[v0.12.18]
>> uboot_overlay_options:[enable_uboot_overlays=1]
>>
>> uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo]
>> uboot_overlay_options:[enable_uboot_cape_universal=1]
>> pkg:[bb-cape-overlays]:[4.4.20180126.0-0rcnee0~jessie+20180126]
>> pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee2~jessie+20180104]
>> pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~jessie+20170830]
>> groups:[debian : debian adm kmem dialout cdrom floppy audio dip video 
>> plugdev users systemd-journal netdev i2c bluetooth cloud9ide gpio pwm eqep 
>> admin spi tisdk weston-launch xenomai]
>> dmesg | grep pinctrl-single
>> [1.212781] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 
>> size 568
>> dmesg | grep gpio-of-helper
>> [1.213903] gpio-of-helper ocp:cape-universal: Allocated GPIO id=0
>> [1.214074] gpio-of-helper ocp:cape-universal: Allocated GPIO id=1
>> [1.214218] gpio-of-helper ocp:cape-universal: Allocated GPIO id=2
>> [1.214357] gpio-of-helper ocp:cape-universal: Allocated GPIO id=3
>> [1.214497] gpio-of-helper ocp:cape-universal: Allocated GPIO id=4
>> [1.214630] gpio-of-helper ocp:cape-universal: Allocated GPIO id=5
>> [1.214762] gpio-of-helper ocp:cape-universal: Allocated GPIO id=6
>> [1.214902] gpio-of-helper ocp:cape-universal: Allocated GPIO id=7
>> [1.215048] gpio-of-helper ocp:cape-universal: Allocated GPIO id=8
>> [1.215192] gpio-of-helper ocp:cape-universal: Allocated GPIO id=9
>> [1.215327] gpio-of-helper ocp:cape-universal: Allocated GPIO id=10
>> [1.215466] gpio-of-helper ocp:cape-universal: Allocated GPIO id=11
>> [1.215609] gpio-of-helper ocp:cape-universal: Allocated GPIO id=12
>> [1.215746] gpio-of-helper ocp:cape-universal: Allocated GPIO id=13
>> [1.215882] gpio-of-helper ocp:cape-universal: Allocated GPIO id=14
>> [1.216023] gpio-of-helper ocp:cape-universal: Allocated GPIO id=15
>> [1.216634] gpio-of-helper ocp:cape-universal: Allocated GPIO id=16
>> [1.216813] gpio-of-helper ocp:cape-universal: Allocated GPIO id=17
>> [1.217031] gpio-of-helper ocp:cape-universal: Allocated GPIO id=18
>> [1.217194] gpio-of-helper ocp:cape-universal: Allocated GPIO id=19
>> [1.217341] gpio-of-helper ocp:cape-universal: Allocated GPIO id=20
>> [1.217481] gpio-of-helper ocp:cape-universal: Allocated GPIO id=21
>> [1.217619] gpio-of-helper ocp:cape-universal: Allocated GPIO id=22
>> [1.217763] gpio-of-helper ocp:cape-universal: Allocated GPIO id=23
>> [1.217902] gpio-of-helper ocp:cape-universal: Allocated GPIO id=24
>> [1.218040] gpio-of-helper ocp:cape-universal: Allocated GPIO id=25
>> [1.218193] gpio-of-helper ocp:cape-universal: Allocated GPIO id=26
>> [1.218338] gpio-of-helper ocp:cape-universal: Allocated GPIO id=27
>> [1.218486] gpio-of-helper ocp:cape-universal: 

[beagleboard] Re: kernel 4.16.0-rc7-bone7 boot hangs

[Robert Nelson]

On Tue, Apr 3, 2018 at 4:27 PM, Robert Nelson  wrote:
> On Sun, Apr 1, 2018 at 1:51 AM, Drew Fustini  wrote:
>> fyi - kernel 4.16.0-rc6-bone7 does work OK.  It is just the
>> 4.16.0-rc7-bone7 kernel that hangs.
>>
>> On Sun, Apr 1, 2018 at 12:22 AM, Drew Fustini  wrote:
>>> Robert -
>>>
>>> I'm using a BeagleBone Black Rev C running Stretch IoT 2018-03-25 SD
>>> card image.  Kernel 4.16.0-rc2-bone3 boots OK.
>>>
>>> I recently updated to the latest mainline rc kernel with:
>>>
>>> /opt/scripts/tools/update_kernel.sh --exp-kernel --bone-kernel
>>>
>>> However, boot of 4.16.0-rc7-bone7 kernel hangs after "Starting kernel ..."
>>>
>>> Full serial console output:
>>> https://gist.github.com/pdp7/3d49624f182cd28a3b3a72dbbd7aa493
>>>
>>> Any idea?
>
> This looks like a fun one..
>
> First git bisect run, lead to a false positive.
>
> Here goes run #2. ;)

Okay got this sucker..

voodoo@hades:/opt/github/4.16.x/bb-kernel/KERNEL$ git bisect log
git bisect start
# good: [c698ca5278934c0ae32297a8725ced2e27585d7f] Linux 4.16-rc6
git bisect good c698ca5278934c0ae32297a8725ced2e27585d7f
# bad: [3eb2ce825ea1ad89d20f7a3b5780df850e4be274] Linux 4.16-rc7
git bisect bad 3eb2ce825ea1ad89d20f7a3b5780df850e4be274
# good: [40013ff20b1beed31184935fc0aea6a859d4d4ef] net: dsa: Fix
functional dsa-loop dependency on FIXED_PHY
git bisect good 40013ff20b1beed31184935fc0aea6a859d4d4ef
# bad: [9ec7ccc8f4f89843991cf692e89fc1fcbca85c83] Merge tag
'drm-fixes-for-v4.16-rc7' of
git://people.freedesktop.org/~airlied/linux
git bisect bad 9ec7ccc8f4f89843991cf692e89fc1fcbca85c83
# bad: [3215b9d57a2c75c4305a3956ca303d7004485200] Merge tag
'clk-fixes-for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/clk/linux
git bisect bad 3215b9d57a2c75c4305a3956ca303d7004485200
# good: [645102eac15eaeb3da79576a9f8816d6e66cec0d] Merge tag
'nfsd-4.16-1' of git://linux-nfs.org/~bfields/linux
git bisect good 645102eac15eaeb3da79576a9f8816d6e66cec0d
# bad: [49012d1bf5f78782d398adb984a080a88ba42965] clk: bcm2835: Fix
ana->maskX definitions
git bisect bad 49012d1bf5f78782d398adb984a080a88ba42965
# bad: [bd13c6cbd3c07f5d69a8b79b5b359c7d417d311a] Merge tag
'ti-clk-fixes-4.16' of https://github.com/t-kristo/linux-pm into
clk-fixes
git bisect bad bd13c6cbd3c07f5d69a8b79b5b359c7d417d311a
# good: [a88bb86d58ceb785d86db2b77a613a04ae2366f2] Merge tag
'clk-imx-fixes-4.16' of
git://git.kernel.org/pub/scm/linux/kernel/git/shawnguo/linux into
clk-fixes
git bisect good a88bb86d58ceb785d86db2b77a613a04ae2366f2
# bad: [c083dc5f3738d394223baa0f90705397b0844acd] clk: ti: am33xx: add
set-rate-parent support for display clkctrl clock
git bisect bad c083dc5f3738d394223baa0f90705397b0844acd
# good: [49159a9dc3da83f17be00acbc7b2ab84ffec1aa7] clk: ti: clkctrl:
add support for CLK_SET_RATE_PARENT flag
git bisect good 49159a9dc3da83f17be00acbc7b2ab84ffec1aa7
# first bad commit: [c083dc5f3738d394223baa0f90705397b0844acd] clk:
ti: am33xx: add set-rate-parent support for display clkctrl clock


https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c083dc5f3738d394223baa0f90705397b0844acd

now boots, pushing out 4.16.0 final shortly..

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/CAOCHtYj7SJC3TP2w%2BU0sJCn4Q8zWye_y%2Bw%3DYf9_N%2BHwf3Vqm-w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] pocket beagle not clean shutdown?

[beatbieler]

The problem seems to be, that the rtc has no active oscillator:
If I set RTC_OSC_REG to 0x40 (internal oscillator) shutdown works normal.
But I'm not sure whether this is the correct way to solve this issue.

Regards
Beat Bieler

-- 
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/636b5aa5-a2fb-4360-ab6e-32b3da29c9f3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Schematic

[Robert Nelson]

On Wed, Apr 4, 2018 at 6:30 AM, Gerald Coley  wrote:
> 1) The TPS65217D came out after the initial design was done.
>
>
>
> 2) The DDR3L can run at 1.5V without issue.
>
>
>
> 3) The SW can set the voltage to 1.35V after power up.

Side note, while u-boot and the kernel support changing the pmic
voltage.  We dropped this during 3.14.x or the 3.18.x cycle in the
default kernel device-tree, as there is no memory "checker" in
u-boot/kernel to verify the "contents" in memory where still "valid"
after the down-scaling.  (i believe some random corruption was
actually seen on a am4x based board, so all am3x/am4x )

So if you do swap in the TPS65217D and want to run it at 1.35 to save
power, make sure you patch both u-boot and kernel.  The voltage must
be set to 1.35 in u-boot SPL during ram init.  (and patch the kernel
device tree to not set the 1.5v level)..

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

[beagleboard] How to Autorun application at the start up in BeagleBone

[santosh . aiwale]

 I am using BBB with latest debian version 9.2.I want Autorun application 
at the start up.
firstly i am trying to crontab & systemd service it's working but not 
showing debugged data on serial debug.  


-- 
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/37c2eb81-9705-41da-9e78-1cad03576d1c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Schematic

[shelby . teknologies]

I was looking at the schematic and noticed two things.

1) They are using the TPS65217C PMIC
2) The DDR3L is based on a 1.35 power source

Why are you not using the TPS65217D and applying the right power to the 
DDR3L?

-- 
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/a4853a75-4024-49d0-8fa8-cb35a512feb9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Help! Beaglebone Blue seems to have died

[jesusandallhisdisciples]

My BBB no longer works from the barrel jack; I plugged it into a 12V 
switching power supply and the smoke escaped (see picture). It still runs 
from a 2S LIPO.



>
>
>
>

-- 
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/417a5c74-6b3b-4707-b57c-3342535ea327%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Enabling SPI in BBB, Debian Stretch

[Jon Lundstrom]

Thanks again, Robert,

The display now works and I've been able to loop the SPI back to the BBB.

I'm grateful for your help,
/Jon.

Den tisdag 3 april 2018 kl. 17:32:17 UTC+2 skrev RobertCNelson:
>
> On Tue, Apr 3, 2018 at 10:26 AM, Jon Lundstrom  > wrote: 
> > 
> > Thank you Robert, 
> > 
> > That did the trick. 
> > 
> > However, it has the side-effect of turning my display all black. 
> > I use a Newhaven display cape and according to its User Guide, there 
> should 
> > be no conflict for these SPI-pins. 
> > (
> http://www.newhavendisplay.com/userguides/NHD-7.0CTP-CAPE_User_Guide.pdf) 
> > 
> > So I had a look at the assigned pins in 
> > /sys/kernel/debug/pinctrl/44e10800.pinmux/pingroups and see that 
> following 
> > group is added (using diff): 
> > 
> >> group: pinmux_bb_spi0_pins 
> >> pin 84 (PIN84) 
> >> pin 85 (PIN85) 
> >> pin 86 (PIN86) 
> >> pin 87 (PIN87) 
> > 
> > which seems in order, but following groups were removed: 
> > 
> > < group: pinmux_bb_lcd_pwm_backlight_pins 
> > < pin 18 (PIN18) 
> > 
> > < group: pinmux_bb_lcd_lcd_pins 
> > < pin 40 (PIN40) 
> > < pin 41 (PIN41) 
> > < pin 42 (PIN42) 
> > < pin 43 (PIN43) 
> > < pin 44 (PIN44) 
> > < pin 45 (PIN45) 
> > < pin 46 (PIN46) 
> > < pin 47 (PIN47) 
> > < pin 48 (PIN48) 
> > < pin 49 (PIN49) 
> > < pin 50 (PIN50) 
> > < pin 51 (PIN51) 
> > < pin 52 (PIN52) 
> > < pin 53 (PIN53) 
> > < pin 54 (PIN54) 
> > < pin 55 (PIN55) 
> > < pin 15 (PIN15) 
> > < pin 14 (PIN14) 
> > < pin 13 (PIN13) 
> > < pin 12 (PIN12) 
> > < pin 11 (PIN11) 
> > < pin 10 (PIN10) 
> > < pin 9 (PIN9) 
> > < pin 8 (PIN8) 
> > < pin 56 (PIN56) 
> > < pin 57 (PIN57) 
> > < pin 58 (PIN58) 
> > < pin 59 (PIN59) 
> > < pin 35 (PIN35) 
> > 
> > < group: pinmux_edt_ft5x06_pins 
> > < pin 105 (PIN105) 
> > 
> > I don't know about the last group (PIN105) but the other two groups most 
> > certainly affect the display function. 
> > 
> > I haven't seen the corresponding .dts-file for BB-SPIDEV0-00A0.dtbo, but 
> I 
> > tried making my own that should not touch these pins: Still, the same 
> result 
> > (same pin groups are removed). 
> > 
> > There seems to be some mechanism that disables the display pins when 
> adding 
> > an overlay to the uEnv.txt. 
> > 
> > Robert, as an expert in BBB, do you have answer to this? 
>
> Well, addr0 -> addr3 is for eeprom detected capes, so change: 
>
> uboot_overlay_addr0=/lib/firmware/BB-SPIDEV0-00A0.dtbo 
>
> to 
>
> uboot_overlay_addr4=/lib/firmware/BB-SPIDEV0-00A0.dtbo 
>
> https://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays 
>
> 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/d5721165-7051-4370-ae86-f0ddc0644191%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] I2C process call

[Francis]

Hi All,

I am using a beaglebone black and a custom board based off it.

On the BBB, I am running Debian Linux 7 (Linux 3.8-13)

On the custom board, I am running Angstrom distribution.


On both boards, when I run *i2cdetect -F 2*, they give the same results, as 
below:

Functionalities implemented by /dev/i2c-2:

I2C  yes

SMBus Quick Command  no

SMBus Send Byte  yes

SMBus Receive Byte   yes

SMBus Write Byte yes

SMBus Read Byte  yes

SMBus Write Word yes

SMBus Read Word  yes

SMBus Process Call   yes

SMBus Block Writeyes

SMBus Block Read no

SMBus Block Process Call no

SMBus PECyes

I2C Block Write  yes

I2C Block Read   yes

 

I REALLY need to use the PROCESS_CALL functionality of the I2C.


The question is: does the PROCESS_CALL functionality rely on the hardware? 

if it is just software, any patches or drivers I could use so I could 
support it on my hardware? 

I have searched the web with regard to this, but have not found any answers.

I am hoping this community would be able to help.


Thanks in advance,

Zeegee

-- 
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/f79c54d7-867c-48f1-b4e1-e7efb50a92fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.