Re: [beagleboard] how to use setup_sdcard.sh and the new oemflasher builds

> > [...] > However for you, just grab: > > https://rcn-ee.net/rootfs/bb.org/testing/2016-10-30/seeed-iot/ > > https://rcn-ee.net/rootfs/bb.org/testing/2016-10-30/seeed- > iot/BBGW-blank-debian-8.6-seeed-iot-armhf-2016-10-30-4gb.img.xz > Perfect. I had misunderstood the purpose of the flasher

Re: [beagleboard] how to use setup_sdcard.sh and the new oemflasher builds

On Thu, Nov 3, 2016 at 4:22 PM, Stephane Charette wrote: > I've read through the posts for the past few weeks, but don't see this as a > topic discussed yet. I downloaded the new oemflasher image I see on > rcn-ee.com: > >

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 2:19 PM, Robert Nelson wrote: > CONFIG_DEBUG_INFO is now disabled... The dbg symbols, while smaller > then they use to be, still just ended up taking up too much server > space. ;) > > heheh, excellent. That worked out good then ;) -- For more

[beagleboard] how to use setup_sdcard.sh and the new oemflasher builds

I've read through the posts for the past few weeks, but don't see this as a topic discussed yet. I downloaded the new oemflasher image I see on rcn-ee.com: https://rcn-ee.com/rootfs/bb.org/testing/2016-10-31/oemflasher/debian-8.6-oemflasher-armhf-2016-10-31.tar.xz This is what I tried: unxz

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 4:17 PM, William Hermans wrote: > > > On Thu, Nov 3, 2016 at 9:19 AM, Gary Thomas wrote: >> >> On 2016-11-03 15:22, Robert Nelson wrote: >>> >>> On Thu, Nov 3, 2016 at 9:18 AM, Gary Thomas wrote: On

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 9:19 AM, Gary Thomas wrote: > On 2016-11-03 15:22, Robert Nelson wrote: > >> On Thu, Nov 3, 2016 at 9:18 AM, Gary Thomas wrote: >> >>> On 2016-11-03 15:11, Robert Nelson wrote: >>> > Thanks, I'll investigate these changes.

Re: [beagleboard] Trying to build tlv430

On Thu, Nov 3, 2016 at 1:23 PM, wrote: > Hi, > I have been lurking about these boards asking a few questions about > beaglebone. Off and on when I have time I am evaluating the beaglebone for a > low latency audio application. > > > I am using the 4.4.20-ti-r44

[beagleboard] Trying to build tlv430

Hi, I have been lurking about these boards asking a few questions about beaglebone. Off and on when I have time I am evaluating the beaglebone for a low latency audio application. I am using the 4.4.20-ti-r44 build at the moment, in a previous post I have swapped using RPMsg for the

[beagleboard] Re: Ubuntu 14.04 for BBGW

Or Ubuntu 16.04? Or 16.10? On Sunday, October 23, 2016 at 8:34:39 AM UTC-7, Käptn Iglo wrote: > > Is there any Ubuntu 14.04 Image available for the Beagle Bone Green > Wireless which supports the Wifi Chip on the Board ? > -- For more options, visit http://beagleboard.org/discuss --- You

Re: [beagleboard] BBB: schizophrenic MMC names

On 2016-11-03 15:22, Robert Nelson wrote: On Thu, Nov 3, 2016 at 9:18 AM, Gary Thomas wrote: On 2016-11-03 15:11, Robert Nelson wrote: Thanks, I'll investigate these changes. Based on the comment "first valid device probed", is there any way to force the eMMC to be the

[beagleboard] Beagle Board Rev. C3 booting problem

I am trying to boot linux on Beagle Board Rev. C3 with no success. Steps I took for booting is taken from this wiki https://eewiki.net/display/linuxonarm/BeagleBoard . It is created by Robert Nelson. I can see that U-Boot is started and trying to start Linux kernel, but as control is passed to

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 9:18 AM, Gary Thomas wrote: > On 2016-11-03 15:11, Robert Nelson wrote: >>> >>> Thanks, I'll investigate these changes. >>> >>> Based on the comment "first valid device probed", is there any way to >>> force the eMMC to be the first valid device (I might

Re: [beagleboard] BBB: schizophrenic MMC names

On 2016-11-03 15:11, Robert Nelson wrote: Thanks, I'll investigate these changes. Based on the comment "first valid device probed", is there any way to force the eMMC to be the first valid device (I might be able to live with the fact that U-Boot sees the eMMC as dev 1 but Linux as dev 0 if it

Re: [beagleboard] BBB: schizophrenic MMC names

> Thanks, I'll investigate these changes. > > Based on the comment "first valid device probed", is there any way to > force the eMMC to be the first valid device (I might be able to live with > the fact that U-Boot sees the eMMC as dev 1 but Linux as dev 0 if it was > always consistent). > >

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 8:55 AM, Gary Thomas wrote: > On 2016-11-03 14:38, Robert Nelson wrote: >> >> On Thu, Nov 3, 2016 at 7:26 AM, Gary Thomas wrote: >>> >>> On my BeagleBoneBlack with a system installed in eMMC, I get >>> different device names for the

Re: [beagleboard] BBB: schizophrenic MMC names

On 2016-11-03 14:58, Robert Nelson wrote: On Thu, Nov 3, 2016 at 8:55 AM, Gary Thomas wrote: On 2016-11-03 14:38, Robert Nelson wrote: On Thu, Nov 3, 2016 at 7:26 AM, Gary Thomas wrote: On my BeagleBoneBlack with a system installed in eMMC, I get

Re: [beagleboard] BBB: schizophrenic MMC names

On 2016-11-03 14:38, Robert Nelson wrote: On Thu, Nov 3, 2016 at 7:26 AM, Gary Thomas wrote: On my BeagleBoneBlack with a system installed in eMMC, I get different device names for the MMC devices, depending on whether or not there is a SD card installed at boot time. With

Re: [beagleboard] BBB: schizophrenic MMC names

On Thu, Nov 3, 2016 at 7:26 AM, Gary Thomas wrote: > On my BeagleBoneBlack with a system installed in eMMC, I get > different device names for the MMC devices, depending on whether > or not there is a SD card installed at boot time. > > With SD card installed: > MMC/SD slot =

[beagleboard] BBB: schizophrenic MMC names

On my BeagleBoneBlack with a system installed in eMMC, I get different device names for the MMC devices, depending on whether or not there is a SD card installed at boot time. With SD card installed: MMC/SD slot = mmcblk0 eMMC = mmcblk1 Without SD card installed (at boot): MMC/SD slot =

[beagleboard] SPI:Got incorret data in BBGW

Hi, I tried to run a spidev_test.c program in my BBGW , but I got incorrect data. My system info .. ubuntu@arm:~$ uname -r 4.4.12-ti-r30 ubuntu@arm:~$ cat /etc/issue Ubuntu 16.04 LTS \n \l ubuntu@arm:~$ ls /dev/spi* /dev/spidev1.0 ubuntu@arm:~$

[beagleboard] Re: Linux Plumbers: questions or comments?

Relevant links from today: Device Tree presentations papers articles http://elinux.org/Device_Tree_presentations_papers_articles#ordered_by_date [PDF] "Device tree Hardware Description vs Configuration vs Policy", Linux Plumbers, November 2016, Frank Rowand [PDF] "Device Tree Tools Status",