[beagleboard] Re: Explanation of PRU Programming in C

[Joseph Heller]

On Tuesday, May 16, 2017 at 1:01:55 AM UTC+2, Clark Sann wrote:
>
> Hi Joseph
>
> Nice writeup. You did a good job of explaining a complex topic...at least 
> it seems complex to me. I have however found a possible error.
>
> Shouldn't you be referring to the DEFAULT_INC value rather than the 
> CMP_INC value in your description?
>

Hi Clark, 

That's a good catch - I've corrected this.

Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e92ff34b-45f0-4374-ab88-23acc3b7cb43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: watchdog messages clutter up serial console

['Barry Day' via BeagleBoard]

Try raising your console log level. I usually have my set to -

# echo 3 4 1 7 > /proc/sys/kernel/printk

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0c445520-efc0-44f8-a8b4-01cc21de3217%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Realtek USB Wifi problems

['Barry Day' via BeagleBoard]

On Sunday, May 14, 2017 at 5:02:47 AM UTC+10, acheesehead wrote:
>
> I have a BBB running Angstrom 3.8.13. I have a Realtek USB Wifi, lsusb 
> shows
> Bus 002 Device 004: ID 0bda:818b Realtek Semiconductor Corp.
>
>
> That's an 8192eu, not an 8192cu 

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/f7e42f79-8e50-4420-af68-f4879609de3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: I2S Audio on the BBB

[Graham]

Yes, I was able to get a CircuitCo Rev.B Audio cape running, using the 
I2S/McASP interface.
I'll write it up for you, if you are interested.

If you are going to use a different CODEC or other device on the I2S/McASP 
interface,
you will need to see if a driver already exists for it, or if it fits a 
generalized I2S audio interface that
is already inside the kernel can be invoked and controlled from a device 
tree.

If it is unique, then you will have to write your own Linux driver and 
recompile the kernel.

If you just want audio, it is a lot easier to just use a USB CODEC.

--- Graham

==

On Monday, May 15, 2017 at 6:11:11 PM UTC-5, ags wrote:
>
> I'm also interested as I have a project where I will interface directly to 
> the I2S/McASP interface. Did you figure it out?
>
>
> On Tuesday, January 3, 2017 at 8:57:29 AM UTC-8, Graham wrote:
>>
>> I spent most of the weekend down in the rabbit-hole, trying to get a
>> CircuitCo Rev_B Audio cape to work, (unsuccessfully.)
>>
>> Is this cape compatible-with / supported-by Debian 8.6/kernel 4.4 ?
>>
>> Does the BB-BONE-AUDI-02-00A0.dtbo overlay that comes with the current 
>> distribution work?
>>
>> How can you tell if an overlay actually loaded, with 4.4? 
>> /sys/devices/platform/bone_capemgr/slots 
>> as well as the boot log, only shows the first physical four, and no 
>> longer shows the higher numbered "pseudo-capes" and overlay status.
>>
>> I understand that
>> The CircuitCo cape does not have an EEPROM, so everything needs to be 
>> configured explicitly.
>> I need to use a base .dts with HDMI audio disabled, then load the overlay 
>> for the CircuitCo card.
>> I also need to load the asound.state file.
>>
>> Am I approaching this correctly?
>>
>> I can not use a USB-soundcard for audio. I have several applications
>> that need McASP/I2S running for several other codecs, but I thought I 
>> would start 
>> with the CircuitCo cape as a starting point.
>>
>> Thanks,
>> --- Graham
>>
>> ==
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dbf661b1-4b7f-4eba-9475-acb6dd9d5b42%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to start gathering CAN frames using candump from within browser

[William Hermans]

Well, here is a guide that I wrote a bit over a year and a half ago, which
I had forgotten:
http://www.embeddedhobbyist.com/2015/09/linux-can-development/

I'm not sure how useful that would be for your overall application, but
it'll show you how to setup the socketCAN can-utils stuff.

On Sun, May 14, 2017 at 4:07 PM, William Hermans  wrote:

> By the way, websockets put simply, is a TCP connection between systems,
> that is always connected. So there is no need for Ajax, or any of that old
> school HTML mumbo jumbo.
>
> On Sun, May 14, 2017 at 4:04 PM, William Hermans 
> wrote:
>
>>
>>
>> On Sun, May 14, 2017 at 12:38 PM, Piotr C  wrote:
>>
>>> Thanks for suggestions.
>>> Do you have any further hints/examples/similar implementations that I
>>> could read, understand and eventually base on?
>>>
>>
>> The code I wrote is not, and will not be available to the public.
>>
>> There is no real way for me to show you how to do what all needs being
>> done. Here is why. By it's self, websockets is not necessarily an easy
>> concept to understand let alone write code for implementation. As such the
>> easiest way to get started, would be to use Nodejs and socket.io. At
>> this point, you need to understand how to install, and use Nodejs +
>> socket.io, as well as probably how to use Express as well. Keeping in
>> mind that having to know all this is just so you can understand the basics.
>> After this, you *may* be ready to move onto using websockets from a web /
>> websocket server written in C, or C++.
>>
>> Not to mention having to know how the CANBUS protocol you're using works,
>> knowing how socketCAN works under linux, and knowing how a multitude of
>> other software technologies work. So you can bring it all together, to make
>> your application work.
>>
>> So can I help you understand how to create such software ? No, not
>> really. This is something you're going to need to spend a lot of time on,
>> before things almost become clear as to how you need to proceed.
>>
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORr56Vx%2B_E2rGd-f60Da6S3Bory-QE1F5gWZfErU%3D%2Bj27g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Explanation of PRU Programming in C

[William Hermans]

On Wed, Apr 26, 2017 at 1:02 AM, Joseph Heller 
wrote:

> Updated link: http://catch22.eu/beaglebone/beaglebone-pru-c/
>

I may have mentioned this before, but I think blinking a USR LED would be
far more useful. Nothing to hook up, and worry about blowing the pins on
the processor, etc. However, then we're talking about involving the L3
interconnect, which might be what you did not want to do ?

A point of contention that I have with the article however, is: How does
the GPIO bank + DATA_OUT register get into the PRU's _R30 register ? This
also has to be dynamic somehow. I can't imagine all registers r0-r31 are
each dedicated to a single control register of *something*. Then yes, I do
know that some PRU registers are reserved, I just do not know which anymore.

In another part of the article:

> The issue faced here is that one has to deep-dive into the workings of the
> header files, and make the relation to the defined variables in those
> header files and the PRU registers defined in the Reference Manual.
> Fortunately the header files and the reference manual closely match each
> other. *Unfortunately, you have to do the footwork to figure it out for
> each common or less common usage of the registers. For instance, here’s a
> relevant section of the pru_iep.h header file for the IEP example above:*


Then you go on to show some "pictures" from various sources, most notably
the applicable registers from the TRM. My point here is, I'm not sure what
your point is. This is pretty much standard procedure when working with any
hardware on this level. That is, *IF* you really need to know for sure,
what you're doing.

So, do not get me wrong, I'm not bashing what you've done there at all.
It's a lot more than I've done in demonstrating the PRU's to the public.
Mostly due to the fact that I do not know how to use the PRU's very well at
all.

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORrSHOWhHF_OL7X3NeEca_GCxN9HpomoXvs7AfnoPwgQ%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Explanation of PRU Programming in C

[William Hermans]

Also very glad you chose to demonstrate this using UIO, instead of
remote_proc.

On Mon, May 15, 2017 at 6:26 PM, William Hermans  wrote:

>
>
> On Wed, Apr 26, 2017 at 1:02 AM, Joseph Heller  > wrote:
>
>> Updated link: http://catch22.eu/beaglebone/beaglebone-pru-c/
>>
>
> I may have mentioned this before, but I think blinking a USR LED would be
> far more useful. Nothing to hook up, and worry about blowing the pins on
> the processor, etc. However, then we're talking about involving the L3
> interconnect, which might be what you did not want to do ?
>
> A point of contention that I have with the article however, is: How does
> the GPIO bank + DATA_OUT register get into the PRU's _R30 register ? This
> also has to be dynamic somehow. I can't imagine all registers r0-r31 are
> each dedicated to a single control register of *something*. Then yes, I do
> know that some PRU registers are reserved, I just do not know which anymore.
>
> In another part of the article:
>
>> The issue faced here is that one has to deep-dive into the workings of
>> the header files, and make the relation to the defined variables in those
>> header files and the PRU registers defined in the Reference Manual.
>> Fortunately the header files and the reference manual closely match each
>> other. *Unfortunately, you have to do the footwork to figure it out for
>> each common or less common usage of the registers. For instance, here’s a
>> relevant section of the pru_iep.h header file for the IEP example above:*
>
>
> Then you go on to show some "pictures" from various sources, most notably
> the applicable registers from the TRM. My point here is, I'm not sure what
> your point is. This is pretty much standard procedure when working with any
> hardware on this level. That is, *IF* you really need to know for sure,
> what you're doing.
>
> So, do not get me wrong, I'm not bashing what you've done there at all.
> It's a lot more than I've done in demonstrating the PRU's to the public.
> Mostly due to the fact that I do not know how to use the PRU's very well at
> all.
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORp7MJ9O-%3Do%2BSmxgqPHKND%2BaWxTrJyKtYic%3DoiA5w0EQ%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: I2S Audio on the BBB

[ags]

I'm also interested as I have a project where I will interface directly to 
the I2S/McASP interface. Did you figure it out?


On Tuesday, January 3, 2017 at 8:57:29 AM UTC-8, Graham wrote:
>
> I spent most of the weekend down in the rabbit-hole, trying to get a
> CircuitCo Rev_B Audio cape to work, (unsuccessfully.)
>
> Is this cape compatible-with / supported-by Debian 8.6/kernel 4.4 ?
>
> Does the BB-BONE-AUDI-02-00A0.dtbo overlay that comes with the current 
> distribution work?
>
> How can you tell if an overlay actually loaded, with 4.4? 
> /sys/devices/platform/bone_capemgr/slots 
> as well as the boot log, only shows the first physical four, and no longer 
> shows the higher numbered "pseudo-capes" and overlay status.
>
> I understand that
> The CircuitCo cape does not have an EEPROM, so everything needs to be 
> configured explicitly.
> I need to use a base .dts with HDMI audio disabled, then load the overlay 
> for the CircuitCo card.
> I also need to load the asound.state file.
>
> Am I approaching this correctly?
>
> I can not use a USB-soundcard for audio. I have several applications
> that need McASP/I2S running for several other codecs, but I thought I 
> would start 
> with the CircuitCo cape as a starting point.
>
> Thanks,
> --- Graham
>
> ==
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8cb2bc47-11ed-4748-9f1f-755266bc5746%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Explanation of PRU Programming in C

[Clark Sann]

Hi Joseph

Nice writeup. You did a good job of explaining a complex topic...at least 
it seems complex to me. I have however found a possible error.

Shouldn't you be referring to the DEFAULT_INC value rather than the CMP_INC 
value in your description?

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/91070fe2-5cf3-4ce3-8199-dc153b39c317%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] mpg123 1.20.1 crashes getting sample rate (FORMAT command)

[ags]

I am building an interface to mpg123 from another application using the 
Remote command interface. I have observed that if the FORMAT command is 
issued to get the audio sample rate (e.g. 44100) after a file is loaded but 
before starting playback, the mpg123 process will crash when playback is 
started. If the file is loaded and played, then paused, then FORMAT issued, 
playback will continue without error. I've duplicated this using a USB 
audio "card" as well as the build-in mcasp interface.

Linux BBB 4.4.30-ti-r64 #1 SMP Fri Nov 4 21:23:33 UTC 2016 armv7l GNU/Linux
mpg123 version: 1.20.1, installed using apt install mpg123 on BBB running 
jessie 
Log: (inline descriptive comments added to actual log output is designated 
by //)

$ mpg123 -R -a default:Device   // start mpg123 in "Remote command 
mode" with standard mcasp audio device

@R MPG123 (ThOr) v8 // response: normal startup message

LOADPAUSED ./my_file.mp3 // command: "LOADPAUSED/LP" - load a 
file ("my_file.mp3") but do not begin playback

@I ID3v2.title:my_track // response: ID3 information...

@I ID3v2.artist:my_artist

@I ID3v2.album:my_album

@I ID3v2.year:2017

@I ID3v2.comment:12++

@I ID3v2.genre:Country & Folk

@P 1// response: file loaded & paused, 
ready to begin file playback

FORMAT  // command: "FORMAT" - get audio sample 
rate and channel count

@FORMAT 44100 2 // response: 44100 Hz, 2-channel

PAUSE   // command: "PAUSE" - pause/un-pause

@P 2// response: OK, playing file, but...


[alsa.c:230] error: Fatal problem with alsa output, error -5.


[audio.c:614] error: Error in writing audio (Success?)!


[mpg123.c:681] error: Deep trouble! Cannot flush to my output anymore!


Doing the same thing without issuing the "FORMAT" command works fine. Doing 
the same thing, but after loading file, beginning playback, then pausing, 
then issuing "FORMAT" command, then continuing playback (or seeking back to 
the beginning of the file and playing) works fine.


Any ideas how to resolve this, or repair it? I've searched and not found 
anything about this (most issues seemed to be related to alsa).


Thanks.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/8f05c91a-b0c8-4ee2-8b6c-9b83bc2d1126%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Development with Eclipse and Remote Debugging

[William Hermans]

There are many way to build a development environment. Me, I just compile
on the beaglebone directly, and if I need anything  "big" compiled, I have
an ODROID XU4 - Octa core 2G ram. I've only ever needed to use a debugger
once, and not for these platforms. If I did however, I'd use gdb, and
perhaps if I needed remote debugging, gdb-server, or the like

On Mon, May 15, 2017 at 10:15 AM, Mark A. Yoder 
wrote:

> Clark:
>   A lot has happened in 7 years.  I've moved from Eclipse on the host to
> running Cloud 9 on the Bone.  It's as easy as pointing the browser on your
> host to http://192.168.7.2:3000 and Cloud 9 appears.  The Bone is fast
> enough for the small (and some not so small) compiles that I do.
>
> My first thought was that a web-based IDE must be sluggish, but I was
> wrong, it very responsive.  In fact I wrote most of the BeagleBone Cookbook
> using Cloud 9.
>
> --Mark
>
>
> On Monday, May 15, 2017 at 10:39:58 AM UTC-4, Clark Sann wrote:
>>
>> I don't yet have a BB but I am doing cross compilation for the RPi. I
>> don't need to chmod and I don't see any reference to chmod on the
>> instructions you linked to ([2]). On my Debian VM I can create the source,
>> compile, copy it to the RPi and execute it from the terminalall in
>> Eclipse. I don't need to do chmod during this workflow.
>>
>> I am hoping the same procedure will work when I get my BB Blue.
>>
>> I am however not able to get remote debugging working. I haven't spent
>> enough time on this and so my debugging is limited to inserting printf
>> statements. It's very inefficient. I've got to spend time to get remote
>> debugging working.
>>
>> To setup my computer I used the procedure in Derek Malloy's book
>> "Exploring the Raspberry Pi". I have recently purchased "Exploring
>> BeagleBone" and it has a similar but not identical procedure. Both of those
>> books are really excellent. They contain a wealth of information about
>> embedded linux programming on those devices. You might consider purchasing
>> his BB book and see if it helps.
>>
>> He also has a youtube video that may help you  Cross Compilation for
>> BB  and his youtube channel
>> has a lot of other very informative videos.
>>
>> I followed his steps but I'm still not able to remote debug. I'm pretty
>> sure I misunderstood one of his steps...or maybe the procedure changed due
>> to a Debian or Eclipse update. Whatever, I'm certain I will get it working
>> when I get time to spend on it.
>>
>> Clark
>>
>>
>> On Friday, April 2, 2010 at 2:49:26 PM UTC-5, Mark A. Yoder wrote:
>>>
>>> Hi:
>>>   Has anyone been successful with using Eclipse[1] on the host
>>> computer to develop for the Beagle?  I had it working last yea, but
>>> now I only have it almost working.  Me setup is at [2].
>>>
>>> I'm able to cross-compile on my host an automatically download the
>>> executable to the Beagle.  However get an error before it does a chmod
>>> on the executable on the Beagle.  (Error during file upload.
>>> Operation failed. File system input or output error.)
>>>
>>> Does anyone know how to fix this?
>>>
>>> --Mark
>>>
>>> [1] http://www.eclipse.org/
>>> [2] http://elinux.org/ECE597_Installing_the_Eclipse_IDE
>>> 
>>>
>>> --
> 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.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/29bec025-2707-4bd7-a3c2-ddc1551dfd65%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALHSORpKX_ABBQ%3DzSNSKiXK8Hj%3D8%2BtkyNg5Lizu5WGrG2THZhg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Development with Eclipse and Remote Debugging

[Mark A. Yoder]

Clark:
  A lot has happened in 7 years.  I've moved from Eclipse on the host to 
running Cloud 9 on the Bone.  It's as easy as pointing the browser on your 
host to http://192.168.7.2:3000 and Cloud 9 appears.  The Bone is fast 
enough for the small (and some not so small) compiles that I do.

My first thought was that a web-based IDE must be sluggish, but I was 
wrong, it very responsive.  In fact I wrote most of the BeagleBone Cookbook 
using Cloud 9.

--Mark

On Monday, May 15, 2017 at 10:39:58 AM UTC-4, Clark Sann wrote:
>
> I don't yet have a BB but I am doing cross compilation for the RPi. I 
> don't need to chmod and I don't see any reference to chmod on the 
> instructions you linked to ([2]). On my Debian VM I can create the source, 
> compile, copy it to the RPi and execute it from the terminalall in 
> Eclipse. I don't need to do chmod during this workflow. 
>
> I am hoping the same procedure will work when I get my BB Blue. 
>
> I am however not able to get remote debugging working. I haven't spent 
> enough time on this and so my debugging is limited to inserting printf 
> statements. It's very inefficient. I've got to spend time to get remote 
> debugging working. 
>
> To setup my computer I used the procedure in Derek Malloy's book 
> "Exploring the Raspberry Pi". I have recently purchased "Exploring 
> BeagleBone" and it has a similar but not identical procedure. Both of those 
> books are really excellent. They contain a wealth of information about 
> embedded linux programming on those devices. You might consider purchasing 
> his BB book and see if it helps. 
>
> He also has a youtube video that may help you  Cross Compilation for 
> BB  and his youtube channel 
> has a lot of other very informative videos.
>
> I followed his steps but I'm still not able to remote debug. I'm pretty 
> sure I misunderstood one of his steps...or maybe the procedure changed due 
> to a Debian or Eclipse update. Whatever, I'm certain I will get it working 
> when I get time to spend on it. 
>
> Clark
>
>
> On Friday, April 2, 2010 at 2:49:26 PM UTC-5, Mark A. Yoder wrote:
>>
>> Hi:
>>   Has anyone been successful with using Eclipse[1] on the host
>> computer to develop for the Beagle?  I had it working last yea, but
>> now I only have it almost working.  Me setup is at [2].
>>
>> I'm able to cross-compile on my host an automatically download the
>> executable to the Beagle.  However get an error before it does a chmod
>> on the executable on the Beagle.  (Error during file upload.
>> Operation failed. File system input or output error.)
>>
>> Does anyone know how to fix this?
>>
>> --Mark
>>
>> [1] http://www.eclipse.org/
>> [2] http://elinux.org/ECE597_Installing_the_Eclipse_IDE 
>> 
>>
>>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/29bec025-2707-4bd7-a3c2-ddc1551dfd65%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

['Torsten K.' via BeagleBoard]

Hi Graham,

Am Montag, 15. Mai 2017 18:39:10 UTC+2 schrieb Graham:
>
> When they say drop the clock speed on the bus, I am sure they mean to drop 
> it down to 50kbps or 10 kbps, and see if it starts working.
> As a diagnostic, that would be strong indication of a timing problem in 
> the PIC software.
>

I tried bus speeds down to 50 kbps to no avail. I'll probably try 10 kbps 
tomorrow.

Unfortunately, I never programmed a PIC, so I'll probably have a hard time 
finding out what's going on.

Best,
Torsten

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ceecae31-0cf2-47bb-9d1c-9f9cbbf72efd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

[Graham Haddock]

When they say drop the clock speed on the bus, I am sure they mean to drop
it down to 50kbps or 10 kbps, and see if it starts working.
As a diagnostic, that would be strong indication of a timing problem in the
PIC software.

If they are using the PIC hardware peripheral, then it is totally I2C
compliant/conforming, although you could still screw up the response time
servicing it slowly internally.

If they are "bit-banging" the I2C interface, then anything can happen,
depending on the quality of the programmer.

--- Graham

On Mon, May 15, 2017 at 11:33 AM, Graham Haddock 
wrote:

> What part number PIC?
> --- Graham
>
> ==
>
> On Mon, May 15, 2017 at 9:36 AM, 'Torsten K.' via BeagleBoard <
> beagleboard@googlegroups.com> wrote:
>
>> Hi Graham,
>>
>> just for reference: The guys who built the motor controller confirmed
>> that they are having trouble with newer kernels on the Raspberry PI, too.
>>
>> https://www.piborg.org/node/2428
>>
>> They say it's probably a timing issue. And with all the information I
>> collected so far I must assume they are probably true. ;-)
>>
>> I hope it's not the PIC itself that can't cope, but rather something that
>> could be solved in software...
>>
>> Best,
>> Torsten
>>
>> --
>> 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/to
>> pic/beagleboard/-cVwfP40L0M/unsubscribe.
>> To unsubscribe from this group and all its topics, send an email to
>> beagleboard+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/6eddd754-92b7-4ec8-bd01-b0aa3b500f9f%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CANN_KV6WjSW0C7y6AAyYbmpEaynz5PptSq9Nn49nT%3DmGU3RbOQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

[Graham Haddock]

What part number PIC?
--- Graham

==

On Mon, May 15, 2017 at 9:36 AM, 'Torsten K.' via BeagleBoard <
beagleboard@googlegroups.com> wrote:

> Hi Graham,
>
> just for reference: The guys who built the motor controller confirmed that
> they are having trouble with newer kernels on the Raspberry PI, too.
>
> https://www.piborg.org/node/2428
>
> They say it's probably a timing issue. And with all the information I
> collected so far I must assume they are probably true. ;-)
>
> I hope it's not the PIC itself that can't cope, but rather something that
> could be solved in software...
>
> Best,
> Torsten
>
> --
> 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/-cVwfP40L0M/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/6eddd754-92b7-4ec8-bd01-b0aa3b500f9f%40googlegroups.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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CANN_KV6D2vU68zxJ-19p-G9Ux%2B62jUE%2BfMwmbPEm0L-e5XMNsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Use UART4 and HDMI Simultaneously

[Robert Nelson]

On Mon, May 15, 2017 at 11:14 AM, Roopak Jada
 wrote:
> Thanks Robert,
>
> I actually enabled the BB-UART 4 in the uEnv.txt and the HDMI stopped
> working. Are the CATS,RTS enabled by default ? How do I check which dto is
> being used ?

Well the RTS is in a separate overlay:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART4-RS485-00A0.dts

CTS not used..

Couple thing to check: bb-cape-overlays version

debian@beaglebone:~$ dpkg --list | grep bb-cape-overlays
ii  bb-cape-overlays
4.4.20170510.0-0rcnee0~jessie+20170510  armhfDevice tree
overlays for Beaglebone.

And whatever "/opt/scripts/tools/version.sh " prints out (it's fairly new)

debian@beaglebone:~$ sudo /opt/scripts/tools/version.sh
git:/opt/scripts/:[6dcd9ecbbb8215a0898b950148a328f06dd8aa0b]
eeprom:[A335BNLTBLA0*]
dogtag:[BeagleBoard.org Debian Image 2017-05-14]
partition_table:[NAME MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT]
partition_table:[mmcblk1boot0 179:804M  1 disk ]
partition_table:[mmcblk1boot1 179:16   04M  1 disk ]
partition_table:[mmcblk1  179:00  3.6G  0 disk ]
partition_table:[└─mmcblk1p1  179:10  3.6G  0 part /]
bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.05-2-gc5dd2565b4]
kernel:[4.4.62-ti-r103]
nodejs:[v4.8.3]
uboot_overlay_options:[enable_uboot_overlays=1]
uboot_overlay_options:[uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo]
uboot_overlay_options:[enable_uboot_cape_universal=1]

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgZgMDxFR3%3DYOwa_Gfbt24st9mbFazuvFAaTCt%2Bg4Yc_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Use UART4 and HDMI Simultaneously

[Roopak Jada]

Thanks Robert,

I actually enabled the BB-UART 4 in the uEnv.txt and the HDMI stopped
working. Are the CATS,RTS enabled by default ? How do I check which dto is
being used ?

On May 15, 2017 7:59 PM, "Robert Nelson"  wrote:

> On Mon, May 15, 2017 at 5:58 AM, rj-ib-23 
> wrote:
> > Hello All
> >
> > I understand that The CTS and RTS pins of UART 4 are used in the HDMI
> > Virtual Cape. I wanted to check if it is possible to use UART 4 TX and Rx
> > pins only and also the HDMI Cape simultaneously. I donto have any
> > requirement for the CTS and RTS pins. Will it be possible to customize
> the
> > device tree to have only the Rx,Tx pins of UART4 and HDMI work
> > simultaneously ?
>
> Yes you can use uart4's rx/tx with the display active:
>
> P9_11 (uart4_rx)
> P9_13 (uart4_tx)
>
> aren't allocated for video.
>
> https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-UART4-00A0.dts
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAGTuzRCBpsyDGNwgK9sJqCtEuaFZ1ZWsfHMuQXpDSaAwPQ60UQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Development with Eclipse and Remote Debugging

[Clark Sann]

I don't yet have a BB but I am doing cross compilation for the RPi. I don't 
need to chmod and I don't see any reference to chmod on the instructions 
you linked to ([2]). On my Debian VM I can create the source, compile, copy 
it to the RPi and execute it from the terminalall in Eclipse. I don't 
need to do chmod during this workflow. 

I am hoping the same procedure will work when I get my BB Blue. 

I am however not able to get remote debugging working. I haven't spent 
enough time on this and so my debugging is limited to inserting printf 
statements. It's very inefficient. I've got to spend time to get remote 
debugging working. 

To setup my computer I used the procedure in Derek Malloy's book "Exploring 
the Raspberry Pi". I have recently purchased "Exploring BeagleBone" and it 
has a similar but not identical procedure. Both of those books are really 
excellent. They contain a wealth of information about embedded linux 
programming on those devices. You might consider purchasing his BB book and 
see if it helps. 

He also has a youtube video that may help you  Cross Compilation for BB 
 and his youtube channel has a 
lot of other very informative videos.

I followed his steps but I'm still not able to remote debug. I'm pretty 
sure I misunderstood one of his steps...or maybe the procedure changed due 
to a Debian or Eclipse update. Whatever, I'm certain I will get it working 
when I get time to spend on it. 

Clark


On Friday, April 2, 2010 at 2:49:26 PM UTC-5, Mark A. Yoder wrote:
>
> Hi:
>   Has anyone been successful with using Eclipse[1] on the host
> computer to develop for the Beagle?  I had it working last yea, but
> now I only have it almost working.  Me setup is at [2].
>
> I'm able to cross-compile on my host an automatically download the
> executable to the Beagle.  However get an error before it does a chmod
> on the executable on the Beagle.  (Error during file upload.
> Operation failed. File system input or output error.)
>
> Does anyone know how to fix this?
>
> --Mark
>
> [1] http://www.eclipse.org/
> [2] http://elinux.org/ECE597_Installing_the_Eclipse_IDE 
> 
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/41200943-88ff-49b5-b047-4eca2eaab0fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

['Torsten K.' via BeagleBoard]

Hi Graham,

just for reference: The guys who built the motor controller confirmed that 
they are having trouble with newer kernels on the Raspberry PI, too.

https://www.piborg.org/node/2428

They say it's probably a timing issue. And with all the information I 
collected so far I must assume they are probably true. ;-)

I hope it's not the PIC itself that can't cope, but rather something that 
could be solved in software...

Best,
Torsten

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/6eddd754-92b7-4ec8-bd01-b0aa3b500f9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Node-red serial port & Digital I/O control question

[Michael Dalby]

Hi All

I wondered if somebody can help.

I am trying to get a simple serial port to work with Node-Red on a 
beagleBone Black running Debian 8.7

The raw install of Debian 8.7 for BBB gives me a pre-installed version of 
Node-red (V0.15.2). This Node-Red image for BBB has a digital I/O library 
included  https://flows.nodered.org/node/node-red-node-beaglebone. allowing 
you  read input pins and set outputs.

Unfortunately this image does not include a serial port function as 
standard - so I have manually added one from 
https://flows.nodered.org/node/node-red-node-serialport

This adds the serial nodes correctly to my panel, but  I found I had to 
enable the required UART port by appending the following to uEnv.txt: 
*capemgr.enable_partno=BB-UART2*

The serial port now works but the BBB Digital I/O read/write nodes have 
*disappeared from 
the node selection panel. *

Does anyone know how can I get the Digital I/O nodes back / to work at the 
same time as having the serial nodes enabled.

I have tried not using the standard serial Node port in favour of using 
OctalBoneScript . but I couldn't work out how to get the read to work 
See my previous unanswered question  
https://groups.google.com/forum/#!searchin/beagleboard/dalby%7Csort:relevance/beagleboard/G5N12N8p2qM/7_WJyaOLBQAJ

All I want is to be able to use a serial port and a digital I/O pin control 
at the same time.

Any help would be appreciated

Many thanks

Michael

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/d7124b68-250c-42b9-9a58-a8b3da471bbe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Use UART4 and HDMI Simultaneously

[Robert Nelson]

On Mon, May 15, 2017 at 5:58 AM, rj-ib-23  wrote:
> Hello All
>
> I understand that The CTS and RTS pins of UART 4 are used in the HDMI
> Virtual Cape. I wanted to check if it is possible to use UART 4 TX and Rx
> pins only and also the HDMI Cape simultaneously. I donto have any
> requirement for the CTS and RTS pins. Will it be possible to customize the
> device tree to have only the Rx,Tx pins of UART4 and HDMI work
> simultaneously ?

Yes you can use uart4's rx/tx with the display active:

P9_11 (uart4_rx)
P9_13 (uart4_tx)

aren't allocated for video.

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART4-00A0.dts

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYjWWrZP-rvDJJ9aqti2QZZ8BkgFZs-4-30qX%3DqB0Ri0-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Use UART4 and HDMI Simultaneously

[rj-ib-23]

Hello All

I understand that The CTS and RTS pins of UART 4 are used in the HDMI 
Virtual Cape. I wanted to check if it is possible to use UART 4 TX and Rx 
pins only and also the HDMI Cape simultaneously. I donto have any 
requirement for the CTS and RTS pins. Will it be possible to customize the 
device tree to have only the Rx,Tx pins of UART4 and HDMI work 
simultaneously ?

Thanks!

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/79c91b72-857a-42f8-a0f8-787093722590%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Using BBBW as Bluetooth SPP device

[fgimbert]

Hello!

I'm using BBB for a few years now and they are great and I'm fan of these!
With BBB, I used to add a external Bluetooth module and to interact with it 
through a serial port. A mobile application connects to the BBB (the BBB is 
the salve and waits for connection).
With BBBW, I hope to be able to remove the external BT module to use the 
onboard one. I made quite a lot of googling around this but I've not been 
able to find out how to setup a slave SPP mode using the BBBW' bluetooth.

Could someone help me on this topic?
Thank you very much!
Florian

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/33c8a4fd-b7de-4240-944c-86377dec3de2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Using RTC

[ph . fouquet]

Hi

I try to use the RCT's SoC but it din't look like work.

I'm using the command : "hwclock -D" and I have a message :

hwclock from util-linux 2.25.2
Using the /dev interface to the clock.
Assuming hardware clock is kept in UTC time.
Waiting for clock tick...
select() to /dev/rtc to wait for clock tick timed out...synchronization 
failed


In dmesg the RTC it loading :

[2.185041] omap_rtc 44e3e000.rtc: already running
[2.185517] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as 
rtc0
[2.456683] PM: bootloader does not support rtc-only!
[2.457802] omap_rtc 44e3e000.rtc: setting system clock to 2000-01-01 00:
00:00 UTC (946684800)

If some body have idea what is wrong?

Thank
Philippe FOUQUET

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/a6be5acf-7898-41cc-b102-4f966d2ae449%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Can´t echo to slotsfile

[Robert Nelson]

On Mon, May 15, 2017 at 8:19 AM, Beagle Boner  wrote:
> Thanks for your response guys,
>
> i figgured out that you have to be root to echo into the slotsfile, sudo
> with debian user is not enough.

That's incorrect, and stated in my previous email

sudo echo "something" > "somewhere"

doesn't work..

You need to:

sudo sh -C "echo 'BB-PWM1-00A0.dtbo' > /sys/devices/platform/bone_capemgr/slots"

Then it works..


> Just in case someone else has the same issue: When you write an overlay for
> your custom cape, you have to include it over /etc/defaut/capemgr, NOT via
> /boot/uEnv !

This just means the *.dtbo file isn't in the "initramfs"..

sudo update-initramfs -uk `uname -r`

and reboot..


>This is for Debian Jessie 8.7 (4.4.54). All the changes with
> different kernels are confusing me so much as a beginner.

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYhMeqi%2Bc7QXkXG5ZsdPbJ6AjW7BU-2R_jF%3DmDTpZCbCUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Can´t echo to slotsfile

[Beagle Boner]

Thanks for your response guys,

i figgured out that you have to be root to echo into the slotsfile, sudo 
with debian user is not enough. 
Just in case someone else has the same issue: When you write an overlay for 
your custom cape, you have to include it over /etc/defaut/capemgr, NOT via 
/boot/uEnv ! This is for Debian Jessie 8.7 (4.4.54). All the changes with 
different kernels are confusing me so much as a beginner.

Cheers!

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ed0f241c-3d3f-4bee-aa6a-7ca73066bfc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

[Graham]

Torsten:

OK. That makes more sense.  

If it is a PIC misbehaving, I would re-program it first, then make sure you 
have good bypass capacitor to ground, with short leads, on the power input 
pin to the ground pin on the PIC.

Good luck.

--- Graham

==

On Monday, May 15, 2017 at 3:59:03 AM UTC-5, Torsten K. wrote:
>
> Hi again,
>
> this morning, I connected another IMU unit (Polulu AltIMU10 v5) in 
> parallel to the motor controller on I²C bus #1.
> It works flawlessly and I can read the ID of the accel/gyro unit using 
> i2cget:
>
> tkurbad@beaglebone:~/projects/mipSIE/python3$ i2cget -y 1 0x6b 0x0f
> 0x69
>
> However, I still can't read from the motor controller. The working IMU 
> however leads to the conclusion that the problem must lie with the motor 
> controller, not with the Beaglebone.
>
> I've ordered a PIC debugger to see what's going on inside the PIC on the 
> motor controller that does all the I²C communication.
>
> Anyway, thanks for all your help!
>
> Best,
> Torsten
>
>

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e918a5c2-3d7d-41be-a6b8-eeb5af5ba4f7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: I²C reads on broken out bus #1 always return 0

['Torsten K.' via BeagleBoard]

Hi again,

this morning, I connected another IMU unit (Polulu AltIMU10 v5) in parallel 
to the motor controller on I²C bus #1.
It works flawlessly and I can read the ID of the accel/gyro unit using 
i2cget:

tkurbad@beaglebone:~/projects/mipSIE/python3$ i2cget -y 1 0x6b 0x0f
0x69

However, I still can't read from the motor controller. The working IMU 
however leads to the conclusion that the problem must lie with the motor 
controller, not with the Beaglebone.

I've ordered a PIC debugger to see what's going on inside the PIC on the 
motor controller that does all the I²C communication.

Anyway, thanks for all your help!

Best,
Torsten

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/46e89a08-1afa-488c-9e2f-24ee368b22b0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] usb0 as a simple serial program interface

[walter harms]

Am 13.05.2017 21:00, schrieb ashwal.harel via BeagleBoard:
> I'm using BBB can I change usb0 (client mode usb ) to show my product CLI 
> interface rather then linux console?
> 

yes,
there are basically 2 ways.
1. with password.
create an useraccount and use .profile to start you program

2. redirect, run via inittab (systemd) e.g top >/dev/tty10

Note: do not forget to disable all interaction with your program
  otherwise a malevolent user can easily access your box.

re,
 wh

-- 
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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/59195C57.40405%40bfs.de.
For more options, visit https://groups.google.com/d/optout.