Re: [beagleboard] Power Management - Suspend

[Robert Nelson]

On Fri, Jan 16, 2015 at 10:35 PM, Robert Fisher  wrote:
> Hi all.
>
> I have been trying to find a way to put my BBB into a suspend or sleep
> state.  I found out that power management was not incorporated into the 3.8
> kernel, however several posts suggested that it would be working in later
> kernel (3.14+).  I have installed several versions of 3.14 through 3.18 and
> still have not been able to find one that will allow me to enter a suspend
> mode.
>
> On some versions I could issue "echo 'mem' > /sys/power/state" and nothing
> would happen.  On 3.18 with Debian, I receive "Permission denied".  I've
> seen a few posts about recompiling firmware from TI with custom cape
> configurations.  Unfortunately this is a bit over my head at the moment.

Well, this is a feature that is currently "only" in the 3.14.x-ti kernel:

sudo apt-get update
sudo apt-get install linux-image-3.14.26-ti-r44
sudo reboot

Based on patch status, it "should" enter mainline during v3.20-rcX (so
the next kernel merge cycle)

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Power Management - Suspend

[Robert Fisher]

Hi all.

I have been trying to find a way to put my BBB into a suspend or sleep 
state.  I found out that power management was not incorporated into the 3.8 
kernel, however several posts suggested that it would be working in later 
kernel (3.14+).  I have installed several versions of 3.14 through 3.18 and 
still have not been able to find one that will allow me to enter a suspend 
mode.

On some versions I could issue "echo 'mem' > /sys/power/state" and nothing 
would happen.  On 3.18 with Debian, I receive "Permission denied".  I've 
seen a few posts about recompiling firmware from TI with custom cape 
configurations.  Unfortunately this is a bit over my head at the moment.

I was hoping someone had some experience with this and could provide a 
step-by-step for how to get it working.  If we could make this more 
straightforward for the BBB community, I think we would see an increase in 
the number of people using BBBs for battery-powered applications.

Thanks in advance!

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

Re: [beagleboard] 2gb image for 4gb BBB?

[William Hermans]

Anyway, I think it is commendable that people like Robert, take their time
to build these images for us, and write scripts to make things such as
resizing a partition bigger. You too Charles for the work you've done.
Truly.

However, running script(s) to do these things for us, teaches us nothing.
Personally, I see a huge distinction between something like say universal
io, and a really simple set of instructions to do basic Linux stuff. We're
using Linux here people, you need to learn how to use it.

The above "guide" I pulled directly off the official ubuntu forums, and
made a few tweaks( some information was left out ). So knowing it could be
done, but not 100% *how*, I was able to google the answer, rewrite my own
instructions ,and apply it in under 10 minutes . . .

On Fri, Jan 16, 2015 at 7:51 PM, William Hermans  wrote:

> *Or you could just boot the uSD card with the 2G uSD image and run:*
>>
>> *   sudo /opt/scripts/tools/grow_*
>
> *partition.sh*
>
> * ...then worst-case you only mess up your BeagleBone and not your x86 PC.*
>
>
> The steps can also be done LIVE on the Beagelbone black, but can only
> resize the partition larger. . . .
>
> On Fri, Jan 16, 2015 at 7:50 PM, Charles Steinkuehler <
> char...@steinkuehler.net> wrote:
>
>> Or you could just boot the uSD card with the 2G uSD image and run:
>>
>>   sudo /opt/scripts/tools/grow_partition.sh
>>
>> ...then worst-case you only mess up your BeagleBone and not your x86 PC.
>>
>> On 1/16/2015 8:45 PM, William Hermans wrote:
>> > Ok, so as a note to all those out there . . . to resize one of the 2G
>> > images to *any* sdcard size, The below "guide" will work. However, this
>> is
>> > only tested on a single partition image, and if using a 2 partition
>> image,
>> > you need to use the appropriate partition. **USE AT YOUR OWN RISK*  *One
>> > single typo can render your file system and / or the boot loader
>> inoperable
>> > . . .
>> >
>> > *These steps were taken on an i386 Debian install ( PC ) with the sdcard
>> > listed at /dev/sdc:*
>> >
>> > *william@eee-pc:~$ sudo fdisk /dev/sdc*
>> >
>> > *Command (m for help): p*
>> >
>> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
>> > 184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
>> > Units = sectors of 1 * 512 = 512 bytes
>> > Sector size (logical/physical): 512 bytes / 512 bytes
>> > I/O size (minimum/optimal): 512 bytes / 512 bytes
>> > Disk identifier: 0x
>> >
>> >Device Boot  Start End  Blocks   Id  System
>> > /dev/sdc1   *2048 3481599 1739776   83  Linux
>> >
>> > *Command (m for help): d*
>> > Selected partition 1
>> > *Command (m for help): p*
>> >
>> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
>> > 184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
>> > Units = sectors of 1 * 512 = 512 bytes
>> > Sector size (logical/physical): 512 bytes / 512 bytes
>> > I/O size (minimum/optimal): 512 bytes / 512 bytes
>> > Disk identifier: 0x
>> >
>> >Device Boot  Start End  Blocks   Id  System
>> >
>> > *Command (m for help): n*
>> > Partition type:
>> >p   primary (0 primary, 0 extended, 4 free)
>> >e   extended
>> >
>> > *Select (default p): p*
>> >
>> >
>> > *Partition number (1-4, default 1): 1First sector (2048-7741439, default
>> > 2048): 2048Last sector, +sectors or +size{K,M,G} (2048-7741439, default
>> > 7741439):*
>> > Using default value 7741439
>> >
>> > *Command (m for help): p*
>> >
>> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
>> > 36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
>> > Units = sectors of 1 * 512 = 512 bytes
>> > Sector size (logical/physical): 512 bytes / 512 bytes
>> > I/O size (minimum/optimal): 512 bytes / 512 bytes
>> > Disk identifier: 0x
>> >
>> >Device Boot  Start End  Blocks   Id  System
>> > /dev/sdc12048 7741439 3869696   83  Linux
>> >
>> > *Command (m for help): a*
>> > *Partition number (1-4): 1*
>> >
>> > *Command (m for help): p*
>> >
>> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
>> > 36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
>> > Units = sectors of 1 * 512 = 512 bytes
>> > Sector size (logical/physical): 512 bytes / 512 bytes
>> > I/O size (minimum/optimal): 512 bytes / 512 bytes
>> > Disk identifier: 0x
>> >
>> >Device Boot  Start End  Blocks   Id  System
>> > /dev/sdc1   *2048 7741439 3869696   83  Linux
>> >
>> >
>> > *Command (m for help): w*
>> > The partition table has been altered!
>> >
>> > Calling ioctl() to re-read partition table.
>> > Syncing disks.
>> > william@eee-pc:~$
>> >
>> > *william@eee-pc:~$ sudo e2fsck -f /dev/sdc1*
>> > e2fsck 1.42.5 (29-Jul-2012)
>> > Pass 1: Checking inodes, blocks, and sizes
>> > Pass 2: Checking directory structure
>> > Pass 3: Checking directory connectivity
>> > Pass 4: Checking reference counts
>> > Pass 5: Checking group summary information
>> > rootfs: 14430/108864 fil

Re: [beagleboard] 2gb image for 4gb BBB?

[William Hermans]

>
> *Or you could just boot the uSD card with the 2G uSD image and run:*
>
> *   sudo /opt/scripts/tools/grow_*

*partition.sh*

* ...then worst-case you only mess up your BeagleBone and not your x86 PC.*


The steps can also be done LIVE on the Beagelbone black, but can only
resize the partition larger. . . .

On Fri, Jan 16, 2015 at 7:50 PM, Charles Steinkuehler <
char...@steinkuehler.net> wrote:

> Or you could just boot the uSD card with the 2G uSD image and run:
>
>   sudo /opt/scripts/tools/grow_partition.sh
>
> ...then worst-case you only mess up your BeagleBone and not your x86 PC.
>
> On 1/16/2015 8:45 PM, William Hermans wrote:
> > Ok, so as a note to all those out there . . . to resize one of the 2G
> > images to *any* sdcard size, The below "guide" will work. However, this
> is
> > only tested on a single partition image, and if using a 2 partition
> image,
> > you need to use the appropriate partition. **USE AT YOUR OWN RISK*  *One
> > single typo can render your file system and / or the boot loader
> inoperable
> > . . .
> >
> > *These steps were taken on an i386 Debian install ( PC ) with the sdcard
> > listed at /dev/sdc:*
> >
> > *william@eee-pc:~$ sudo fdisk /dev/sdc*
> >
> > *Command (m for help): p*
> >
> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
> > 184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
> > Units = sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disk identifier: 0x
> >
> >Device Boot  Start End  Blocks   Id  System
> > /dev/sdc1   *2048 3481599 1739776   83  Linux
> >
> > *Command (m for help): d*
> > Selected partition 1
> > *Command (m for help): p*
> >
> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
> > 184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
> > Units = sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disk identifier: 0x
> >
> >Device Boot  Start End  Blocks   Id  System
> >
> > *Command (m for help): n*
> > Partition type:
> >p   primary (0 primary, 0 extended, 4 free)
> >e   extended
> >
> > *Select (default p): p*
> >
> >
> > *Partition number (1-4, default 1): 1First sector (2048-7741439, default
> > 2048): 2048Last sector, +sectors or +size{K,M,G} (2048-7741439, default
> > 7741439):*
> > Using default value 7741439
> >
> > *Command (m for help): p*
> >
> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
> > 36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
> > Units = sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disk identifier: 0x
> >
> >Device Boot  Start End  Blocks   Id  System
> > /dev/sdc12048 7741439 3869696   83  Linux
> >
> > *Command (m for help): a*
> > *Partition number (1-4): 1*
> >
> > *Command (m for help): p*
> >
> > Disk /dev/sdc: 3963 MB, 3963617280 bytes
> > 36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
> > Units = sectors of 1 * 512 = 512 bytes
> > Sector size (logical/physical): 512 bytes / 512 bytes
> > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > Disk identifier: 0x
> >
> >Device Boot  Start End  Blocks   Id  System
> > /dev/sdc1   *2048 7741439 3869696   83  Linux
> >
> >
> > *Command (m for help): w*
> > The partition table has been altered!
> >
> > Calling ioctl() to re-read partition table.
> > Syncing disks.
> > william@eee-pc:~$
> >
> > *william@eee-pc:~$ sudo e2fsck -f /dev/sdc1*
> > e2fsck 1.42.5 (29-Jul-2012)
> > Pass 1: Checking inodes, blocks, and sizes
> > Pass 2: Checking directory structure
> > Pass 3: Checking directory connectivity
> > Pass 4: Checking reference counts
> > Pass 5: Checking group summary information
> > rootfs: 14430/108864 files (0.1% non-contiguous), 74875/434944 blocks
> >
> > *william@eee-pc:~$ sudo resize2fs /dev/sdc1*
> > resize2fs 1.42.5 (29-Jul-2012)
> > Resizing the filesystem on /dev/sdc1 to 967424 (4k) blocks.
> > The filesystem on /dev/sdc1 is now 967424 blocks long.
> >
> > *Then on the Beagelbone Black once booted . . .*
> >
> > *root@beaglebone:~# df -h /*
> > Filesystem  Size  Used Avail Use% Mounted on
> > /dev/mmcblk0p1  3.7G  235M  3.2G   7% /
> >
> > *root@beaglebone:~# uname -a*
> > Linux beaglebone 3.14.26-ti-r39 #1 SMP PREEMPT Mon Dec 8 04:56:09 UTC
> 2014
> > armv7   l GNU/Linux
> >
> > *root@beaglebone:~# cat /ID.txt*
> > BeagleBoard.org BeagleBone Debian Image 2014-11-19
> >
> > For those who may be wondering. This image was pulled off the recommended
> > links for "official" testing images. The initial partition size is 2G (
> > minimal command line image ). This is an "all-in-one" partition where the
> > boot loader files are in a

Re: [beagleboard] 2gb image for 4gb BBB?

[Charles Steinkuehler]

Or you could just boot the uSD card with the 2G uSD image and run:

  sudo /opt/scripts/tools/grow_partition.sh

...then worst-case you only mess up your BeagleBone and not your x86 PC.

On 1/16/2015 8:45 PM, William Hermans wrote:
> Ok, so as a note to all those out there . . . to resize one of the 2G
> images to *any* sdcard size, The below "guide" will work. However, this is
> only tested on a single partition image, and if using a 2 partition image,
> you need to use the appropriate partition. **USE AT YOUR OWN RISK*  *One
> single typo can render your file system and / or the boot loader inoperable
> . . .
> 
> *These steps were taken on an i386 Debian install ( PC ) with the sdcard
> listed at /dev/sdc:*
> 
> *william@eee-pc:~$ sudo fdisk /dev/sdc*
> 
> *Command (m for help): p*
> 
> Disk /dev/sdc: 3963 MB, 3963617280 bytes
> 184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
> 
>Device Boot  Start End  Blocks   Id  System
> /dev/sdc1   *2048 3481599 1739776   83  Linux
> 
> *Command (m for help): d*
> Selected partition 1
> *Command (m for help): p*
> 
> Disk /dev/sdc: 3963 MB, 3963617280 bytes
> 184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
> 
>Device Boot  Start End  Blocks   Id  System
> 
> *Command (m for help): n*
> Partition type:
>p   primary (0 primary, 0 extended, 4 free)
>e   extended
> 
> *Select (default p): p*
> 
> 
> *Partition number (1-4, default 1): 1First sector (2048-7741439, default
> 2048): 2048Last sector, +sectors or +size{K,M,G} (2048-7741439, default
> 7741439):*
> Using default value 7741439
> 
> *Command (m for help): p*
> 
> Disk /dev/sdc: 3963 MB, 3963617280 bytes
> 36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
> 
>Device Boot  Start End  Blocks   Id  System
> /dev/sdc12048 7741439 3869696   83  Linux
> 
> *Command (m for help): a*
> *Partition number (1-4): 1*
> 
> *Command (m for help): p*
> 
> Disk /dev/sdc: 3963 MB, 3963617280 bytes
> 36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
> Units = sectors of 1 * 512 = 512 bytes
> Sector size (logical/physical): 512 bytes / 512 bytes
> I/O size (minimum/optimal): 512 bytes / 512 bytes
> Disk identifier: 0x
> 
>Device Boot  Start End  Blocks   Id  System
> /dev/sdc1   *2048 7741439 3869696   83  Linux
> 
> 
> *Command (m for help): w*
> The partition table has been altered!
> 
> Calling ioctl() to re-read partition table.
> Syncing disks.
> william@eee-pc:~$
> 
> *william@eee-pc:~$ sudo e2fsck -f /dev/sdc1*
> e2fsck 1.42.5 (29-Jul-2012)
> Pass 1: Checking inodes, blocks, and sizes
> Pass 2: Checking directory structure
> Pass 3: Checking directory connectivity
> Pass 4: Checking reference counts
> Pass 5: Checking group summary information
> rootfs: 14430/108864 files (0.1% non-contiguous), 74875/434944 blocks
> 
> *william@eee-pc:~$ sudo resize2fs /dev/sdc1*
> resize2fs 1.42.5 (29-Jul-2012)
> Resizing the filesystem on /dev/sdc1 to 967424 (4k) blocks.
> The filesystem on /dev/sdc1 is now 967424 blocks long.
> 
> *Then on the Beagelbone Black once booted . . .*
> 
> *root@beaglebone:~# df -h /*
> Filesystem  Size  Used Avail Use% Mounted on
> /dev/mmcblk0p1  3.7G  235M  3.2G   7% /
> 
> *root@beaglebone:~# uname -a*
> Linux beaglebone 3.14.26-ti-r39 #1 SMP PREEMPT Mon Dec 8 04:56:09 UTC 2014
> armv7   l GNU/Linux
> 
> *root@beaglebone:~# cat /ID.txt*
> BeagleBoard.org BeagleBone Debian Image 2014-11-19
> 
> For those who may be wondering. This image was pulled off the recommended
> links for "official" testing images. The initial partition size is 2G (
> minimal command line image ). This is an "all-in-one" partition where the
> boot loader files are in a "1M hole" at the beginning of the sdcard.
> Initial kernel was 3.8.13-bone67 then upgraded to the latest 3.14.x TI
> kernel using APT.
> 
> *root@beaglebone:~# ls /boot/*
> SOC.sh config-3.8.13-bone67   uEnv.txt
> System.map-3.14.26-ti-r39  dtbs   uboot
> System.map-3.8.13-bone67   initrd.img-3.14.26-ti-r39  vmlinuz-3.14.26-ti-r39
> config-3.14.26-ti-r39  initrd.img-3.8.13-bone67   vmlinuz-3.8.13-bone67
> 
> I actually made a mistake, by forgetting to check / update the partition to
> active ( * boot ) by using "a" while in fdisk. I then inserted the sdcard
> into the B

Re: [beagleboard] 2gb image for 4gb BBB?

[William Hermans]

Ok, so as a note to all those out there . . . to resize one of the 2G
images to *any* sdcard size, The below "guide" will work. However, this is
only tested on a single partition image, and if using a 2 partition image,
you need to use the appropriate partition. **USE AT YOUR OWN RISK*  *One
single typo can render your file system and / or the boot loader inoperable
. . .

*These steps were taken on an i386 Debian install ( PC ) with the sdcard
listed at /dev/sdc:*

*william@eee-pc:~$ sudo fdisk /dev/sdc*

*Command (m for help): p*

Disk /dev/sdc: 3963 MB, 3963617280 bytes
184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System
/dev/sdc1   *2048 3481599 1739776   83  Linux

*Command (m for help): d*
Selected partition 1
*Command (m for help): p*

Disk /dev/sdc: 3963 MB, 3963617280 bytes
184 heads, 31 sectors/track, 1357 cylinders, total 7741440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System

*Command (m for help): n*
Partition type:
   p   primary (0 primary, 0 extended, 4 free)
   e   extended

*Select (default p): p*


*Partition number (1-4, default 1): 1First sector (2048-7741439, default
2048): 2048Last sector, +sectors or +size{K,M,G} (2048-7741439, default
7741439):*
Using default value 7741439

*Command (m for help): p*

Disk /dev/sdc: 3963 MB, 3963617280 bytes
36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System
/dev/sdc12048 7741439 3869696   83  Linux

*Command (m for help): a*
*Partition number (1-4): 1*

*Command (m for help): p*

Disk /dev/sdc: 3963 MB, 3963617280 bytes
36 heads, 27 sectors/track, 7964 cylinders, total 7741440 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x

   Device Boot  Start End  Blocks   Id  System
/dev/sdc1   *2048 7741439 3869696   83  Linux


*Command (m for help): w*
The partition table has been altered!

Calling ioctl() to re-read partition table.
Syncing disks.
william@eee-pc:~$

*william@eee-pc:~$ sudo e2fsck -f /dev/sdc1*
e2fsck 1.42.5 (29-Jul-2012)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
rootfs: 14430/108864 files (0.1% non-contiguous), 74875/434944 blocks

*william@eee-pc:~$ sudo resize2fs /dev/sdc1*
resize2fs 1.42.5 (29-Jul-2012)
Resizing the filesystem on /dev/sdc1 to 967424 (4k) blocks.
The filesystem on /dev/sdc1 is now 967424 blocks long.

*Then on the Beagelbone Black once booted . . .*

*root@beaglebone:~# df -h /*
Filesystem  Size  Used Avail Use% Mounted on
/dev/mmcblk0p1  3.7G  235M  3.2G   7% /

*root@beaglebone:~# uname -a*
Linux beaglebone 3.14.26-ti-r39 #1 SMP PREEMPT Mon Dec 8 04:56:09 UTC 2014
armv7   l GNU/Linux

*root@beaglebone:~# cat /ID.txt*
BeagleBoard.org BeagleBone Debian Image 2014-11-19

For those who may be wondering. This image was pulled off the recommended
links for "official" testing images. The initial partition size is 2G (
minimal command line image ). This is an "all-in-one" partition where the
boot loader files are in a "1M hole" at the beginning of the sdcard.
Initial kernel was 3.8.13-bone67 then upgraded to the latest 3.14.x TI
kernel using APT.

*root@beaglebone:~# ls /boot/*
SOC.sh config-3.8.13-bone67   uEnv.txt
System.map-3.14.26-ti-r39  dtbs   uboot
System.map-3.8.13-bone67   initrd.img-3.14.26-ti-r39  vmlinuz-3.14.26-ti-r39
config-3.14.26-ti-r39  initrd.img-3.8.13-bone67   vmlinuz-3.8.13-bone67

I actually made a mistake, by forgetting to check / update the partition to
active ( * boot ) by using "a" while in fdisk. I then inserted the sdcard
into the Beaglebone black. Only to be greeted by 3 solidly lit USR LEDs.
After which, I put the sdcard back into my PC, started fdisk again, and
marked the partition appropriately.  Of course then the board booted up
fine.






On Fri, Jan 16, 2015 at 6:38 PM, William Hermans  wrote:

> *Wonders how long before someone gets / tries a 256GB card*
>
> On Fri, Jan 16, 2015 at 6:12 PM, Ridemywideglide 
> wrote:
>
>> Yea is was the only spare I had laying around.. It's installed the 5-14
>> image 

Re: [beagleboard] 2gb image for 4gb BBB?

[William Hermans]

*Wonders how long before someone gets / tries a 256GB card*

On Fri, Jan 16, 2015 at 6:12 PM, Ridemywideglide 
wrote:

> Yea is was the only spare I had laying around.. It's installed the 5-14
> image several times so it should be fine.. I have a couple 8 gig'rs on the
> way so maybe I'll try again when they get here..
>
>
> On Friday, January 16, 2015 at 5:16:52 PM UTC-7, RobertCNelson wrote:
>
>> On Fri, Jan 16, 2015 at 6:03 PM, Ridemywideglide 
>> wrote:
>> >
>> > I'm using a 128gb card so I meet the minimum size, but this image won't
>> go
>> > onto the BBB for some reason. Since it's your image, can you tell me
>> how to
>> > get it onto the BBB?
>>
>> Really? A "128gb" card...
>>
>> You do realilze it's only been advertised as "mircroSD SDHC" thus 32gb
>> is the limit. Although in this forum, we've discovered that 64GB
>> "microSD SDXC" devices from SanDisk do work.. Just not using any of
>> the faster "SDCX" transfer modes..
>>
>> So..  Which brand/model "128gb" do you have?
>>
>> I would say use any other microSD that you have (SDHC) and retry..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Setting up a microSD card for storage purposes

[William Hermans]

Yes . . .

google + "beaglebone black sdcard as storage" ==  About 34,400 results
(0.55 seconds)

On Fri, Jan 16, 2015 at 4:25 PM, Jeffrey Huang  wrote:

> Hi guys, I've only just started playing around with BeagleBone Black. I'm
> trying to use the inserted microSD card as a storage device to write text
> files to. Could someone point me in the right direction to set this up?
> Thanks beforehand.
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 2gb image for 4gb BBB?

[Ridemywideglide]

Yea is was the only spare I had laying around.. It's installed the 5-14 
image several times so it should be fine.. I have a couple 8 gig'rs on the 
way so maybe I'll try again when they get here..


On Friday, January 16, 2015 at 5:16:52 PM UTC-7, RobertCNelson wrote:
>
> On Fri, Jan 16, 2015 at 6:03 PM, Ridemywideglide  > wrote: 
> > 
> > I'm using a 128gb card so I meet the minimum size, but this image won't 
> go 
> > onto the BBB for some reason. Since it's your image, can you tell me how 
> to 
> > get it onto the BBB? 
>
> Really? A "128gb" card... 
>
> You do realilze it's only been advertised as "mircroSD SDHC" thus 32gb 
> is the limit. Although in this forum, we've discovered that 64GB 
> "microSD SDXC" devices from SanDisk do work.. Just not using any of 
> the faster "SDCX" transfer modes.. 
>
> So..  Which brand/model "128gb" do you have? 
>
> I would say use any other microSD that you have (SDHC) and retry.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 2gb image for 4gb BBB?

[Robert Nelson]

On Fri, Jan 16, 2015 at 6:03 PM, Ridemywideglide  wrote:
>
> I'm using a 128gb card so I meet the minimum size, but this image won't go
> onto the BBB for some reason. Since it's your image, can you tell me how to
> get it onto the BBB?

Really? A "128gb" card...

You do realilze it's only been advertised as "mircroSD SDHC" thus 32gb
is the limit. Although in this forum, we've discovered that 64GB
"microSD SDXC" devices from SanDisk do work.. Just not using any of
the faster "SDCX" transfer modes..

So..  Which brand/model "128gb" do you have?

I would say use any other microSD that you have (SDHC) and retry..

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 2gb image for 4gb BBB?

[Ridemywideglide]

I'm using a 128gb card so I meet the minimum size, but this image won't go 
onto the BBB for some reason. Since it's your image, can you tell me how to 
get it onto the BBB?

Thanks


On Friday, January 16, 2015 at 4:36:04 PM UTC-7, RobertCNelson wrote:
>
> On Fri, Jan 16, 2015 at 5:24 PM, Ridemywideglide  > wrote: 
> > I'm looking at updates for the BBB, and the eMMC flasher versions all 
> say 
> > 2gb. Why is this when it's supposed to be a 4gb eMMC? 
> > 
> > I also tried downloading 
> > 
> https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz
>  
> > from here 
> > 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29_2
>  
> > and after writing the extracted image to SD and booting to it, the 4 
> lights 
> > on the BBB just flashed in sequence back and forth... 
> > 
> > Am I missing something here? Can't put a 4gb image on a 4gb BBB?? 
>
> So the way my file naming works: 
>
> BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz 
>
> lxde-4gb: lxde deskop for the 4gb eMMC BBB's.. 
>
> 4gb.img: needs a minimal of a 4GB microSD to transfer the data to the 
> bbb.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 2gb image for 4gb BBB?

[William Hermans]

Not to Mention that the RevC is probably in the minority of the total
boards sold to the public. RevA / RevB both had 2GB eMMCs on board . .

On Fri, Jan 16, 2015 at 4:35 PM, Robert Nelson 
wrote:

> On Fri, Jan 16, 2015 at 5:24 PM, Ridemywideglide 
> wrote:
> > I'm looking at updates for the BBB, and the eMMC flasher versions all say
> > 2gb. Why is this when it's supposed to be a 4gb eMMC?
> >
> > I also tried downloading
> >
> https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz
> > from here
> >
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29_2
> > and after writing the extracted image to SD and booting to it, the 4
> lights
> > on the BBB just flashed in sequence back and forth...
> >
> > Am I missing something here? Can't put a 4gb image on a 4gb BBB??
>
> So the way my file naming works:
>
> BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz
>
> lxde-4gb: lxde deskop for the 4gb eMMC BBB's..
>
> 4gb.img: needs a minimal of a 4GB microSD to transfer the data to the bbb..
>
> Regards,
>
> --
> Robert Nelson
> http://www.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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 2gb image for 4gb BBB?

[Robert Nelson]

On Fri, Jan 16, 2015 at 5:24 PM, Ridemywideglide  wrote:
> I'm looking at updates for the BBB, and the eMMC flasher versions all say
> 2gb. Why is this when it's supposed to be a 4gb eMMC?
>
> I also tried downloading
> https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz
> from here
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29_2
> and after writing the extracted image to SD and booting to it, the 4 lights
> on the BBB just flashed in sequence back and forth...
>
> Am I missing something here? Can't put a 4gb image on a 4gb BBB??

So the way my file naming works:

BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz

lxde-4gb: lxde deskop for the 4gb eMMC BBB's..

4gb.img: needs a minimal of a 4GB microSD to transfer the data to the bbb..

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Setting up a microSD card for storage purposes

[Jeffrey Huang]

Hi guys, I've only just started playing around with BeagleBone Black. I'm 
trying to use the inserted microSD card as a storage device to write text 
files to. Could someone point me in the right direction to set this up? 
Thanks beforehand.

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

[beagleboard] 2gb image for 4gb BBB?

[Ridemywideglide]

I'm looking at updates for the BBB, and the eMMC flasher versions all say 
2gb. Why is this when it's supposed to be a 4gb eMMC?

I also tried 
downloading 
https://rcn-ee.net/rootfs/bb.org/testing/2014-12-19/lxde-4gb/BBB-eMMC-flasher-debian-7.7-lxde-4gb-armhf-2014-12-19-4gb.img.xz
from 
here 
http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_Rev_C_.284GB_eMMC.29_2 
and after writing the extracted image to SD and booting to it, the 4 lights 
on the BBB just flashed in sequence back and forth...

Am I missing something here? Can't put a 4gb image on a 4gb BBB??


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

[beagleboard] Re: Checking GPIOpins for being healthy

[TJF]

This shouldn't be a problem, since most header pins are configured as GPIO 
input by default and therefor can receive 3V2 input.

Am Donnerstag, 15. Januar 2015 16:30:30 UTC+1 schrieb meino@gmx.de:
>
> I would like to check, whether these PINS had survived me. 
>
> What is a valid most simplistic way to do so? 
>

You could use the examples in libpruio to check the pins. Ie. io_input 

 
shows the state of all GPIOs. Or button 

 
configures a single GPIO as input and shows its state. It's easy to 
customize the code for your pins or to test a GPIO pin as output.

Run analyse 

 
right after booting to get a list of the default header pin configuration.

Good luck!

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

Re: [beagleboard] UART loopback

[Peter Hurley]

On 01/16/2015 03:48 AM, philippe.frossard wrote:
> Hi,
> I have a problem when I connect P9.24 (ttyO1.TX) with P9.26 (ttyO1.RX),
> If I send data on serial port like this : echo 1 > /dev/ttyO1
> And read data on serial port like this : cat /dev/ttyO1
> The command output a lot of data indefinitely ... and my ssh link doesn't 
> respond,
> If I remove the jumper the system come back ...
> What wrong ?
> 
> Same problem with ttyO2,
> Same problem with ttyO1 connected to ttyO2
> 
> I'm using kernel  3.8.13-bone69 (trying also 40 and 47) with debian 7.7,

The initial state for all ttys in Linux is ECHO.
When you setup loopback, you need to turn echo off.

stty -a -F /dev/ttyO1 will show you the current termios settings for the port.
See "man termios" for the manual on Linux terminal control.

Regards,
Peter Hurley

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

[beagleboard] Re: UART loopback

[Stephen Agate]

I have the same problem too on the 3.18.1 kernel.

It can be fixed by initialising the port first, with something like:
stty -F /dev/ttyO1 raw clocal -crtscts -echo

S.

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

Re: [beagleboard] off-by-1 enumeration of some devices in .dts* files (what does ti,hwmods do?)

[Robert Nelson]

On Fri, Jan 16, 2015 at 2:57 PM, Jim Giles  wrote:
> (I also posted to the Beaglebone Group; please advise which group is more
> appropriate)
>
> Hello,
>
> I'm trying to create a .dts file for a design based on the BBB, but using
> the am3352b-zce60 pinout.  I'm confused about how to reference several of
> the devices in the Device Tree, and what "ti,hwmods" is used for.
>
> I'm using the following files for reference (from linux-stable, and from Dr.
> Molloy's "Exploring Beaglebone" book/chp06/deviceTree/DTSource3.8.13):
>
> - am33xx.dtsi
> - am335x-bone-common.dtsi
> - am335x-boneblack.dts
>
> 1. Why the off-by-1 enumeration between the node name and the ti,hwmods
> property for some of the devices? Examples:
>
> i2c2: i2c@4819c000 {  /* i2c2 node name, but
> ti,hwmods = "i2c3"
> compatible = "ti,omap4-i2c";
> #address-cells = <1>;
> #size-cells = <0>;
> ti,hwmods = "i2c3";   /* TODO: Fix hwmod
> */
> reg = <0x4819c000 0x1000>;
> interrupts = <30>;
> status = "disabled";
> };
>
> In Dr. Molloy's version (3.8.13), this has been resolved for some devices;
> in linux-stable (am33xx.dtsi), it hasn't:
>
> uart1: serial@44e09000 {/* uart1 node name matches
> ti,hwmods */
> compatible = "ti,omap3-uart";
> ti,hwmods = "uart1";
> 
> clock-frequency = <4800>;
> reg = <0x44e09000 0x2000>;
> interrupts = <72>;
> status = "disabled";
> };
>
> In linux-stable, here's the corresponding entry in am33xx.dtsi:
> uart1: serial@48022000 {   /* uart1 node name, but
> ti,hwmods = "uart2 */
> compatible = "ti,omap3-uart";
> ti,hwmods = "uart2";<
> clock-frequency = <4800>;
> reg = <0x48022000 0x2000>;
> interrupts = <73>;
> status = "disabled";
> };
>
> 2. This also seems to be the case for the mmcs, where mmc0 isn't explicitly
> defined, but &mmc2 maps to the emmc. Example:
>
> - mmc0 is referenced explicitly in linux-stable (am335x-bone-common.dtsi)
> for mapping the LEDs, but nowhere else.
> - How is the reference to mmc0 resolved, given that mmc references in
> am33xx.dtsi start at 1?  (mmc1, mmc2, mmc3)

btw, don't use 3.8.x as the "set" in stone naming.. A few things such
as the gpio where mis-numbered and later corrected in mainline.

That aside..  In kernel land, most devices start with xyz0 where as
"marketing" people call this xyz1, i guess it's hard to sell something
to a customer labeled as xyz0..

https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/am33xx.dtsi

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] off-by-1 enumeration of some devices in .dts* files (what does ti,hwmods do?)

[Jim Giles]

(I also posted to the Beaglebone Group; please advise which group is more 
appropriate)

Hello,

I'm trying to create a .dts file for a design based on the BBB, but using 
the am3352b-zce60 pinout.  I'm confused about how to reference several of 
the devices in the Device Tree, and what "ti,hwmods" is used for.

I'm using the following files for reference (from linux-stable, and from 
Dr. Molloy's "Exploring Beaglebone" book/chp06/deviceTree/DTSource3.8.13):
 
- am33xx.dtsi
- am335x-bone-common.dtsi
- am335x-boneblack.dts

1. Why the off-by-1 enumeration between the node name and the ti,hwmods 
property for some of the devices? Examples:

i2c2: i2c@4819c000 {  /* i2c2 node name, 
but ti,hwmods = "i2c3"
compatible = "ti,omap4-i2c";
#address-cells = <1>;
#size-cells = <0>;
ti,hwmods = "i2c3";   /* TODO: Fix 
hwmod */
reg = <0x4819c000 0x1000>;
interrupts = <30>;
status = "disabled";
};

In Dr. Molloy's version (3.8.13), this has been resolved for some devices; 
in linux-stable (am33xx.dtsi), it hasn't:

uart1: serial@44e09000 {/* uart1 node name matches 
ti,hwmods */
compatible = "ti,omap3-uart";
ti,hwmods = "uart1"; 

clock-frequency = <4800>;
reg = <0x44e09000 0x2000>;
interrupts = <72>;
status = "disabled";
};

In linux-stable, here's the corresponding entry in am33xx.dtsi:
uart1: serial@48022000 {   /* uart1 node name, but 
ti,hwmods = "uart2 */
compatible = "ti,omap3-uart";
ti,hwmods = "uart2";<
clock-frequency = <4800>;
reg = <0x48022000 0x2000>;
interrupts = <73>;
status = "disabled";
};

2. This also seems to be the case for the mmcs, where mmc0 isn't explicitly 
defined, but &mmc2 maps to the emmc. Example:

- mmc0 is referenced explicitly in linux-stable (am335x-bone-common.dtsi) 
for mapping the LEDs, but nowhere else. 
- How is the reference to mmc0 resolved, given that mmc references in 
am33xx.dtsi start at 1?  (mmc1, mmc2, mmc3)

Thanks,

Jim


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

Re: [beagleboard] ethernet gadget with beagleboard

[Ran Shalit]

Hi,

I solved the issue.
I compile now inside kernel and added:
CONFIG_USB_MUSB_OMAP2PLUS_GLUE

Thank you very much for all help!
Ran

On Fri, Jan 16, 2015 at 8:23 AM, Ran Shalit  wrote:

> Hello,
>
> Can anyone please try to see if he can work with usb otg and beagleboard
> this is the download page for kernel 2.6.37 I use:
>
> http://downloads.ti.com/dsps/dsps_public_sw/psp/LinuxPSP/OMAP_04_02/04_02_00_07/index_FDS.html
>
> Regards,
> Ran
>
> On Thu, Jan 15, 2015 at 8:16 PM, Ran Shalit  wrote:
>
>> Hi,
>>
>> When I compiled earlier kernel version which are supposed to support
>> OMAP3530 with beaglebone I fail to start kernel (psp 3.0.1.6, kernel
>> 2.6.32);
>>
>> 1920736 bytes read
>> ## Booting kernel from Legacy Image at 8030 ...
>>Image Name:   Linux-2.6.32
>>Image Type:   ARM Linux Kernel Image (uncompressed)
>>Data Size:1920672 Bytes =  1.8 MB
>>Load Address: 80008000
>>Entry Point:  80008000
>>Verifying Checksum ... OK
>>Loading Kernel Image ... OK
>> OK
>>
>> Starting kernel ...
>>
>> Uncompressing
>> Linux
>> done, booting the kernel.
>>
>> <<-- NO  more prinings -->>
>>
>> I just need to work with usb ethernet in 2.6.37... why does it fail with
>> the kernel 2.6.37 ?
>>
>> Regards,
>> Ran
>>
>>
>>
>> On Thu, Jan 15, 2015 at 7:14 PM, Ran Shalit  wrote:
>>
>>> Hi,
>>>
>>> Did anyone tried to work with the usb connector (the one that is marked
>>> as "usb otg"), for ethernet with 2.6.37 ?
>>> If not - maybe I should try use some older version for beagleboard ?
>>> Regards,
>>> Ran
>>>
>>> On Thu, Jan 15, 2015 at 6:36 PM, Ran Shalit  wrote:
>>>
 Hi Robert,

 Thanks,
 I have compiled both modules and kernel, but still some error, without
 any information.

 root@beagleboard:/lib/modules/2.6.37/kernel/drivers/usb/gadget# insmod
 g_ether.ko
 insmod: error inserting 'g_ether.ko': -1 No such device

 The new boot log is below.

 Is there any idea why it fails ?

 Texas Instruments X-Loader 1.5.0 (Jun 14 2011 - 22:04:07)
 Beagle Rev C5
 Reading boot sector
 Loading u-boot.bin from mmc


 U-Boot 2009.06-rc2 (Jan 15 2015 - 11:12:37)

 , CPU-OPP2 L3-165MHz
 OMAP3 Beagle board + LPDDR/NAND
 DRAM:  256 MB
 NAND:  512 MiB
 In:serial
 Out:   serial
 Err:   serial
 Board revision Ax/Bx
 Die ID #74aa0007015a676401014023
 Hit any key to stop autoboot:  0
 mmc1 is available
 reading uImage

 2927348 bytes read
 ## Booting kernel from Legacy Image at 8030 ...
Image Name:   Linux-2.6.37
Image Type:   ARM Linux Kernel Image (uncompressed)
Data Size:2927284 Bytes =  2.8 MB
Load Address: 80008000
Entry Point:  80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
 OK

 Starting kernel ...

 Uncompressing Linux... done, booting the kernel.
 [0.00] Linux version 2.6.37 (ubuntu@ubuntu-laptop) (gcc
 version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #8 Thu Jan 15 18:29:23 IST
 2015
 [0.00] CPU: ARMv7 Processor [411fc087] revision 7 (ARMv7),
 cr=10c53c7f
 [0.00] CPU: VIPT nonaliasing data cache, VIPT nonaliasing
 instruction cache
 [0.00] Machine: OMAP3 Beagle Board
 [0.00] Reserving 4194304 bytes SDRAM for VRAM
 [0.00] Memory policy: ECC disabled, Data cache writeback
 [0.00] OMAP3430/3530 ES3.1.2 (l2cache iva sgx neon isp 720mhz )
 [0.00] SRAM: Mapped pa 0x4020 to va 0xfe40 size: 0x1
 [0.00] Built 1 zonelists in Zone order, mobility grouping on.
 Total pages: 64000
 [0.00] Kernel command line: console=ttyO2,115200n8
 root=/dev/mmcblk0p2 rw rootwait
 [0.00] PID hash table entries: 1024 (order: 0, 4096 bytes)
 [0.00] Dentry cache hash table entries: 32768 (order: 5, 131072
 bytes)
 [0.00] Inode-cache hash table entries: 16384 (order: 4, 65536
 bytes)
 [0.00] Memory: 252MB = 252MB total
 [0.00] Memory: 242712k/242712k available, 19432k reserved, 0K
 highmem
 [0.00] Virtual kernel memory layout:
 [0.00] vector  : 0x - 0x1000   (   4 kB)
 [0.00] fixmap  : 0xfff0 - 0xfffe   ( 896 kB)
 [0.00] DMA : 0xffc0 - 0xffe0   (   2 MB)
 [0.00] vmalloc : 0xd080 - 0xf800   ( 632 MB)
 [0.00] lowmem  : 0xc000 - 0xd000   ( 256 MB)
 [0.00] modules : 0xbf00 - 0xc000   (  16 MB)
 [0.00]   .init : 0xc0008000 - 0xc003a000   ( 200 kB)
 [0.00]   .text : 0xc003a000 - 0xc056e0d0   (5329 kB)
 [0.00]   .data : 0xc057 -

Re: [beagleboard] write new sd card image

[Robert Nelson]

On Fri, Jan 16, 2015 at 12:24 PM, Arturo Gómez  wrote:
>
> Thank you for your prompt response.
> I have tried plugging only a Power supply of 5v/2.4A  with the same problem.
> The sequence of LEDS start blinking but abruptly only the User LED 2 remains
> on.

Umm.. What "else" did you have plugged in?


> The releases tested:
> Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz
> BBB-eMMC-flasher-2013.09.04.img.xz
> BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
> bone-debian-7.5-2014-05-14-2gb.img.xz
> kali-1.0.9-bbb.img.xz

Everything old..

Give the latest snapshot a try:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-12-31

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBone Black as reliable 3G/4G router/ modem

[Bremenpl]

Sorry for that, ive done it by accident i think.
So I tried to install the network-manager, but it was not fully 
installed because it run into some errors (I think im not abble to 
install a single package clean there...). After the restart there is 
still no eth1 or any other.


Normally I was also always using interface file to config everything.

W dniu 2015-01-16 o 21:02, David Goodenough pisze:

On Friday 16 January 2015 20:51:23 you wrote:

The autgor claims that he installed "network manager", but doesnt specify
what exacly- do you kbow maybe what program does he mean?


Dnia 16 stycznia 2015 20:41:06 David Goodenough

 napisał(a):

On Friday 16 January 2015 20:38:19 you wrote:

The problem is I dont see the sr0 device. After I connect the huawei
modem I already see the changed ID, which is 12d1:14db. but when I check
ifconfig, there is no eth1 like it should be like in the tutorial.

W dniu 2015-01-16 o 20:21, David Goodenough pisze:

On Friday 16 January 2015 20:07:14 you wrote:

Ive been there some time a go. I am seing the Huawei as 12d1:14db
from
the beggining and theres no eth1 available. Also no /dev/sr0...

W dniu 2015-01-16 o 20:00, David Goodenough pisze:

On Friday 16 January 2015 10:53:06 bremenpl wrote:

Right now I am trying to use the tutorial from here:
http://crazy-embedder.blogspot.it/2014/12/beaglebone-black-as-3g-ro
uter
-o
r.h tml?m=1

The difference I have other model of the huawei modem (e3131).
After I
hit
lsusb, I dont see the full string like:
Bus 002 Device 005: ID 12d1:1003 Huawei chnologies Co., Ltd. E220
HSDPA
Modem / E230/E270/E870 HSDPA/HSUPA Modem

All I see is:
Bus 001 Device 003: ID 12d1:14db Huawei Technologies Co., Ltd.

Dont I have a driver? How can I install it? Is it even available?
Tried
to
google and found nothing.

After i get to the sakis3g config I choose the Huawei stick:
https://lh3.googleusercontent.com/-DmEg3k3NJe4/VLlddzhmZuI/
Afw/
kD
CGy kbeWng/s1600/huawei.png

And after that I cant connect:
https://lh5.googleusercontent.com/-AIxBrN7xBAE/VLld8bFCucI/
Af4/
1P
SQt Q08u3Q/s1600/failed.png

I would really aprichiate any help.

Well a quick google lead me to:-

http://www.raspberrypi.org/forums/viewtopic.php?t=18996

which I suspect will solve your problem (or at least move it
forward).

David

The bit that is important is the bit about using sg_raw.  The USB
stick
defaults to looking like a CD (so that the windows driver can be
loaded)
and you need to tell it that is not what you want, you want the modem.
That is what the instructions do.

David

try:-

http://forums.debian.net/viewtopic.php?f=7&t=112944

David

I notice you have dropped the beageboard group, I have added it back, please
keep this thread on the group.

David


--
Bremenpl

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

Re: [beagleboard] write new sd card image

[Arturo Gómez]

Thank you for your prompt response.
I have tried plugging only a Power supply of 5v/2.4A  with the same problem.
The sequence of LEDS start blinking but abruptly only the User LED 2
remains on.

The releases tested:
Angstrom-Cloud9-IDE-GNOME-eglibc-ipk-v2012.12-beaglebone-2013.06.20.img.xz
BBB-eMMC-flasher-2013.09.04.img.xz
BBB-eMMC-flasher-debian-7.5-2014-05-14-2gb.img.xz
bone-debian-7.5-2014-05-14-2gb.img.xz
kali-1.0.9-bbb.img.xz

Any ideas of what to do or Try please let me know!
Thank you
Arturo

-The output of my BBB--
U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)
reading args
spl_load_image_fat_os: error reading image args, err - -1
reading
u-boot.img

reading
u-boot.img





U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 -
13:23:54)


I2C:
ready

DRAM:  512
MiB

NAND:  0
MiB

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC:
1
*** Warning - readenv() failed, using default
environment


Net:not set. Validating first E-fuse
MAC
Could not get PHY for cpsw: addr
0

cpsw,
usb_ether

Hit any key to stop autoboot:
0

gpio: pin 53 (gpio 53) value is
1

mmc0 is current
device

gpio: pin 54 (gpio 54) value is
1

SD/MMC found on device
0

reading
uEnv.txt

14 bytes read in 4 ms (2.9
KiB/s)

gpio: pin 55 (gpio 55) value is
1

Loaded environment from
uEnv.txt

Importing environment from mmc
...

Checking if uenvcmd is set
...



uenvcmd was not defined in uEnv.txt
...
gpio: pin 56 (gpio 56) value is
0

gpio: pin 55 (gpio 55) value is
0

gpio: pin 54 (gpio 54) value is
0

mmc1(part 0) is current
device

gpio: pin 54 (gpio 54) value is
1

SD/MMC found on device
1

reading
uEnv.txt

1430 bytes read in 5 ms (279.3
KiB/s)

gpio: pin 55 (gpio 55) value is
1

Loaded environment from
uEnv.txt

Importing environment from mmc
...

Checking if uenvcmd is set
...

gpio: pin 56 (gpio 56) value is
1

Running uenvcmd
...

reading
zImage

3717760 bytes read in 206 ms (17.2
MiB/s)

reading
initrd.img

2868964 bytes read in 160 ms (17.1
MiB/s)

reading
/dtbs/am335x-boneblack.dtb

25080 bytes read in 8 ms (3
MiB/s)

Kernel image @ 0x8200 [ 0x00 - 0x38ba80
]
## Flattened Device Tree blob at
8800

   Booting using the fdt blob at
0x8800

   Using Device Tree in place at 8800, end
880091f7


Starting kernel
...



Uncompressing Linux... done, booting the
kernel.
[0.382828] omap2_mbox_probe: platform not
supported
[0.550551] tps65217-bl tps65217-bl: no platform data
provided
[0.614703] bone-capemgr bone_capemgr.9: slot #0: No cape
found
[0.651812] bone-capemgr bone_capemgr.9: slot #1: No cape
found
[0.688919] bone-capemgr bone_capemgr.9: slot #2: No cape
found
[0.726028] bone-capemgr bone_capemgr.9: slot #3: No cape
found
[0.742158] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN
conflict P8.45 (#5:BB-BONELT-HDMI)
[0.751761] bone-capemgr bone_capemgr.9: slot #6: Failed
verification
[0.758522] bone-capemgr bone_capemgr.9: loader: failed to load slot-6
BB-BONELT-HDMIN:00A0 (prio 2)
[0.774999] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
failed
[0.837639] pinctrl-single 44e10800.pinmux: pin 44e10854 already
requested by 44e10800.pinmux; cannot claim 8
[0.849322] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
-22
[0.856616] pinctrl-single 44e10800.pinmux: could not request pin 21 on
device pinctrl-single
[1.064536] Unhandled fault: external abort on non-linefetch (0x1008) at
0xe089c000
[1.072667] Internal error: : 1008 [#1] SMP
THUMB2
[1.077723] Modules linked
in:

[1.080955] CPU: 0Not tainted  (3.8.13-bone47
#1)
[1.086313] PC is at
cpsw_probe+0x3f4/0x87a

[1.090747] LR is at
ioremap_page_range+0xb5/0xf0

[1.095719] pc : []lr : []psr:
8033
[1.095719] sp : df051e20  ip : c07e52f4  fp :
0001
[1.107836] r10: de5f7d90  r9 : de5f7800  r8 :

[1.113352] r7 : df112400  r6 : df112410  r5 : e089c000  r4 :
de5f7800
[1.120245] r3 :   r2 : 0800  r1 : c02d7063  r0 :
e089c000
[1.127125] Flags: Nzcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb
Segment kernel
[1.135011] Control: 50c5387d  Table: 9e28c019  DAC:
0015
[1.141076] Process swapper/0 (pid: 1, stack limit =
0xdf050240)
[1.147408] Stack: (0xdf051e20 to
0xdf052000)
[1.152009] 1e20:  c045a173 de5f7d40 de5f7a98 df051e44 df051e58
df051e88 c00e6355
[1.160642] 1e40: df051e88 de5fc288 df051e70 df04f640 de5fc288 de5f8f40
de5fc288 c00e6293
[1.169265] 1e60: de5fc288  de5fc308 df114d48 0001 c00e6aab
df0474b8 c004370b
[1.177899] 1e80:  0003 0020 0008 c0806754 df112410
c0806754 df112444
[1.186528] 1ea0: c0806754 0100 c07641bd c079b700  c0284303
c02842f7 c02838bd
[1.195162] 1ec0:  df112410 c0806754 df112444  c02839bd
c0806754 df051ee8
[1.203784] 1ee0: c028398d c0282acb df047478 df110b80 c0806754 c0806754
de5f8f40 c07fbe50
[1.212402] 1f00:  c028336b c066eecd df001288 c0806754 c077e535
 c0

Re: [beagleboard] Re: BeagleBone Black as reliable 3G/4G router/ modem

[David Goodenough]

On Friday 16 January 2015 20:51:23 you wrote:
> The autgor claims that he installed "network manager", but doesnt specify
> what exacly- do you kbow maybe what program does he mean?
> 
> 
> Dnia 16 stycznia 2015 20:41:06 David Goodenough
> 
>  napisał(a):
> > On Friday 16 January 2015 20:38:19 you wrote:
> > > The problem is I dont see the sr0 device. After I connect the huawei
> > > modem I already see the changed ID, which is 12d1:14db. but when I check
> > > ifconfig, there is no eth1 like it should be like in the tutorial.
> > > 
> > > W dniu 2015-01-16 o 20:21, David Goodenough pisze:
> > > > On Friday 16 January 2015 20:07:14 you wrote:
> > > >> Ive been there some time a go. I am seing the Huawei as 12d1:14db
> > > >> from
> > > >> the beggining and theres no eth1 available. Also no /dev/sr0...
> > > >> 
> > > >> W dniu 2015-01-16 o 20:00, David Goodenough pisze:
> > > >>> On Friday 16 January 2015 10:53:06 bremenpl wrote:
> > >  Right now I am trying to use the tutorial from here:
> > >  http://crazy-embedder.blogspot.it/2014/12/beaglebone-black-as-3g-ro
> > >  uter
> > >  -o
> > >  r.h tml?m=1
> > >  
> > >  The difference I have other model of the huawei modem (e3131).
> > >  After I
> > >  hit
> > >  lsusb, I dont see the full string like:
> > >  Bus 002 Device 005: ID 12d1:1003 Huawei chnologies Co., Ltd. E220
> > >  HSDPA
> > >  Modem / E230/E270/E870 HSDPA/HSUPA Modem
> > >  
> > >  All I see is:
> > >  Bus 001 Device 003: ID 12d1:14db Huawei Technologies Co., Ltd.
> > >  
> > >  Dont I have a driver? How can I install it? Is it even available?
> > >  Tried
> > >  to
> > >  google and found nothing.
> > >  
> > >  After i get to the sakis3g config I choose the Huawei stick:
> > >  https://lh3.googleusercontent.com/-DmEg3k3NJe4/VLlddzhmZuI/
> > >  Afw/
> > >  kD
> > >  CGy kbeWng/s1600/huawei.png
> > >  
> > >  And after that I cant connect:
> > >  https://lh5.googleusercontent.com/-AIxBrN7xBAE/VLld8bFCucI/
> > >  Af4/
> > >  1P
> > >  SQt Q08u3Q/s1600/failed.png
> > >  
> > >  I would really aprichiate any help.
> > > >>> 
> > > >>> Well a quick google lead me to:-
> > > >>> 
> > > >>> http://www.raspberrypi.org/forums/viewtopic.php?t=18996
> > > >>> 
> > > >>> which I suspect will solve your problem (or at least move it
> > > >>> forward).
> > > >>> 
> > > >>> David
> > > > 
> > > > The bit that is important is the bit about using sg_raw.  The USB
> > > > stick
> > > > defaults to looking like a CD (so that the windows driver can be
> > > > loaded)
> > > > and you need to tell it that is not what you want, you want the modem.
> > > > That is what the instructions do.
> > > > 
> > > > David
> > 
> > try:-
> > 
> > http://forums.debian.net/viewtopic.php?f=7&t=112944
> > 
> > David
I notice you have dropped the beageboard group, I have added it back, please
keep this thread on the group.

David

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

Re: [beagleboard] Re: I think I have found something that rPI and arduino can do but BBB cannot

[William Hermans]

There are also *many* low cost M0+, M3, and M4 dev boards out there. Not to
mention the MSP430 launchpad. Some of the NXP MCUs can even be used with
very minimal external circuitry to get them up and running, Something like
one resistor and one capacitor, if memory serves correctly Other MCU's such
as the MSP430G2553 are very low power, can operate between 1-16Mhz, and can
do I2C, UART, and SPI in hardware. Among other things.

*OR* one could just buy a "proper" 1-wire / I C sensor . . .

On Fri, Jan 16, 2015 at 11:59 AM,  wrote:

> Alternatively, use an Arduino to manage the I2C butchering device and get
> your data from the Arduino.   Honestly I wish these psudo-I2C  devices were
> driven out.   There is a protocol for a reason.
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBone Black as reliable 3G/4G router/ modem

[David Goodenough]

On Friday 16 January 2015 10:53:06 bremenpl wrote:
> Right now I am trying to use the tutorial from here:
> http://crazy-embedder.blogspot.it/2014/12/beaglebone-black-as-3g-router-or.h
> tml?m=1
> 
> The difference I have other model of the huawei modem (e3131). After I hit
> lsusb, I dont see the full string like:
> Bus 002 Device 005: ID 12d1:1003 Huawei chnologies Co., Ltd. E220 HSDPA
> Modem / E230/E270/E870 HSDPA/HSUPA Modem
> 
> All I see is:
> Bus 001 Device 003: ID 12d1:14db Huawei Technologies Co., Ltd.
> 
> Dont I have a driver? How can I install it? Is it even available? Tried to
> google and found nothing.
> 
> After i get to the sakis3g config I choose the Huawei stick:
> https://lh3.googleusercontent.com/-DmEg3k3NJe4/VLlddzhmZuI/Afw/kDCGy
> kbeWng/s1600/huawei.png
> 
> And after that I cant connect:
> https://lh5.googleusercontent.com/-AIxBrN7xBAE/VLld8bFCucI/Af4/1PSQt
> Q08u3Q/s1600/failed.png
> 
> I would really aprichiate any help.
Well a quick google lead me to:-

http://www.raspberrypi.org/forums/viewtopic.php?t=18996

which I suspect will solve your problem (or at least move it forward).

David

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

[beagleboard] Re: I think I have found something that rPI and arduino can do but BBB cannot

[kyle]

Alternatively, use an Arduino to manage the I2C butchering device and get 
your data from the Arduino.   Honestly I wish these psudo-I2C  devices were 
driven out.   There is a protocol for a reason.

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

[beagleboard] What happens if PRU & host try and write same memory address at same time?

[Bill Gray]

Hi,

I've been writing a program to have the PRU on my BBB manage a 
switched-mode power converter.

I want to make sure that if something goes wrong in the host program the 
power converter is shutdown gracefully, so I have implemented a simple 
"watch dog timer" scheme.

The idea is that the host program is constantly setting an address in 
shared memory to 0 in a loop.  The PRU is also constantly incrementing that 
same address.  If the host loop stops, the value at the address climbs 
above a maximum and the PRU knows that the host program has gone away.

As I think this scheme through, I realize that there is a large likelihood 
that the host program and the PRU will try to operate on this shared memory 
address at the same time!

So far my program has not appeared to suffer any ill effects, but I guess 
I'm just interested in how this is handled by the am335x and if I ought to 
aware of possible gotchas!

Thanks,

Bill

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

Re: [beagleboard] Re: BeagleBone Black as reliable 3G/4G router/ modem

[bremenpl]

Right now I am trying to use the tutorial from here:
http://crazy-embedder.blogspot.it/2014/12/beaglebone-black-as-3g-router-or.html?m=1

The difference I have other model of the huawei modem (e3131). After I hit 
lsusb, I dont see the full string like:
Bus 002 Device 005: ID 12d1:1003 Huawei chnologies Co., Ltd. E220 HSDPA 
Modem / E230/E270/E870 HSDPA/HSUPA Modem

All I see is:
Bus 001 Device 003: ID 12d1:14db Huawei Technologies Co., Ltd.

Dont I have a driver? How can I install it? Is it even available? Tried to 
google and found nothing.

After i get to the sakis3g config I choose the Huawei stick:
https://lh3.googleusercontent.com/-DmEg3k3NJe4/VLlddzhmZuI/Afw/kDCGykbeWng/s1600/huawei.png

And after that I cant connect:
https://lh5.googleusercontent.com/-AIxBrN7xBAE/VLld8bFCucI/Af4/1PSQtQ08u3Q/s1600/failed.png

I would really aprichiate any help.

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

Re: [beagleboard] Can't ssh with Chipsee images

[Robert Nelson]

On Fri, Jan 16, 2015 at 11:46 AM, Robert Nelson  wrote:
> On Fri, Jan 16, 2015 at 11:43 AM, Caio Marcos Malheiros Alves
>  wrote:
>> Hi all,
>>
>> I was given a BBB and a Chipsee 7" to work with.
>>
>> With the provided images (Angstrom, Debian and EZSDK) they boot and run and
>> work fine, but with none of them I can ssh through USB into them.
>>
>> I've worked on the same BBB but with other LCD cape (4d systems' 4D-CAPE70T)
>> that runs on original angstrom that comes with the board, and ssh was no
>> problem, I was able to implement a Qt environment, remote deploy and
>> everything, but not with the images provided by Chipsee.
>>
>> What am I missing? Is ssh enabled? I've seen dropbear stuff on the images
>> but can't tell if it is enabled, running or if it is supposed to run. What
>> should I look into?
>
> ssh over USB isn't a hardware thing, it's a software setting by
> loading g_multi on startup.
>
> For the offical images, you can see how this is loaded on bootup here:
>
> https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L91
>
> Note, it's more then just loading g_multi as udcpd or dnsmasq is used
> behind the scene to set the eth ip address.

btw, the chipsee cape should be mostly supported in the newer "jessie" image:

see: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot

and: http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Chipsee_bbb-exp-c

For /boot/uEnv.txt (dtb changes)
and /etc/X11/xorg.conf change..

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Can't ssh with Chipsee images

[Robert Nelson]

On Fri, Jan 16, 2015 at 11:43 AM, Caio Marcos Malheiros Alves
 wrote:
> Hi all,
>
> I was given a BBB and a Chipsee 7" to work with.
>
> With the provided images (Angstrom, Debian and EZSDK) they boot and run and
> work fine, but with none of them I can ssh through USB into them.
>
> I've worked on the same BBB but with other LCD cape (4d systems' 4D-CAPE70T)
> that runs on original angstrom that comes with the board, and ssh was no
> problem, I was able to implement a Qt environment, remote deploy and
> everything, but not with the images provided by Chipsee.
>
> What am I missing? Is ssh enabled? I've seen dropbear stuff on the images
> but can't tell if it is enabled, running or if it is supposed to run. What
> should I look into?

ssh over USB isn't a hardware thing, it's a software setting by
loading g_multi on startup.

For the offical images, you can see how this is loaded on bootup here:

https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L91

Note, it's more then just loading g_multi as udcpd or dnsmasq is used
behind the scene to set the eth ip address.

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Can't ssh with Chipsee images

[Caio Marcos Malheiros Alves]

Hi all,

I was given a BBB and a Chipsee 7" to work with.

With the provided images (Angstrom, Debian and EZSDK) they boot and run and 
work fine, but with none of them I can ssh through USB into them.

I've worked on the same BBB but with other LCD cape (4d systems' 
4D-CAPE70T) that runs on original angstrom that comes with the board, and 
ssh was no problem, I was able to implement a Qt environment, remote deploy 
and everything, but not with the images provided by Chipsee.

What am I missing? Is ssh enabled? I've seen dropbear stuff on the images 
but can't tell if it is enabled, running or if it is supposed to run. What 
should I look into?

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

Re: [beagleboard] BeagleBone Black doesn't sometimes start. Only Power LED is on

[Patrick Schmidt]

Hi Mikkel,

I am trying to follow Andrew's post as close as I can. The tree I am 
building from is git://git.denx.de/u-boot.git, the one provided in Andrew's 
post.

RESOLVED:
>
> Upon investigating the u-boot output we found we were facing the same 
> problem reported earlier in this thread by duckhunter: u-boot was detecting 
> spurious data on uart0 and entering the u-boot console on about 1/20 
> power-ups.
>
> Rather than making any hardware mods I decided to reconfigured u-boot to 
> look for a specific key sequence before entering the u-boot console. To do 
> this I firstly downloaded and rebuilt u-boot following instructions here: 
> http://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot.
>  
> (Testing with the default config produced the same 'failure' rate)
> I then modified '/include/config.h' in the u-boot source files, adding the 
> following:
>
> #define CONFIG_AUTOBOOT_KEYED 1 
> #define CONFIG_AUTOBOOT_DELAY_STR "uboot"
>
> This now forces a user to enter the string 'uboot' before entering the 
> u-boot console, otherwise the device will boot up normally.
>
> Rebuilding with this configuration still gave the same failure rate 
> however. This is when I learned that the boot files on the eMMC flash are 
> still loading before jumping to the files on the sd card I am using. So 
> upon deleting the MLO file on the eMMC flash I had more luck.
>
> We setup a programmable power supply and a script looking at the output of 
> uart0 to detect whether the device had successfully booted or had become 
> stuck in u-boot, and then left it cycling power. We were then able to get 
> many hundreds of consecutive successful boots - we only stopped the test 
> because we decided it would probably never fail.
>
> So in the end it all came down to spurious data on uart0 - along with 
> disabling booting from the eMMC. (we could have simply reconfigured u-boot 
> on the eMMC in the same way, but disabling it drops a few seconds off the 
> boot time).
>
>
> Thanks for all your help Gerald (and duckhunter).
>
> Regards,
> Andrew Glen.
>

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

Re: [beagleboard] BeagleBone Black doesn't sometimes start. Only Power LED is on

[Robert Nelson]

On Fri, Jan 16, 2015 at 9:45 AM, Mikkel Kirkgaard Nielsen
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi again Patrick.
>
> On 2015-01-16 16:01, Patrick Schmidt wrote:
>> After I do the clean and configure steps, I am looking for the
>> /include/config.h file but I don't see it anywhere.
>
> You could do like in my mainline patch, add the options to a specific
> am335x file (I used /include/configs/ti_am335x_common.h). What tree
> are you building from?
>
>> Oh and also the runtime config file sounds like something I want to
>>  check out but a google search didn't help me much. Which file
>> would I be editing for this? Thank you!
>
> This option puzzled me too, hadn't thought this was possible, mostly
> because in the boot sequence it seems like the environment is loaded
> after the autoboot prompt.
>
> I haven't tried it yet, but if you got the full source tree look for the
> autoboot documentation in README and doc/README.autoboot.
>
> In Denx's master you can use the env vars "bootdelaykey" or
> "bootstopkey" to disable "any key" autoboot abort. But be sure u-boot is
> built with CONFIG_AUTOBOOT_KEYED defined or else these options will not
> be enabled.
>
>
> Environment vars are what can be used at boot time to define how u-boot
> should commence booting the OS, besides the options set at compile time.
> The environment is read from the uEnv.txt file residing besides MLO and
> u-boot typically on eMMC/flash or the SD-card. Normally BBB first tries
> the eMMC, then SD. If the boot switch is depressed at powerup (not
> reset) eMMC is skipped (actually SPI is tried instead) and u-boot on
> the SD-card is used.
>
>
> Anybody know if these options are available and enabled in u-boot on the
> stock BBB images?

The patch-delta used in the BBB images is available here:

https://github.com/RobertCNelson/Bootloader-Builder/blob/master/patches/v2015.01/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

It's built against the "am335x_evm" u-boot target..

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black doesn't sometimes start. Only Power LED is on

[Mikkel Kirkgaard Nielsen]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi again Patrick.

On 2015-01-16 16:01, Patrick Schmidt wrote:
> After I do the clean and configure steps, I am looking for the 
> /include/config.h file but I don't see it anywhere.

You could do like in my mainline patch, add the options to a specific
am335x file (I used /include/configs/ti_am335x_common.h). What tree
are you building from?

> Oh and also the runtime config file sounds like something I want to
>  check out but a google search didn't help me much. Which file
> would I be editing for this? Thank you!

This option puzzled me too, hadn't thought this was possible, mostly
because in the boot sequence it seems like the environment is loaded
after the autoboot prompt.

I haven't tried it yet, but if you got the full source tree look for the
autoboot documentation in README and doc/README.autoboot.

In Denx's master you can use the env vars "bootdelaykey" or
"bootstopkey" to disable "any key" autoboot abort. But be sure u-boot is
built with CONFIG_AUTOBOOT_KEYED defined or else these options will not
be enabled.


Environment vars are what can be used at boot time to define how u-boot
should commence booting the OS, besides the options set at compile time.
The environment is read from the uEnv.txt file residing besides MLO and
u-boot typically on eMMC/flash or the SD-card. Normally BBB first tries
the eMMC, then SD. If the boot switch is depressed at powerup (not
reset) eMMC is skipped (actually SPI is tried instead) and u-boot on
the SD-card is used.


Anybody know if these options are available and enabled in u-boot on the
stock BBB images?

- -- 
Mikkel
  ,= ,-_-. =.
 ((_/)o o(\_))
  `-'(. .)`-'
  \_/
keybase.io/mikini
-BEGIN PGP SIGNATURE-
Version: GnuPG v1

iQEcBAEBAgAGBQJUuTIFAAoJEJ2luFWzaTSans8IAOqtPsx4kfmA/gs8tDpw5/7r
UxNa0GK/jMyNSZTZraaJEjA9tUQRJw+f23i3Yj9SLzncpQ8l7f8sHKl7JcCrsbNi
8P+G/QWnvDq2mZdlW8VjB+OwO6tqlYTna0xy72tQJlY8CpVcUVneKjqMFMJxV60E
yLlHGCLF+NGiMDPW+AlqaqhQz0+iE6rnUZYTPOyAvHXl/yyAA3rFlgKa+zhFGVEG
QAvvMB95ljTpl7Z3cJdUFe/9L+IKPKiFHPUb4XzJAAjGP44UiiCkXUye1cJzO6vj
jL7Bv1lJh7qwuWXlghKv69Iz917hblNxXgqR//ZzGS4wCDbT26kGPSR3A4hmVVI=
=Pz4n
-END PGP SIGNATURE-

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

Re: [beagleboard] USB-RS232 adapter problem in 3.14.xx

[Robert Nelson]

On Fri, Jan 16, 2015 at 2:53 AM,   wrote:
> Hi,
>
> I have a simple C program which writes something to a serial port and then
> reads an answer, every 5 ms or so. I'm using an FTDI USB-to-RS232 adapter
> connected to BBB at 115200 bps. In 3.8.13-bone63 this works fine, but there
> are some reasons I need to use a later kernel. I upgraded to the
> 3.14.22-ti-r31 kernel, where my program freezes the user space completely
> after a couple of seconds. Unplugging the USB adapter makes everything run
> again (but of course my program closes since the serial port is no longer
> there). Nothing special in dmesg. I then upgraded to 3.14.26-ti-r43, where
> the problem is slightly different, appearing after several minutes to an
> hour or so, and not freezing completely, making everything just incredibly
> slow (softirq's use about 70 % of CPU time according to top). Closing my
> program brings everything back to normal. Then I tried 3.18.2-bone1, where
> it works again correctly.
>
> I see that bone-kernels have DMA disabled in USB, but I also tried use_dma=0
> module parameter with 3.14.26-ti-r43 and it didn't help. I'd use 3.18.2, but
> unfortunately dtb-rebuilder doesn't have a branch for that kernel, and I
> need to modify the GPIO's a little. The .dtb-file for 3.14.26 doesn't boot
> with 3.18.2.
>
> So,
> 1) Is there something I could try to make it work on 3.14-ti kernels?

Disable:
CONFIG_USB_TI_CPPI41_DMA

Enable:
CONFIG_MUSB_PIO_ONLY

> 2) Is there an easy way to create a custom dtb for the 3.18-bone kernels?

Use the v3.19.x branch:

https://github.com/RobertCNelson/dtb-rebuilder/tree/3.19.x

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] write new sd card image

[Robert Nelson]

On Thu, Jan 15, 2015 at 9:20 PM,   wrote:
>
> I just bought a BBB and  after a week I have the same output error.
> I've tried to reflash the eMMC and using the SD card  with several releases,
> but no success and the same situations described by faimbs. I've an
> expensive brick
> is there a solution or maybe the reason of the problem?
> Any help is welcome.

Do you have a usb-serial adapter or hdmi device plugged in?

Using: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-12-31

the error will be shown in either case:

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)

[Robert Nelson]

On Thu, Jan 15, 2015 at 10:45 AM, Matthijs van Duin
 wrote:
>
> On 14 January 2015 at 17:17, Gerald Coley  wrote:
>>
>> I agree. But, the IP owners seem to be worried about someone copying their
>> IP than they are using it and getting royalties.
>
>
> *stares at the PCIe chapter again and wonders how that would be helpful*  Is
> there some magic PDF-to-VHDL converter? ;-)
>
> But I appreciate it's ultimately not within your (TI's) power to force the
> issue since it's not your IP.

It's the 3rd parties IP, they can do stupid things like that. ;)

>
> However, you guys are doing the same thing with some stuff that *is* (afaik)
> your IP.  Can we have a real ICEPick-D manual please?  Debug functionality
> is of pretty major importance.
>
> And it's for example also pretty silly that docs on the Centaurus (DM814x)
> ISS and HDVPSS subsystems are not publicly available when almost identical
> instances of ISS are in the public OMAP4/5 TRMs, and HDVPSS appears to be
> similar to Vayu's VIP/VPE/DSS (but much more limited and stuffed into a
> single subsystem). Especially since TI doesn't really seem to be maintaining
> a kernel for the DM81xx series anymore, it would be nice if the necessary
> docs were available for third party efforts.

Check on linux-omap, Tony's been adding DM81xx support..  I think the
problem with lack of mainline DM81xx support, is TI/etc never made a
low cost "BeagleBoard" thus, the community never worked on it. ;)

> IVA-HD has also been lacking public documentation since its appearance in
> the OMAP4 (and subsequently in Netra, Centaurus, and now Vayu).

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)

[Gerald Coley]

I no longer work for TI. So you need to address TI directly on this issue.

Gerald


On Thu, Jan 15, 2015 at 10:45 AM, Matthijs van Duin <
matthijsvand...@gmail.com> wrote:

>
> On 14 January 2015 at 17:17, Gerald Coley  wrote:
>
>> I agree. But, the IP owners seem to be worried about someone copying
>> their IP than they are using it and getting royalties.
>
>
> *stares at the PCIe chapter again and wonders how that would be helpful*
>  Is there some magic PDF-to-VHDL converter? ;-)
>
> But I appreciate it's ultimately not within your (TI's) power to force the
> issue since it's not your IP.
>
> However, you guys are doing the same thing with some stuff that *is*
> (afaik) your IP.  Can we have a real ICEPick-D manual please?  Debug
> functionality is of pretty major importance.
>
> And it's for example also pretty silly that docs on the Centaurus (DM814x)
> ISS and HDVPSS subsystems are not publicly available when almost identical
> instances of ISS are in the public OMAP4/5 TRMs, and HDVPSS appears to be
> similar to Vayu's VIP/VPE/DSS (but much more limited and stuffed into a
> single subsystem). Especially since TI doesn't really seem to be
> maintaining a kernel for the DM81xx series anymore, it would be nice if the
> necessary docs were available for third party efforts.
>
> IVA-HD has also been lacking public documentation since its appearance in
> the OMAP4 (and subsequently in Netra, Centaurus, and now Vayu).
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/
http://circuitco.com/support/

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

[beagleboard] DM3730 from the ground up; XDS100v2; register access problem

[sergey . chub . radiofizika]

Hello.

I'd like to preface my question by saying outright that I'm not sure 
whether it's the right place to raise such questions as the one about to 
follow, but I'm truly at sea on this one and I need help. 

The lab I'm working in has acquired a BeagleBoard-xM to explore the extent 
of DM37xx processing prowess with a very specific view to developing a much 
smaller board - tailored/watered-down/fine-tuned/honed/whatever - to meet 
the requirements of the application at hand, no more no less. As I'd been 
put in charge of this small endeavor, I tentatively succeeded in 
implementing schematic and PCB designs, the latter now awaiting to be sent 
out to a board-manufacturing house. But before I'd do just that, I need to 
make sure I understand perfectly what I'm dealing with and lay some 
groundwork for the future.

As any OS involvement was out of the question (except maybe for SYS/BIOS at 
the most), I am now taking small steps in building baby-size test 
applications each one revealing more of a functionality of the SoC. 
However, I've run into a problem.

I'm using XDS100v2 USB Emulator as a bridge between CCS debugger and BB-xM. 
My problem consists in a rather strange behavior of the processor's 
registers. I do everything seemingly right, and sometimes it results in a 
valid and predictable response from the processor. On the other hand, 
sometimes I fail to gain access to certain peripheral registers. I'm not 
allowed to read or write, and when I try to do so, Data Abort is invoked. I 
know for a fact that toggling power supply may or may not help in this 
situation. For example, when I first attempted to get UART3 up and running, 
I was blatantly denied to access corresponding registers and thrown into 
dead loop section. At the same time, GPIOs were easily accessed and 
responded to my manipulations in a very friendly way. After I power-cycled 
the board, miraculously UART3 registers came to life and allowed itself to 
be configured and put into operation, although some other peripherals from 
the PER domain remained cold and unreachable. 

I'm wondering now if it is possible for me to get some answers here. I 
would very much appreciate it. Is it an emulator problem, or is it just 
what I do that is at fault?

Thank you very much in advance.

Sergey.

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

[beagleboard] USB-RS232 adapter problem in 3.14.xx

[malaakso]

Hi,

I have a simple C program which writes something to a serial port and then 
reads an answer, every 5 ms or so. I'm using an FTDI USB-to-RS232 adapter 
connected to BBB at 115200 bps. In 3.8.13-bone63 this works fine, but there 
are some reasons I need to use a later kernel. I upgraded to the 
3.14.22-ti-r31 kernel, where my program freezes the user space completely 
after a couple of seconds. Unplugging the USB adapter makes everything run 
again (but of course my program closes since the serial port is no longer 
there). Nothing special in dmesg. I then upgraded to 3.14.26-ti-r43, where 
the problem is slightly different, appearing after several minutes to an 
hour or so, and not freezing completely, making everything just incredibly 
slow (softirq's use about 70 % of CPU time according to top). Closing my 
program brings everything back to normal. Then I tried 3.18.2-bone1, where 
it works again correctly.

I see that bone-kernels have DMA disabled in USB, but I also tried 
use_dma=0 module parameter with 3.14.26-ti-r43 and it didn't help. I'd use 
3.18.2, but unfortunately dtb-rebuilder doesn't have a branch for that 
kernel, and I need to modify the GPIO's a little. The .dtb-file for 3.14.26 
doesn't boot with 3.18.2.

So,
1) Is there something I could try to make it work on 3.14-ti kernels?
2) Is there an easy way to create a custom dtb for the 3.18-bone kernels?

Thanks,
Matti

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

[beagleboard] Reduce PRU DDR read latency

[djg]

I see up to 5.8 microseconds of latency when the PRU is reading from DDR 
memory. Is it possible to reduce this? I tried changing registers that 
looked promising for giving the PRU priority but they didn't have a 
noticeable effect. This is running on a Beaglebone black using a PRU timer 
to measure the maximum time a LBBO from DDR takes.while the ARM is busy.


The examples I found for doing DMA from the PRU were all for older kernels 
and wouldn't work with Linux 3.8.13. Is there an example I missed that 
works with this kernel?

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

Re: [beagleboard] USB OTG Host mode with BBB?

[m017kc]

Hi, I have got BBB Rev C. I did it, but BBB died and I can't restore him

четверг, 18 декабря 2014 г., 21:37:28 UTC+3 пользователь shei...@gmail.com 
написал:
>
> Dear Ian,
>
> Did you able to convert USB0 Port in BBB to Host?  If So, Can you explain? 
>  I need to Convert Both the ports in BBB to Host.  It is urgent.
>
> With regards
>
> Siddhiq
>
> On Wednesday, September 3, 2014 8:04:25 AM UTC+5:30, Ian Collins wrote:
>>
>> Has anyone made any progress with this?
>>
>> I'm in the same boat trying to get this work and realise we will have to 
>> add some hardware to provide the correctly timed 5V.  It looks like the 
>> biggest problem is the DRVVBUS pin for USB0 isn't tracked.
>>
>> Thanks.
>>
>> Ian. 
>>
>> On Wednesday, 12 February 2014 22:42:58 UTC+13, AndrewTaneGlen wrote:
>>>
>>> This guy seems to have had some success, with some minor hardware 
>>> modifications:
>>>
>>> http://pansenti.wordpress.com/2013/05/27/beaglebone-black-with-two-usb-host-ports-it-can-be-done-but-its-not-easy/
>>>
>>> Andrew.
>>>
>>>
>>> On 12 February 2014 20:18, Mahammad  wrote:
>>>
 Hi There

 I am too trying to make the mini usb port to work as a host. 

 I am trying to scan the expansion port signals it seams like none of 
 the pins offers direct access to the processor vbus signal. Should I do 
 this with some software?

 If with software; what time should it work to enable/disable the volt? 
 And should it listen to the signal all the time or just during the port 
 initialization stage?

 Best Regards

 Mahammad








 On Wednesday, August 21, 2013 4:38:47 AM UTC+2, AndrewTaneGlen wrote:
>
> Understood. Thanks for taking the time to clear that up for me.
>
>
> Andy.
>
> On Wednesday, 21 August 2013 14:36:59 UTC+12, Gerald wrote:
>>
>> Yes, that is what I am saying. I did a design where the 5V was always 
>> there. It din't work. I had to add a power switch like I did on the BBB 
>> design.
>>
>>
>> Gerald
>>
>>
>> On Tue, Aug 20, 2013 at 9:33 PM, AndrewTaneGlen > > wrote:
>>
>>> Thanks Gerald,
>>>
>>> That was one thing I was not absolutely clear on. The TRM has the 
>>> following passage concerning USB power control:
>>>
>>> "*When any of the USB controllers assumes the role of a host, the 
>>> USB is required to supply a 5V power*
>>> *source to an attached device through its VBUS line. In order to 
>>> achieve this task, the USB controller*
>>> *requires the use of an external power logic (or charge pump) 
>>> capable of sourcing 5V power. A*
>>> *USB_DRVVBUS is used as a control signal to enable/disable this 
>>> external power logic to either source or*
>>> *disable power on the VBUS line. The control on the USB_DRVVBUS is 
>>> automatic and is handled by the*
>>> *USB controller.*" (AM335X TRM, pg. 1697)
>>>
>>> So are you saying, in addition to the above, that the USB port must 
>>> be in control of the VBUS enable - assumedly detecting the voltage as 
>>> off 
>>> when disabled, and on when enabled, with specific timing requirements 
>>> around these edges - so that there is no way to simply have the 5V 
>>> there 
>>> the whole time?
>>>
>>> If this is the case I guess there is a chance that I could add some 
>>> kind of gpio control through the expansion header to enable/disable the 
>>> 5V 
>>> rail as and when required (or I could just modify the board - but I'm 
>>> trying to avoid this and be able to just plug my clean BBB into my 
>>> horrible 
>>> looking base board...)
>>>
>>>
>>> Regards,
>>> Andy.
>>>
>>> On Wednesday, 21 August 2013 14:20:08 UTC+12, Gerald wrote:
>>>
 Like the fact that the processor needs to see the 5V on 
 the processor pin when it turns on the 5V?

 Take a look at the host port design. Both ports are actually OTG 
 ports by design. To make the state machine in the HW function as a 
 host, 
 you need to make it work like the other OTG port, the one we call the 
 Host 
 port, which is configured for host..


 Gerald



 On Tue, Aug 20, 2013 at 9:12 PM, AndrewTaneGlen <
 andrewt...@gmail.com> wrote:

> Hi All,
>
> I've been playing around with getting the mini-USB pc connector to 
> function as a second USB host (I'm using RCN's Ubuntu, Raring, but 
> I'd 
> assume this would apply to Angstrom as well). There is a post here 
> http://pansenti.wordpress.com/2013/05/27/beaglebone-
> black-with-two-usb-host-ports-it-can-be-done-but-its-not-easy/ 
> decribing 
> how to do this with some hardware modifications, but looking at the 
>>>

[beagleboard] Re: Beaglebone Black and Web Servers?

[Phil]

(iii) Django can be installed. "apt-get install python-django"

On Tuesday, 4 November 2014 11:40:21 UTC+11, Nick Apperley wrote:
>
> Have answers to some of your questions. See the replies below:
>
> (i) Apache
> (ii)Linux (Debian or Ubuntu)
>
> Not sure if Django can be installed on the BBB. Will largely depend upon 
> whether or not Django uses any native C/C++ libraries.
>
>
> On Saturday, 11 January 2014 16:37:07 UTC+13, COG wrote:
>>
>> Hi:
>>
>> I am a newbie to the Beaglebone arena and I have some questions dealing 
>> with which web server(s) to use.  
>>
>> (i) What is a good web server(s) to use?
>> (ii) On which Operating System?
>> (iii) Can Django be installed on the Beaglebone Black?
>> (iv) If Yes, what would I have to do?  E.g. Where to find the install 
>> file and instructions?
>>
>> *Note:*  I have experience programming in both Java and Python; and 
>> using the OS Ubuntu and a desktop.
>>
>> Regards
>> COG
>>
>

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

[beagleboard] DM3730 from the ground up; problems debuggibg via XDS100v2

[sergey . chub . radiofizika]

Hello.

I'd like to preface my question by saying outright that I'm not sure 
whether it's the right place to raise such questions as the one about to 
follow, but I'm truly at sea on this one and I need help. 

The lab I'm working in has acquired a BeagleBoard-xM to explore the extent 
of DM37xx processing prowess with a very specific view to developing a much 
smaller board - tailored/watered-down/fine-tuned/honed/whatever - to meet 
the requirements of the application at hand, no more no less. As I'd been 
put in charge of this small endeavor, I tentatively succeeded in 
implementing schematic and PCB designs, the latter now awaiting to be sent 
out to a board-manufacturing house. But before I'd do just that, I need to 
make sure I understand perfectly what I'm dealing with and lay some 
groundwork for the future.

As any OS involvement was out of the question (except maybe for SYS/BIOS at 
the most), I am now taking small steps in building baby-size test 
applications each one revealing more of a functionality of the SoC. 
However, I've run into a problem.

I'm using XDS100v2 USB Emulator as a bridge between CCS debugger and BB-xM. 
My problem consists in a rather strange behavior of the processor's 
registers. I do everything seemingly right, and sometimes it results in a 
valid and predictable response from the processor. On the other hand, 
sometimes I fail to gain access to certain peripheral registers. I'm not 
allowed to read or write, and when I try to do so, Data Abort is invoked. I 
know for a fact that toggling power supply may or may not help in this 
situation. For example, when I first attempted to get UART3 up and running, 
I was blatantly denied to access corresponding registers and thrown into 
dead loop section. At the same time, GPIOs were easily accessed and 
responded to my manipulations in a very friendly way. After I power-cycled 
the board, miraculously UART3 registers came to life and allowed itself to 
be configured and put into operation, although some other peripherals from 
the PER domain remained cold and unreachable. 

I'm wondering now if it is possible for me to get some answers here. I 
would very much appreciate it. Is it an emulator problem, or is it just 
what I do that is at fault?

Thank you very much in advance.

Sergey.

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

Re: [beagleboard] BeagleBone Black doesn't sometimes start. Only Power LED is on

[patch914]

Mikkel,

I just found this forum after having these same boot problems with a couple 
beaglebones I have. I figured I would reply to you since I noticed you just 
posted a reply. I am a little confused on how to apply the fix Andrew 
provided. I am able to follow the instructions on downloading and building 
the u-boot, everything seems to work fine there. Then I have a MLO and 
u-boot.img file that I copy to the /boot/uboot directory ( I am using 
Debian booting off the eMMC). My question is when are the #DEFINES suppose 
to be added to the config.h file? Andrew mentions that he made the changes 
to the config.h file and rebuilt the u-boot, but when I do that it just 
overwrites the config.h file back to the original. So I assume the process 
should be first download and build the u-boot, then move MLO and u-boot.img 
into the uboot directory (/boot/uboot), then modify the config.h file 
adding in the #DEFINES Andrew provides. Is this correct? I have tried 
everything I can think of, but I you will have to forgive me because I am 
not too familiar with Debian. Thank you for any help you can provide! 

On Thursday, January 15, 2015 at 8:43:07 AM UTC-6, Mikkel Kirkgaard Nielsen 
wrote:
>
> -BEGIN PGP SIGNED MESSAGE- 
> Hash: SHA1 
>
> Hi there Martin. 
>
> On 2015-01-14 18:05, martin...@spotme.com  wrote: 
> > Just as a +1 to Andrew's findings: In summary, this software fix is 
> >  still highly useful. 
>
> Glad you were able to solve your issue. 
> I'm just wondering if Andrew's autoboot solution/hack hasn't 
> propagated to the official software yet? 
>
> Seems odd if not, since so many has been bitten by it and it is now 15 
> months since it was first described (2013-10-28: 
> https://groups.google.com/forum/#!msg/beagleboard/aXv6An1xfqI/2_tLa7oWQBIJ). 
>
>
>
> I haven't studied the u-boot source before but I just took a sniff at 
> the mainline repository (http://git.denx.de/u-boot.git). 
> I found that for BBB (really am335x) u-boot still defaults to aborting 
> autoboot if any characters are received on the serial console and then 
> waiting forever for further commands. 
>
> Below is a patch mitigating this situation in mainline master 
> (binaries at 
>
> http://www.mikini.dk/wp-content/uploads/2015/01/u-boot_mainline_BBB-autoboot-patch_201501151.zip).
>  
>
> It requires typing more characters ("stop") to abort and uses a new(?) 
> config feature to reset the board if autoboot is aborted but no 
> commands are entered (for 30 sec). 
> Except for the 30 sec timeout, which doesn't kick in for some unknown 
> reason, it seems to behave ok. 
>
> Disclaimer: this is mostly an experiment, there is a lot of u-boot 
> trees and patches floating around for the BBB (like 
> https://github.com/beagleboard/u-boot), so probably mainline hasn't 
> got the most recent stuff for BBB yet. 
>
>
> diff --git a/include/configs/ti_am335x_common.h 
> b/include/configs/ti_am335x_common.h 
> index 5ed86d9..c58f467 100644 
> - --- a/include/configs/ti_am335x_common.h 
> +++ b/include/configs/ti_am335x_common.h 
> @@ -12,6 +12,12 @@ 
>  #ifndef __CONFIG_TI_AM335X_COMMON_H__ 
>  #define __CONFIG_TI_AM335X_COMMON_H__ 
>
> +#define CONFIG_AUTOBOOT_KEYED 
> +#define CONFIG_AUTOBOOT_STOP_STR "stop" 
> +#define CONFIG_AUTOBOOT_PROMPT "autoboot in %d seconds (type '%s' to 
> abort)\n",bootdelay,CONFIG_AUTOBOOT_STOP_STR 
> +#define CONFIG_BOOT_RETRY_TIME 30 
> +#define CONFIG_RESET_TO_RETRY 
> + 
>  #define CONFIG_AM33XX 
>  #define CONFIG_ARCH_CPU_INIT 
>  #define CONFIG_SYS_CACHELINE_SIZE   64 
> @@ -102,4 +108,7 @@ 
>  /* Now bring in the rest of the common code. */ 
>  #include  
>
> +#undef  CONFIG_BOOTDELAY 
> +#define CONFIG_BOOTDELAY   5 
> + 
>  #endif /* __CONFIG_TI_AM335X_COMMON_H__ */ 
>
>
> > Thank you Andrew and Guglielmo for your work! 
>
> Thumbs up, also for Guillermo ;). 
>
> - -- 
> Mikkel 
>   ,= ,-_-. =. 
>  ((_/)o o(\_)) 
>   `-'(. .)`-' 
>   \_/ 
> keybase.io/mikini 
> -BEGIN PGP SIGNATURE- 
> Version: GnuPG v1 
>
> iQEcBAEBAgAGBQJUt9HnAAoJEJ2luFWzaTSaqCoH/2cuFepOVkHGM0gGaGV5U8Dg 
> /Z3O4Cb1zGyasSeYLZbU5XfOms6k66hbLmbQiDYIKkMv/KS0gcjjkuFaZBE2NdVJ 
> xFnaPS/XPd8MJcwWQMVScFafNJE1E4KLHe437FeenPZLEBcgtZc/AsTFX+mybKhC 
> oQfaUmrA9gT2KGmFoGB8Sp+4q4reciXicHRfet78aEF8g9FdqprQvf4xjfcZYgxL 
> 0cNNbXh+mmT+AjSCB4CEze25V5yitvfT744WUUHFznfRWXkRVvKpiVeiDwdswKcs 
> AaV5yjCqxb0F3iM4leRxdDy3FhuMjxmyZxk9HpwO/sLKExigNktpd3aRjuHO7ds= 
> =jU44 
> -END PGP SIGNATURE- 
>

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

Re: [beagleboard] write new sd card image

[arturo . goomez]

I just bought a BBB and  after a week I have the same output error.
I've tried to reflash the eMMC and using the SD card  with several 
releases, but no success and the same situations described by faimbs. I've 
an expensive brick 
is there a solution or maybe the reason of the problem?
Any help is welcome. 
Regards, Arturo

El martes, 4 de noviembre de 2014, 13:40:02 (UTC-6), RobertCNelson escribió:
>
> Please retest with: 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2014-10-22
> On Nov 4, 2014 10:20 AM, "faimbs" > wrote:
>
>> Hello!
>>
>> I downloaded this file via Bittorrent and direct:
>> Debian (BeagleBone, BeagleBone Black - 2GB SD) 2014-05-14  
>> 
>>
>> I use Win32 Disk Imager and generate the sd card.
>> I put the card into the BBB, press USER button and Power up. All 4 LED 
>> are on.
>> I release the button and from the LED is only 1 on and keep on.
>>
>> I made some teste with the DeviceTree and have to reflash the eMMC. 
>> Because the BBB doesn´t start.
>>
>> I connect the serial debug cable ... and see that he are not booting from 
>> sd card?
>> When I check MD5 Hash at Win32 Disk Imager, I get another as on the 
>> website, where I download the image.
>> Or is the website Hash for the .xzFile and not for the .img file?
>>
>> <\0><\0><30><\0><\r><\n>
>> U-Boot SPL 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)<\r><\n>
>> reading args<\r><\n>
>> spl_load_image_fat_os: error reading image args, err - -1<\r><\n>
>> reading u-boot.img<\r><\n>
>> reading u-boot.img<\r><\n>
>> <\r><\n>
>> <\r><\n>
>> U-Boot 2014.04-00014-g47880f5 (Apr 22 2014 - 13:23:54)<\r><\n>
>> <\r><\n>
>> I2C:   ready<\r><\n>
>> DRAM:  512 MiB<\r><\n>
>> NAND:  0 MiB<\r><\n>
>> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1<\r><\n>
>> *** Warning - readenv() failed, using default environment<\r><\n>
>> <\r><\n>
>> Net:not set. Validating first E-fuse MAC<\r><\n>
>> Could not get PHY for cpsw: addr 0<\r><\n>
>> cpsw, usb_ether<\r><\n>
>> Hit any key to stop autoboot:  1 <\b><\b><\b> 0 <\r><\n>
>> gpio: pin 53 (gpio 53) value is 1<\r><\n>
>> mmc0 is current device<\r><\n>
>> gpio: pin 54 (gpio 54) value is 1<\r><\n>
>> SD/MMC found on device 0<\r><\n>
>> reading uEnv.txt<\r><\n>
>> 1672 bytes read in 5 ms (326.2 KiB/s)<\r><\n>
>> gpio: pin 55 (gpio 55) value is 1<\r><\n>
>> Loaded environment from uEnv.txt<\r><\n>
>> Importing environment from mmc ...<\r><\n>
>> Checking if uenvcmd is set ...<\r><\n>
>> gpio: pin 56 (gpio 56) value is 1<\r><\n>
>> Running uenvcmd ...<\r><\n>
>> reading zImage<\r><\n>
>> 4103240 bytes read in 226 ms (17.3 MiB/s)<\r><\n>
>> reading initrd.img<\r><\n>
>> 2957458 bytes read in 165 ms (17.1 MiB/s)<\r><\n>
>> reading /dtbs/am335x-boneblack.dtb<\r><\n>
>> 25926 bytes read in 9 ms (2.7 MiB/s)<\r><\n>
>> Kernel image @ 0x8200 [ 0x00 - 0x3e9c48 ]<\r><\n>
>> ## Flattened Device Tree blob at 8800<\r><\n>
>>Booting using the fdt blob at 0x8800<\r><\n>
>>Using Device Tree in place at 8800, end 88009545<\r><\n>
>> <\r><\n>
>> Starting kernel ...<\r><\n>
>> <\r><\n>
>> Uncompressing Linux... done, booting the kernel.<\r><\n>
>> [0.378378] omap2_mbox_probe: platform not supported<\r><\n>
>> [0.532918] tps65217-bl tps65217-bl: no platform data provided<\r><\n>
>> [0.596810] bone-capemgr bone_capemgr.9: slot #0: No cape found<\r><\n>
>> [0.633918] bone-capemgr bone_capemgr.9: slot #1: No cape found<\r><\n>
>> [0.671026] bone-capemgr bone_capemgr.9: slot #2: No cape found<\r><\n>
>> [0.708135] bone-capemgr bone_capemgr.9: slot #3: No cape found<\r><\n>
>> [0.722803] bone-capemgr bone_capemgr.9: slot #6: BB-BONELT-HDMIN 
>> conflict P8.45 (#5:BB-BONELT-HDMI)<\r><\n>
>> [0.732415] bone-capemgr bone_capemgr.9: slot #6: Failed 
>> verification<\r><\n>
>> [0.739161] bone-capemgr bone_capemgr.9: loader: failed to load slot-6 
>> BB-BONELT-HDMIN:00A0 (prio 2)<\r><\n>
>> [0.756685] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset' 
>> failed<\r><\n>
>> [0.819747] pinctrl-single 44e10800.pinmux: pin 44e10854 already 
>> requested by 44e10800.pinmux; cannot claim for gpio-leds.8<\r><\n>
>> [0.831432] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) 
>> status -22<\r><\n>
>> [0.838714] pinctrl-single 44e10800.pinmux: could not request pin 21 
>> on device pinctrl-single<\r><\n>
>> [1.044647] Unhandled fault: external abort on non-linefetch (0x1008) 
>> at 0xe089c000<\r><\n>
>> [1.052776] Internal error: : 1008 [#1] SMP THUMB2<\r><\n>
>> [1.057847] Modules linked in:<\r><\n>
>> [1.061092] CPU: 0Not tainted  (3.8.13-bone50 #1)<\r><\n>
>> [1.066442] PC is at cpsw_probe+0x348/0x960<\r><\n>
>> [1.070871] LR is at ioremap_page_range+0x95/0xf8<\r><\n>
>> [1.075841] pc : []lr : []psr: 
>> a033<\r><\n>
>> [1.075841] sp : df071e18  ip :   fp : df0d3400<\r><\n>
>> [1.087964] r10: c081de48  r9 : de5fb800  

Re: [beagleboard] Re: BeagleBoard-X15 - seriously? :)

[Matthijs van Duin]

On 14 January 2015 at 17:17, Gerald Coley  wrote:

> I agree. But, the IP owners seem to be worried about someone copying their
> IP than they are using it and getting royalties.


*stares at the PCIe chapter again and wonders how that would be helpful*
 Is there some magic PDF-to-VHDL converter? ;-)

But I appreciate it's ultimately not within your (TI's) power to force the
issue since it's not your IP.

However, you guys are doing the same thing with some stuff that *is*
(afaik) your IP.  Can we have a real ICEPick-D manual please?  Debug
functionality is of pretty major importance.

And it's for example also pretty silly that docs on the Centaurus (DM814x)
ISS and HDVPSS subsystems are not publicly available when almost identical
instances of ISS are in the public OMAP4/5 TRMs, and HDVPSS appears to be
similar to Vayu's VIP/VPE/DSS (but much more limited and stuffed into a
single subsystem). Especially since TI doesn't really seem to be
maintaining a kernel for the DM81xx series anymore, it would be nice if the
necessary docs were available for third party efforts.

IVA-HD has also been lacking public documentation since its appearance in
the OMAP4 (and subsequently in Netra, Centaurus, and now Vayu).

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

[beagleboard] Re: Setting up a WiFi hotspot on BB black using WiFI USB adapter with RTL8188CUS chipset

[ftagius]

On Wednesday, January 14, 2015 at 5:16:51 PM UTC-5, AK@hobbyist wrote:
>
> Hi 
>
> I am new to Beagleboen black and am trying to set up a WiFi hotpspot on 
> Beagleboe Black using the USB adapters with RTL8188CUS chipset. I am not 
> able to create it. If somebody has done ti please let me know. Thanks
>

I have successfully set up my beaglebone black as an access point using a 
USB wifi adapter with the RTL8188CUS chipset. Here are the details:

Hardware:
Beaglebone Black rev C
LB link wireless usb adapter 
(http://chicagodist.com/products/long-range-wifi-usb-with-antenna-for-raspberry-pi)

Bone Software:
Debian GNU/Linux 7
Kernel - Linux beaglebone 3.8.13-bone69 
manually built rtl8188CUS device driver, 8192cu.ko (from sources at 
https://github.com/mcantarutti/ShopBot-API/tree/master/Arch_linux_config/rtl8188CUS-driver-beaglebone)
hostapd

Procedure:
The stock 8192cu driver worked as a client, but could not be setup as an 
access point.  Apparently the stock 8192cu driver does not have nl80211 
support, which I believe is needed for access point functionality.  I 
obtained the driver source from 
https://github.com/jlucidar/FabMo-Platform/tree/master/Arch_linux_config/rtl8188CUS-driver-beaglebone.
  
This source has nl80211 support.  I compiled the module from source and 
then replaced the stock 8192cu.ko file.  At the next boot hostapd 
successfully set up wlan0 as an access point.  As a bonus, the new version 
of the driver has concurrence enabled.  With this function, the 8192cu 
driver creates two wifi interfaces, wlan0 and wlan1.  I can use each of 
these wifi interfaces independently.

frank agius
 



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

[beagleboard] beaglebone black HD camera cape issue

[patelaxar1456]

Hello everyone

I need a help over this issue. I've bought a beaglebone black and its hd 
camera cape, Whenever i put the cape on the bbb board, the board is able to 
communicate computer from PuTTY terminals only by serial communication 
setting and doesn't work using SSH setting. Hence i cannot provide a 
internet connection to beaglebone using serial communication.
   The board runs fine when the cape is unattached. it is even able to 
connecte= to internet using serial communication.

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

[beagleboard] Kernel compile problem

[weidesire]

Hello

I was trying to add some modules into my kernel.
After selecting, the system tells me to insert "make" 

Then I got this error.

root@beaglebone:/usr/src/kernel# make
  CHK include/generated/uapi/linux/version.h
  CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
make[1]: *** No rule to make target `kernel/bounds.c', needed by 
`kernel/bounds.s'.  Stop.
make: *** [prepare0] Error 2

Does anyone know how to fix this?
Please help. Thank you very much!


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

[beagleboard] Cannot set mux to gpio

[stefan . mavrodiev]

Hello, 

I'm using beaglebone with kernel 3.12. I want to use I2c0-sda and i2c0-scl 
as gpio, but I cannot change multiplexing. 
I do NOT want to use overlay, but to rebuild dtb file. 

I've removed all i2c0 configuration and added multiplexing description but 
still my value is 0x60. (I2C)

Is it enough to add new node to am33xx_pinmux to change mux ?

&am33xx_pinmux { 
gpio3_pins_default: gpio3_pins_default {
pinctrl-single,pins = <
0x188 0x2f /* I2C0_SDA */
0x18c 0x2f /* I2C0_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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Load the MLO and U-BOOT in beaglebone black though USB port

[gokul . gcg]

hi

According to Silicon Errata SPRZ360 section 3.1.3 Boot:

USB Boot ROM Code Uses Default DATAPOLARITY .The AM335x USB PHYs supports a 
DATAPOLARITY feature that allows the data plus (DP) and data minus (DM) 
data signals to be swapped. This feature was added to simplify PCB 
layout.In some cases, the DP and DM data signals may need to cross over 
each other to connect to the respective USB connector pins. Crossing these 
signals on the PCB may cause signal integrity issues if not implemented 
properly since they must be routed as high-speed differential transmission 
lines. The DATAPOLARITY feature in the USB PHYs can be used resolve this 
issue.The DATAPOLARITY feature is controlled by DATAPOLARITY_INV (bit 23) 
of the respective USB_CTRL register.
The USB boot ROM code uses the default value for DATAPOLARITY_INV when 
booting from USB. Therefore, the PCB must be designed to use the default 
DATAPOLARITY if the system must support USB boot



How Beagle bone black  is designed . is this considered in the design ?

On Wednesday, January 14, 2015 at 9:53:07 PM UTC+5:30, RobertCNelson wrote:
>
> On Wed, Jan 14, 2015 at 7:00 AM,  > 
> wrote: 
> > How we can load the MLO and U-BOOT in beaglebone black though USB port? 
> I 
> > know it can be done by SD card/serial port  and it will load to eMMC but 
> if 
> > I have a USB stick/External HDD/USB connected to host, how can MLO and 
> UBOOT 
> > be fetch through USB port and able transfer directly to eMMC. 
> > 
> > Once these are done and we get the UBOOT prompt, we can surely upload 
> the 
> > kernel image to any of the known memory interfaces . 
>
> Well... It's not 100% of what you want.. but close.. 
>
> First flash this "console" eMMC flasher: 
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_.28All_Revs.29_eMMC_Flashers
>  
>
> After flashing has finished, remove microSD... 
>
> From u-boot: 
>
> ums 0 mmc 1 
>
> Now you can flash the "eMMC" thru usb the port.. (thanks to u-boot) 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BeagleBone Black doesn't sometimes start. Only Power LED is on

[martin . zoller]

Hi Mikkel,

I'm just wondering if Andrew's autoboot solution/hack hasn't 
> propagated to the official software yet? 
>
It's been a while that I haven't looked at the preinstalled software of a 
BBB since I get them pre-flashed with my own image...
The official Angstrom image releases for BBB seem to be 
at http://elinux.org/Beagleboard:Updating_The_Software (the page title is 
slightly misleading).
The most recent image dates from 2013-09-04, and the u-boot files on its 
boot partition are from 2013-06-19. This corresponds to the latest 
modification of [1], where apparently the u-boot patches for BBB are stored.
Clearly there is no fix yet! It looks like that repository is maintained by 
Koen Kooi, so maybe you can send him your patch.
Changing the upstream u-boot source probably doesn't make sense since the 
issue does not apply to other am335x-based systems.

Thumbs up, also for Guillermo ;). 
>
Indeed, I noticed that typo this morning. My apologies!

Thanks,
Martin

[1] 
- 
https://github.com/beagleboard/meta-beagleboard/tree/master/common-bsp/recipes-bsp/u-boot/u-boot-denx

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

Re: [beagleboard] Load the MLO and U-BOOT in beaglebone black though USB port

[gokul . gcg]

Hi all,

So as far as I know  we need to take support from TI for USB boot option . 
right?
Since we don't know what is actually expected by ROM code,we cant. is there 
any source available for ROM code ?

Gokul c g 
goku...@kalkitech.in
On Wednesday, January 14, 2015 at 9:53:07 PM UTC+5:30, RobertCNelson wrote:
>
> On Wed, Jan 14, 2015 at 7:00 AM,  > 
> wrote: 
> > How we can load the MLO and U-BOOT in beaglebone black though USB port? 
> I 
> > know it can be done by SD card/serial port  and it will load to eMMC but 
> if 
> > I have a USB stick/External HDD/USB connected to host, how can MLO and 
> UBOOT 
> > be fetch through USB port and able transfer directly to eMMC. 
> > 
> > Once these are done and we get the UBOOT prompt, we can surely upload 
> the 
> > kernel image to any of the known memory interfaces . 
>
> Well... It's not 100% of what you want.. but close.. 
>
> First flash this "console" eMMC flasher: 
>
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#BBB_.28All_Revs.29_eMMC_Flashers
>  
>
> After flashing has finished, remove microSD... 
>
> From u-boot: 
>
> ums 0 mmc 1 
>
> Now you can flash the "eMMC" thru usb the port.. (thanks to u-boot) 
>
> Regards, 
>
> -- 
> Robert Nelson 
> http://www.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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Reversed Image on LCD - BeagleBoard-xM Display Panel ULCD7

[stavros . pothoulakis]

I'll look into this possibility. So as I understand, that the resistor may 
be a "pull-up" or "pull-down", that sets a logic
level and hence the inversion?
 

On Thursday, January 15, 2015 at 4:02:36 AM UTC+11, Gerald wrote:

> Not sure why it  is. There are resistors on the board that set this 
> function.
>
> http://elinux.org/CircuitCo:BeagleBone_LCD7#BeagleBone_LCD7_Revision_A3
>
> This was an issue with older XM SW. Not sure if you got the latest or not.
>
> Gerald
>
> On Tue, Jan 13, 2015 at 9:56 PM, AuralOnslaught  > wrote:
>
>> Hi there,
>>
>> I have an issue with my screen display. I purchased the Beagleboard -xM 
>> and the Angstrom OS build (pre-built). 
>> So I haven't done anything novel or contentious with the OS. 
>>
>> The LCD was purchased from digikey as shown.
>>
>> http://www.digikey.com.au/catalog/en/partgroup/beagleboard-xm-display-panel-ulcd7/15428
>>
>> Despite whichever OS I boot up with and use, the image appears reversed, 
>> with text and images from 
>> right to left. (Much like Hebrew)
>>
>> Has anyone come across this issue and how do I overcome it? 
>>
>> 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...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Gerald
>  
> ger...@beagleboard.org 
> http://beagleboard.org/
> http://circuitco.com/support/
>  

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

Re: [beagleboard] BeagleBone Black doesn't sometimes start. Only Power LED is on

[Patrick Schmidt]

>
> Hi Andrew,
>>
> Thank you for your reply. I feel like this is steering me in the right 
direction but I have one more question. After I do the clean and configure 
steps, I am looking for the /include/config.h file but I don't see it 
anywhere. I do see it after I do the compile step so it must be created 
after the compilation. Maybe I am missing something and looking for the 
wrong thing. Once I get this worked out it is going to save me a lot of 
frustration so thank you for all your help. Oh and also the runtime config 
file sounds like something I want to check out but a google search didn't 
help me much. Which file would I be editing for this? Thank you!

>  
>>
>

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

Re: [beagleboard] USB Ethernet not starting after flashing image to eMMC

[Robert Nelson]

On Fri, Jan 16, 2015 at 7:23 AM, Steve Osselton
 wrote:
> I have been maintaining an up to data Ubuntu 14.04.1 image and TI kernel on
> an SD  card
> then flashing to the eMMC using bbb-eMMC-flasher-eewiki-ext4.sh
>
> Now when I do this the Bone appears not to have USB ethernet after rebooting
> to eMMC,
> am pretty sure this has worked previously. Booting from SD card and USB
> ethernet starts fine.
> Bote that bone is actually booting OK from eMMC as can connect via wired
> ethernet.
>
> Any ideas what is happening here?

That's expected... You ran "bbb-eMMC-flasher-eewiki-ext4.sh" which
creates a 'single' ext4 partition.

The g_multi driver only works with two or more partitions, thus the
logic just enables g_serial in that situation:

https://github.com/RobertCNelson/boot-scripts/blob/master/boot/am335x_evm.sh#L84

under: /opt/scripts/boot/am335x_evm.sh

Regards,

-- 
Robert Nelson
http://www.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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] USB Ethernet not starting after flashing image to eMMC

[Steve Osselton]

I have been maintaining an up to data Ubuntu 14.04.1 image and TI kernel on 
an SD  card
then flashing to the eMMC using bbb-eMMC-flasher-eewiki-ext4.sh

Now when I do this the Bone appears not to have USB ethernet after 
rebooting to eMMC,
am pretty sure this has worked previously. Booting from SD card and USB 
ethernet starts fine.
Bote that bone is actually booting OK from eMMC as can connect via wired 
ethernet. 

Any ideas what is happening here?

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

[beagleboard] Cloud9 don't work

[Santosh Nagargoje]

Cloud9 don't work when doing programming related to led blink. What can I do? 

-Original Message-
From: "beagleboard@googlegroups.com" 
Sent: ‎16-‎01-‎2015 03:16
To: "Digest recipients" 
Subject: [beagleboard] Digest for beagleboard@googlegroups.com - 25 updates in9 
topics

beagleboard@googlegroups.com Google Groups  

Topic digest 
View all topics 
BeagleBone Black as reliable 3G/4G router/ modem - 3 Updates 
SYS_5V rail timing on the BeagleBone - 2 Updates 
Still having problems compiling Kernel :( - 4 Updates 
ethernet gadget with beagleboard - 9 Updates 
Recompile kernel - 2 Updates 
Debugging bluetooth - 1 Update 
Checking GPIOpins for being healthy - 2 Updates 
BeagleBone Black doesn't sometimes start. Only Power LED is on - 1 Update 
bmp085 with uext connection with BBB - 1 Update 
BeagleBone Black as reliable 3G/4G router/ modem Miguel Aveiro 
: Jan 15 02:35PM -0200 

I've used 3 or 4 different Huawei usb 3G modems. All worked pretty 
easily. I'm using an old version of the RCN images with Debian Wheezy 
and kernel 3.8.13-bone51.
 
All the tutorials for 3G modem for linux in general works good in BBB. A 
good one is this:
https://www.thefanclub.co.za/how-to/how-setup-usb-3g-modem-raspberry-pi-using-usbmodeswitch-and-wvdial
 
And I've tested only one 4G modem. It needed a newer version of 
usb_modeswitch, which is available in the Jessie images of RCN:
http://elinux.org/BeagleBoardDebian#Debian_Testing_.28jessie.29
 
I think I had to recompile the kernel because one option was not turned 
on in the default kernel I used. But I don't remember which one. It was 
a long time ago and maybe this option is available now.
 
I haven't "shared" the 3G connection with the ethernet port, but I have 
already read somewhere that it can be accomplished with firestarter and 
dhcp3-server (to provide the IP's). Maybe this can help you.
 
Miguel Aveiro
 
 
On 14-01-2015 21:33, bremenpl wrote:

c...@isbd.net: Jan 15 09:12PM 

> I would like BeagleBone Black to do- get and then distribute internet.
> I would really aprichiate any help in here, it would be really great for me 
> to set this up.
 
openwrt maybe?
 
-- 
Chris Green
·

Bremenpl : Jan 15 10:31PM +0100 

Thanks for the tips. I was wondering about openwrt, but im not sure either 
everything is supported there. I could get more pain than usage i fear.
 
 


Back to top 
SYS_5V rail timing on the BeagleBone ybea...@rehut.com: Jan 15 12:24PM -0800 

Might also be of interest to others and I wanted a second opinion before 
making things more complex -
 
Does power from the SYS_5V rail meet timing to drive IO on the 
BeagleBone/AM335x? That is -
If I use SYS_5V to drive an always enabled 3.3V LDO, will the output of the 
LDO be safe to directly connect to an input GPIO.
 
The PMIC datasheet suggests it is not (it is the input to the 3.3V regulator 
on there). Delays in the 3.3V regulator would cause the 3.3V rail to come up 
later then the SYS_5V line. Checking before adding more switching and 
sequencing.
 
Thanks. 
-- 
Hunyue Yau
http://www.hy-research.com/

Gerald Coley : Jan 15 02:51PM -0600 

Basically,no. You need to enable the LDO with 3.3V rail on the expansion
header.
 
Gerald
 
 
-- 
Gerald
 
ger...@beagleboard.org
http://beagleboard.org/
http://circuitco.com/support/


Back to top 
Still having problems compiling Kernel :( rh_ : 
Jan 15 07:42AM -0800 

On Thu, 15 Jan 2015 02:58:46 -0500
 
> It is a software RAID, and I am struggling with Robert's scripts :(
 
I dunno anything about that. I can only say what I would do.
I would provide enough info about what I've tried so far then someone
might know right away what's up.

Robert Nelson : Jan 15 09:55AM -0600 

On Thu, Jan 15, 2015 at 1:58 AM, William Pretty Security
> Thanks RH;
 
> It is a software RAID, and I am struggling with Robert's scripts :(
 
Well,
 
CONFIG_MD_RAID
 
is already built as a module, what module do you actually need?
 
Regards,
 
-- 
Robert Nelson
http://www.rcn-ee.com/

"William Pretty Security" : Jan 15 01:09PM -0500 

> It is a software RAID, and I am struggling with Robert's scripts :(
 
I dunno anything about that. I can only say what I would do.
I would provide enough info about what I've tried so far then someone might 
know right away what's up.
 
Ok here we go:
 
A couple of months ago I was looking for a Debian image with software RAID 
support.
The one I was using did not. Robert kindly pointed me to one that, as it turned 
out had 'crippled' RAID
support. In that while 'md' was present none of the software RAID Modem modules 
were.
I tried to get some help just "adding" the modules support to my existing 
image. But nobody replied.
 
So I looked around an found the following instructions:
 
---
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev
git checkout origin/ti-linux-3.14.y -b tmp
./build_kernel.sh
 
After that kernel upgrades are as easy as:
 
wget http

[beagleboard] UART loopback

[philippe.frossard]

Hi,
I have a problem when I connect P9.24 (ttyO1.TX) with P9.26 (ttyO1.RX),
If I send data on serial port like this : echo 1 > /dev/ttyO1
And read data on serial port like this : cat /dev/ttyO1
The command output a lot of data indefinitely ... and my ssh link doesn't 
respond,
If I remove the jumper the system come back ...
What wrong ?

Same problem with ttyO2,
Same problem with ttyO1 connected to ttyO2

I'm using kernel  3.8.13-bone69 (trying also 40 and 47) with debian 7.7,
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.
For more options, visit https://groups.google.com/d/optout.