Re: [beagleboard] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

Did you build using Robert  guide on eewiki ? If so, you probably did not
install an ssh server such as openssh-server . . .

*william@eee-pc:~$ ssh debian@192.168.7.2 *
> *Debian GNU/Linux 7*
>
> *BeagleBoard.org Debian Image 2015-03-01*
>
> *Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
> *
>
> *default username:password is [debian:temppwd]*
>
> *debian@192.168.7.2 's password:*
> *Last login: Tue May 12 16:34:45 2015 from 192.168.7.1*
> *debian@beaglebone:~$ uname -r*
> *4.1.0-rc3-bone0*
>

Slightly older kernel here, but it should be the same. Well actually, I'm
running SYSV init daemon, so I suppose that could be systemd giving you
"problems". e.g. A systemd service may need to be enabled to get your ssh
server running at boot ? Knowing the process you went through to get a
working image would be helpful in nailing down what your issue is . . .

On Sun, May 17, 2015 at 9:12 PM, rattus  wrote:

> Hi - my weekend experiment was to build a Debian Jessie with
> 4.1.0-rc3-bone1.2 kernel image to play with; sadly, while it appears to be
> running, I have no way to communicate with it. Pings to its IP address are
> responded to promptly, but SSH login attempts are rejected immediately, and
> there is no apparent serial path either.
> I checked the SSH entries in /etc/init on the SD image; they appear to be
> set to enable the sshd server.
> Anyone able to coax the beast out of its shell?
>
> Thx, Mike
>
> --
> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

>
> *and there is no apparent serial path either*


For this, you would need g_serial.ko located in the kernel version+modules
directory. For me the path is:

/lib/modules/4.1.0-rc3-bone0/kernel/drivers/usb/gadget/legacy/g_serial.ko

You would need to add "g_serial" to the file located at /etc/modules,
assuming systemd does not stand in your way. Which supposedly systemd is
supposed to be backwards compatible with SYSV LSB init scripts, etc.

You would possibly also have to either setup a systemd service to start up
an agetty or similar connection. or modify /etc/inittab to reflect that
change. Which ever works for your use case.

On Mon, May 18, 2015 at 12:34 AM, William Hermans  wrote:

> Did you build using Robert  guide on eewiki ? If so, you probably did not
> install an ssh server such as openssh-server . . .
>
> *william@eee-pc:~$ ssh debian@192.168.7.2 *
>> *Debian GNU/Linux 7*
>>
>> *BeagleBoard.org Debian Image 2015-03-01*
>>
>> *Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>> *
>>
>> *default username:password is [debian:temppwd]*
>>
>> *debian@192.168.7.2 's password:*
>> *Last login: Tue May 12 16:34:45 2015 from 192.168.7.1*
>> *debian@beaglebone:~$ uname -r*
>> *4.1.0-rc3-bone0*
>>
>
> Slightly older kernel here, but it should be the same. Well actually, I'm
> running SYSV init daemon, so I suppose that could be systemd giving you
> "problems". e.g. A systemd service may need to be enabled to get your ssh
> server running at boot ? Knowing the process you went through to get a
> working image would be helpful in nailing down what your issue is . . .
>
> On Sun, May 17, 2015 at 9:12 PM, rattus  wrote:
>
>> Hi - my weekend experiment was to build a Debian Jessie with
>> 4.1.0-rc3-bone1.2 kernel image to play with; sadly, while it appears to be
>> running, I have no way to communicate with it. Pings to its IP address are
>> responded to promptly, but SSH login attempts are rejected immediately, and
>> there is no apparent serial path either.
>> I checked the SSH entries in /etc/init on the SD image; they appear to be
>> set to enable the sshd server.
>> Anyone able to coax the beast out of its shell?
>>
>> Thx, Mike
>>
>> --
>> 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.

[beagleboard] Using both CS signals of SPI1

[bremenpl]

Hello there,
I would like to interface with 2 separate devices on SPI1 bus of BeagleBone 
Black. I have found this dts with the spi1_cs1 pin commented out: 
https://github.com/beagleboard/linux/blob/3.8/firmware/capes/BB-SPIDEV1-00A0.dts
I was wondering if I reenable this pin, will I be able to use the 2 
separate cs 0 and 1? Will this overlay then show spidev1.0 and spidev1.1 in 
my devices?

-- 
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] will a buildroot build for BBB work out of the box?

[g4]

Apologies for the late follow-up here. I’ve pretty much the same problem. Using 
BR 2015.02 I get a sane looking set of outputs post build. 

u-boot spew follows.

Both mmc 0:1 and mmc 0:2 show the expected SD card content. It just looks like 
uEnv is wrong (?). 

Any help here would be much appreciated. TVMIA

---snip
micro SD card found
mmc0 is current device
gpio: pin 54 (gpio 54) value is 1
SD/MMC found on device 0
reading uEnv.txt
96 bytes read in 3 ms (31.3 KiB/s)
Loaded environment from uEnv.txt
Importing environment from mmc ...
Running uenvcmd ...
## Error: "loadimage" not defined
reading ramdisk.gz
** Unable to read file ramdisk.gz **
reading /am335x-boneblack.dtb
34004 bytes read in 9 ms (3.6 MiB/s)
Booting from ramdisk ...
Wrong Image Format for bootm command
ERROR: can't get kernel image!
gpio: pin 55 (gpio 55) value is 1
reading /uImage
** Unable to read file /uImage **
U-Boot#
---snip---

From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com] On 
Behalf Of Chris Morgan
Sent: 16 April 2015 03:09
To: beagleboard@googlegroups.com
Subject: Re: [beagleboard] will a buildroot build for BBB work out of the box?

On Wednesday, April 15, 2015, Robert P. J. Day  wrote:

  just a yes or no ... if i configure and build buildroot for a BBB,
will the generated artifacts simply "work" if i copy them to an
appropriately formatted SD card?

  i ask as i downloaded the current state of buildroot, did the
obligatory:

  $ make beaglebone_defconfig
  $ make

and got fairly predictable results:

-rw-rw-r--. 1 rpjday rpjday   34004 Apr 15 10:41 am335x-boneblack.dtb
-rw-rw-r--. 1 rpjday rpjday   32858 Apr 15 10:41 am335x-bone.dtb
-rw-rw-r--. 1 rpjday rpjday  102416 Apr 15 10:07 MLO
-rw-rw-r--. 1 rpjday rpjday 3013632 Apr 15 10:41 rootfs.ext2
-rw-rw-r--. 1 rpjday rpjday  364200 Apr 15 10:07 u-boot.img
-rw-rw-r--. 1 rpjday rpjday  96 Apr 15 10:41 uEnv.txt
-rwxrwxr-x. 1 rpjday rpjday 3600224 Apr 15 10:41 zImage

  *however*, without a chance to test this at the moment, i note that
the contents of uEnv.txt are kind of skimpy:

bootpart=0:1
bootdir=
uenvcmd=run loadimage;run loadramdisk;run findfdt;run loadfdt;run ramboot

as in, no reference to the kernel image file or the dtb file, so i'm
only assuming that all of that is somehow encoded in the u-boot.img.

  i'm going to dig deeper later, but can anyone who's done this verify
that just copying those artifacts to an SD card will give me a
bootable system? thanks.

rday

Hello.

I've seen your work on the yocto list.

It looks like you have most of the parts there. I think the am335x will use the 
file system and load the mlo. So yep, it looks like you can copy the files over 
and the bbb should boot off of it (assuming you hold the boot button or have 
zeroed out the first block of emmc). At least you should get into uboot. Not 
sure what that roofs.ext2 is but that's probably because we boot to another 
partition, that may work just fine.

Chris 
-- 
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] how to install non-gui vlc on beagleboard

[Gurpartap Singh]

how to get static ip on beagleboard Xm.


On Fri, May 15, 2015 at 11:33 PM, bzk0711 via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Gurpartap Singh  wrote:
> > Hi, I am using debian jessie on Beagleboard Xm.I want to know how i can
> > install vlc non-gui version on board using apt-get .
>
> Hi,
>
> There seems to be the vlc-nox package in jessie, as a quick search on
> packages.debian.org shows: https://packages.debian.org/jessie/vlc-nox
>
> Cheers
> --
> Patric Schmitz 
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/iPcLhrYppNA/unsubscribe.
> To unsubscribe from this group and all its topics, 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] how to install non-gui vlc on beagleboard

['Patric Schmitz' via BeagleBoard]

On Mon, 18 May 2015 17:27:32 +0530
Gurpartap Singh  wrote:

> how to get static ip on beagleboard Xm.

Please consult the debian documentation (for both of these issues
actually), there is nothing specific to the beagleboard about what
you are asking. Also, use a new mail subject for different issues
you have.

Best regards
-- 
Patric Schmitz 

-- 
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 root access

[Harke Smits]

Hello,

I must have done something stupid because all of a sudden /root is no 
longer existing or better probably: no more accessible. 
The ls command result starts with /bin . ends with /usr. But no /root 
anymore.
Very annoying of course. I also no longer have access to IO pins.

Please help.

Thanks in advance
Harke


  

-- 
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] Issue with multiple USB microphones, can't record sound

[Daniel Barbosa]

Hello.

I'm trying to record audio from 3 USB microphones, using ALSA.
When I connect 1 USB mic directly to the BBB, everything works fine. It 
gets recognized and it records without any issue.
However, when I connect the 3 USB mics to a USB hub (that connects to the 
BBB), the microphones aren't detected by ALSA. The microphones are 
connected and powered, they are listed by 'lsusb', but ALSA does not 
recognize them as sound cards and so, the mics can't be used to record 
sound.

I've tried changing ALSA related files (config files), but the mics remain 
undetected. If I connect just 1 mic directly to the BBB, it works without 
any issue.
Has anyone here with more experinece with ALSA knows what's going on and 
has any suggestion to solve this?  

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

Re: [beagleboard] Issue with multiple USB microphones, can't record sound

[Przemek Klosowski]

On Mon, May 18, 2015 at 9:08 AM, Daniel Barbosa  wrote:
> Hello.
>
> I'm trying to record audio from 3 USB microphones, using ALSA.
> When I connect 1 USB mic directly to the BBB, everything works fine. It gets
> recognized and it records without any issue.
> However, when I connect the 3 USB mics to a USB hub (that connects to the
> BBB), the microphones aren't detected by ALSA. The microphones are connected
> and powered, they are listed by 'lsusb', but ALSA does not recognize them as
> sound cards and so, the mics can't be used to record sound.

It could be simply a power problem---how are you powering your system?
If you're drawing extra power for your USB devices the usual advice is
to use a) powered hub b) use the BBB power jack and c) use externally
powered USB devices (like hard drives).

-- 
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] Why not 2 microSD slots instead of the current eMMC + microSD slot?

[kuolas]

I have a question about the inclusion of eMMC in the current BeagleBone 
Black.

Could it been cheaper to include 2 microSD slots instead of the current 
setup of eMMC + microSD?

I just wondered why it was included the eMMC, because, the board could have 
been cheaper without the eMMC (abeit getting the microSD cages was a 
problem once).

-- 
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: [Beaglebone] overclocking success

[kw9075yu]

Hello there Joe!
I've been looking everywhere trying to find where exactly I can modify the 
MPU PLL. 
If you could please point us in the right direction that would be great. 
Thank you.

On Thursday, March 1, 2012 at 3:55:15 AM UTC-8, Uncle Joe wrote:
>
> Fellow high performance computing enthusiasts, 
>
> I just overclocked my dog from 720MHz to 1152 MHz (only MPU PLL) ! 
> Take that you lazy dog! Get those ARMs moving! Crunch those numbers 
> like you mean it. 
>
> Strangely, increasing the TPS65217's  DCDC3  voltage from 1.1V to 1.3V 
> didn't add more overclocking room. I just realized OMAP3 is an 
> overclocker's dream. So many PLLs and clock dividers to play with. 
> I've also doubled the clock to the SGX graphics unit to 400MHz without 
> problem. Too bad I don't have the HDMI cape so that I can make a video 
> showing how much faster the graphics go. Next, I will attempt to 
> overclock the DDR2 memory from 266 MhZ to its 400MHz spec. 
>
> Has anyone pushed their board beyond 1.2 GHz? Anyways, I'd better 
> hide. Gerald Coley is going to come after me with a shotgun for 
> abusing his pet like he did to that cheating PCB vendor. Yikes! 
>
>
> ---before - 720 MHz-- 
>
> LINPACK benchmark, Single precision. 
> Machine precision:  6 digits. 
> Array size 200 X 200. 
> Average rolled and unrolled performance: 
>
> Reps Time(s) DGEFA   DGESL  OVERHEADKFLOPS 
>  
>   16   0.79  87.34%   5.06%   7.59%  30100.461 
>   32   1.60  88.13%   3.75%   8.12%  29895.688 
>   64   3.18  88.68%   2.52%   8.81%  30308.049 
>  128   6.37  88.70%   2.51%   8.79%  30255.896 
>  256  12.73  88.53%   2.59%   8.88%  30308.035 
>  512  25.47  89.05%   2.20%   8.76%  30255.877 
> 1024  50.93  88.65%   2.61%   8.74%  30255.879 
>
> --after - 1152 
> MHz 
>
> LINPACK benchmark, Single precision. 
> Machine precision:  6 digits. 
> Array size 200 X 200. 
> Average rolled and unrolled performance: 
>
> Reps Time(s) DGEFA   DGESL  OVERHEADKFLOPS 
>  
>   32   0.99  94.95%   1.01%   4.04%  46259.645 
>   64   1.96  90.31%   2.04%   7.65%  48559.863 
>  128   3.94  90.10%   3.30%   6.60%  47768.129 
>  256   7.86  89.69%   2.93%   7.38%  48293.012 
>  512  15.73  89.96%   2.48%   7.57%  48359.477 
> 1024  31.45  89.79%   2.80%   7.41%  48293.090 
> 2048  62.89  89.89%   2.61%   7.51%  48351.172 
>
>
> (synthetic test I made, measuring only raw arithmetic throughput) 
>
> --before - 720 
> MHz--- 
> 1.15017G int adds/s 
> 0.359117G int multiplies/s 
> 0.102649G float adds/s 
> 2.87421G neon int32 adds/s 
> 0.718913G neon int32 multiplies/s 
> 1.43731G neon float adds/s 
> 1.43813G neon float multiplies/s 
> 1.43747G neon float madds/s 
>
> --after - 1152 
> MhZ--- 
> 1.84078G int adds/s 
> 0.574921G int multiplies/s 
> 0.164397G float adds/s 
> 4.60351G neon int32 adds/s 
> 1.15064G neon int32 multiplies/s 
> 2.30213G neon float adds/s 
> 2.2995G neon float multiplies/s 
> 2.30176G neon float madds/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.

[beagleboard] Losing bytes in RX buffer?

[ralphvannellestijn]

I have a problem with ttyO4. It looks like something is emptying the uarts 
buffer.

When is run two bash scripts at the same time I can send characters and 
receive characters at the same time. The two files running parallel look 
like this (simplified):

1:
for ((x=0;x<100;x++)); do
echo -en '\xAA' > /dev/ttyO4
done

2:
for ((x=0;x<100;x++)); do
read -n 1 -t 1 < /dev/ttyO4
done

Number 1 is sending and I receive the 0xAA at number 2.

Now I try to combine these two files:

for ((x=0;x<100;x++)); do
echo -en '\xAA' > /dev/ttyO4
read -n 1 -t 1 < /dev/ttyO4
done

This does not work. So I write one byte and I am to late to receive this 
byte. When I use the bash script reading parallel it works again.

The 0xAA received at the RX, where does it go? Why isn't it in the 
Beaglebones (hardware) buffer? Is there some linux process reading these 
bytes before my own read (from the bash file) is ready to read?

-- 
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] Why not 2 microSD slots instead of the current eMMC + microSD slot?

[Gerald Coley]

eMMC is 8 bit wide. That makes it faster.

SD card cage plus SD card is more expensive than one eMMC. eMMC is cheaper.

Gerald


On Mon, May 18, 2015 at 7:54 AM,  wrote:

> I have a question about the inclusion of eMMC in the current BeagleBone
> Black.
>
> Could it been cheaper to include 2 microSD slots instead of the current
> setup of eMMC + microSD?
>
> I just wondered why it was included the eMMC, because, the board could
> have been cheaper without the eMMC (abeit getting the microSD cages was a
> problem once).
>
> --
> 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.

Re: [beagleboard] Losing bytes in RX buffer?

[Dr. H. Nikolaus Schaller]

read  I have a problem with ttyO4. It looks like something is emptying the uarts 
> buffer.
> 
> When is run two bash scripts at the same time I can send characters and 
> receive characters at the same time. The two files running parallel look like 
> this (simplified):
> 
> 1:
> for ((x=0;x<100;x++)); do
> echo -en '\xAA' > /dev/ttyO4
> done
> 
> 2:
> for ((x=0;x<100;x++)); do
> read -n 1 -t 1 < /dev/ttyO4
> done
> 
> Number 1 is sending and I receive the 0xAA at number 2.
> 
> Now I try to combine these two files:
> 
> for ((x=0;x<100;x++)); do
> echo -en '\xAA' > /dev/ttyO4
> read -n 1 -t 1 < /dev/ttyO4
> done
> 
> This does not work. So I write one byte and I am to late to receive this 
> byte. When I use the bash script reading parallel it works again.
> 
> The 0xAA received at the RX, where does it go? Why isn't it in the 
> Beaglebones (hardware) buffer? Is there some linux process reading these 
> bytes before my own read (from the bash file) is ready to read?
> 
> -- 
> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[rattus]

On Monday, May 18, 2015 at 1:35:06 AM UTC-6, William Hermans wrote:
>
> Did you build using Robert  guide on eewiki ? If so, you probably did not 
> install an ssh server such as openssh-server . . .
> ...
>
>> *Last login: Tue May 12 16:34:45 2015 from 192.168.7.1*
>> *debian@beaglebone:~$ uname -r*
>> *4.1.0-rc3-bone0*
>>
>  
> Slightly older kernel here, but it should be the same. Well actually, I'm 
> running SYSV init daemon, so I suppose that could be systemd giving you 
> "problems". e.g. A systemd service may need to be enabled to get your ssh 
> server running at boot ? Knowing the process you went through to get a 
> working image would be helpful in nailing down what your issue is . . .
>

Yes, I was running Robert's BBB instructions. I agree it's probably a 
systemd startup issue, but haven't been able to find setup instructions 
that merely altered file contents - which I can do while burning the SD - 
rather than using systemctl on a running system. Can't start SSH without 
SSH... although the full openssh-server package seems to have been 
installed in the debian-8.0-minimal... rootfs.

-- 
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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[rattus]

There's my question - how does one set up a systemd service to start up 
anything without running systemctl on the system?

On Monday, May 18, 2015 at 1:49:30 AM UTC-6, William Hermans wrote:
>
> *...*
>
>  

> You would possibly also have to either setup a systemd service to start up 
> an agetty or similar connection. or modify /etc/inittab to reflect that 
> change. Which ever works for your use case.
>
>

-- 
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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[Robert Nelson]

On Mon, May 18, 2015 at 10:30 AM, rattus  wrote:
> There's my question - how does one set up a systemd service to start up
> anything without running systemctl on the system?

You just symlink the *.service.

but ssh is running by default in the image.

more then likely, you have a board that needs the phy-search patch,
that's currently disabled in my v4.1.0-rcX tree..

login over serial thru the debug header to verify..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

[beagleboard] Re: Beaglebone root access

[Harke Smits]

sudo -i also does not work anymore.

On Monday, 18 May 2015 15:07:29 UTC+2, Harke Smits wrote:
>
> Hello,
>
> I must have done something stupid because all of a sudden /root is no 
> longer existing or better probably: no more accessible. 
> The ls command result starts with /bin . ends with /usr. But no /root 
> anymore.
> Very annoying of course. I also no longer have access to IO pins.
>
> Please help.
>
> Thanks in advance
> Harke
>
>
>   
>

-- 
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 root access

[William Hermans]

Sounds like it is time for you to "try out" a new image . . .

On Mon, May 18, 2015 at 8:50 AM, Harke Smits  wrote:

> sudo -i also does not work anymore.
>
>
> On Monday, 18 May 2015 15:07:29 UTC+2, Harke Smits wrote:
>>
>> Hello,
>>
>> I must have done something stupid because all of a sudden /root is no
>> longer existing or better probably: no more accessible.
>> The ls command result starts with /bin . ends with /usr. But no /root
>> anymore.
>> Very annoying of course. I also no longer have access to IO pins.
>>
>> Please help.
>>
>> Thanks in advance
>> Harke
>>
>>
>>
>>
>  --
> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

Better yet, enable g_serial, or g_ether.

@Robert, does systemd get in the way when trying to enable either of those
gadget drivers ? I know for me it was pretty easy, but don't think I dd'd
over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in preparation
was comment out the systemd init line in uEnv.txt

On Mon, May 18, 2015 at 8:36 AM, Robert Nelson 
wrote:

> On Mon, May 18, 2015 at 10:30 AM, rattus  wrote:
> > There's my question - how does one set up a systemd service to start up
> > anything without running systemctl on the system?
>
> You just symlink the *.service.
>
> but ssh is running by default in the image.
>
> more then likely, you have a board that needs the phy-search patch,
> that's currently disabled in my v4.1.0-rcX tree..
>
> login over serial thru the debug header to verify..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[Robert Nelson]

On Mon, May 18, 2015 at 11:17 AM, William Hermans  wrote:
> Better yet, enable g_serial, or g_ether.
>
> @Robert, does systemd get in the way when trying to enable either of those
> gadget drivers ? I know for me it was pretty easy, but don't think I dd'd
> over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in preparation
> was comment out the systemd init line in uEnv.txt

systemd actually does the right thing, even when it has to wait for us
to decide g_multi vs g_ether

btw, here's how the systemd serial-getty service was enabled for
ttyGS0 (without systemctr).. (when we modprobe g_multi and the
usb-slave device starts: usb flash, usb ether, & usb serial)

cp /lib/systemd/system/serial-getty@.service
/etc/systemd/system/serial-getty@ttyGS0.service
ln -s /etc/systemd/system/serial-getty@ttyGS0.service
/etc/systemd/system/getty.target.wants/serial-getty@ttyGS0.service

after g_multi is loaded, systemd correctly fires up the getty service
for usb serial...

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

Yeah Wheezy 7.8 is was. Pretty sure this would not work on Jessie. As
Jessie needs SYSV packages installed in order to use SYSV( uses systemd as
default ). However, systemd is supposed to be backwards compatible with
SYSV, so if you do not comment out the line i suggest below in uEnv.txt, it
may just work.

william@eee-pc:~/downloads/linux-images$ sudo dd if=/dev/zero of=/dev/sdb
bs=1024 count=22+0 records in
2+0 records out
2048 bytes (2.0 kB) copied, 0.255138 s, 8.0 kB/s

william@eee-pc:~/downloads/linux-images$ sudo dd
if=/home/william/downloads/linux-images/bone-debian-7.8-console-armhf-2015-03-01-2gb.img
of=/dev/sdb
3481600+0 records in
3481600+0 records out
1782579200 bytes (1.8 GB) copied, 560.021 s, 3.2 MB/s

OPTIONAL:

If like me you wish to disable systemd . . .period.

william@eee-pc:~$ mkdir tmp
william@eee-pc:~$ sudo mount /dev/sdb1 /home/wiliam/tmp
william@eee-pc:~$ sudo nano ~/tmp/boot/uEnv.txt

And change:
cmdline=quiet init=/lib/systemd/systemd
to
#cmdline=quiet init=/lib/systemd/systemd

If you then wish to have USB networking . . .

william@eee-pc:~$ sudo nano /etc/network/interfaces
# Ethernet/RNDIS gadget (g_ether)
# ... or on host side, usbnet and random hwaddr
# Note on some boards, usb0 is automaticly setup with an init script
# Add "auto usb0" if not using systemd
auto usb0
iface usb0 inet static
address 192.168.7.2
netmask 255.255.255.0
network 192.168.7.0
gateway 192.168.7.1

william@eee-pc:~$ sudo nano /etc/modules
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
g_ether

william@eee-pc:~$ sudo umount /home/william/tmp

william@eee-pc:~/downloads/linux-images$ sudo sync

remove sdcard from development host, place it into the beaglebone black.
Then power up the beaglebone black. Log into the beagelbone . . .

On Mon, May 18, 2015 at 9:17 AM, William Hermans  wrote:

> Better yet, enable g_serial, or g_ether.
>
> @Robert, does systemd get in the way when trying to enable either of those
> gadget drivers ? I know for me it was pretty easy, but don't think I dd'd
> over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in preparation
> was comment out the systemd init line in uEnv.txt
>
> On Mon, May 18, 2015 at 8:36 AM, Robert Nelson 
> wrote:
>
>> On Mon, May 18, 2015 at 10:30 AM, rattus  wrote:
>> > There's my question - how does one set up a systemd service to start up
>> > anything without running systemctl on the system?
>>
>> You just symlink the *.service.
>>
>> but ssh is running by default in the image.
>>
>> more then likely, you have a board that needs the phy-search patch,
>> that's currently disabled in my v4.1.0-rcX tree..
>>
>> login over serial thru the debug header to verify..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

err, wow just realized my noted are  riddled with mistakes . . . paths are
wrong, etc.

On Mon, May 18, 2015 at 9:23 AM, Robert Nelson 
wrote:

> On Mon, May 18, 2015 at 11:17 AM, William Hermans 
> wrote:
> > Better yet, enable g_serial, or g_ether.
> >
> > @Robert, does systemd get in the way when trying to enable either of
> those
> > gadget drivers ? I know for me it was pretty easy, but don't think I dd'd
> > over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in
> preparation
> > was comment out the systemd init line in uEnv.txt
>
> systemd actually does the right thing, even when it has to wait for us
> to decide g_multi vs g_ether
>
> btw, here's how the systemd serial-getty service was enabled for
> ttyGS0 (without systemctr).. (when we modprobe g_multi and the
> usb-slave device starts: usb flash, usb ether, & usb serial)
>
> cp /lib/systemd/system/serial-getty@.service
> /etc/systemd/system/serial-getty@ttyGS0.service
> ln -s /etc/systemd/system/serial-getty@ttyGS0.service
> /etc/systemd/system/getty.target.wants/serial-getty@ttyGS0.service
>
> after g_multi is loaded, systemd correctly fires up the getty service
> for usb serial...
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

@Robert, ah cool, but the idea was to help this person enable one of the
USB gadget devices via his / her dev machine. As it does not seem as though
he/she has access to a serial debug cable.

With sysv, I've done this, and know how to go about it, but with systemd .
. . yeah no idea.

On Mon, May 18, 2015 at 9:27 AM, William Hermans  wrote:

> err, wow just realized my noted are  riddled with mistakes . . . paths are
> wrong, etc.
>
> On Mon, May 18, 2015 at 9:23 AM, Robert Nelson 
> wrote:
>
>> On Mon, May 18, 2015 at 11:17 AM, William Hermans 
>> wrote:
>> > Better yet, enable g_serial, or g_ether.
>> >
>> > @Robert, does systemd get in the way when trying to enable either of
>> those
>> > gadget drivers ? I know for me it was pretty easy, but don't think I
>> dd'd
>> > over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in
>> preparation
>> > was comment out the systemd init line in uEnv.txt
>>
>> systemd actually does the right thing, even when it has to wait for us
>> to decide g_multi vs g_ether
>>
>> btw, here's how the systemd serial-getty service was enabled for
>> ttyGS0 (without systemctr).. (when we modprobe g_multi and the
>> usb-slave device starts: usb flash, usb ether, & usb serial)
>>
>> cp /lib/systemd/system/serial-getty@.service
>> /etc/systemd/system/serial-getty@ttyGS0.service
>> ln -s /etc/systemd/system/serial-getty@ttyGS0.service
>> /etc/systemd/system/getty.target.wants/serial-getty@ttyGS0.service
>>
>> after g_multi is loaded, systemd correctly fires up the getty service
>> for usb serial...
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> 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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[William Hermans]

So sounds as though *maybe* you're saying if "we" edit /etc/modules, and
add "g_serial" or "g_ether" or "g_multi". The respective service would
start ?

On Mon, May 18, 2015 at 9:31 AM, William Hermans  wrote:

> @Robert, ah cool, but the idea was to help this person enable one of the
> USB gadget devices via his / her dev machine. As it does not seem as though
> he/she has access to a serial debug cable.
>
> With sysv, I've done this, and know how to go about it, but with systemd .
> . . yeah no idea.
>
> On Mon, May 18, 2015 at 9:27 AM, William Hermans 
> wrote:
>
>> err, wow just realized my noted are  riddled with mistakes . . . paths
>> are wrong, etc.
>>
>> On Mon, May 18, 2015 at 9:23 AM, Robert Nelson 
>> wrote:
>>
>>> On Mon, May 18, 2015 at 11:17 AM, William Hermans 
>>> wrote:
>>> > Better yet, enable g_serial, or g_ether.
>>> >
>>> > @Robert, does systemd get in the way when trying to enable either of
>>> those
>>> > gadget drivers ? I know for me it was pretty easy, but don't think I
>>> dd'd
>>> > over a Jessie image. Wheezy 7.8 I'm thinking, and all I did in
>>> preparation
>>> > was comment out the systemd init line in uEnv.txt
>>>
>>> systemd actually does the right thing, even when it has to wait for us
>>> to decide g_multi vs g_ether
>>>
>>> btw, here's how the systemd serial-getty service was enabled for
>>> ttyGS0 (without systemctr).. (when we modprobe g_multi and the
>>> usb-slave device starts: usb flash, usb ether, & usb serial)
>>>
>>> cp /lib/systemd/system/serial-getty@.service
>>> /etc/systemd/system/serial-getty@ttyGS0.service
>>> ln -s /etc/systemd/system/serial-getty@ttyGS0.service
>>> /etc/systemd/system/getty.target.wants/serial-getty@ttyGS0.service
>>>
>>> after g_multi is loaded, systemd correctly fires up the getty service
>>> for usb serial...
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>> --
>>> For more options, visit http://beagleboard.org/discuss
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "BeagleBoard" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to beagleboard+unsubscr...@googlegroups.com.
>>> 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] Issue with multiple USB microphones, can't record sound

[Daniel Barbosa]

segunda-feira, 18 de Maio de 2015 às 14:48:58 UTC+1, Przemek Klosowski 
escreveu:
>
> On Mon, May 18, 2015 at 9:08 AM, Daniel Barbosa  > wrote: 
> > Hello. 
> > 
> > I'm trying to record audio from 3 USB microphones, using ALSA. 
> > When I connect 1 USB mic directly to the BBB, everything works fine. It 
> gets 
> > recognized and it records without any issue. 
> > However, when I connect the 3 USB mics to a USB hub (that connects to 
> the 
> > BBB), the microphones aren't detected by ALSA. The microphones are 
> connected 
> > and powered, they are listed by 'lsusb', but ALSA does not recognize 
> them as 
> > sound cards and so, the mics can't be used to record sound. 
>
> It could be simply a power problem---how are you powering your system? 
> If you're drawing extra power for your USB devices the usual advice is 
> to use a) powered hub b) use the BBB power jack and c) use externally 
> powered USB devices (like hard drives). 
>


I am using an external power source on the BBB power jack, with enough 
power to power everything. It's not a power problem (it doesn't seem to 
be). I tried using a powered hub, but the usb devices connected to it 
weren't even detected by the BBB.
The microphones I'm using (they are the Playstation Eye, a video camera 
with a mic) have a light that turns on when they are powered up, and they 
have the light on. They get listed as USB devices (using the 'lsusb' 
command), so they are indeed connected. However, when I list the recording 
devices (not the USB devices) connected to the BBB, nothing gets listed (if 
I connect just 1 mic directly to the BBB, it gets listed as a recording 
device). I haven't tried another hub, but it seems odd to detect the mic as 
a USB device and not as a recording device when it's connected to the hub. 
To be honest, it seems to be a software issue, some configuration of ALSA 
but I'm not sure.

-- 
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] Issue with multiple USB microphones, can't record sound

[Przemek Klosowski]

On Mon, May 18, 2015 at 1:14 PM, Daniel Barbosa  wrote:

> The microphones I'm using (they are the Playstation Eye, a video camera with
> a mic) have a light that turns on when they are powered up, and they have
> the light on. They get listed as USB devices (using the 'lsusb' command), so
> they are indeed connected. However, when I list the recording devices (not
> the USB devices) connected to the BBB, nothing gets listed (if I connect
> just 1 mic directly to the BBB, it gets listed as a recording device). I
> haven't tried another hub, but it seems odd to detect the mic as a USB
> device and not as a recording device when it's connected to the hub. To be
> honest, it seems to be a software issue, some configuration of ALSA but I'm
> not sure.
>
I agree, it does look like software. Does this setup run on your
desktop PC? I'd debug it on desktop and then start looking for
differences vs. the BBB. Sound is tricky: at the moment I don't have
sound on my own desktop (I think it's a confusion between the
motherboard sound card and the HDMI sound) and I have failed fixing it
so far.

-- 
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: Add a new cape for BeagleBone

[Pascal FIFRE]

Hi,

 

Did you receive my mail ?

 

Best regards,

Pascal

 

 

Pascal FIFRE

IOTYS

43, Garenne Poull ar Rouz

22300 LANNION

www.iotys.com

 

De : Pascal FIFRE [mailto:pascal.fi...@iotys.com] 
Envoyé : samedi 16 mai 2015 11:01
À : 'beagleboard@googlegroups.com'
Objet : RE: Add a new cape for BeagleBone

 

Hi,

 

Yesterday, I’ve told you that I‘ve created a wiki page for my new cape
IOTCape.

I’ve changed this wiki page to http://elinux.org/IOTYS:IOTCape.

 

Thanks a lot for your help.

 

Best Regards,

 

Pascal

 

 

Pascal FIFRE

IOTYS

43, Garenne Poull ar Rouz

22300 LANNION

www.iotys.com

 

De : Pascal FIFRE [mailto:pascal.fi...@iotys.com] 
Envoyé : vendredi 15 mai 2015 18:40
À : 'beagleboard@googlegroups.com'
Objet : Add a new cape for BeagleBone

 

Hi,

 

I want to add the my new cape (IOTCape) for BeagleBone to BeagleBone capes
site.

I’ve created a wiki page http://elinux.org/User:IOTCape  based on the

http://elinux.org/CircuitCo:BeagleBone_LCD3 wiki page.

 

Attached to this mail you will find :

* A user manual of this new cape.

* DTS file for cape

 

Thanks a lot for your help.

 

Best Regards,

 

Pascal FIFRE

IOTYS

43, Garenne Poull ar Rouz

22300 LANNION

www.iotys.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] will a buildroot build for BBB work out of the box?

[William Hermans]

Lets see what your uEnv.txt looks like.

On Mon, May 18, 2015 at 3:54 AM,  wrote:

> Apologies for the late follow-up here. I’ve pretty much the same problem.
> Using BR 2015.02 I get a sane looking set of outputs post build.
>
> u-boot spew follows.
>
> Both mmc 0:1 and mmc 0:2 show the expected SD card content. It just looks
> like uEnv is wrong (?).
>
> Any help here would be much appreciated. TVMIA
>
> ---snip
> micro SD card found
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> SD/MMC found on device 0
> reading uEnv.txt
> 96 bytes read in 3 ms (31.3 KiB/s)
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Running uenvcmd ...
> ## Error: "loadimage" not defined
> reading ramdisk.gz
> ** Unable to read file ramdisk.gz **
> reading /am335x-boneblack.dtb
> 34004 bytes read in 9 ms (3.6 MiB/s)
> Booting from ramdisk ...
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!
> gpio: pin 55 (gpio 55) value is 1
> reading /uImage
> ** Unable to read file /uImage **
> U-Boot#
> ---snip---
>
> From: beagleboard@googlegroups.com [mailto:beagleboard@googlegroups.com]
> On Behalf Of Chris Morgan
> Sent: 16 April 2015 03:09
> To: beagleboard@googlegroups.com
> Subject: Re: [beagleboard] will a buildroot build for BBB work out of the
> box?
>
> On Wednesday, April 15, 2015, Robert P. J. Day 
> wrote:
>
>   just a yes or no ... if i configure and build buildroot for a BBB,
> will the generated artifacts simply "work" if i copy them to an
> appropriately formatted SD card?
>
>   i ask as i downloaded the current state of buildroot, did the
> obligatory:
>
>   $ make beaglebone_defconfig
>   $ make
>
> and got fairly predictable results:
>
> -rw-rw-r--. 1 rpjday rpjday   34004 Apr 15 10:41 am335x-boneblack.dtb
> -rw-rw-r--. 1 rpjday rpjday   32858 Apr 15 10:41 am335x-bone.dtb
> -rw-rw-r--. 1 rpjday rpjday  102416 Apr 15 10:07 MLO
> -rw-rw-r--. 1 rpjday rpjday 3013632 Apr 15 10:41 rootfs.ext2
> -rw-rw-r--. 1 rpjday rpjday  364200 Apr 15 10:07 u-boot.img
> -rw-rw-r--. 1 rpjday rpjday  96 Apr 15 10:41 uEnv.txt
> -rwxrwxr-x. 1 rpjday rpjday 3600224 Apr 15 10:41 zImage
>
>   *however*, without a chance to test this at the moment, i note that
> the contents of uEnv.txt are kind of skimpy:
>
> bootpart=0:1
> bootdir=
> uenvcmd=run loadimage;run loadramdisk;run findfdt;run loadfdt;run ramboot
>
> as in, no reference to the kernel image file or the dtb file, so i'm
> only assuming that all of that is somehow encoded in the u-boot.img.
>
>   i'm going to dig deeper later, but can anyone who's done this verify
> that just copying those artifacts to an SD card will give me a
> bootable system? thanks.
>
> rday
>
> Hello.
>
> I've seen your work on the yocto list.
>
> It looks like you have most of the parts there. I think the am335x will
> use the file system and load the mlo. So yep, it looks like you can copy
> the files over and the bbb should boot off of it (assuming you hold the
> boot button or have zeroed out the first block of emmc). At least you
> should get into uboot. Not sure what that roofs.ext2 is but that's probably
> because we boot to another partition, that may work just fine.
>
> Chris
> --
> 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.
>

-- 
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] will a buildroot build for BBB work out of the box?

[Robert Nelson]

On Mon, May 18, 2015 at 5:54 AM,   wrote:
> Apologies for the late follow-up here. I’ve pretty much the same problem. 
> Using BR 2015.02 I get a sane looking set of outputs post build.
>
> u-boot spew follows.
>
> Both mmc 0:1 and mmc 0:2 show the expected SD card content. It just looks 
> like uEnv is wrong (?).
>
> Any help here would be much appreciated. TVMIA
>
> ---snip
> micro SD card found
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> SD/MMC found on device 0
> reading uEnv.txt
> 96 bytes read in 3 ms (31.3 KiB/s)
> Loaded environment from uEnv.txt
> Importing environment from mmc ...
> Running uenvcmd ...
> ## Error: "loadimage" not defined
> reading ramdisk.gz
> ** Unable to read file ramdisk.gz **
> reading /am335x-boneblack.dtb
> 34004 bytes read in 9 ms (3.6 MiB/s)
> Booting from ramdisk ...
> Wrong Image Format for bootm command
> ERROR: can't get kernel image!

Yuck! bootm!!

> gpio: pin 55 (gpio 55) value is 1
> reading /uImage
> ** Unable to read file /uImage **
> U-Boot#
> ---snip---

You have a really old bootloader in eMMC.. Robert's original post
assumes at-least the Debian May 2014 release or newer stored in eMMC..

http://beagleboard.org/latest-images

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

RE: [beagleboard] will a buildroot build for BBB work out of the box?

[g4]

Thanks.

> 
> You have a really old bootloader in eMMC.. Robert's original post assumes at-
> least the Debian May 2014 release or newer stored in eMMC..
> 
> http://beagleboard.org/latest-images
>

Ah. That would make an awful lot of sense. I will reflash and report back.

BR,


-- 
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: HDMI audio truncated

[Matteo Guallini]

One step more...

If i do "speaker-test -c2 -t wav" the first playng doesn't emit sound.

On Saturday, May 16, 2015 at 11:49:38 PM UTC+2, Matteo Guallini wrote:
>
> Hello,
>
> If I do "aplay /usr/share/sounds/alsa/Front_Right.wav" from SSH and from 
> command line the audio is truncated or missing.
> Truncated signify that the played sound is like "right" or "ight".
>
> The strange thing is that the sound is good if I open PCMANFM and i go to 
> /usr/share/sounds/alsa/
> then I select the "Front_Right.wav" with the right mouse button and I open 
> the file wiith alsagui.
>
> Youtube video don't play sound as well.
>

-- 
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: Add a new cape for BeagleBone

[Peter Lawler]

On 19/05/15 03:07, Pascal FIFRE wrote:
> Hi,
> 
>  
> 
> Did you receive my mail ?

Yes we did. I (and I can't speak for others but would not be surprised
if similar there) suspect you aren't receiving the responses.

Please see Gerald's comments:
https://groups.google.com/d/msg/beagleboard/5uADXLOfZzw/I-WFZb4QmHEJ
https://groups.google.com/d/msg/beagleboard/5uADXLOfZzw/qknY4wixk74J
(and as an aside you may be interested in Wulf Man's comment)
https://groups.google.com/d/msg/beagleboard/5uADXLOfZzw/Q_0F_u84mE4J


P.

> 
>  
> 
> Best regards,
> 
> Pascal
> 
>  
> 
>  
> 
> Pascal FIFRE
> 
> IOTYS
> 
> 43, Garenne Poull ar Rouz
> 
> 22300 LANNION
> 
> www.iotys.com
> 
>  
> 
> De : Pascal FIFRE [mailto:pascal.fi...@iotys.com] 
> Envoyé : samedi 16 mai 2015 11:01
> À : 'beagleboard@googlegroups.com'
> Objet : RE: Add a new cape for BeagleBone
> 
>  
> 
> Hi,
> 
>  
> 
> Yesterday, I’ve told you that I‘ve created a wiki page for my new cape
> IOTCape.
> 
> I’ve changed this wiki page to http://elinux.org/IOTYS:IOTCape.
> 
>  
> 
> Thanks a lot for your help.
> 
>  
> 
> Best Regards,
> 
>  
> 
> Pascal
> 
>  
> 
>  
> 
> Pascal FIFRE
> 
> IOTYS
> 
> 43, Garenne Poull ar Rouz
> 
> 22300 LANNION
> 
> www.iotys.com
> 
>  
> 
> De : Pascal FIFRE [mailto:pascal.fi...@iotys.com] 
> Envoyé : vendredi 15 mai 2015 18:40
> À : 'beagleboard@googlegroups.com'
> Objet : Add a new cape for BeagleBone
> 
>  
> 
> Hi,
> 
>  
> 
> I want to add the my new cape (IOTCape) for BeagleBone to BeagleBone capes
> site.
> 
> I’ve created a wiki page http://elinux.org/User:IOTCape  based on the
> 
> http://elinux.org/CircuitCo:BeagleBone_LCD3 wiki page.
> 
>  
> 
> Attached to this mail you will find :
> 
> * A user manual of this new cape.
> 
> * DTS file for cape
> 
>  
> 
> Thanks a lot for your help.
> 
>  
> 
> Best Regards,
> 
>  
> 
> Pascal FIFRE
> 
> IOTYS
> 
> 43, Garenne Poull ar Rouz
> 
> 22300 LANNION
> 
> www.iotys.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] 4.1.0-rc3-bone1.2 trapped in board - no SSH or serial

[rattus]

I dropped back to 3.14 in the meantime; ssh is healthy there, as my main 
intent was to mess with kernel modules.

Thanks.

On Monday, May 18, 2015 at 9:36:47 AM UTC-6, RobertCNelson wrote:
>
> On Mon, May 18, 2015 at 10:30 AM, rattus > 
> wrote: 
> > There's my question - how does one set up a systemd service to start up 
> > anything without running systemctl on the system? 
>
> You just symlink the *.service. 
>
> but ssh is running by default in the image. 
>
> more then likely, you have a board that needs the phy-search patch, 
> that's currently disabled in my v4.1.0-rcX tree.. 
>
> login over serial thru the debug header to verify.. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

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

Re: [beagleboard] Re: Disabling HDMI makes mounted drives not authorized

[Jack Fisher]

William and Sam,

Just a newb trying to follow along and learn, byt he serial debug cable you 
mean the FTDI 3.3V serial-USB cable with the six pin  header? It seems this 
one gives insight at a lower level than the straight mini-USB port...

Sorry for my gross ignorance, but I am working on that...

Regards,

Jack

On Thursday, May 7, 2015 at 6:14:47 PM UTC-7, Sam wrote:
>
> Don't be sorry! I appreciate the help. 
> It's a bit weird. Especially since no one else seems to be having the 
> issue. 
> I'll order myself a cable and continue the investigation. 
>
> On Fri, 8 May 2015 9:59 am William Hermans > 
> wrote:
>
>> Sorry I couldn't help more Sam . . .
>>
>> This problem seems kind of obscure to me. I do not remember reading 
>> about, or hearing of a similar issue. If you did happen to buy, or borrow a 
>> serial debug cable. You could run both configurations, logging the boot log 
>> output to file. Then run a diff on them to see if anything stands out.
>>
>> You can also try this with dmesg . . . and . . . just poking around 
>> myself . . .
>>
>> debian@beaglebone:~$* dmesg > ~/file*
>> debian@beaglebone:~$ *nano ./file*
>>
>> *[3.590829] bone-pinmux-helper P8_27_pinmux.18: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.598760] bone-pinmux-helper P8_28_pinmux.19: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.606640] bone-pinmux-helper P8_29_pinmux.20: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.614507] bone-pinmux-helper P8_30_pinmux.21: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.622286] bone-pinmux-helper P8_31_pinmux.22: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.630087] bone-pinmux-helper P8_32_pinmux.23: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.637903] bone-pinmux-helper P8_33_pinmux.24: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.645782] bone-pinmux-helper P8_34_pinmux.25: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.653558] bone-pinmux-helper P8_35_pinmux.26: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.661459] bone-pinmux-helper P8_36_pinmux.27: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.669453] bone-pinmux-helper P8_37_pinmux.28: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.677472] bone-pinmux-helper P8_38_pinmux.29: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.685519] bone-pinmux-helper P8_39_pinmux.30: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.693538] bone-pinmux-helper P8_40_pinmux.31: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.701634] bone-pinmux-helper P8_41_pinmux.32: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.709755] bone-pinmux-helper P8_42_pinmux.33: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.717978] bone-pinmux-helper P8_43_pinmux.34: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.726225] bone-pinmux-helper P8_44_pinmux.35: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.734519] bone-pinmux-helper P8_45_pinmux.36: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.742802] bone-pinmux-helper P8_46_pinmux.37: Set initial pinmux 
>>> mode to hdmi*
>>> *[3.756370] bone-pinmux-helper P9_19_pinmux.46: Set initial pinmux 
>>> mode to i2c*
>>> *[3.764617] bone-pinmux-helper P9_20_pinmux.47: Set initial pinmux 
>>> mode to i2c*
>>> *[3.777412] bone-pinmux-helper P9_25_pinmux.52: Set initial pinmux 
>>> mode to audio*
>>> *[3.789016] bone-pinmux-helper P9_28_pinmux.55: Set initial pinmux 
>>> mode to audio*
>>> *[3.798144] bone-pinmux-helper P9_29_pinmux.56: Set initial pinmux 
>>> mode to audio*
>>>
>>
>> I wonder if somehow pinmux-helper could somehow be causing issues here ?
>>
>> On Thu, May 7, 2015 at 2:01 PM, Sam Thomas > > wrote:
>>
>>> I am pretty sure it isn't a pin conflict since I can remote desktop in 
>>> as root and access the mounted drives no problem. 
>>>
>>> Something strange is happening to my permissions as soon as I run 
>>> uEnv.txt
>>>
>>> I have checked my sudoers file and nothing in there has changed.
>>>
>>> Unfortunately I don't have a usb to serial cable.
>>>
>>> Thanks for your help William
>>>
>>> On Thu, 7 May 2015 at 08:49 William Hermans >> > wrote:
>>>
 So, the comment by me above "sounds like a pin conflict", doesn't mean 
 I think for a second that it *is* a pin conflict. I just meant that it is 
 a 
 "reaction" one might expect from having a pin conflict . . . the sdcard, 
 and hdmi should be able to work properly at the same time.

 I seem to recall reading something about a udev rule fix a long time 
 back - For situations like these but . . . What I am "remembering" is 
 rather vague in my mind at the moment.

 On Wed, May 6, 2015 at 3:40 PM, William Hermans >>> > wrote:

> Sounds like a possible pin conflict but . . .
>
> I was reading an ARCHLinux post concerning a similar problem( but on 
> PC ), and the person fixed it by making some additions to the PAM 
> configuration file.
>
> https://bbs.archlinux.org/viewtopic.php?id=167947
>
> ( post #

Re: [beagleboard] TESTERS WANTED: beaglebone's cape manager

[William Hermans]

Robert,

So whats up with the LPAE kernel versions ? From what I've read this
"extension" is only for Cortex A15 ( 40 bit addressing ), and typically /
always this only matters for systems with more than 4GB( addressable ) RAM.

The beaglebone black only has 512MB, so is moot, and the X15 from what I
understand will only have 2GB RAM ? Plus it's not a "bone"

Also while on the subject, what are these *-armv7-x0 kernels ?  Searching
the web is not very forthcoming. LPAE was kind of obvious, just was not
aware that it was an "ARM extension".

On Thu, May 14, 2015 at 9:57 AM, Robert Nelson 
wrote:

> The repo is now on: https://github.com/beagleboard/
>
> https://github.com/beagleboard/bb.org-overlays
>
> Cape Issue tracker:
> https://github.com/beagleboard/bb.org-overlays/issues
>
> Pleases fork and add support for your capes! ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> 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: Disabling HDMI makes mounted drives not authorized

[William Hermans]

>
> *just a newb trying to follow along and learn, byt he serial debug cable
> you mean the FTDI 3.3V serial-USB cable with the six pin  header? It seems
> this one gives insight at a lower level than the straight mini-USB port...*
>

Yes. The USB serial gadget driver is not funcitonal until the OS has
control, and loads the driver. Where as the serial debug is functional far
earlier. From memory, the serial debug serial interface is loaded late
x-loader / MLO, but either way. For all intents and purposes. When u-boot
is loaded into memory( and operational ), this is where you have
communication potential with the system.

This means you're able to view all uboot output, as well as when the kernel
takes control of the board. You get all boot up kernel output as well. With
the USB gadget, you will not get any ouput until late Linux boot, if any at
all.

The main purpose of the serial debug cable is exactly as the name implies.
"Debugging" in the sense of something akin to code debugging using printf()
in C. But it can also come in handy in a pinch for other uses as well. Such
as gaining access to the board when there are no other means.

On Mon, May 18, 2015 at 4:27 PM, Jack Fisher  wrote:

> William and Sam,
>
> Just a newb trying to follow along and learn, byt he serial debug cable
> you mean the FTDI 3.3V serial-USB cable with the six pin  header? It seems
> this one gives insight at a lower level than the straight mini-USB port...
>
> Sorry for my gross ignorance, but I am working on that...
>
> Regards,
>
> Jack
>
> On Thursday, May 7, 2015 at 6:14:47 PM UTC-7, Sam wrote:
>>
>> Don't be sorry! I appreciate the help.
>> It's a bit weird. Especially since no one else seems to be having the
>> issue.
>> I'll order myself a cable and continue the investigation.
>>
>> On Fri, 8 May 2015 9:59 am William Hermans  wrote:
>>
>>> Sorry I couldn't help more Sam . . .
>>>
>>> This problem seems kind of obscure to me. I do not remember reading
>>> about, or hearing of a similar issue. If you did happen to buy, or borrow a
>>> serial debug cable. You could run both configurations, logging the boot log
>>> output to file. Then run a diff on them to see if anything stands out.
>>>
>>> You can also try this with dmesg . . . and . . . just poking around
>>> myself . . .
>>>
>>> debian@beaglebone:~$* dmesg > ~/file*
>>> debian@beaglebone:~$ *nano ./file*
>>>
>>> *[3.590829] bone-pinmux-helper P8_27_pinmux.18: Set initial pinmux
 mode to hdmi*
 *[3.598760] bone-pinmux-helper P8_28_pinmux.19: Set initial pinmux
 mode to hdmi*
 *[3.606640] bone-pinmux-helper P8_29_pinmux.20: Set initial pinmux
 mode to hdmi*
 *[3.614507] bone-pinmux-helper P8_30_pinmux.21: Set initial pinmux
 mode to hdmi*
 *[3.622286] bone-pinmux-helper P8_31_pinmux.22: Set initial pinmux
 mode to hdmi*
 *[3.630087] bone-pinmux-helper P8_32_pinmux.23: Set initial pinmux
 mode to hdmi*
 *[3.637903] bone-pinmux-helper P8_33_pinmux.24: Set initial pinmux
 mode to hdmi*
 *[3.645782] bone-pinmux-helper P8_34_pinmux.25: Set initial pinmux
 mode to hdmi*
 *[3.653558] bone-pinmux-helper P8_35_pinmux.26: Set initial pinmux
 mode to hdmi*
 *[3.661459] bone-pinmux-helper P8_36_pinmux.27: Set initial pinmux
 mode to hdmi*
 *[3.669453] bone-pinmux-helper P8_37_pinmux.28: Set initial pinmux
 mode to hdmi*
 *[3.677472] bone-pinmux-helper P8_38_pinmux.29: Set initial pinmux
 mode to hdmi*
 *[3.685519] bone-pinmux-helper P8_39_pinmux.30: Set initial pinmux
 mode to hdmi*
 *[3.693538] bone-pinmux-helper P8_40_pinmux.31: Set initial pinmux
 mode to hdmi*
 *[3.701634] bone-pinmux-helper P8_41_pinmux.32: Set initial pinmux
 mode to hdmi*
 *[3.709755] bone-pinmux-helper P8_42_pinmux.33: Set initial pinmux
 mode to hdmi*
 *[3.717978] bone-pinmux-helper P8_43_pinmux.34: Set initial pinmux
 mode to hdmi*
 *[3.726225] bone-pinmux-helper P8_44_pinmux.35: Set initial pinmux
 mode to hdmi*
 *[3.734519] bone-pinmux-helper P8_45_pinmux.36: Set initial pinmux
 mode to hdmi*
 *[3.742802] bone-pinmux-helper P8_46_pinmux.37: Set initial pinmux
 mode to hdmi*
 *[3.756370] bone-pinmux-helper P9_19_pinmux.46: Set initial pinmux
 mode to i2c*
 *[3.764617] bone-pinmux-helper P9_20_pinmux.47: Set initial pinmux
 mode to i2c*
 *[3.777412] bone-pinmux-helper P9_25_pinmux.52: Set initial pinmux
 mode to audio*
 *[3.789016] bone-pinmux-helper P9_28_pinmux.55: Set initial pinmux
 mode to audio*
 *[3.798144] bone-pinmux-helper P9_29_pinmux.56: Set initial pinmux
 mode to audio*

>>>
>>> I wonder if somehow pinmux-helper could somehow be causing issues here ?
>>>
>>> On Thu, May 7, 2015 at 2:01 PM, Sam Thomas 
>>> wrote:
>>>
 I am pretty sure it isn't a pin conflict since I can remote desktop in
 as r

Re: [beagleboard] Re: Disabling HDMI makes mounted drives not authorized

[William Hermans]

As an aside / semi correction to what I wrote.  I believe that u-boot has
the USB serial gadget built in. Not sure how to go about using it, but I
also believe it has to be loaded by u-boot first so will not give you as
much output as a serial debug cable.

If you're wondering if an FTDI cable is worth the $20 . . . it is. However
I actually got a $2 prolific cable off ebay from China. That works fine.
It's exactly the same as the new one ADA Fruit sells. You just need to make
sure it's 3v3 TTL. If this is confusing to you, just stick with the
recommended cables / adapters from the beagleboard.org ewiki pages.

On Mon, May 18, 2015 at 4:50 PM, William Hermans  wrote:

> *just a newb trying to follow along and learn, byt he serial debug cable
>> you mean the FTDI 3.3V serial-USB cable with the six pin  header? It seems
>> this one gives insight at a lower level than the straight mini-USB port...*
>>
>
> Yes. The USB serial gadget driver is not funcitonal until the OS has
> control, and loads the driver. Where as the serial debug is functional far
> earlier. From memory, the serial debug serial interface is loaded late
> x-loader / MLO, but either way. For all intents and purposes. When u-boot
> is loaded into memory( and operational ), this is where you have
> communication potential with the system.
>
> This means you're able to view all uboot output, as well as when the
> kernel takes control of the board. You get all boot up kernel output as
> well. With the USB gadget, you will not get any ouput until late Linux
> boot, if any at all.
>
> The main purpose of the serial debug cable is exactly as the name implies.
> "Debugging" in the sense of something akin to code debugging using printf()
> in C. But it can also come in handy in a pinch for other uses as well. Such
> as gaining access to the board when there are no other means.
>
> On Mon, May 18, 2015 at 4:27 PM, Jack Fisher  wrote:
>
>> William and Sam,
>>
>> Just a newb trying to follow along and learn, byt he serial debug cable
>> you mean the FTDI 3.3V serial-USB cable with the six pin  header? It seems
>> this one gives insight at a lower level than the straight mini-USB port...
>>
>> Sorry for my gross ignorance, but I am working on that...
>>
>> Regards,
>>
>> Jack
>>
>> On Thursday, May 7, 2015 at 6:14:47 PM UTC-7, Sam wrote:
>>>
>>> Don't be sorry! I appreciate the help.
>>> It's a bit weird. Especially since no one else seems to be having the
>>> issue.
>>> I'll order myself a cable and continue the investigation.
>>>
>>> On Fri, 8 May 2015 9:59 am William Hermans  wrote:
>>>
 Sorry I couldn't help more Sam . . .

 This problem seems kind of obscure to me. I do not remember reading
 about, or hearing of a similar issue. If you did happen to buy, or borrow a
 serial debug cable. You could run both configurations, logging the boot log
 output to file. Then run a diff on them to see if anything stands out.

 You can also try this with dmesg . . . and . . . just poking around
 myself . . .

 debian@beaglebone:~$* dmesg > ~/file*
 debian@beaglebone:~$ *nano ./file*

 *[3.590829] bone-pinmux-helper P8_27_pinmux.18: Set initial pinmux
> mode to hdmi*
> *[3.598760] bone-pinmux-helper P8_28_pinmux.19: Set initial pinmux
> mode to hdmi*
> *[3.606640] bone-pinmux-helper P8_29_pinmux.20: Set initial pinmux
> mode to hdmi*
> *[3.614507] bone-pinmux-helper P8_30_pinmux.21: Set initial pinmux
> mode to hdmi*
> *[3.622286] bone-pinmux-helper P8_31_pinmux.22: Set initial pinmux
> mode to hdmi*
> *[3.630087] bone-pinmux-helper P8_32_pinmux.23: Set initial pinmux
> mode to hdmi*
> *[3.637903] bone-pinmux-helper P8_33_pinmux.24: Set initial pinmux
> mode to hdmi*
> *[3.645782] bone-pinmux-helper P8_34_pinmux.25: Set initial pinmux
> mode to hdmi*
> *[3.653558] bone-pinmux-helper P8_35_pinmux.26: Set initial pinmux
> mode to hdmi*
> *[3.661459] bone-pinmux-helper P8_36_pinmux.27: Set initial pinmux
> mode to hdmi*
> *[3.669453] bone-pinmux-helper P8_37_pinmux.28: Set initial pinmux
> mode to hdmi*
> *[3.677472] bone-pinmux-helper P8_38_pinmux.29: Set initial pinmux
> mode to hdmi*
> *[3.685519] bone-pinmux-helper P8_39_pinmux.30: Set initial pinmux
> mode to hdmi*
> *[3.693538] bone-pinmux-helper P8_40_pinmux.31: Set initial pinmux
> mode to hdmi*
> *[3.701634] bone-pinmux-helper P8_41_pinmux.32: Set initial pinmux
> mode to hdmi*
> *[3.709755] bone-pinmux-helper P8_42_pinmux.33: Set initial pinmux
> mode to hdmi*
> *[3.717978] bone-pinmux-helper P8_43_pinmux.34: Set initial pinmux
> mode to hdmi*
> *[3.726225] bone-pinmux-helper P8_44_pinmux.35: Set initial pinmux
> mode to hdmi*
> *[3.734519] bone-pinmux-helper P8_45_pinmux.36: Set initial pinmux
> mode to hdmi*
> *[3.742802] bo

Re: [beagleboard] TESTERS WANTED: beaglebone's cape manager

[Robert Nelson]

On Mon, May 18, 2015 at 6:34 PM, William Hermans  wrote:
> Robert,
>
> So whats up with the LPAE kernel versions ? From what I've read this
> "extension" is only for Cortex A15 ( 40 bit addressing ), and typically /
> always this only matters for systems with more than 4GB( addressable ) RAM.
>
> The beaglebone black only has 512MB, so is moot, and the X15 from what I
> understand will only have 2GB RAM ? Plus it's not a "bone"

Large Physical Address Extensions (LPAE) is the main identifier, but
the Cortex-A7/A12/A15/A17 also have hardware virturalization support.

>
> Also while on the subject, what are these *-armv7-x0 kernels ?  Searching
> the web is not very forthcoming. LPAE was kind of obvious, just was not
> aware that it was an "ARM extension".

The armv7 label just matches up with ARM: ARMv7-A instruction set architecture.

Any Cortex-Ax device should boot with it.

btw, the config delta between armv7 & bone is getting smaller with
every kernel release.  In v4.1-rcX erratum 430973 (thumb2 r1pX
omap3/dm3730) was minimized to only affect performance on affected
cores. So it doesn't slow down none Cortex-A8 devices anymore.  And
cores such as am335x (r3px) which we enable thumb2 across the board
(bone kernel) aren't affected as much..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] TESTERS WANTED: beaglebone's cape manager

[Robert Nelson]

On Mon, May 18, 2015 at 7:11 PM, Robert Nelson  wrote:
> On Mon, May 18, 2015 at 6:34 PM, William Hermans  wrote:
>> Robert,
>>
>> So whats up with the LPAE kernel versions ? From what I've read this
>> "extension" is only for Cortex A15 ( 40 bit addressing ), and typically /
>> always this only matters for systems with more than 4GB( addressable ) RAM.
>>
>> The beaglebone black only has 512MB, so is moot, and the X15 from what I
>> understand will only have 2GB RAM ? Plus it's not a "bone"
>
> Large Physical Address Extensions (LPAE) is the main identifier, but
> the Cortex-A7/A12/A15/A17 also have hardware virturalization support.

I should also mention... Just like non-pae and pae x86 hardware..

a non-lpae device will not boot with an lpae enabled kernel. Thus we
have a special lpae kernel. ;)

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] TESTERS WANTED: beaglebone's cape manager

[William Hermans]

>
> *I should also mention... Just like non-pae and pae x86 hardware..*
>
> * a non-lpae device will not boot with an lpae enabled kernel. Thus we*
> * have a special lpae kernel. ;)*


What use is this in the context of the beaglebone ? The X15 I can see use
cases, and I'm sure you're not allowed to talk about that platform. Which
is fine. But am I missing something about this in the context of the
beaglebone black ?


On Mon, May 18, 2015 at 5:13 PM, Robert Nelson 
wrote:

> On Mon, May 18, 2015 at 7:11 PM, Robert Nelson 
> wrote:
> > On Mon, May 18, 2015 at 6:34 PM, William Hermans 
> wrote:
> >> Robert,
> >>
> >> So whats up with the LPAE kernel versions ? From what I've read this
> >> "extension" is only for Cortex A15 ( 40 bit addressing ), and typically
> /
> >> always this only matters for systems with more than 4GB( addressable )
> RAM.
> >>
> >> The beaglebone black only has 512MB, so is moot, and the X15 from what I
> >> understand will only have 2GB RAM ? Plus it's not a "bone"
> >
> > Large Physical Address Extensions (LPAE) is the main identifier, but
> > the Cortex-A7/A12/A15/A17 also have hardware virturalization support.
>
> I should also mention... Just like non-pae and pae x86 hardware..
>
> a non-lpae device will not boot with an lpae enabled kernel. Thus we
> have a special lpae kernel. ;)
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to beagleboard+unsubscr...@googlegroups.com.
> 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] TESTERS WANTED: beaglebone's cape manager

[William Hermans]

And yeah. With x86 systems, you had to have a system board ( motherboard )
that had 36bit->40bit memory addressing as a configurable option.

On Mon, May 18, 2015 at 5:19 PM, William Hermans  wrote:

> *I should also mention... Just like non-pae and pae x86 hardware..*
>>
>> * a non-lpae device will not boot with an lpae enabled kernel. Thus we*
>> * have a special lpae kernel. ;)*
>
>
> What use is this in the context of the beaglebone ? The X15 I can see use
> cases, and I'm sure you're not allowed to talk about that platform. Which
> is fine. But am I missing something about this in the context of the
> beaglebone black ?
>
>
> On Mon, May 18, 2015 at 5:13 PM, Robert Nelson 
> wrote:
>
>> On Mon, May 18, 2015 at 7:11 PM, Robert Nelson 
>> wrote:
>> > On Mon, May 18, 2015 at 6:34 PM, William Hermans 
>> wrote:
>> >> Robert,
>> >>
>> >> So whats up with the LPAE kernel versions ? From what I've read this
>> >> "extension" is only for Cortex A15 ( 40 bit addressing ), and
>> typically /
>> >> always this only matters for systems with more than 4GB( addressable )
>> RAM.
>> >>
>> >> The beaglebone black only has 512MB, so is moot, and the X15 from what
>> I
>> >> understand will only have 2GB RAM ? Plus it's not a "bone"
>> >
>> > Large Physical Address Extensions (LPAE) is the main identifier, but
>> > the Cortex-A7/A12/A15/A17 also have hardware virturalization support.
>>
>> I should also mention... Just like non-pae and pae x86 hardware..
>>
>> a non-lpae device will not boot with an lpae enabled kernel. Thus we
>> have a special lpae kernel. ;)
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to beagleboard+unsubscr...@googlegroups.com.
>> 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.

[beagleboard] beaglebone black x wofson sound card

[reginaldo . cardoso]

hello,
someone has an idea how to make a voip device with audio card Wolfson and 
BEAGLEBONE BLACK?

-- 
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] TESTERS WANTED: beaglebone's cape manager

[Robert Nelson]

On May 18, 2015 7:19 PM, "William Hermans"  wrote:
>>
>> I should also mention... Just like non-pae and pae x86 hardware..
>>
>> a non-lpae device will not boot with an lpae enabled kernel. Thus we
>> have a special lpae kernel. ;)
>
>
> What use is this in the context of the beaglebone ? The X15 I can see use
cases, and I'm sure you're not allowed to talk about that platform. Which
is fine. But am I missing something about this in the context of the
beaglebone black ?
>

Not sure where the context came from. I run it on my omap5'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] TESTERS WANTED: beaglebone's cape manager

[William Hermans]

>
> *Not sure where the context came from. I run it on my omap5's...*
>

Just me wondering why it was in the same repo is all. No biggy.

Great to hear that the delta between *bone and *armv7(mainline ? ) is
getting smaller and smaller. Sounds like big/little still giving a little
Resistance though eh ?

On Mon, May 18, 2015 at 5:54 PM, Robert Nelson 
wrote:

>
> On May 18, 2015 7:19 PM, "William Hermans"  wrote:
> >>
> >> I should also mention... Just like non-pae and pae x86 hardware..
> >>
> >> a non-lpae device will not boot with an lpae enabled kernel. Thus we
> >> have a special lpae kernel. ;)
> >
> >
> > What use is this in the context of the beaglebone ? The X15 I can see
> use cases, and I'm sure you're not allowed to talk about that platform.
> Which is fine. But am I missing something about this in the context of the
> beaglebone black ?
> >
>
> Not sure where the context came from. I run it on my omap5'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.
>

-- 
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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[Jack Fisher]

Getting a "not enough memory on device (28)" message repeatedly at the end 
when it switches from  cylon  flashing to fast double flash. I was 
surveilling through the 3.3 FTDI cable, hopefully the observation was not 
the root of the problem. I will try one more time without the FTDI cable 
and see if it makes a difference, then I suppose I will try to re-download 
the flasher image and re-unpack it...

I would have included more of the output than this dim recollection, but 
Putty does not seem to support select and copy...

Any better suggestions?

I guess I can get the board working with an SD boot system rather than 
flashing the EMMC, but that doesn't really get me where I want to and 
 should be able to go,

Regards and thanks in advance,

Jack

-- 
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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[William Hermans]

copy / paste with putty is:

1) Select the text you wish to copy with the mouse.
2) left click the selection.

Be careful not to right click in the putty window when you have something
in the clipboard, as this will put whatever is in the clipboard into the
prompt, and putty will process return + newlines as if you pressed 
on the keyboard . . . depending on what you have in the clipboard this can
be dangerous.

Which board do you have, and which image are you trying to flash ?

On Mon, May 18, 2015 at 6:25 PM, Jack Fisher  wrote:

> Getting a "not enough memory on device (28)" message repeatedly at the end
> when it switches from  cylon  flashing to fast double flash. I was
> surveilling through the 3.3 FTDI cable, hopefully the observation was not
> the root of the problem. I will try one more time without the FTDI cable
> and see if it makes a difference, then I suppose I will try to re-download
> the flasher image and re-unpack it...
>
> I would have included more of the output than this dim recollection, but
> Putty does not seem to support select and copy...
>
> Any better suggestions?
>
> I guess I can get the board working with an SD boot system rather than
> flashing the EMMC, but that doesn't really get me where I want to and
>  should be able to go,
>
> Regards and thanks in advance,
>
> Jack
>
> --
> 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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[William Hermans]

>
> *Which board do you have, and which image are you trying to flash ?*
>

Never mind that question. You have either and A5A or an REVB based on the
distro you mentioned "Angstrom".

Make sure you're not trying to use a REVC 4GB image. It should be marked on
the ewiki page.

On Mon, May 18, 2015 at 6:43 PM, William Hermans  wrote:

> copy / paste with putty is:
>
> 1) Select the text you wish to copy with the mouse.
> 2) left click the selection.
>
> Be careful not to right click in the putty window when you have something
> in the clipboard, as this will put whatever is in the clipboard into the
> prompt, and putty will process return + newlines as if you pressed 
> on the keyboard . . . depending on what you have in the clipboard this can
> be dangerous.
>
> Which board do you have, and which image are you trying to flash ?
>
> On Mon, May 18, 2015 at 6:25 PM, Jack Fisher  wrote:
>
>> Getting a "not enough memory on device (28)" message repeatedly at the
>> end when it switches from  cylon  flashing to fast double flash. I was
>> surveilling through the 3.3 FTDI cable, hopefully the observation was not
>> the root of the problem. I will try one more time without the FTDI cable
>> and see if it makes a difference, then I suppose I will try to re-download
>> the flasher image and re-unpack it...
>>
>> I would have included more of the output than this dim recollection, but
>> Putty does not seem to support select and copy...
>>
>> Any better suggestions?
>>
>> I guess I can get the board working with an SD boot system rather than
>> flashing the EMMC, but that doesn't really get me where I want to and
>>  should be able to go,
>>
>> Regards and thanks in advance,
>>
>> Jack
>>
>> --
>> 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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[William Hermans]

go to:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases

Scroll down to:

BBB (All Revs) eMMC Flashers

Then pick your poison. LXDE or console.

On Mon, May 18, 2015 at 6:50 PM, William Hermans  wrote:

> *Which board do you have, and which image are you trying to flash ?*
>>
>
> Never mind that question. You have either and A5A or an REVB based on the
> distro you mentioned "Angstrom".
>
> Make sure you're not trying to use a REVC 4GB image. It should be marked
> on the ewiki page.
>
> On Mon, May 18, 2015 at 6:43 PM, William Hermans 
> wrote:
>
>> copy / paste with putty is:
>>
>> 1) Select the text you wish to copy with the mouse.
>> 2) left click the selection.
>>
>> Be careful not to right click in the putty window when you have something
>> in the clipboard, as this will put whatever is in the clipboard into the
>> prompt, and putty will process return + newlines as if you pressed 
>> on the keyboard . . . depending on what you have in the clipboard this can
>> be dangerous.
>>
>> Which board do you have, and which image are you trying to flash ?
>>
>> On Mon, May 18, 2015 at 6:25 PM, Jack Fisher  wrote:
>>
>>> Getting a "not enough memory on device (28)" message repeatedly at the
>>> end when it switches from  cylon  flashing to fast double flash. I was
>>> surveilling through the 3.3 FTDI cable, hopefully the observation was not
>>> the root of the problem. I will try one more time without the FTDI cable
>>> and see if it makes a difference, then I suppose I will try to re-download
>>> the flasher image and re-unpack it...
>>>
>>> I would have included more of the output than this dim recollection, but
>>> Putty does not seem to support select and copy...
>>>
>>> Any better suggestions?
>>>
>>> I guess I can get the board working with an SD boot system rather than
>>> flashing the EMMC, but that doesn't really get me where I want to and
>>>  should be able to go,
>>>
>>> Regards and thanks in advance,
>>>
>>> Jack
>>>
>>> --
>>> 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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[Jack Fisher]

On Monday, May 18, 2015 at 6:54:15 PM UTC-7, William Hermans wrote:
>
> go to:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases
>
> Scroll down to:
>
> BBB (All Revs) eMMC Flashers
>
> Then pick your poison. LXDE or console.
>
> On Mon, May 18, 2015 at 6:50 PM, William Hermans  > wrote:
>
>> *Which board do you have, and which image are you trying to flash ?*
>>
>>  
William,

I have two BBBs. The one I had the problem on (see attached log) may be a 
B, I can't tell for sure from my personal knowledge base. The second is 
definitely a C. I am going to try to repeat the flash on the confirmed C 
with the Debian 2015.03.01 4GB Flasher.

Maybe it is buried in the log file what the hardware version is? It did not 
jump out at me. 

I would like to get this working with LXDE.

Thanks for your replies.

Jack

 

>
>>>
>> Never mind that question. You have either and A5A or an REVB based on the 
>> distro you mentioned "Angstrom".
>>
>> Make sure you're not trying to use a REVC 4GB image. It should be marked 
>> on the ewiki page.
>>
>> On Mon, May 18, 2015 at 6:43 PM, William Hermans > > wrote:
>>
>>> copy / paste with putty is:
>>>
>>> 1) Select the text you wish to copy with the mouse.
>>> 2) left click the selection.
>>>
>>> Be careful not to right click in the putty window when you have 
>>> something in the clipboard, as this will put whatever is in the clipboard 
>>> into the prompt, and putty will process return + newlines as if you pressed 
>>>  on the keyboard . . . depending on what you have in the clipboard 
>>> this can be dangerous.
>>>
>>> Which board do you have, and which image are you trying to flash ?
>>>
>>>
>>>

-- 
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.


putty1.log
Description: Binary data

Re: [beagleboard] Re-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[Robert Nelson]

On Mon, May 18, 2015 at 9:35 PM, Jack Fisher  wrote:
>
>
> On Monday, May 18, 2015 at 6:54:15 PM UTC-7, William Hermans wrote:
>>
>> go to:
>>
>> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases
>>
>> Scroll down to:
>>
>> BBB (All Revs) eMMC Flashers
>>
>> Then pick your poison. LXDE or console.
>>
>>
>> On Mon, May 18, 2015 at 6:50 PM, William Hermans  wrote:

 Which board do you have, and which image are you trying to flash ?
>
>
> William,
>
> I have two BBBs. The one I had the problem on (see attached log) may be a B,
> I can't tell for sure from my personal knowledge base. The second is
> definitely a C. I am going to try to repeat the flash on the confirmed C
> with the Debian 2015.03.01 4GB Flasher.
>
> Maybe it is buried in the log file what the hardware version is? It did not
> jump out at me.
>
> I would like to get this working with LXDE.
>
> Thanks for your replies.

mmcblk0  179:00   7.4G  0 disk
|-mmcblk0p1  179:1096M  0 part /boot/uboot
`-mmcblk0p2  179:20   3.5G  0 part /
mmcblk1  179:80   1.8G  0 disk
|-mmcblk1p1  179:9096M  0 part
`-mmcblk1p2  179:10   0   1.7G  0 part

Yeap, you tried "flashing" the 4GB image to the Rev B (with only 2GB eMMC)..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Re-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[Jack Fisher]

On Monday, May 18, 2015 at 7:39:20 PM UTC-7, RobertCNelson wrote:
>
> On Mon, May 18, 2015 at 9:35 PM, Jack Fisher  > wrote: 
> > 
> > 
> > On Monday, May 18, 2015 at 6:54:15 PM UTC-7, William Hermans wrote: 
> >> 
> >> go to: 
> >> 
> >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases 
> >> 
> >> Scroll down to: 
> >> 
> >> BBB (All Revs) eMMC Flashers 
> >> 
> >> Then pick your poison. LXDE or console. 
> >> 
> >> 
> >> On Mon, May 18, 2015 at 6:50 PM, William Hermans  
> wrote: 
>  
>  Which board do you have, and which image are you trying to flash ? 
> > 
> > 
> > William, 
> > 
> > I have two BBBs. The one I had the problem on (see attached log) may be 
> a B, 
> > I can't tell for sure from my personal knowledge base. The second is 
> > definitely a C. I am going to try to repeat the flash on the confirmed C 
> > with the Debian 2015.03.01 4GB Flasher. 
> > 
> > Maybe it is buried in the log file what the hardware version is? It did 
> not 
> > jump out at me. 
> > 
> > I would like to get this working with LXDE. 
> > 
> > Thanks for your replies. 
>
> mmcblk0  179:00   7.4G  0 disk 
> |-mmcblk0p1  179:1096M  0 part /boot/uboot 
> `-mmcblk0p2  179:20   3.5G  0 part / 
> mmcblk1  179:80   1.8G  0 disk 
> |-mmcblk1p1  179:9096M  0 part 
> `-mmcblk1p2  179:10   0   1.7G  0 part 
>
> Yeap, you tried "flashing" the 4GB image to the Rev B (with only 2GB 
> eMMC).. 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

Yeah,

Rpbert,

No guts, no glory. :)

 Seriously, the flash went fine on the C and now I am preparing to flash 
the B with the lighter weight 2GB Debian flasher. I did not remember buying 
them that far apart, but the memory goes second. 

I can still put the full version on Debian on an SD and load from that 
right? I just don't really want to have two different versions of doing 
things for two boards, but kind of too late for that. I recall reading that 
the default behavior at boot-up is now to boot off an SD if it is present, 
is that correct? Or is it configurable?

As I write this the B just took the 2GB package just fine. Next, to play 
around with the LCD7 module and get it working with one or the other. 

Respectfully,

Jack

-- 
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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[William Hermans]

>
> *I can still put the full version on Debian on an SD and load from that
> right?*
>

Yes. But you would use one of the standalone images, instead of a flasher
image.

*I just don't really want to have two different versions of doing things
> for two boards, but kind of too late for that. I recall reading that the
> default behavior at boot-up is now to boot off an SD if it is present, is
> that correct? Or is it configurable?*
>

The default behavior as I understand it is that the board will load the
first, a stage bootloader ( MLO ) off of the eMMC. *Unless* you press the
boot switch button, where then it would load the first stage bootloader
from the sdcard.

In either above case, the board would then attempt to boot off the sdcard.
Starting with u-boot, and finally booting Linux. This is why some have
issues with trying to boot a newer image off of sdcard, when they're using
an older BBB. The first stage bootloader on the eMMC is too old.

Anyway, with all that said. Yes, you can configure this behavior somewhat
through uEnv.txt. You'll still load the first stage bootloader off the
eMMC, but depending on how key variables are set in uEnv.txt, you can
"automagically" load files. and / or linux images choosing your specific
boot medium.

Now, we're straying off onto a topic that is fairly large. A topic that I
spent nearly 2 weeks reading about before I could even think of a question
to ask. I would suggest if you need to know more that you search the web
for anything / everything u-boot, MLO ( and perhaps even x-loader ) in
regards to the beaglebone black.

On Mon, May 18, 2015 at 8:03 PM, Jack Fisher  wrote:

>
>
> On Monday, May 18, 2015 at 7:39:20 PM UTC-7, RobertCNelson wrote:
>
>> On Mon, May 18, 2015 at 9:35 PM, Jack Fisher  wrote:
>> >
>> >
>> > On Monday, May 18, 2015 at 6:54:15 PM UTC-7, William Hermans wrote:
>> >>
>> >> go to:
>> >>
>> >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases
>> >>
>> >> Scroll down to:
>> >>
>> >> BBB (All Revs) eMMC Flashers
>> >>
>> >> Then pick your poison. LXDE or console.
>> >>
>> >>
>> >> On Mon, May 18, 2015 at 6:50 PM, William Hermans 
>> wrote:
>> 
>>  Which board do you have, and which image are you trying to flash ?
>> >
>> >
>> > William,
>> >
>> > I have two BBBs. The one I had the problem on (see attached log) may be
>> a B,
>> > I can't tell for sure from my personal knowledge base. The second is
>> > definitely a C. I am going to try to repeat the flash on the confirmed
>> C
>> > with the Debian 2015.03.01 4GB Flasher.
>> >
>> > Maybe it is buried in the log file what the hardware version is? It did
>> not
>> > jump out at me.
>> >
>> > I would like to get this working with LXDE.
>> >
>> > Thanks for your replies.
>>
>> mmcblk0  179:00   7.4G  0 disk
>> |-mmcblk0p1  179:1096M  0 part /boot/uboot
>> `-mmcblk0p2  179:20   3.5G  0 part /
>> mmcblk1  179:80   1.8G  0 disk
>> |-mmcblk1p1  179:9096M  0 part
>> `-mmcblk1p2  179:10   0   1.7G  0 part
>>
>> Yeap, you tried "flashing" the 4GB image to the Rev B (with only 2GB
>> eMMC)..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> https://rcn-ee.com/
>>
>
> Yeah,
>
> Rpbert,
>
> No guts, no glory. :)
>
>  Seriously, the flash went fine on the C and now I am preparing to flash
> the B with the lighter weight 2GB Debian flasher. I did not remember buying
> them that far apart, but the memory goes second.
>
> I can still put the full version on Debian on an SD and load from that
> right? I just don't really want to have two different versions of doing
> things for two boards, but kind of too late for that. I recall reading that
> the default behavior at boot-up is now to boot off an SD if it is present,
> is that correct? Or is it configurable?
>
> As I write this the B just took the 2GB package just fine. Next, to play
> around with the LCD7 module and get it working with one or the other.
>
> Respectfully,
>
> Jack
>
> --
> 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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[William Hermans]

>
> *You'll still load the first stage bootloader off the eMMC . . .*
>

That is, *if* it exists. If it does not find a first stage bootloader on
the eMMC, it should also look for it on the sdcard.

On Mon, May 18, 2015 at 8:39 PM, William Hermans  wrote:

> *I can still put the full version on Debian on an SD and load from that
>> right?*
>>
>
> Yes. But you would use one of the standalone images, instead of a flasher
> image.
>
> *I just don't really want to have two different versions of doing things
>> for two boards, but kind of too late for that. I recall reading that the
>> default behavior at boot-up is now to boot off an SD if it is present, is
>> that correct? Or is it configurable?*
>>
>
> The default behavior as I understand it is that the board will load the
> first, a stage bootloader ( MLO ) off of the eMMC. *Unless* you press the
> boot switch button, where then it would load the first stage bootloader
> from the sdcard.
>
> In either above case, the board would then attempt to boot off the sdcard.
> Starting with u-boot, and finally booting Linux. This is why some have
> issues with trying to boot a newer image off of sdcard, when they're using
> an older BBB. The first stage bootloader on the eMMC is too old.
>
> Anyway, with all that said. Yes, you can configure this behavior somewhat
> through uEnv.txt. You'll still load the first stage bootloader off the
> eMMC, but depending on how key variables are set in uEnv.txt, you can
> "automagically" load files. and / or linux images choosing your specific
> boot medium.
>
> Now, we're straying off onto a topic that is fairly large. A topic that I
> spent nearly 2 weeks reading about before I could even think of a question
> to ask. I would suggest if you need to know more that you search the web
> for anything / everything u-boot, MLO ( and perhaps even x-loader ) in
> regards to the beaglebone black.
>
> On Mon, May 18, 2015 at 8:03 PM, Jack Fisher  wrote:
>
>>
>>
>> On Monday, May 18, 2015 at 7:39:20 PM UTC-7, RobertCNelson wrote:
>>
>>> On Mon, May 18, 2015 at 9:35 PM, Jack Fisher  wrote:
>>> >
>>> >
>>> > On Monday, May 18, 2015 at 6:54:15 PM UTC-7, William Hermans wrote:
>>> >>
>>> >> go to:
>>> >>
>>> >> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Debian_Releases
>>> >>
>>> >> Scroll down to:
>>> >>
>>> >> BBB (All Revs) eMMC Flashers
>>> >>
>>> >> Then pick your poison. LXDE or console.
>>> >>
>>> >>
>>> >> On Mon, May 18, 2015 at 6:50 PM, William Hermans 
>>> wrote:
>>> 
>>>  Which board do you have, and which image are you trying to flash ?
>>> >
>>> >
>>> > William,
>>> >
>>> > I have two BBBs. The one I had the problem on (see attached log) may
>>> be a B,
>>> > I can't tell for sure from my personal knowledge base. The second is
>>> > definitely a C. I am going to try to repeat the flash on the confirmed
>>> C
>>> > with the Debian 2015.03.01 4GB Flasher.
>>> >
>>> > Maybe it is buried in the log file what the hardware version is? It
>>> did not
>>> > jump out at me.
>>> >
>>> > I would like to get this working with LXDE.
>>> >
>>> > Thanks for your replies.
>>>
>>> mmcblk0  179:00   7.4G  0 disk
>>> |-mmcblk0p1  179:1096M  0 part /boot/uboot
>>> `-mmcblk0p2  179:20   3.5G  0 part /
>>> mmcblk1  179:80   1.8G  0 disk
>>> |-mmcblk1p1  179:9096M  0 part
>>> `-mmcblk1p2  179:10   0   1.7G  0 part
>>>
>>> Yeap, you tried "flashing" the 4GB image to the Rev B (with only 2GB
>>> eMMC)..
>>>
>>> Regards,
>>>
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>
>> Yeah,
>>
>> Rpbert,
>>
>> No guts, no glory. :)
>>
>>  Seriously, the flash went fine on the C and now I am preparing to flash
>> the B with the lighter weight 2GB Debian flasher. I did not remember buying
>> them that far apart, but the memory goes second.
>>
>> I can still put the full version on Debian on an SD and load from that
>> right? I just don't really want to have two different versions of doing
>> things for two boards, but kind of too late for that. I recall reading that
>> the default behavior at boot-up is now to boot off an SD if it is present,
>> is that correct? Or is it configurable?
>>
>> As I write this the B just took the 2GB package just fine. Next, to play
>> around with the LCD7 module and get it working with one or the other.
>>
>> Respectfully,
>>
>> Jack
>>
>> --
>> 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...@googlegro

Re: [beagleboard] Re: beaglebone black not being detected when plugged in through USB cable

[Mehreen Qayas]

​@William
The only thing I did was to follow this tutorial of adafruit :
http://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/overview
to install Python library. Even after installing it it was working. I had
plugged and unplugged it from my computer through the USB cable. But the
problem now I face is that the computer doesn't detect the presence of any
device connected to it once I plug in the beagle.

I plugged in different flashdrives through the same port, same computer,
same cable - they work. The beagle refuses to budge. I was thinking of
flashing an image now - as being the last resort - but can i flash a new
image from the SD card even when the beagle is not detected by the
computer? Sure, it powers up and the leds lit up in the normal way they do.
What do you suggest?​

On Mon, May 18, 2015 at 3:10 AM, William Hermans  wrote:

> @Nova Jack
>
> Did you change anything recently ? e.g. change Linux images, or update the
> kernel ?
>
> On Sat, May 16, 2015 at 6:16 PM, Andre Castro 
> wrote:
>
>> As far as I know, there is a known problem related to hot plugging USB
>> devices at BBB.
>> Try connecting Desktop computer before restart the board.
>>
>> --
>> 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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/NWc-m2ZWiwk/unsubscribe.
> To unsubscribe from this group and all its topics, 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-flashing an Angstrom EMMC with Debian Latest from beagleboard, fail

[Robert Nelson]

> Yeah,
>
> Rpbert,
>
> No guts, no glory. :)
>
>  Seriously, the flash went fine on the C and now I am preparing to flash the
> B with the lighter weight 2GB Debian flasher. I did not remember buying them
> that far apart, but the memory goes second.
>
> I can still put the full version on Debian on an SD and load from that
> right? I just don't really want to have two different versions of doing
> things for two boards, but kind of too late for that. I recall reading that
> the default behavior at boot-up is now to boot off an SD if it is present,
> is that correct? Or is it configurable?
>
> As I write this the B just took the 2GB package just fine. Next, to play
> around with the LCD7 module and get it working with one or the other.

Yeah, there's 2 "lxde" flasher images, one for the 4GB and the other
for the 2GB.

The 2GB just removes chromium (which is a large package) and a few
other things to keep it under 2GB..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

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

Re: [beagleboard] Re: beaglebone black not being detected when plugged in through USB cable

[William Hermans]

A problem like this is hard to solve . . . from over here . . . without any
solid information. As it stands, the only thing I can think of. Would be to
*somehow* log into the beaglebone. The only way that comes to mind is by
using a serial debug cable / device.

There are surely many potential causes for this problem. But without
logging in *somehow* and troubleshooting directly on the beaglebone . . .
Yeah that just turns into hit /miss guessing.

On Mon, May 18, 2015 at 9:10 PM, Mehreen Qayas  wrote:

> ​@William
> The only thing I did was to follow this tutorial of adafruit :
> http://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/overview
> to install Python library. Even after installing it it was working. I had
> plugged and unplugged it from my computer through the USB cable. But the
> problem now I face is that the computer doesn't detect the presence of any
> device connected to it once I plug in the beagle.
>
> I plugged in different flashdrives through the same port, same computer,
> same cable - they work. The beagle refuses to budge. I was thinking of
> flashing an image now - as being the last resort - but can i flash a new
> image from the SD card even when the beagle is not detected by the
> computer? Sure, it powers up and the leds lit up in the normal way they do.
> What do you suggest?​
>
> On Mon, May 18, 2015 at 3:10 AM, William Hermans 
> wrote:
>
>> @Nova Jack
>>
>> Did you change anything recently ? e.g. change Linux images, or update
>> the kernel ?
>>
>> On Sat, May 16, 2015 at 6:16 PM, Andre Castro 
>> wrote:
>>
>>> As far as I know, there is a known problem related to hot plugging USB
>>> devices at BBB.
>>> Try connecting Desktop computer before restart the board.
>>>
>>> --
>>> 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 a topic in the
>> Google Groups "BeagleBoard" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/beagleboard/NWc-m2ZWiwk/unsubscribe.
>> To unsubscribe from this group and all its topics, 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.
>

-- 
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 not being detected when plugged in through USB cable

[Mehreen Qayas]

Thanks for the input! I'll look into that. I'm thinking maybe there is a
hardware problem. Because I have never experienced a problem like this.
Normally the devices are recognized by the computer and one can start from
there. But anyway, thank you again. Everyone, for your answers.

On Tue, May 19, 2015, 9:32 AM William Hermans  wrote:

> A problem like this is hard to solve . . . from over here . . . without
> any solid information. As it stands, the only thing I can think of. Would
> be to *somehow* log into the beaglebone. The only way that comes to mind is
> by using a serial debug cable / device.
>
> There are surely many potential causes for this problem. But without
> logging in *somehow* and troubleshooting directly on the beaglebone . . .
> Yeah that just turns into hit /miss guessing.
>
> On Mon, May 18, 2015 at 9:10 PM, Mehreen Qayas 
> wrote:
>
>> ​@William
>> The only thing I did was to follow this tutorial of adafruit :
>> http://learn.adafruit.com/setting-up-io-python-library-on-beaglebone-black/overview
>> to install Python library. Even after installing it it was working. I had
>> plugged and unplugged it from my computer through the USB cable. But the
>> problem now I face is that the computer doesn't detect the presence of any
>> device connected to it once I plug in the beagle.
>>
>> I plugged in different flashdrives through the same port, same computer,
>> same cable - they work. The beagle refuses to budge. I was thinking of
>> flashing an image now - as being the last resort - but can i flash a new
>> image from the SD card even when the beagle is not detected by the
>> computer? Sure, it powers up and the leds lit up in the normal way they do.
>> What do you suggest?​
>>
>> On Mon, May 18, 2015 at 3:10 AM, William Hermans 
>> wrote:
>>
>>> @Nova Jack
>>>
>>> Did you change anything recently ? e.g. change Linux images, or update
>>> the kernel ?
>>>
>>> On Sat, May 16, 2015 at 6:16 PM, Andre Castro 
>>> wrote:
>>>
 As far as I know, there is a known problem related to hot plugging USB
 devices at BBB.
 Try connecting Desktop computer before restart the board.

 --
 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 a topic in the
>>> Google Groups "BeagleBoard" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/beagleboard/NWc-m2ZWiwk/unsubscribe.
>>> To unsubscribe from this group and all its topics, 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.
>>
>
>  --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/beagleboard/NWc-m2ZWiwk/unsubscribe.
> To unsubscribe from this group and all its topics, 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.

[beagleboard] Future of BeagleBone (Black)?

[Karl Karpfen]

Hi,

I'm aware of the fact that there can't be a obligatory answer to my 
question, so I'm happy with any kind of rumours and rough ideas:

As far as I know TI does not further develop the AM335X series, more than 
this I remember an article where they stated they drop the whole mobile 
devices marked where this CPU was intended for originally. So I don't think 
there will be a multi core variant of this Sitara SoC or even a version 
with higher clock.

So: what future could be there for the BeagleBone (Black)? Will there be a 
somehow compatible successor? Or what else is planned?

Thanks!

Karl


-- 
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.