[beagleboard] UART at run time

I understood the process for accessing the GPIOs at run time but I'm unable to do the same for UART. I executed the following commands on the terminal window for accessing UART, which I want to add into the (init.genericam33xx(flatteneddevicetr.rc) file such that the commands could be well exe

[beagleboard] Integration of EVAL-ADAU1X61EBZ with BeagleBone Black

Hello all, I am trying to integrate the EVAL-ADAU1X61EBZ evaluation board with BeagleBone Black. I tried installing the 1761 driver referring to the example code: linux/adi,adau17x1.txt at master · torvalds/linux · GitHub

Re: [beagleboard] X15 Availability

Gerald Any update on shipping dates for the X15? The page at http://elinux.org/Beagleboard:BeagleBoard-X15 says that assembly is on hold. Is this still the case, or have the boards been built and are out for FCC testing? Thanks Pete. On Tuesday, 19 April 2016 19:26:19 UTC+1, Gerald wrote: > >

[beagleboard] Device-Tree Clarifications (Beaglebone Black)

The starting point for my questions is the BB-SPIDEV0-00A0.dts . *1. Description of problem:* The following fragment was taken from the above device tree spec: fragment@0 { target = <&am33xx_pi

[beagleboard] BBB has some strange FS-properties and boot-behaviur?

Hello BBB-hackers (and others... :) ) I am trying to understand the various parts that make up the bootprocess and properties that affect booting and flashing. Some questions that I have: When reading around, I get the impression that an SPL-file named "MLO" should be stored on mmcblk0p1. When

[beagleboard] Understanding the BBB boot process and how to flash

Hello BBB-hackers! My first attempt to post here sees to have failed. If this is a double post, a moderator can remove this or my previous post Im trying to understand how the boot process works and how to flash an am335x-based design. This raises some questions: Reading around I get the imp

Re: [beagleboard] X15 Availability

We have not built any boards yet. When we do, I will update the status. When the status changes it will be updated. Gerald On Fri, Jun 17, 2016 at 3:44 AM, <2ndeastleakesco...@gmail.com> wrote: > Gerald > > Any update on shipping dates for the X15? > The page at http://elinux.org/Beagleboard:Bea

Re: [beagleboard] Understanding the BBB boot process and how to flash

Unless you take the time to register, your posts are moderated. It is part of a complicated SPAM prevention process. Register and and after your first post it will go through without moderation. Gerald On Fri, Jun 17, 2016 at 4:45 AM, wrote: > Hello BBB-hackers! > > My first attempt to post he

[beagleboard] Need to hire someone to change the BBB layout

We have spend ~$40K on software for the BeagleBone Black. However, it will not physically fit in our application. We need someone to layout a new board and remove a few connectors and perhaps remove the HDMI circuits. Is there some place to post such a message in hopes of finding someone? Than

Re: [beagleboard] Device-Tree Clarifications (Beaglebone Black)

On Fri, Jun 17, 2016 at 4:03 AM, wrote: > The starting point for my questions is the BB-SPIDEV0-00A0.dts. > > 1. Description of problem: > > The following fragment was taken from the above device tree spec: > > fragment@0 { > target = <&am33xx_pinmux>; > __overlay__ { >

Re: [beagleboard] Need to hire someone to change the BBB layout

And you might consider looking at this to help with size as well: http://octavosystems.com/octavo_products/osd335x/ On Fri, Jun 17, 2016 at 8:50 AM, Randy Normann wrote: > We have spend ~$40K on software for the BeagleBone Black. However, it > will not physically fit in our application. > >

Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

@John Syne: Correct, remoteproc is stabil since month. Stabil in the point that it isn't usable. And that's why it is and it should be experimental. And experimental features shouldn't polute the main stream images! @Jason Reeder and Suman Anna: Thanks for joining that discussion and for sharin

Re: [beagleboard] Device-Tree Clarifications (Beaglebone Black)

Why did we switch to the macro AM33XX_IOPAD ? What is the advantage doing so ? By curiousity Le ven. 17 juin 2016 à 16:05, Robert Nelson a écrit : > On Fri, Jun 17, 2016 at 4:03 AM, wrote: > > The starting point for my questions is the BB-SPIDEV0-00A0.dts. > > > > 1. Description of problem:

Re: [beagleboard] Device-Tree Clarifications (Beaglebone Black)

On Fri, Jun 17, 2016 at 9:23 AM, Micka wrote: > Why did we switch to the macro AM33XX_IOPAD ? > > What is the advantage doing so ? By curiousity We switched, such that the random magic #'s now match TI's reference manual.. Regards, -- Robert Nelson https://rcn-ee.com/ -- For more options, v

Re: [beagleboard] BBB has some strange FS-properties and boot-behaviur?

MLO, and u-boot.img are in the MBR of the disk now days. See "Install bootloader" subsection here: https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-SetupmicroSDcard On Fri, Jun 17, 2016 at 2:17 AM, wrote: > Hello BBB-hackers (and others... :) ) > > I am trying to understand

[beagleboard] SPL bad magic at boot in the MLO file

Hi, when the board boot, I've the message that tell me : bad magic. and after a deep research, it come from the SPL : common/spl/spl_mmc.c if (image_get_magic(header) != IH_MAGIC) { puts("bad magic\n"); how can i fix that ? Micka, -- For more options, visit http://be

[beagleboard] Re: SPL bad magic at boot in the MLO file

I've compiled the uboot again and again, and it doesn't change anything when I replace the old MLO file : dd if=./MLO of=${DISK} count=1 seek=1 bs=128k Le ven. 17 juin 2016 à 18:16, Micka a écrit : > Hi, when the board boot, I've the message that tell me : > > bad magic. and after a deep rese

[beagleboard] Re: SPL bad magic at boot in the MLO file

On Fri, Jun 17, 2016 at 11:18 AM, Micka wrote: > I've compiled the uboot again and again, and it doesn't change anything when > I replace the old MLO file : > > dd if=./MLO of=${DISK} count=1 seek=1 bs=128k > > > > Le ven. 17 juin 2016 à 18:16, Micka a écrit : >> >> Hi, when the board boot, I've

[beagleboard] Re: SPL bad magic at boot in the MLO file

Lol, ok But what went wrong ? It's checking a magic number to prevent something broken. Can I write back the correct magic number ? I found that in this file : arch/powerpc/cpu/mpc8xx/start.S it write somewhere the magic number : 0x27051956 But I don't see where the magic number is written fo

Re: [beagleboard] Re: SPL bad magic at boot in the MLO file

//if (image_get_magic(header) != IH_MAGIC) { // puts("bad magic\n"); // } fixed! hehe ! On Fri, Jun 17, 2016 at 9:31 AM, Micka wrote: > Lol, ok > > But what went wrong ? It's checking a magic number to prevent something > broken. > > Can I write back the co

[beagleboard] Re: SPL bad magic at boot in the MLO file

On Fri, Jun 17, 2016 at 11:31 AM, Micka wrote: > Lol, ok > > But what went wrong ? It's checking a magic number to prevent something > broken. > > Can I write back the correct magic number ? > > I found that in this file : arch/powerpc/cpu/mpc8xx/start.S > > it write somewhere the magic number :

[beagleboard] Re: SPL bad magic at boot in the MLO file

ok When I compile the uboot, are we using this one ? arch/arm/cpu/armv7/start.S Can we add something like that : .long 0x27051956 /* U-Boot Magic Number */ Le ven. 17 juin 2016 à 18:47, Robert Nelson a écrit : > On Fri, Jun 17, 2016 at 11:31 AM, Micka wrote: >

[beagleboard] New project Bonejs

I've recently created very simple wrapper code for several peripherals, and one cmd line tool. In a similar context as Bonescript. Except the code I've written is very minimal and simple. I've been working on this in my spare time, while also working on other project simultaneously. So I may not

Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

> On Jun 17, 2016, at 7:17 AM, TJF wrote: > > @John Syne: > Correct, remoteproc is stabil since month. Stabil in the point that it isn't > usable. And that's why it is and it should be experimental. And experimental > features shouldn't polute the main stream images! I don’t agree, remoteproc

Re: [beagleboard] Re: Latest Jessie: cannot write to disk, cannot connect Eth over USB, could before

On Monday, June 13, 2016 at 4:56:26 PM UTC-7, William Hermans wrote: > > No, my goal is not to learn how to use Linux properly. My goal is to get a >> small app going in Android on a development board that uses BB as user >> interface. I think I know how to write an app in Android, but I'll be th

[beagleboard] Re: SPL bad magic at boot in the MLO file

OK that not it I think. I've tried to understand when the header is written in the MLO. And it looks like that it is the mkimage job . ( not sure ) . the mkimage is call to create the MLO file. I discovered that the function omapimage_set_header is called to create the header file. So it's not a

Re: [beagleboard] Re: Latest Jessie: cannot write to disk, cannot connect Eth over USB, could before

> > *It should be obvious from William's message immediately above why we will > not use BeagleBone going forward. His messages were unhelpful and I don't > see why I should be thankful for ridicule.* > Now you're just being spiteful, and silly. Anyone with half a brain can read up on this topic a

Re: [beagleboard] Re: Latest Jessie: cannot write to disk, cannot connect Eth over USB, could before

So let me share with you my perspective. Everything was all fine and dandy until you starting talking smack about the instructions to grow your partition. Which I tried explaining to everyone, is not the instructions, but the tools used in the instructions. At which point I tried to make it perfect

Re: [beagleboard] trying to use the USB networking with the IoT snapshot image

I came back to this, still not getting it to work. Seeing the same problem with Wheezy (had to go back). On Friday, April 22, 2016 at 8:53:57 PM UTC-5, John Stoner wrote: > > crap, reinstalled connman, reran the script, and no luck: > > [ root@beaglebone:~ ] > 0s 👍 #> ./beaglebone-black-g-ethe

Re: [beagleboard] Ti's RPMsg Examples Significantly Changed

> On Jun 17, 2016, at 2:22 PM, Anna, Suman wrote: > > Hi TJF, > > My responses inlined.. > > Regards > Suman > > From: John Syne [mailto:john3...@gmail.com ] > Sent: Friday, June 17, 2016 12:44 PM > To: beagleboard@googlegroups.com

Re: [beagleboard] Re: Latest Jessie: cannot write to disk, cannot connect Eth over USB, could before

On Friday, June 17, 2016 at 11:46:59 AM UTC-7, William Hermans wrote: > > *It should be obvious from William's message immediately above why we will >> not use BeagleBone going forward. His messages were unhelpful and I don't >> see why I should be thankful for ridicule.* >> > > Now you're just

RE: [beagleboard] Ti's RPMsg Examples Significantly Changed

Hi TJF, My responses inlined.. Regards Suman From: John Syne [mailto:john3...@gmail.com] Sent: Friday, June 17, 2016 12:44 PM To: beagleboard@googlegroups.com Cc: Reeder, Jason; jkrid...@beagleboard.org; Anna, Suman Subject: Re: [beagleboard] Ti's RPMsg Examples Significantly Changed On Jun 17,

RE: [beagleboard] Ti's RPMsg Examples Significantly Changed

On Jun 17, 2016, at 2:22 PM, Anna, Suman mailto:s-a...@ti.com>> wrote: Hi TJF, My responses inlined.. Regards Suman From: John Syne [mailto:john3...@gmail.com] Sent: Friday, June 17, 2016 12:44 PM To: beagleboard@googlegroups.com Cc: Reeder, Jason; jkrid...

[beagleboard] installa nginx on BBB - Debian

Hi, Just a simple question on desktop/server Debian installing nginx is just as simple as sudo apt-get install nginx. Is this the same for installing on BeagleBone Black (=the package available in the Debian distro for BBB)? Thanks. -- For more options, visit http://beagleboard.org/discuss --

Re: [beagleboard] installa nginx on BBB - Debian

If the package exists for the architecture, yes, it's the same. The architecture is armhf for the beaglebones. Also this is true for *any* software package or otherwise. The majority of software just needs to be compiled from source on an armhf system in order to work on that hardwre platform. *$

RE: [beagleboard] Ti's RPMsg Examples Significantly Changed

Greg, A quick test would be to revert the following patch (assuming you are using a BeagleBone variant) in your tree, if you continue to use your old firmware https://github.com/beagleboard/linux/commit/620cab817e7a06065452d4c119c3066061ad5f03 regards Suman From: Greg [mailto:soapy-sm...@comca