[beagleboard] After inserting sd image on bbb board, it does not work.

[나종식]

Hello!

I bought BeagleBone Black.


I followed the procedure linked below.

 -> https://eewiki.net/display/linuxonarm/BeagleBone+Black


After removing the micro SD card,
When you insert an SD card into BeagleBone, only one LED blink continuously 
and it appears to have no action.

I do not know why.  



I have run it like this:


1. *u-boot*

  1) wget -c https:
//rcn-ee.com/repos/git/u-boot-patches/v2017.03-rc2/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch
 

  2) patch -p1 < 0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch


*2.Linux Kernel*

  1) git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
  2) git checkout origin/ti-linux-rt-4.4.y -b tmp

*3.Ubuntu 16.04 LTS*
  1) wget -c https:
//rcn-ee.com/rootfs/eewiki/minfs/ubuntu-16.04.2-minimal-armhf-2017-03-02.tar.xz

*4.Setup microSD card*


-- 
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/06cefb5b-f768-478e-b77b-958afa18e8a7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Is there a way to send an interrupt from userspace to the PRU-ICSS?

[ags]

@William Hermans like you I won't be able to dig into the gory details of 
loading Linux. This is an interesting read (albeit high-level and prompting 
more questions). I think I can say a few things without understanding all 
the details:

It is correct (from detailed reading of the TI TRM) that 0x8000 is the 
physical memory address of the L3 DDR.
If Linux is leaving any physical memory unmapped, unused - that's a shame. 
Wasted precious resource.
The PRUSS UIO driver allocates memory and exposes the physical address in 
userspace. If this is not used, it is also a precious wasted resource.

Now comes the subjective stuff:

I'm going to presume that Linux isn't stupid, and not count on it leaving 
permanently-allocated and undocumented physical memory addresses available 
for those that know the secret handshake.
I will use the memory allocated by the PRUSS UIO driver to communicate 
between userspace the PRUICSS.

If someone from TI/BeagleBoard.org responds with clarification on where I'm 
incorrect, I'll adjust my position. As of now, for over two  years I've 
been asking this same question and gotten no definitive response. Anyone 
know who came up with the the am335x_pru_package examples?

Thanks for your input and replies. Much appreciated.

On Friday, March 10, 2017 at 7:30:25 PM UTC-8, William Hermans wrote:
>
> Here is another link that should explain it clear enough. 
> http://processors.wiki.ti.com/index.php/HOWTO_Change_the_Linux_Kernel_Start_Address#Modifying_memory.h
>
> So I would say that it is not by accident that the base address of 
> 0x800 works. In fact, if you think about it a little bit. . Read the 
> opening paragraph labeled "purpose", and replace "DSP" with "PRU", for all 
> intents and purposes. of this discussion.
>
>
> On Fri, Mar 10, 2017 at 7:59 PM, William Hermans  > wrote:
>
>> OK, according to some dicumentation I was able to find quickly, address 
>> 0x800 is the base address for the start of the DDR memory on the TI EVM 
>> board. Which is very similar to the beaglebone in memory layout.
>>
>> On Fri, Mar 10, 2017 at 7:38 PM, William Hermans > > wrote:
>>
>>> Thinking on it for a little longer, I almost want to say that the 
>>> Address 0x800h is actually the start of Linux's virtual memory map. But 
>>> I'm not 100% sure.
>>>  I'm doing my own research for a paying project, so can't really dive 
>>> into documentation for something else right now . . .
>>>
>>> On Fri, Mar 10, 2017 at 7:24 PM, William Hermans >> > wrote:
>>>


 On Fri, Mar 10, 2017 at 2:53 PM, ags  wrote:

> I've had a hard time getting any definitive responses to questions on 
> the subject of memory access & latency. It is true that the PRU cores 
> have 
> faster access to DRAM that is part of the PRU-ICSS (through the 32-bit 
> interconnect SCR) - though not single-cycle - than to system DDR. 
> However, 
> the ARM core accesses DDR through L3 fabric, but the PRU-ICSS through 
> L4FAST, so I'm thinking that it can access DDR faster than PRU-ICSS 
> memory.
>
> I've also asked about differences in latency/throughput/contention 
> comparing PRU-ICSS 12KB shared RAM v the 8KB data RAM. No response. Since 
> both 8K data RAM is accessible to both PRU cores, I'm not sure what the 
> benefit of the 12KB shared RAM is (thought I imagine there is, I just 
> can't 
> figure it out).
>
> Lastly - and even more importantly - is total agreement that you have 
> to be careful about accessing any memory correctly. I have posted several 
> times asking about the am335x_pru_package examples (using UIO). In at 
> least 
> one (
> https://github.com/beagleboard/am335x_pru_package/blob/master/pru_sw/example_apps/PRU_PRUtoPRU_Interrupt/PRU_PRUtoPRU_Interrupt.c),
>  
> there is hardcoded use of the first 8 bytes of physical memory at 
> 0x8000_. I don't see how that can be OK. It may be that I don't know 
> some secrets of Linux internals, but from a theoretical perspective, I 
> just 
> don't know how one can make the assumption that any part of main memory 
> is 
> not in use by another process unless it is guaranteed by the kernel.
>
>
 So here is what I meant. Of course, I have no personal hands on,but 
 looking at things from 35k feet. I *know* writing directly to the PRU 
 shared memory from userspace, would be, performance wise, just as fast as 
 writing to the 512M of system DDR. Through /dev/mem/. On the PRU side 
 however, the PRU's would have single cycle access to their own memory. So 
 the tricky part for me here would not be making sure we're writing to the 
 right memory location, but knowing it's possible to begin with because I 
 have not attempted this personally. In fact my hands on experience with 
 the 
 

Re: [beagleboard] Re: on accessing the p8/9 headers

[Peter Lawler]

On 13/03/17 12:26, 'woody stanford' via BeagleBoard wrote:


Or I will be forced to go to Mouser and ask for a refund on my BB.
Wait, Mouser will process refunds if the owner posts spam to a moderated 
list?!


P.

--
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/f91ed84d-790b-14c5-5186-e14434f6f9ce%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: on accessing the p8/9 headers

[William Hermans]

Well, this guy is already on my blacklist, so as far as I'm concerned . . .
let me post corny joke garbage posts. Granted, I'm only 1 of those 11,495
people who got mailed. . .

On Mon, Mar 13, 2017 at 2:29 PM, Robert Nelson 
wrote:

> On Sun, Mar 12, 2017 at 8:26 PM, 'woody stanford' via BeagleBoard
>  wrote:
> > Gerald, can you articulate what you difficulty with my posts are,
> according
> > to TOS where the violations are, and I will correct them. I am NOT
> trying to
> > monopolize your board or whatever, I just have questions is all. But if
> you
> > could be a good moderator and let me know what you concern is with me.
> If it
> > is reasonable I will agree and make the proper changes.
>
> The "post" in question is deleted, you sent it via email to 11,495
> members.  It was a random spam Question & Answer crap
>
> the post was the one before this post "
> https://groups.google.com/d/msg/beagleboard/9HoWwEPz-5Q/vNrmYwP0AwAJ "
>
> "proper changes" it already got sent out to 11,495 via email...
> there's nothing to change... just don't do it again...
>
> > Or I will be forced to go to Mouser and ask for a refund on my BB. I like
> > it. But I am not committed to using it.
>
> 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/CAOCHtYiSjb0g9%2B2rFCFrRThQnMVk39TOm1FxJMp79Q
> -%2BVGWr_w%40mail.gmail.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/CALHSORqiquKc0_Ayiq8WC0c8whFerkbd6Ru4rfgLZARhBFefBA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: on accessing the p8/9 headers

[Robert Nelson]

On Sun, Mar 12, 2017 at 8:26 PM, 'woody stanford' via BeagleBoard
 wrote:
> Gerald, can you articulate what you difficulty with my posts are, according
> to TOS where the violations are, and I will correct them. I am NOT trying to
> monopolize your board or whatever, I just have questions is all. But if you
> could be a good moderator and let me know what you concern is with me. If it
> is reasonable I will agree and make the proper changes.

The "post" in question is deleted, you sent it via email to 11,495
members.  It was a random spam Question & Answer crap

the post was the one before this post "
https://groups.google.com/d/msg/beagleboard/9HoWwEPz-5Q/vNrmYwP0AwAJ "

"proper changes" it already got sent out to 11,495 via email...
there's nothing to change... just don't do it again...

> Or I will be forced to go to Mouser and ask for a refund on my BB. I like
> it. But I am not committed to using it.

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/CAOCHtYiSjb0g9%2B2rFCFrRThQnMVk39TOm1FxJMp79Q-%2BVGWr_w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Detecting (probing) MPU-9250 connected to beaglebone board black

[christ christ]

Thanks Graham, got it working. I think it was the cable length that was
causing problem.  At the moment I'm just trying to figure out why the
magnetometer data are not varying while i can see the changes for the
accelerometer and gyroscope.

On Sun, Mar 12, 2017 at 2:31 AM, Graham  wrote:

> That all looks fine.
>
> Any I2C chip, that is properly connected to P9-19 and 20 should show up on
> bus 2.
>
> What are the DC Voltages on P9-19 and P9-20?
>
> --- Graham
>
> ==
>
>
>
> On Saturday, March 11, 2017 at 6:00:00 PM UTC-6, christ christ wrote:
>>
>>
>> -- Forwarded message --
>> From: christ christ 
>> Date: Sat, Mar 11, 2017 at 3:37 PM
>> Subject: Re: Detecting (probing) MPU-9250 connected to beaglebone board
>> black
>> To: Graham 
>> Cc: BeagleBoard 
>>
>>
>> Hi Graham,
>> I just thought that a visual of what I'm doing would help with your
>> assistance. Please let me know if there is anything i'm missing here.​
>>  Debian result0.jpg
>> 
>> ​​
>>  Debian result1.jpg
>> 
>> ​​
>>  Debian result2.jpg
>> 
>> ​​
>>  Debian result3.jpg
>> 
>> ​​
>>  Debian result4.jpg
>> 
>> ​​
>>  Debian result5.jpg
>> 
>> ​​
>>  Debian result6.jpg
>> 
>> ​​
>>  Debian result7.jpg
>> 
>> ​
>>
>>

-- 
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/CAPTvsHj3v0UsNAA3S0Qowp_d0%3DmZ6JERRw2h6RgCv%3DgxXL7zGQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Detecting (probing) MPU-9250 connected to beaglebone board black

[christ christ]

thanks for the help  and advices

On Mon, Mar 13, 2017 at 3:10 PM, Graham Haddock 
wrote:

> I am glad it is running now.
> It is not a chip I have used, so you will have to sort it out, now that
> you are communicating with it.
>
> If you do need to remote it in the future, you should use shielded cable
> with a good ground, increase the size of the bypass / filter cap at the IC,
> from the 0.1 uF to something much bigger, and also reduce the value of the
> pull-up resistors at the IC from the current 10K to something down in the
> range of 1K to 2K.  But still keep that cable length as short as possible.
>
> Good luck,
> --- Graham
>
> ==
>
> On Mon, Mar 13, 2017 at 7:56 AM, christ christ 
> wrote:
>
>> Thanks Graham, got it working. I think it was the cable length that was
>> causing problem.  At the moment I'm just trying to figure out why the
>> magnetometer data are not varying while i can see the changes for the
>> accelerometer and gyroscope.
>>
>> On Sun, Mar 12, 2017 at 2:31 AM, Graham  wrote:
>>
>>> That all looks fine.
>>>
>>> Any I2C chip, that is properly connected to P9-19 and 20 should show up
>>> on bus 2.
>>>
>>> What are the DC Voltages on P9-19 and P9-20?
>>>
>>> --- Graham
>>>
>>> ==
>>>
>>>
>>>
>>> On Saturday, March 11, 2017 at 6:00:00 PM UTC-6, christ christ wrote:


 -- Forwarded message --
 From: christ christ 
 Date: Sat, Mar 11, 2017 at 3:37 PM
 Subject: Re: Detecting (probing) MPU-9250 connected to beaglebone board
 black
 To: Graham 
 Cc: BeagleBoard 


 Hi Graham,
 I just thought that a visual of what I'm doing would help with your
 assistance. Please let me know if there is anything i'm missing here.​
  Debian result0.jpg
 
 ​​
  Debian result1.jpg
 
 ​​
  Debian result2.jpg
 
 ​​
  Debian result3.jpg
 
 ​​
  Debian result4.jpg
 
 ​​
  Debian result5.jpg
 
 ​​
  Debian result6.jpg
 
 ​​
  Debian result7.jpg
 
 ​


>>
>

-- 
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/CAPTvsHgHRpXPi-KYgv%3D4ih%3D%3Dwb9JdaVa-AZShmdvNNbojK-PQQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Regarding booting Beagleboard with SD card.

[나종식]

Hello!

I bought BeagleBone Black.


Applied it to the compilation / sd card using the url below.

-> 
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-BackupBootloader
 



After removing the micro SD card,
When you insert an SD card into BeagleBone, only one LED blink continuously 
and it appears to have no action.



* My main information is as follows.


1. wget -c 
*https://rcn-ee.com/repos/git/u-boot-patches/v2017.03-rc2/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch*
 




2. git clone *https://github.com/RobertCNelson/ti-linux-kernel-dev.git* 




3. wget -c 
*https://rcn-ee.com/rootfs/eewiki/minfs/ubuntu-16.04.1-minimal-armhf-2017-01-14.tar.xz*
 



Thank you.


-- 
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/c7d74b29-1a8f-4537-997f-d844a53ef2aa%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Booting the BeagleBone with MicroSD

[나종식]

Hello!

I bought BeagleBone Black.
Applied it to the compilation / sd card using the url below.

-> 
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-BackupBootloader
 

After removing the micro SD card,
When you insert an SD card into BeagleBone, only one LED blink continuously 
and it appears to have no action.

* My main information is as follows.

1. wget -c 
https://rcn-ee.com/repos/git/u-boot-patches/v2017.03-rc2/0001-am335x_evm-uEnv.txt-bootz-n-fixes.patch

2. git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git

3. wget -c 
https://rcn-ee.com/rootfs/eewiki/minfs/ubuntu-16.04.1-minimal-armhf-2017-01-14.tar.xz
Thank you.

-- 
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/b4ea4c36-3dc4-466a-92a1-3cf6df07ce78%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: on accessing the p8/9 headers

['woody stanford' via BeagleBoard]

Gerald, can you articulate what you difficulty with my posts are, according 
to TOS where the violations are, and I will correct them. I am NOT trying 
to monopolize your board or whatever, I just have questions is all. But if 
you could be a good moderator and let me know what you concern is with me. 
If it is reasonable I will agree and make the proper changes.

Or I will be forced to go to Mouser and ask for a refund on my BB. I like 
it. But I am not committed to using it.

Thank you.

On Thursday, March 9, 2017 at 5:17:59 AM UTC-7, woody stanford wrote:
>
> OK, I want to get to the bottom of this whole GPIO issue on the BBB, so 
> I'm opening up this thread as a "documenter" whereby which I can take notes 
> based on my research into how you consistently, stably and SOLIDLY 
> programatically access the GPIO pins on a BBB. I've already done a lot of 
> the footwork so I'm not entirely unknowledgeable, but I want to get to the 
> heart of this issue and solve the mental block people have with this. A 
> private hope.
>
> Either way, probably a good mess of processed links, articles and 
> information where you can start.
>

-- 
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/fc39d93b-a319-48bd-b07d-933d05df8eef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian testing: 2017-03-12

[William Hermans]

Yeah,sorry about that, had overlays on the mind, and couldn't find my
workflow file easily to remember the name of the service.

-- 
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/CALHSORqjXh%2BQrC-g5fCwLaVOAkvGfo-Q9B9LMfy2WHBZLS-h-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian testing: 2017-03-12

[Robert Nelson]

On Mon, Mar 13, 2017 at 2:23 PM, William Hermans  wrote:
>
>
> On Mon, Mar 13, 2017 at 12:06 PM, Robert Nelson 
> wrote:
>>
>>
>> Yeah, we are back to being more stable again.. The Windows Driver
>> "patch" required lots of changes behind the scenes to now deal with
>> the "dual" usb-ethernet adapters.
>>
>>
>
>
> OK, cool.So what I should be able to test over the next month or hopefully
> sooner is:
>
> i2c-1 - multiple devices on the bus
> ds3232 real-time clock.
> Cape eeprom's
> D20B18 one-wire temp sensor
> the beaglebone's ADC, 2 channels.
> *Maybe* PWM
> uboot overlays for all of the above.
> At some point I may need to rewrite, or changed the existing PMIC / battery
> capabilities through acpid - I could use a link to the beaglebone source for
> this package by the way. Which I should be able to contribute back.
>
>
> Various other mechanisms such as systemd services / timers etc. Which I
> doubt would have and flaws.
>
> Is the overlay you're loading for all the stock stuff at boot still done
> through the generic-overlay service ? I really need to disable all the USB
> gadget stuff, as it can conflict with some of our systems which run a 3G/4G
> modem over USB.

Yeah, just:

sudo systemctl disable generic-board-startup.service

and then the usb gadget won't load.

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/CAOCHtYh7Ray3wUpsczMaZbBCjjqVx0jROXPO0wfZLJPzV%3DVF7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian testing: 2017-03-12

[William Hermans]

On Mon, Mar 13, 2017 at 12:06 PM, Robert Nelson 
wrote:
>
>
> Yeah, we are back to being more stable again.. The Windows Driver
> "patch" required lots of changes behind the scenes to now deal with
> the "dual" usb-ethernet adapters.

>
>

OK, cool.So what I should be able to test over the next month or hopefully
sooner is:


   - i2c-1 - multiple devices on the bus
   - ds3232 real-time clock.
   - Cape eeprom's
   - D20B18 one-wire temp sensor
   - the beaglebone's ADC, 2 channels.
   - *Maybe* PWM
   - uboot overlays for all of the above.
   - At some point I may need to rewrite, or changed the existing PMIC /
   battery capabilities through acpid - I could use a link to the beaglebone
   source for this package by the way. Which I should be able to contribute
   back.


Various other mechanisms such as systemd services / timers etc. Which I
doubt would have and flaws.

Is the overlay you're loading for all the stock stuff at boot still done
through the generic-overlay service ? I really need to disable all the USB
gadget stuff, as it can conflict with some of our systems which run a 3G/4G
modem over USB.

-- 
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/CALHSORqCuFAB1C7eJgsuryArAJXJt%2Bj_RVkq7CbaZTi5r9PDbw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian testing: 2017-03-12

[Robert Nelson]

On Mon, Mar 13, 2017 at 2:00 PM, William Hermans  wrote:
> Robert,
>
> heh, i like the hash tag for the last link.
>
> Would you say that these images to the best of your knowledge are stable
> enough to test on a "production" system? e.g. a test system that is looking
> towards production. I wouldn't mind testing, but I do have work to complete
> as well. What we're using is mostly I2C( perhaps I2C1 or the unused bus ),
> and the rest would be standard Debian / Linux utilities, with some custom
> software tossed in. Mostly shell script, with a sprinkling of golang + C.

Yeah, we are back to being more stable again.. The Windows Driver
"patch" required lots of changes behind the scenes to now deal with
the "dual" usb-ethernet adapters.

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/CAOCHtYijTYbmRb3RS4cj%3Dfq77H4mtsNrev1SNWaY2J_yoH95%3Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] debian testing: 2017-03-12

[William Hermans]

Robert,

heh, i like the hash tag for the last link.

Would you say that these images to the best of your knowledge are stable
enough to test on a "production" system? e.g. a test system that is looking
towards production. I wouldn't mind testing, but I do have work to complete
as well. What we're using is mostly I2C( perhaps I2C1 or the unused bus ),
and the rest would be standard Debian / Linux utilities, with some custom
software tossed in. Mostly shell script, with a sprinkling of golang + C.

On Mon, Mar 13, 2017 at 11:19 AM, Robert Nelson 
wrote:

> Howdy!
>
> I just pushed out another round of images for testing, this time we
> have a new decicated u-boot overlay image.
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2017-03-12
>
> Big changes...
>
> Windows 7, 8, 8.1, 10.. No external driver required (network interface
> thanks to David and Jason)
>
> While 7 needs a usb-cdm driver (built-in 8/8.1/10)
>
> WinXP, sorry, it's EOL...
>
> U-Boot Overlays:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_
> Snapshot_lxqt_U-Boot_Overlay
>
> Here are the current supported confict capes: (aka they need
> hdmi/emmc/etc to be disabled)
>
> /lib/firmware/BB-CAPE-DISP-CT4-00A0.dtbo
> /lib/firmware/NL-AB-BBCL-00B0.dtbo
> /lib/firmware/BB-GREEN-HDMI-00A0.dtbo
> /lib/firmware/BB-BONE-LCD7-01-00A3.dtbo
> /lib/firmware/BB-BONE-4D5R-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D4R-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D4N-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D4C-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D7N-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D7C-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D5N-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D5C-01-00A1.dtbo
> /lib/firmware/BB-BONE-4D7R-01-00A1.dtbo
> /lib/firmware/BB-BONE-LCD4-01-00A1.dtbo
>
> don't see your cape on the conflict list, time to test...
>
> Here is the /boot/uEnv.txt options for U-Boot overlays if your cape
> doesn't have an eeprom:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays\
>
> and yes, this image, ssh over root is now disabled, to re-enable see:
>
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#i_take_
> full_responsibility_for_knowing_my_beagle_is_now_insecure
>
> 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/CAOCHtYjVHd%3DUub%3D-QvoRfEgGqgF726jJ%
> 3DuO6sN03b9WcKJLdsQ%40mail.gmail.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/CALHSORrEdbdTKHnohOPL4BNK5jQVBdZzHuzAuZT356QgkyMJkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] debian testing: 2017-03-12

[Robert Nelson]

Howdy!

I just pushed out another round of images for testing, this time we
have a new decicated u-boot overlay image.

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#2017-03-12

Big changes...

Windows 7, 8, 8.1, 10.. No external driver required (network interface
thanks to David and Jason)

While 7 needs a usb-cdm driver (built-in 8/8.1/10)

WinXP, sorry, it's EOL...

U-Boot Overlays:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_lxqt_U-Boot_Overlay

Here are the current supported confict capes: (aka they need
hdmi/emmc/etc to be disabled)

/lib/firmware/BB-CAPE-DISP-CT4-00A0.dtbo
/lib/firmware/NL-AB-BBCL-00B0.dtbo
/lib/firmware/BB-GREEN-HDMI-00A0.dtbo
/lib/firmware/BB-BONE-LCD7-01-00A3.dtbo
/lib/firmware/BB-BONE-4D5R-01-00A1.dtbo
/lib/firmware/BB-BONE-4D4R-01-00A1.dtbo
/lib/firmware/BB-BONE-4D4N-01-00A1.dtbo
/lib/firmware/BB-BONE-4D4C-01-00A1.dtbo
/lib/firmware/BB-BONE-4D7N-01-00A1.dtbo
/lib/firmware/BB-BONE-4D7C-01-00A1.dtbo
/lib/firmware/BB-BONE-4D5N-01-00A1.dtbo
/lib/firmware/BB-BONE-4D5C-01-00A1.dtbo
/lib/firmware/BB-BONE-4D7R-01-00A1.dtbo
/lib/firmware/BB-BONE-LCD4-01-00A1.dtbo

don't see your cape on the conflict list, time to test...

Here is the /boot/uEnv.txt options for U-Boot overlays if your cape
doesn't have an eeprom:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays\

and yes, this image, ssh over root is now disabled, to re-enable see:

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

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/CAOCHtYjVHd%3DUub%3D-QvoRfEgGqgF726jJ%3DuO6sN03b9WcKJLdsQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Fwd: Robots. Fast. BeagleBone Blue is here!

[Jason Kridner]

Begin forwarded message:

> From: BeagleBoard.org Foundation 
> Date: March 13, 2017 at 3:01:45 PM GMT+1
> Subject: Robots. Fast. BeagleBone Blue is here!
> Reply-To: BeagleBoard.org Foundation 
> 
> 
>
> Meet BeagleBone® Blue.
> Robots. Fast.
> 
>
>
> 
> BeagleBone® Blue is the affordable and complete robotics controller built 
> around the popular BeagleBone® open hardware computer. Linux-enabled, Blue is 
> community-supported and fully open-source.  High-performance, flexible 
> networking capabilities are coupled with a real-time capable Linux system and 
> a compelling set of peripherals for building mobile robots quickly and 
> affordably.  By utilizing the pre-configured WiFi access point, starting code 
> development is as simple as connecting a battery and opening a web browser.
> 
> Robots.
> 
> 
> The electronic components needed for a wide variety of mobile and flying 
> robots are all included. BeagleBone® Blue has onboard 2 cell (2S) LiPo 
> battery management with charger and battery level LEDs, 8 real-time software 
> controlled PWM/PPM outputs for 6V servo motors or 
> electronic-speed-controllers (ESCs), 4 PWM-enabled DC motor drivers, 4 
> quadrature encoder inputs, on-board sensors including a 9-axis IMU and 
> barometer, a wide array of GPIO and serial protocol connectors including 
> CAN,4 ADC inputs, a PC USB interface, a USB 2.0 host port, a reset button, a 
> power button, two user configurable buttons and eleven user configurable LED 
> indicators.  Built on Octavo Systems’ System-In-Package that integrates a 
> high-performance TI AM3358 processor, 512MB of DDR3 and power management, 
> customizing the Autodesk EAGLE based design to include any of your specific 
> needs is simple and affordable. BeagleBone® Blue is ready to be a component 
> of your robot.
> 
>  
> 
> Fast.
>  
> 
> BeagleBone® Blue leverages and engages a large community of experienced Linux 
> and robotics developers, providing integrated solutions for numerous robotics 
> challenges. Designed and developed in coordination with the UCSD Coordinated 
> Robotics Lab, the basis for the hardware and software setup has been utilized 
> by hundreds of students already, before this general public release. Several 
> programming approaches are supported today, including a C API supporting the 
> integrated sensors and drivers, mainline support for the Ardupilot 
> open-source autopilot software for UAVs, multi-rotor-copters and rovers and 
> an evolving integration with Robot Operating System (ROS) allowing for 
> high-level programming in Python or across the network. Additionally, 
> partners have created fully graphical programming options, eliminating 
> barriers even to those brand new to programming. Not yet another 
> microcontroller robotics platform, the high-performance interactive 
> Linux-based BeagleBone® Blue has test programs ready-to-run and cycles to 
> spare, helping you get your robot moving fast.
> 
>  
> 
> Summary of Key Features
> 
> Processor: Octavo Systems OSD3358 1GHz ARM® Cortex-A8
> 512MB DDR3 RAM
> 2×32-bit 200-MHz programmable real-time units (PRUs)
> 4GB 8-bit on-board flash storage programmed with Debian Linux distribution
> Connectivity and Sensors
> Battery: 2-cell LiPo support with balancing, 9-18V charger input
> Wireless: 802.11bgn, Bluetooth 4.1 and BLE
> Motor control: 8 6V servo out, 4 DC motor out, 4 quadrature encoder in
> Sensors: 9 axis IMU, barometer
> Connectivity: HighSpeed USB 2.0 client and host
> Other easy connect interfaces: GPS, DSM2 radio, UARTs, SPI, I2C, analog, 
> buttons, LEDs
> Software Compatibility
> Debian, ROS, Ardupilot, ...
> Graphical programming, Cloud9 IDE on Node.js
> plus much more
> Find Out More
> 
> 
> 
> 
> 
> 
> Copyright © 2017 BeagleBoard.org Foundation, All rights reserved. 
> As an participant in the BeagleBoard.org community, we've added you to our 
> newsletter list and will remove you promptly from all lists if you choose to 
> opt-out. 
> 
> Our mailing address is: 
> BeagleBoard.org Foundation
> 4467 Ascot Ct
> Oakland Twp, MI 48306
> 
> Add us to your address book
> 
> 

-- 
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/877A2424-401A-4FDA-AAED-98A9A2A1ADF3%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Detecting (probing) MPU-9250 connected to beaglebone board black

[Graham Haddock]

I am glad it is running now.
It is not a chip I have used, so you will have to sort it out, now that you
are communicating with it.

If you do need to remote it in the future, you should use shielded cable
with a good ground, increase the size of the bypass / filter cap at the IC,
from the 0.1 uF to something much bigger, and also reduce the value of the
pull-up resistors at the IC from the current 10K to something down in the
range of 1K to 2K.  But still keep that cable length as short as possible.

Good luck,
--- Graham

==

On Mon, Mar 13, 2017 at 7:56 AM, christ christ 
wrote:

> Thanks Graham, got it working. I think it was the cable length that was
> causing problem.  At the moment I'm just trying to figure out why the
> magnetometer data are not varying while i can see the changes for the
> accelerometer and gyroscope.
>
> On Sun, Mar 12, 2017 at 2:31 AM, Graham  wrote:
>
>> That all looks fine.
>>
>> Any I2C chip, that is properly connected to P9-19 and 20 should show up
>> on bus 2.
>>
>> What are the DC Voltages on P9-19 and P9-20?
>>
>> --- Graham
>>
>> ==
>>
>>
>>
>> On Saturday, March 11, 2017 at 6:00:00 PM UTC-6, christ christ wrote:
>>>
>>>
>>> -- Forwarded message --
>>> From: christ christ 
>>> Date: Sat, Mar 11, 2017 at 3:37 PM
>>> Subject: Re: Detecting (probing) MPU-9250 connected to beaglebone board
>>> black
>>> To: Graham 
>>> Cc: BeagleBoard 
>>>
>>>
>>> Hi Graham,
>>> I just thought that a visual of what I'm doing would help with your
>>> assistance. Please let me know if there is anything i'm missing here.​
>>>  Debian result0.jpg
>>> 
>>> ​​
>>>  Debian result1.jpg
>>> 
>>> ​​
>>>  Debian result2.jpg
>>> 
>>> ​​
>>>  Debian result3.jpg
>>> 
>>> ​​
>>>  Debian result4.jpg
>>> 
>>> ​​
>>>  Debian result5.jpg
>>> 
>>> ​​
>>>  Debian result6.jpg
>>> 
>>> ​​
>>>  Debian result7.jpg
>>> 
>>> ​
>>>
>>>
>

-- 
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_KV4BVYggSnOVsLyXtuhfNZT4sdHqUKpbPXV_8c%2Bg-RX7Ag%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: after flashing to Debian 8.6 no gui anymore

[Harke Smits]

The gui is present if you load the Debian version indicated above. You have
to modify the uEnv.txt file. Look here:
https://mail.google.com/mail/u/0/?shva=1#inbox/159e9f22d12d2eb3
Still my current script does not work as expected in this version but the
normal gui functions do. I need to look further.
Good luck,
Harke


On 12 March 2017 at 03:37, evilwulfie  wrote:

> So install your favorite GUI.
>
> On 3/11/2017 12:28 AM, beeke...@gmail.com wrote:
>
> I am curious how you ended up on beaglebone. I had two I bought some time
> back. I flashed them both with the 8.6 and both have exactly what you
> describe. I can ssh via USB.  No GUI. I put a monitor / keybard with
> nothing.   What did you learn and what would you suggest?  I really just
> want to play with the boards. I have a Rapberry pi cluster configured and
> wanted to have the beaglebone in the mix somehow...  Anyways curious what
> you learned? did? etc.
>
> On Sunday, December 18, 2016 at 10:23:33 AM UTC-5, Harke Smits wrote:
>>
>> Dear all,
>>
>> I managed to flash a recent purchased BBB to Debian 8.6
>> (BBB-blank-debian8.6-lxqt-4gb-2016-11-27).It works (partly) as I can see
>> via Cloud 9 acces. But the gui is gone. I no longer have a graphical
>> display (4D systems) nor keyboard/mouse access (via usb dongle). The
>> display is fully lit. The board is completely accessable via Cloud9 and
>> normal linux commands work via this interface. I did an update (sudo
>> apt-get update) followed by reboot but no succes. Do I miss something?
>> Please advise. Many thanks in advance,
>> Harke
>> Btw: the Debian version of 2015-11-03 works great! (I still have the SD
>> card)
>>
> --
> 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/b160dfe7-53c2-4ea8-92f7-cdc3adf95504%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 a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/B_qLqwXwEwo/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/17807c6e-ca1c-bd9d-cddd-ed2e2ba0db7d%40gmail.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/CAHmciabSRj2AqF%2BPPPjM6okSmS8o6hyYvuaFEj7YX2HgXko6ZQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Secret sauce for RNDIS on Beaglebone? How to get reliable RNDIS connection on Windows 10

[Robert Budde]

Hi!

I am looking for getting a reliable RNDIS connection of a i.MX6-based board 
on Windows 10. Being a long-time extensive Beaglebone user, I know my 
Beaglebones reliably show up with a RNDIS device on my Windows 10 for quite 
a while.

I have found and implemented the hints as described on 
http://irq5.io/2016/12/22/raspberry-pi-zero-as-multiple-usb-gadgets/ and 
https://gist.github.com/geekman/5bdb5abdc9ec6ac91d5646de0c0c60c4 but had no 
luck so far. I was not yet able to locate where the "gadget-schema" gets 
created for the Beaglebone, and since "gadget-export" (a neat tool - see 
https://github.com/libusbg/libusbg/blob/master/examples/gadget-export.c) 
was not yet compiled in I was not able to exactly replicate on the i.MX6. I 
will check the actual config using it, but I already did browsing manually 
through the "configfs" entries and in fact did not even find evidence 
Beaglebone is using the "os_desc".

Can somebody shed some light on the matter?

BR
Robert

-- 
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/c46cb2b5-e296-4a56-9035-1f13f3f3b149%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Managing GPIO with C++

[Dror Lugasi]

Thanks for answering guys! 

Jacek >> 
Thank you so much for the library! it looks like a very hard work was 
invested in it!
but i tend to go with williams's approach.. i want to know how to do it my 
self also as a part of learning the BBB
i am planning on making more complicated programs than just read and write 
some GPIO.

I saw in some places that there are the FS and MMAP way and that the MMAP 
is a lot faster!
If you could tell me just how to approach this and so i could write some 
basic functions like read write and set as in or out
that would be great!

i also want to get the best performance as possible, but i am not that 
knowledgeable about deep embedded programming, i know that the beagle bone 
has 2 PRU's and they can be accessed to make the calculations and use all 
the peripherals (UART, PWM, I2C etc..)
so is there a way to access the PRU with c++??


William >> 
Thanks for the example! right now i am using the same terminal commands 
with the "system" function
cat - to read 
echo - to write

does using a file stream will be faster then this? if so i will change the 
code so it will use a file instead.


Thanks a lot guys! :)

-- 
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/8c99fd79-ed6a-43d5-a60b-161b9700445c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.