[beagleboard] Issue creating "flasher" SD Card

Hi all, I have used beaglebone-black-make-microSD-flasher-from-eMMC.sh for quite some time and I have just come to update an image I was using. I updated to the latest scripts in the boot-scripts and managed to create an SD card flasher as per normal. The SD card on a new BBB boots and

[beagleboard] Re: Announcement: Debian 8.6 released for all boards

Is there a way to update an existing BB to this version without re-flashing at all? On Monday, November 14, 2016 at 8:54:26 PM UTC, Jason Kridner wrote: > > Thanks to Robert and the rest of the BeagleBoard.org community! > > http://beagleboard.org/latest-images/ > > The above URL is now updated

Re: [beagleboard] Re: Create eMMC Flasher that flashes the bootloader also?

device, and you can > put whatever you want onto it. > > > On Friday, May 13, 2016 at 4:17:27 AM UTC-4, Lee Armstrong wrote: >> >> >> I am happy creating an eMMC flasher that flashes the eMMC but is it >> possible to create a version that takes the current boot

[beagleboard] Create eMMC Flasher that flashes the bootloader also?

I am happy creating an eMMC flasher that flashes the eMMC but is it possible to create a version that takes the current bootloader and flashes that also? -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups

Re: [beagleboard] Re: Basic lock down

Yes very true but the 2 easy vectors I can see are serial debug cable and micro SD. If anything could be done to discourage it then that would be welcomed. Will look into encrypting the OS though. Good idea. On Mon, 2 May 2016 at 12:49, <c...@isbd.net> wrote: > Lee Armstrong <l...@p

[beagleboard] Basic lock down

I have my BBB flashed onto the eMMC and it is feasible for someone to boot from the SD Card and/or use the serial debug cable to gain access. What methods if any have people used to prevent some access? -- For more options, visit http://beagleboard.org/discuss --- You received this message

Re: [beagleboard] BBB Boot Issue

Perfect thank you, pretty recently then it seems. I can't seem to find a way of getting u-boot version from a booted userspace but pretty sure I will need to update some :-D On Sunday, February 21, 2016 at 6:10:04 PM UTC, RobertCNelson wrote: > > > On Feb 21, 2016 11:56 AM, "Lee

Re: [beagleboard] BBB Boot Issue

Thanks & understood. What release was it changed from? Is there a way of checking a booted board too? On Sun, 21 Feb 2016 at 17:55, Robert Nelson <robertcnel...@gmail.com> wrote: > > On Feb 21, 2016 11:51 AM, "Lee Armstrong" <l...@planefinder.net> wrote: >

Re: [beagleboard] BBB Boot Issue

Great thanks. Will the update-bootloader.sh script get boards in the field up to date? On Sun, 21 Feb 2016 at 17:49, Robert Nelson <robertcnel...@gmail.com> wrote: > > On Feb 21, 2016 11:45 AM, "Robert Nelson" <robertcnel...@gmail.com> wrote: > > > > >

[beagleboard] BBB Boot Issue

>From time to time I will see the issue described in this blog post. >http://andicelabs.com/2014/07/beaglebone-black-boot-issues/ I also note some previous discussion on this very group about it. Is the uboot issue widespread and will making it a specific key make it into the production repos

Re: [beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

Understood. Very clear. Thank you On Mon, 4 Jan 2016 at 20:17, Robert Nelson <robertcnel...@gmail.com> wrote: > On Mon, Jan 4, 2016 at 2:08 PM, Lee Armstrong <l...@pinkfroot.com> wrote: > > Thanks Robert, > > > > I'll admit I stuck to the ti release as this

Re: [beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

Thanks Robert, I'll admit I stuck to the ti release as this was part of the Jessie console image. Would you recommend staying with that? On Mon, 4 Jan 2016 at 20:06, Robert Nelson <robertcnel...@gmail.com> wrote: > On Mon, Jan 4, 2016 at 1:57 PM, Lee Armstrong <l...@pinkfroo

[beagleboard] Re: 4.4-lts plans (4.1-lts not going away)

Robert, What is the difference between the bone and ti releases please? Lee -- 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

[beagleboard] Different Kernel Options

Hi All, Had a bit of a search around but can't see anything recent on this subject. I'm trying to understand the difference between all the Kernel options we have to us on the BBB. By this I specifically mean the options we have for 4.1 (at the moment). bone ti ti-rt omap2plus armv7 Any

Re: [beagleboard] UART FIFO Size & CTS Threshold

The other end is our own board and so signals cts all the time. I think it is fine now that we have ascertained that the trigger is 48 out of 64 On Fri, 11 Dec 2015 at 19:19, Peter Hurley <pe...@hurleysoftware.com> wrote: > On 12/11/2015 11:13 AM, Lee Armstrong wrote: > &g

Re: [beagleboard] UART FIFO Size & CTS Threshold

again! On Thursday, December 10, 2015 at 7:07:10 PM UTC, Lee Armstrong wrote: > > Thanks Robert. > > 64 for the FIFO is what I suspected but couldn't see the CTS threshold. > Was that 48? > > Also these look pretty hard coded into the kernel. Anyone know a way of

Re: [beagleboard] UART FIFO Size & CTS Threshold

t; Hi Lee, > > On 12/11/2015 11:01 AM, Lee Armstrong wrote: > > Hi Peter, > > > > It is on the RX side of things into the BBB and I am seeing the RTS > > signal goign across to our hardware. I think the threshold is 48 out > > of the 64 buffer from looking at and

Re: [beagleboard] UART FIFO Size & CTS Threshold

seems to be working now that we have worked it out that the throttling happens at 48. Lee On Fri, Dec 11, 2015 at 6:59 PM Peter Hurley <pe...@hurleysoftware.com> wrote: > On 12/11/2015 09:20 AM, Lee Armstrong wrote: > > Anyone know what the RTS/CTS thresholds are for the 8

Re: [beagleboard] UART FIFO Size & CTS Threshold

Thanks Robert. 64 for the FIFO is what I suspected but couldn't see the CTS threshold. Was that 48? Also these look pretty hard coded into the kernel. Anyone know a way of setting these after a compilation or how to compile in with other values? Lee -- For more options, visit

Re: [beagleboard] debian jessie: nodejs users (v4.2.3 now available)

4.x is the new LTS version whilst 5.x is "stable". I would stick with 4.x and it is a HUGE improvement over the older versions as they have now merged with iojs which kept up to date with V8 improvements. Lee On Thursday, December 10, 2015 at 6:26:15 PM UTC, William Hermans wrote: > > Scratch

[beagleboard] UART FIFO Size & CTS Threshold

Hi all, Been looking through the kernel source for 4.1 with Debian 8.1 and trying to work out some of the things on the UARTs, but I can't seem to find the code! - What is the FIFO UART buffer size and is it configurable? - What is the FIFO trigger size for the CTS line to assert and is

[beagleboard] Re: Bulk flashing of BBB eMMC

Thanks for all of your experiences. Interesting you use the SD in production. That is similar to what I am doing now. Günter, that is much quicker than the 5 minutes I have it down to at the moment so may invest some time in that process. Lee On Monday, December 7, 2015 at 2:56:56 PM UTC,

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

Wow that is a sizeable difference, I will create some new SD cards later to speed things up! :-) On Monday, December 7, 2015 at 4:07:57 PM UTC, RobertCNelson wrote: > > > > On Mon, Dec 7, 2015 at 9:57 AM, William Hermans > wrote: > >> I should also add, that I tested USB

Re: [beagleboard] Re: Bulk flashing of BBB eMMC

. . . but also note that an NFS mount will be slower than both USB, > or using the sdcard directly. In fact, for reads, I do not think anything > will be faster than sdcard . . . in this context. > On Mon, Dec 7, 2015 at 8:46 AM, Lee Armstrong <l...@pinkfroot.com> wrote: &g

Re: [beagleboard] Bulk flashing of BBB eMMC

rd copier. > Gerald > On Mon, Dec 7, 2015 at 12:38 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> What is the quickest way to bulk flash say 10 BBB's eMMC? >> >> At the moment I have 10 Micro SD Card with a custom flasher image on and >> this works but wondered if the

[beagleboard] Bulk flashing of BBB eMMC

What is the quickest way to bulk flash say 10 BBB's eMMC? At the moment I have 10 Micro SD Card with a custom flasher image on and this works but wondered if there was a more slick solution out there at all? -- For more options, visit http://beagleboard.org/discuss --- You received this

Re: [beagleboard] Updating U-Boot?

Ah yes, I see it now. update_bootloader.sh So if running on a flashed eMMC it will update the one there? On Tuesday, December 1, 2015 at 4:54:00 PM UTC, RobertCNelson wrote: > > On Tue, Dec 1, 2015 at 3:15 AM, Lee Armstrong <l...@pinkfroot.com > > wrote: > > > >

[beagleboard] Updating U-Boot?

Hi all! We have the update_kernel.sh for updating the kernel but I can't see a way to keep U-Boot up to date. Is there a way to update it without reflashing the entire eMMC? Lee -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are

[beagleboard] Issue with UART1 and UART2...

Does this happen with r33? -- 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

Re: [beagleboard] Rolling back to old kernel

com> wrote: > On Tue, Nov 24, 2015 at 10:05 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> Seeing the system hang with a 3Mbps UART on the system that is generating a >> HUGE amount of overrun errors on the port. >> >> Wanted to see if an older 4.1 kernel behav

Re: [beagleboard] Rolling back to old kernel

now as well. Finally, if I do get the lockup, is there any info I can get you at all!! Lee On Tue, Nov 24, 2015 at 4:31 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Tue, Nov 24, 2015 at 10:21 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> I can certainly

Re: [beagleboard] Rolling back to old kernel

if this works around it!!! On Tue, Nov 24, 2015 at 4:49 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Tue, Nov 24, 2015 at 10:37 AM, Lee Armstrong <l...@pinkfroot.com> wrote: > > Thanks Robert, really appreciate that and did’t see dtb-rebuilder before. > >

Re: [beagleboard] Rolling back to old kernel

the port is now in PIO mode at all? On Tue, Nov 24, 2015 at 5:06 PM, Lee Armstrong <l...@planefinder.net> wrote: > Hmm ok, so I removed the > > cape_enable=bone_capemgr.enable_partno=BB_UART2 > > and added > > dtb=am335x-boneblack-ttyS2.dtb > > from/to uEnv and n

[beagleboard] Rolling back to old kernel

I am running the following command (that I usually use to update the kernel) to go back to an earlier version for a test. ./update_kernel.sh --kernel v4.1.2-ti-r3 Is the command I am using but I get errors such as error: [linux-image-v4.1.2-ti-r3] unavailable Are these still available to

Re: [beagleboard] Rolling back to old kernel

are empty when I power off and back on again.  I lose network connectivity with the unit too. On Tue, Nov 24, 2015 at 4:02 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Tue, Nov 24, 2015 at 9:56 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> I am running the foll

Re: [beagleboard] Re: BBB Rev C Lockup - nothing logged

gt; On Mon, Nov 23, 2015 at 12:32 PM, evilwulfie <evilwul...@gmail.com> wrote: >> Oh one more question >> >> Does the board lockup while not running your application. >> >> >> On 11/23/2015 10:59 AM, Lee Armstrong wrote: >> >> Gerald, >&g

Re: [beagleboard] Re: BBB Rev C Lockup - nothing logged

Ok thanks Gerald On Mon, Nov 23, 2015 at 7:28 PM, Gerald Coley <ger...@beagleboard.org> wrote: > You might hook up a JTAG emulator and break in and see where it is stuck. > Gerald > On Mon, Nov 23, 2015 at 1:27 PM, Lee Armstrong <l...@pinkfroot.com> wrote: >> OK that

[beagleboard] Re: BBB Rev C Lockup - nothing logged

on the BBB. The BBB is powered via the SYS_5V pins. On Friday, November 20, 2015 at 11:48:12 AM UTC, Lee Armstrong wrote: > > Also further to that the USR LEDs are all extinguished but the LED's on > the NIC are ok and the power LED is still lit. > > > > On Friday, November 20

Re: [beagleboard] Re: BBB Rev C Lockup - nothing logged

> > On Mon, Nov 23, 2015 at 11:35 AM, Lee Armstrong <l...@pinkfroot.com > > wrote: > >> Anyone got any ideas, this is happening on a few units and nothing is >> logged at all. >> >> Need to narrow down if it is software or hardware issue, from the Debia

Re: [beagleboard] Re: BBB Rev C Lockup - nothing logged

? > Gerald > On Mon, Nov 23, 2015 at 11:42 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> Thank you Gerald, >> >> Sorry I meant that we are using the VDD_5V pins to power the unit and not >> the SYS_5V. Fat fingers there! >> >> With that in mind a

Re: [beagleboard] Re: BBB Rev C Lockup - nothing logged

> . > On Mon, Nov 23, 2015 at 11:49 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> Hi Gerald, >> >> Not that I am aware of, We use UART2 & UART4 (TX & RX) and also GPIO3_19. >> >> We also have the PWR_But & Sys_Reset pins wired in. >&

[beagleboard] BBB Rev C Lockup - nothing logged

Hello, I have a very strange issue that I cannot seem to work out and get more info for! We have a BBB Rev C that is powered via the 5V header pins. It also uses UART2 heavily (3MBps) and this is configured using the built in BB-UART2 device tree overlay. The board is running...

[beagleboard] Re: BBB Rev C Lockup - nothing logged

Also further to that the USR LEDs are all extinguished but the LED's on the NIC are ok and the power LED is still lit. On Friday, November 20, 2015 at 11:36:03 AM UTC, Lee Armstrong wrote: > > Hello, > > I have a very strange issue that I cannot seem to work out and get

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

Oh no! I will try building myself but failing that I can probably wait till Thursday. Will report back if the issue gets fixed. Lee On Mon, Oct 26, 2015 at 5:07 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Mon, Oct 26, 2015 at 11:53 AM, Lee Armstrong <l...@p

Re: [beagleboard] Power Button doesn't work on 4.1.10-ti-r24

Ah thanks Robert! Is there a way to get this update with one of the scripts built in like the update_kernel.sh ? I’d love to try this out but not really sure how to apply this! Lee On Mon, Oct 26, 2015 at 4:52 PM, Robert Nelson wrote: > On Sat, Oct 24, 2015

Re: [beagleboard] Kernel 4.1.9 overlays not working

Robert, Yes that is much better thank you.  Working well now :-) Thank you very much, Lee On Tue, Oct 13, 2015 at 4:22 PM, Robert Nelson <robertcnel...@gmail.com> wrote: > On Tue, Oct 13, 2015 at 10:20 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> Thanks Ro

Re: [beagleboard] Kernel 4.1.9 overlays not working

Thanks Robert,  I am simply trying to enable UART4 which I didn’t think needed anything disabling though? Lee On Tue, Oct 13, 2015 at 4:00 PM, Robert Nelson wrote: > On Tue, Oct 13, 2015 at 9:36 AM, wrote: >> I am also getting the same

Re: [beagleboard] Kernel 4.1.9 overlays not working

nel...@gmail.com> wrote: > On Tue, Oct 13, 2015 at 10:01 AM, Lee Armstrong <l...@pinkfroot.com> wrote: >> Thanks Robert, >> >> I am simply trying to enable UART4 which I didn’t think needed anything >> disabling though? > in /boot/uEnv.txt > cape_enable=bon

Re: [beagleboard] Image 2015-7-26, kernel 4.1.3-ti-r6

What is the best way to get this applied to the last snapshot 2015-08-09 Is there a download of a .deb? For other units, will they pick this up using apt-get when this gets published? On Wednesday, August 12, 2015 at 9:27:15 PM UTC+1, Felipe Balbi wrote: On Wed, Aug 12, 2015 at 03:23:03PM

Re: [beagleboard] PPS Support from GPIO

Ah ok, I do actually mean to use P8.26 which I think is GPIO1_29. I am using a 3.8 kernel, any way to check at all if it is fixed or not as well? On 29 January 2014 at 19:19:00, selsin...@gmail.com (selsin...@gmail.com) wrote: On 28/01/14 15:18, l...@pinkfroot.com wrote: I have what I think

Re: [beagleboard] PPS Support from GPIO

On 29 January 2014 at 21:05:00, selsin...@gmail.com (selsin...@gmail.com) wrote: On 29/01/14 19:24, Lee Armstrong wrote: Ah ok, I do actually mean to use P8.26 which I think is GPIO1_29. I am using a 3.8 kernel, any way to check at all if it is fixed or not as well? It's