Re: [beagleboard] putty black screen

[William Hermans]

This means you're unable to connect via puTTY to the Beaglebone. Now, there
are several reasons why this can be, and you're going to have to figure
that out on your own. Google should be a good source of information for
this.

On Sun, Mar 21, 2021 at 3:55 PM Meric  wrote:

> hi guys i have a issue when i connect my beaglebone blue to my computer,
> when i try to use putty the putty screen's stays black and i can't do
> anyhing.
>
>
> --
> 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/e0094433-1de0-412b-95a5-1b664b25dc9bn%40googlegroups.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/CALHSORpWVM-XXW8SWzRDKv%3DyYHMDKe4-HtUKKyU9s5D0rTNxvQ%40mail.gmail.com.

Re: [beagleboard] How to make can0 work

[William Hermans]

By the way "1F334455#1122334455667788" doesn't look like a valid J1939
packet. But I barely know that particular protocol.

On Wed, May 20, 2020 at 4:15 PM William Hermans  wrote:

> Without any code, or steps you've taken. No one can help, or say what's
> going on. I will say this however. I wrote in a relatively short period of
> time( with help! From multiple sources). Software that could communicate
> over CANBUS that was able to decode information from a "TRACE"
> inverter(XanBus) in real-time. This ran for weeks at a time, displaying the
> information in a web interface. Proven 100% accurate.
>
> I would not say that using the CANBUS hardware interface on the beaglebone
> is 100% rock solid, but it had been very reliable in my case. Once I knew
> what I was doing. The only real problem we had was we were completely
> off-grid, powered by solar. So when we switched from solar power, to the
> genset. The quick power blip would sometimes put the beaglebone in a wonkey
> state. However, creating, and using canbus traffic logs. I was able to keep
> a working beaglebone powered via a laptop for months.
>
> Probably the first place to look is at the hardware you're using. But I'd
> double check everything.
>
> On Wed, May 20, 2020 at 1:29 PM Andrey  wrote:
>
>> Guys, thanks for the answers!
>> Unfortunately, I can't use can1, it is have no output on my Board.
>> It is strange that after a bus crash, ifconfig shows the number of
>> packets transmit 0 and received 3.
>> If the tire falls after only three attempts to send, it is not normal and
>> does not look like a system for cars that is designed to be reliable.
>>
>> debian@bone:~$ cansend can0 *1F334455#1122334455667788*
>> [  273.654439] can: raw protocol (rev 20170425)
>> [  273.670296] c_can_platform 481cc000.can can0: bus-off
>> debian@bone:~$ sudo ifconfig
>> can0: flags=129  mtu 16
>> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>> txqueuelen 10  (UNSPEC)
>> RX packets *3*  bytes 24 (24.0 B)
>> RX errors 0  dropped 0  overruns 0  frame 0
>> TX packets 0  bytes 0 (0.0 B)
>> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>> device interrupt 47
>> ...
>>
>> This is more complicated than I thought.
>>
>> --
>> 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/1a0b4dcf-2f7e-46a1-8083-43336085c415%40googlegroups.com
>> <https://groups.google.com/d/msgid/beagleboard/1a0b4dcf-2f7e-46a1-8083-43336085c415%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/CALHSORrHPStJu8F7LwF-%2BjPqwBP4WMXdJGqYKGTAqAiKG_QbQQ%40mail.gmail.com.

Re: [beagleboard] How to make can0 work

[William Hermans]

Without any code, or steps you've taken. No one can help, or say what's
going on. I will say this however. I wrote in a relatively short period of
time( with help! From multiple sources). Software that could communicate
over CANBUS that was able to decode information from a "TRACE"
inverter(XanBus) in real-time. This ran for weeks at a time, displaying the
information in a web interface. Proven 100% accurate.

I would not say that using the CANBUS hardware interface on the beaglebone
is 100% rock solid, but it had been very reliable in my case. Once I knew
what I was doing. The only real problem we had was we were completely
off-grid, powered by solar. So when we switched from solar power, to the
genset. The quick power blip would sometimes put the beaglebone in a wonkey
state. However, creating, and using canbus traffic logs. I was able to keep
a working beaglebone powered via a laptop for months.

Probably the first place to look is at the hardware you're using. But I'd
double check everything.

On Wed, May 20, 2020 at 1:29 PM Andrey  wrote:

> Guys, thanks for the answers!
> Unfortunately, I can't use can1, it is have no output on my Board.
> It is strange that after a bus crash, ifconfig shows the number of packets
> transmit 0 and received 3.
> If the tire falls after only three attempts to send, it is not normal and
> does not look like a system for cars that is designed to be reliable.
>
> debian@bone:~$ cansend can0 *1F334455#1122334455667788*
> [  273.654439] can: raw protocol (rev 20170425)
> [  273.670296] c_can_platform 481cc000.can can0: bus-off
> debian@bone:~$ sudo ifconfig
> can0: flags=129  mtu 16
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen
> 10  (UNSPEC)
> RX packets *3*  bytes 24 (24.0 B)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 0  bytes 0 (0.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 47
> ...
>
> This is more complicated than I thought.
>
> --
> 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/1a0b4dcf-2f7e-46a1-8083-43336085c415%40googlegroups.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/CALHSORrZ3EmOoq-rYCFfQ-YgzNwZWizg0nH2TVqxRdKGhjpdEw%40mail.gmail.com.

Re: [beagleboard] How to make can0 work

[William Hermans]

J1939 bit positioning -> https://photos.app.goo.gl/7X24xgY8dR1aYTHDA

On Wed, May 20, 2020 at 1:45 PM William Hermans  wrote:

> Oh forgot to mention. You'd need to use socketCAN. Perhaps this guy will
> give you some ideas.
> https://fabiobaltieri.com/2013/07/23/hacking-into-a-vehicle-can-bus-toyothack-and-socketcan/
>
>
> On Wed, May 20, 2020 at 1:40 PM William Hermans  wrote:
>
>> For the record, you do not have to wait for kernel 5.4 to do J1939. I
>> wrote software using kernel 3.8.x that read a hybrid  NIMEA 2000 protocol,
>> which uses the same high level protocol as J1939. All you have to do is
>> understand J1939, and bit wrangle . . .
>>
>> On Wed, May 20, 2020 at 7:33 AM Robert Nelson 
>> wrote:
>>
>>>
>>>
>>> On Wed, May 20, 2020 at 2:54 AM Gwen Stouthuysen <
>>> gwen.stouthuy...@gmail.com> wrote:
>>>
>>>> I have the impression that your network is set up for J1939 or CANOpen
>>>> (CAN 2.0B)
>>>>
>>>> when you send a message to a short address (CAN 2.0A) it doesn't get
>>>> acknowledged, and this might crash your bus, as the BB will try to send it
>>>> till the message is acknowledged..
>>>> Try to send a message to  a 29bit address, or add a second can
>>>> interface that will acknowledge your messages. (CAN1 on the BB).
>>>>
>>>> I'm a bit stuck on moving over to J1939, as that requires at least
>>>> kernel 5.4, which results in boot issues due the overlay approach as
>>>> applied in the Beaglebone OS
>>>>
>>>
>>> The issue with 5.4 should now have been resolved...  If you have free
>>> time, please re-test and let me know.
>>>
>>> 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/CAOCHtYjJ4TpHSSmA9R0uL7YRYO3j8KPwv%3Dk74UB%3DCBJs8CTiJA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYjJ4TpHSSmA9R0uL7YRYO3j8KPwv%3Dk74UB%3DCBJs8CTiJA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>

-- 
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/CALHSORq%2BSUdbdF5wEaFPy5DwxND2subqnwDdTDDCqa%2Bs4W11Tg%40mail.gmail.com.

Re: [beagleboard] How to make can0 work

[William Hermans]

Oh forgot to mention. You'd need to use socketCAN. Perhaps this guy will
give you some ideas.
https://fabiobaltieri.com/2013/07/23/hacking-into-a-vehicle-can-bus-toyothack-and-socketcan/


On Wed, May 20, 2020 at 1:40 PM William Hermans  wrote:

> For the record, you do not have to wait for kernel 5.4 to do J1939. I
> wrote software using kernel 3.8.x that read a hybrid  NIMEA 2000 protocol,
> which uses the same high level protocol as J1939. All you have to do is
> understand J1939, and bit wrangle . . .
>
> On Wed, May 20, 2020 at 7:33 AM Robert Nelson 
> wrote:
>
>>
>>
>> On Wed, May 20, 2020 at 2:54 AM Gwen Stouthuysen <
>> gwen.stouthuy...@gmail.com> wrote:
>>
>>> I have the impression that your network is set up for J1939 or CANOpen
>>> (CAN 2.0B)
>>>
>>> when you send a message to a short address (CAN 2.0A) it doesn't get
>>> acknowledged, and this might crash your bus, as the BB will try to send it
>>> till the message is acknowledged..
>>> Try to send a message to  a 29bit address, or add a second can interface
>>> that will acknowledge your messages. (CAN1 on the BB).
>>>
>>> I'm a bit stuck on moving over to J1939, as that requires at least
>>> kernel 5.4, which results in boot issues due the overlay approach as
>>> applied in the Beaglebone OS
>>>
>>
>> The issue with 5.4 should now have been resolved...  If you have free
>> time, please re-test and let me know.
>>
>> 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/CAOCHtYjJ4TpHSSmA9R0uL7YRYO3j8KPwv%3Dk74UB%3DCBJs8CTiJA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/beagleboard/CAOCHtYjJ4TpHSSmA9R0uL7YRYO3j8KPwv%3Dk74UB%3DCBJs8CTiJA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/CALHSORqfP_sZEa3UBRDfr_Cya1ja_DRSwtPgAn9b8J2zDdjhbA%40mail.gmail.com.

Re: [beagleboard] How to make can0 work

[William Hermans]

For the record, you do not have to wait for kernel 5.4 to do J1939. I wrote
software using kernel 3.8.x that read a hybrid  NIMEA 2000 protocol, which
uses the same high level protocol as J1939. All you have to do is
understand J1939, and bit wrangle . . .

On Wed, May 20, 2020 at 7:33 AM Robert Nelson 
wrote:

>
>
> On Wed, May 20, 2020 at 2:54 AM Gwen Stouthuysen <
> gwen.stouthuy...@gmail.com> wrote:
>
>> I have the impression that your network is set up for J1939 or CANOpen
>> (CAN 2.0B)
>>
>> when you send a message to a short address (CAN 2.0A) it doesn't get
>> acknowledged, and this might crash your bus, as the BB will try to send it
>> till the message is acknowledged..
>> Try to send a message to  a 29bit address, or add a second can interface
>> that will acknowledge your messages. (CAN1 on the BB).
>>
>> I'm a bit stuck on moving over to J1939, as that requires at least kernel
>> 5.4, which results in boot issues due the overlay approach as applied in
>> the Beaglebone OS
>>
>
> The issue with 5.4 should now have been resolved...  If you have free
> time, please re-test and let me know.
>
> 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/CAOCHtYjJ4TpHSSmA9R0uL7YRYO3j8KPwv%3Dk74UB%3DCBJs8CTiJA%40mail.gmail.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/CALHSORph3eH_c%3D3ntE3GAdogVwecwywEQQDXLj7AqeSmo%2Bpx6A%40mail.gmail.com.

Re: [beagleboard] use mass storage to send files from host to device

[William Hermans]

I'm not sure what's going on with g_multi for you there. But I will say
this. There are other, probably better suited options for moving files over
to the device.

I've used g_multi in the past and have always found it problematic for this
platform. So personally, I dedicated a cheap netbook to operate as a server
for the beaglebone(black), and just used NFS shares, and Samba for my dev
workstation.

Another option would be to use ssh file transfers, after running a ssh
server on the beaglebone.

It really depends on what you're trying to do, and your dev system.

On Fri, May 8, 2020 at 1:07 PM  wrote:

> I'm stuck on this and while I don't expect anyone to answer, I would
> greatly appreciate it.
> I understand that the g_multi gadget has backing storage for the mass
> storage device in /var/cache/doc-beaglebone-getting-started.
> I know that if I want to read from this storage, I have to do it while the
> storage is not in use.
> I think I should be able to mount and read the backing storage before
> am335x_evm.sh is run (this is the code which configures the g_multi gadget
> and enables it). However, when I do this the contents of
> the backing storage disappear. What could be going wrong?
>
> For reference, this is how i'm attempting to read the storage:
> I edited am335x_evm.sh to make the device read/write
> I pointed /var/local/bb_usb_mass_storage.img to another file:
> /root/data/backing_storage - a fat32 partition with 512 byte sectors
> starting at sector 2048
> I created the following directory: /mnt/loop
>
> losetup -o 1048576 /dev/loop0 /root/data/backing_file
> mkdosfs -F 32 /dev/loop0
> mount -t vfat /dev/loop0 /mnt/loop
> ls /mnt/loop >> /var/log/messages
> umount /dev/loop0
> losetup -d /dev/loop0
>
> --
> 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/77acb0c3-3fb1-418b-8b31-32d87bf3be71%40googlegroups.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/CALHSORoN--ice4LXMxyYPVz-%3DpMitrzvFymiA%2BD-e%2B76xdftXg%40mail.gmail.com.

Re: [beagleboard] How to configure extra USB gadgets on BBB?

[William Hermans]

https://www.kernel.org/doc/Documentation/usb/gadget_multi.rst

On Thu, May 7, 2020 at 1:48 AM Andrew P. Lentvorski 
wrote:

> Is there a way to configure extra USB gadget endpoints in addition to the
> BBB default ones or do I just have to go in and edit the am335x_evm.sh
> script?
>
> 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/378ec705-3e00-4fe9-aed1-66ba32506684%40googlegroups.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/CALHSORq7oaaWqe2Ve3SM9JdhF4cKSqb6uS7Ta_vySgLn6-DLuQ%40mail.gmail.com.

Re: [beagleboard] BeagleBone Black SRM released from asciidoc version on wiki

[William Hermans]

Wow, what board is your hand model holding ? Can't tell. Every time I look
at the opening picture. My eye goes straight to those bright red
fingernails . . . Just sayin`

On Wed, May 6, 2020 at 3:00 PM Jason Kridner  wrote:

> I've updated
> https://github.com/beagleboard/beaglebone-black/blob/master/BBB_SRM.pdf
> such that we can use it as a template for future SRMs as well as to accept
> community edits.
>
> Source is at
> https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual
> in asciidoc format. PDF conversion done with asciidoctor-pdf. Looking to
> move to asciidoctor.js in the future.
>
> --
> https://beagleboard.org/about
>
> --
> 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/CA%2BT6QP%3DWQDHZf8ztEYBtZK8UGbf9SNpKDtKy4TEomPK2p9RVwA%40mail.gmail.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/CALHSORoUactN7-4TJaTw4Ybw4-9nAXT4z5UeCZLH2qMGxsgebg%40mail.gmail.com.

Re: [beagleboard] libgpiod on Beaglebone AI

[William Hermans]

On Fri, Mar 27, 2020 at 11:46 AM Drew Fustini  wrote:

> On Fri, Mar 27, 2020 at 4:48 PM John Allwine 
> wrote:
> >
> > That was it! gpioget gpiochip3 10 worked.
>
> It would be interesting to know if libgpiod proves fast enough for
> your application.  It has C++ and Python bindings that allow you to
> set and get multiple lines on a gpiochip with a single ioctl().
>
> I am in communication with Bartosz, who made the libgpiod userspace
> library and utilities, and Linus Walleij who created the gpiod
> interface (which includes the gpiochip character devices).  They both
> seem open minded to improving interfaces to address real-world use
> cases.
>
Personally. I think trying to toggle a GPIO as fast as possible in Linux is
the wrong way to go about it. According to what I've read(and I have no
personal desire to test it). An empty ioctl() has 63ns latency. Add that on
top of gpiod's time. Then it starts to add up. Not to mention: how
proficient a given developer is when writing performant code.

So, for doing anything blazing fast, we're back full circle. However, I
think it would be better to use/buy hardware specialized for the task at
hand. With that said, there is nothing wrong with experimenting. Until you
let the blue smoke out. . .

-- 
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/CALHSORptFxx%3DHy7Rxi085HzUwXMnv4oc1t_N6pO%3DrmqQZDngEQ%40mail.gmail.com.

Re: [beagleboard] how to access GPIO on Beaglebone AI via /dev/mem

[William Hermans]

On Thu, Mar 26, 2020 at 10:59 AM John Allwine 
wrote:

> I'm happy to leave the pinmux alone, but if all I'm doing is reading or
> writing to the GPIO can I do so from /dev/mem?
>
> According to this post, it's about 1000x faster:
> http://chiragnagpal.com/examples.html
>
> It's also how hal_bb_gpio is implemented:
> https://github.com/machinekit/machinekit-hal/blob/master/src/hal/drivers/hal_bb_gpio/hal_bb_gpio.c
>
> If necessary, it could be rewritten to use sysfs, but if it means being
> 1000x slower, that's not ideal.
>

I've used /dev/mem to access(read, and write), registers on the BBB and I
do agree. It is much faster.

The reason why it's bad to use /dev/mem . . . is that there is no way for
the kernel to know what state a given "device" is in. That is, without a
physical read. Potentially, this could be bad. Especially if another driver
or application has access to the given hardware register.

-- 
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/CALHSORqqqeLqoCbGh3r%2BAkVJQFBnX3akFEexCQELKVH%2Bw5GZEA%40mail.gmail.com.

Re: [beagleboard] Re: BeagleBone AI is here!

[William Hermans]

All you need is some air flow over the board/heatsinks. I just stick mine
in front of a 20" box fan and it's fine. I'd assume a much smaller house
fan would work fine as well.

On Tue, Nov 5, 2019, 9:07 AM  wrote:

> Just bought one from Mouser few days ago, and experiencing overheating
> issue when startup, anyone else having the same problem?
>
> On Thursday, 19 September 2019 20:02:00 UTC+8, Jason Kridner wrote:
>>
>> *BeagleBoard.org® Launches BeagleBone® AI, Offering a Fast Track to
>> Getting Started with Artificial Intelligence at the Edge*
>>
>> ROCHESTER, Mich., Sept.19, 2019 /PRNewswire/ -- The BeagleBoard.org®
>> Foundation today announces general availability of the newest, fastest,
>> most powerful BeagleBoard.org® BeagleBone® low cost development board yet,
>> and it’s driving a whole new AI revolution. Built on our proven open source
>> Linux approach, BeagleBone® AI fills the gap between small single board
>> computers (SBCs) and more powerful industrial computers. Leveraging the
>> Texas Instruments Sitara™ AM5729 processor, developers have access to
>> powerful machine learning capabilities with the ease of the BeagleBone®
>> Black header and mechanical compatibility.
>>
>> BeagleBone® AI makes it easy to explore how artificial intelligence (AI)
>> and machine learning can be used in everyday life. Through BeagleBone® AI,
>> developers can take advantage of the TI C66x digital-signal-processor (DSP)
>> cores and embedded-vision-engine (EVE) cores on the Sitara AM5729
>> processor. Machine learning is supported by an optimized TI Deep Learning
>> (TIDL) software framework and pre-installed software tools. Downloading and
>> running the latest examples of edge inference algorithms and applications
>> is only a few clicks away.
>>
>> “This board is the answer to our community’s request to see the next
>> major advancement in the BeagleBone® family” says Jason Kridner, co-founder
>> of the BeagleBoard.org*®* Foundation. “Its feature set is jam packed and
>> offers capabilities unparalleled by any other single board computer, open
>> hardware or not.”
>>
>> BeagleBone® AI has a feature set that includes:
>>
>>-
>>
>>BeagleBone® Black mechanical and header compatibility
>>-
>>
>>   Works with existing BeagleBoard.org® BeagleBone® cape add-on
>>   boards and many available third-party cape add-on boards and enclosures
>>
>>
>>-
>>
>>1GB RAM and 16GB on-board eMMC flash with a high-speed interface
>>
>>
>>-
>>
>>USB Type-C for power and superspeed dual-role controller; and USB
>>Type-A host
>>
>>
>>-
>>
>>Gigabit Ethernet, 2.4/5GHz WiFi, and Bluetooth 4.2/BLE
>>
>>
>>-
>>
>>microHDMI video and audio output
>>
>>
>>-
>>
>>Zero-download out-of-box software experience
>>-
>>
>>TI Sitara™ *AM5729 * processor with:
>>-
>>
>>   Dual 1.5GHz Arm® Cortex®-A15 microprocessor subsystem
>>   -
>>
>>   2 C66x Floating-Point VLIW DSPs
>>   -
>>
>>   4 Embedded Vision Engines (EVEs) supported by the TIDL software
>>   framework library for machine learning
>>   -
>>
>>   2x Dual-Core Programmable Real-Time Unit (PRU) subsystems (4 PRUs
>>   total) for ultra-low latency control and software generated peripherals
>>   -
>>
>>   2x Dual Arm® Cortex®-M4 co-processors for real-time control and
>>   subsystem management
>>   -
>>
>>   IVA-HD subsystem with support for 4K at 15fps H.264 encode/decode
>>   and other codecs at 1080p60
>>   -
>>
>>   Vivante® GC320 2D graphics accelerator
>>   -
>>
>>   Dual-Core PowerVR® SGX544™ 3D GPU
>>
>> “We believe this board will excel in everyday automation in industrial,
>> commercial and home applications” stated Christine Long, Executive Director
>> of the BeagleBoard.org® Foundation. “And at an extremely competitive price
>> point we’ve made this board available to everyone. It’s an industry game
>> changer.”
>>
>> BeagleBone® AI is available to buy as a standalone board, heat sink and
>> antenna included, from BeagleBoard.org’s® key distribution partners. Visit 
>> *http://beaglebone.ai
>> *.
>> --
>>
>> For information about BeagleBoard.org® Foundation, contact Christine
>> Long, Executive Director, at *chri...@beagleboard.org*
>>
>> BeagleBoard.org*®* and BeagleBone*®* are registered trademarks of the
>> BeagleBoard.org*®* Foundation, a 501c3 US-based non-profit corporation
>>
>> Sitara is a trademark of Texas Instruments
>>
>> --
>> https://beagleboard.org/about - a 501c3 non-profit educating around open
>> hardware computing
>>
> --
> 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 

Re: [beagleboard] BBONE-AI - Operating Temp Min & Max

[William Hermans]

I've just got my AI sitting in front of a 20" box fan(on low) I have
running 24/7 anyhow

debian@beaglebone:~$ uptime
 15:13:17 up 12 days,  9:30,  3 users,  load average: 0.23, 0.15, 0.10
debian@beaglebone:~$ cat /sys/class/thermal/thermal_zone*/temp
53400
53800
54600
53000
53800
Anyway, not sure what all the talk is about. It states plain as day on the
beaglebone.org "product" page that the board is prone to run hot . . .
.

On Thu, Oct 10, 2019 at 5:48 AM jonnymo  wrote:

> Thanks for the update.
>
> Yeah, I seen that Cape in a Jason vid and will be grabbing one when
> available.  There is someone on the element14 forums creating their own Fan
> cape as well.
>
> Cheers,
>
> Jon
>
> On Thu, Oct 10, 2019 at 3:17 PM Robert Nelson 
> wrote:
>
>> On Thu, Oct 10, 2019 at 10:11 AM jonnymo  wrote:
>> >
>> > Robert,
>> >
>> > Interesting.  There has been a ton of discussion regarding the heating
>> issue with the BB AI on the Element14 forums, however, in the end, the
>> BeagleBoard forum seems to be the location that is referenced for the final
>> say and info regarding this.  If Avent build the board, then they should
>> provide this information.   Thanks for the clarification.
>>
>> So Jason's been working on cpu setting:
>> https://github.com/beagleboard/BeagleBoard-DeviceTrees/commits/v4.14.x-ti
>>
>> Usually when users ask for the "Operating Temp Min & Max" values,
>> someone has to go dig thru all the components used on the board.. That
>> hasn't been done..
>>
>> > I've added the X-15 fan kit to my BB AI as is stated in the SRM and it
>> seems to stay around 40C during normal use.
>>
>> That one will work, it's noisy, i'm using a desk fan.. There is a 'fan
>> cape' coming..
>>
>> 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/CAG99bkrX%2BvTSonQJzArj12hCKdy_UEHth%3DySvKAD07FZ31WE6Q%40mail.gmail.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/CALHSORr1okfwqrCwjHozV_YKnFf9ixpsO6UsR4DuVcGhjzRWVw%40mail.gmail.com.

Re: [beagleboard] Re: BeagleBone AI is here!

[William Hermans]

Mine is on the way.

On Thu, Sep 19, 2019 at 12:16 PM Mala Dies  wrote:

> Hello,
>
> I saw that yesterday online at Mouser. Today, the email showed up. Nice!
>
> Seth
>
> P.S. I think you guys out-did yourselves. We shall see. Time to save a bit
> and then splurge on a nice, new board. Yea boy!
>
> On Thursday, September 19, 2019 at 7:02:00 AM UTC-5, Jason Kridner wrote:
>>
>> *BeagleBoard.org® Launches BeagleBone® AI, Offering a Fast Track to
>> Getting Started with Artificial Intelligence at the Edge*
>>
>> ROCHESTER, Mich., Sept.19, 2019 /PRNewswire/ -- The BeagleBoard.org®
>> Foundation today announces general availability of the newest, fastest,
>> most powerful BeagleBoard.org® BeagleBone® low cost development board yet,
>> and it’s driving a whole new AI revolution. Built on our proven open source
>> Linux approach, BeagleBone® AI fills the gap between small single board
>> computers (SBCs) and more powerful industrial computers. Leveraging the
>> Texas Instruments Sitara™ AM5729 processor, developers have access to
>> powerful machine learning capabilities with the ease of the BeagleBone®
>> Black header and mechanical compatibility.
>>
>> BeagleBone® AI makes it easy to explore how artificial intelligence (AI)
>> and machine learning can be used in everyday life. Through BeagleBone® AI,
>> developers can take advantage of the TI C66x digital-signal-processor (DSP)
>> cores and embedded-vision-engine (EVE) cores on the Sitara AM5729
>> processor. Machine learning is supported by an optimized TI Deep Learning
>> (TIDL) software framework and pre-installed software tools. Downloading and
>> running the latest examples of edge inference algorithms and applications
>> is only a few clicks away.
>>
>> “This board is the answer to our community’s request to see the next
>> major advancement in the BeagleBone® family” says Jason Kridner, co-founder
>> of the BeagleBoard.org*®* Foundation. “Its feature set is jam packed and
>> offers capabilities unparalleled by any other single board computer, open
>> hardware or not.”
>>
>> BeagleBone® AI has a feature set that includes:
>>
>>-
>>
>>BeagleBone® Black mechanical and header compatibility
>>-
>>
>>   Works with existing BeagleBoard.org® BeagleBone® cape add-on
>>   boards and many available third-party cape add-on boards and enclosures
>>
>>
>>-
>>
>>1GB RAM and 16GB on-board eMMC flash with a high-speed interface
>>
>>
>>-
>>
>>USB Type-C for power and superspeed dual-role controller; and USB
>>Type-A host
>>
>>
>>-
>>
>>Gigabit Ethernet, 2.4/5GHz WiFi, and Bluetooth 4.2/BLE
>>
>>
>>-
>>
>>microHDMI video and audio output
>>
>>
>>-
>>
>>Zero-download out-of-box software experience
>>-
>>
>>TI Sitara™ *AM5729 * processor with:
>>-
>>
>>   Dual 1.5GHz Arm® Cortex®-A15 microprocessor subsystem
>>   -
>>
>>   2 C66x Floating-Point VLIW DSPs
>>   -
>>
>>   4 Embedded Vision Engines (EVEs) supported by the TIDL software
>>   framework library for machine learning
>>   -
>>
>>   2x Dual-Core Programmable Real-Time Unit (PRU) subsystems (4 PRUs
>>   total) for ultra-low latency control and software generated peripherals
>>   -
>>
>>   2x Dual Arm® Cortex®-M4 co-processors for real-time control and
>>   subsystem management
>>   -
>>
>>   IVA-HD subsystem with support for 4K at 15fps H.264 encode/decode
>>   and other codecs at 1080p60
>>   -
>>
>>   Vivante® GC320 2D graphics accelerator
>>   -
>>
>>   Dual-Core PowerVR® SGX544™ 3D GPU
>>
>> “We believe this board will excel in everyday automation in industrial,
>> commercial and home applications” stated Christine Long, Executive Director
>> of the BeagleBoard.org® Foundation. “And at an extremely competitive price
>> point we’ve made this board available to everyone. It’s an industry game
>> changer.”
>>
>> BeagleBone® AI is available to buy as a standalone board, heat sink and
>> antenna included, from BeagleBoard.org’s® key distribution partners. Visit 
>> *http://beaglebone.ai
>> *.
>> --
>>
>> For information about BeagleBoard.org® Foundation, contact Christine
>> Long, Executive Director, at *chri...@beagleboard.org*
>>
>> BeagleBoard.org*®* and BeagleBone*®* are registered trademarks of the
>> BeagleBoard.org*®* Foundation, a 501c3 US-based non-profit corporation
>>
>> Sitara is a trademark of Texas Instruments
>>
>> --
>> https://beagleboard.org/about - a 501c3 non-profit educating around open
>> hardware computing
>>
> --
> 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
> 

Re: [beagleboard] Re: Can this beaglebone AI run raspbian OS?

[William Hermans]

Not to mention the hardware that makes up a Beaglebone AI is close to 2-3x
superior/better/more than a RaspberryPI 3. WIth about 4-5x as many I/O pins
exposed. Not to mention the additional processors built into the chip that
are exclusive to Beaglebone/Sitara.

On Wed, Sep 18, 2019 at 12:36 AM William Hermans  wrote:

> There is absolutely zero point to running "rasbian" on any beagle
> hardware. None of the software that is used for interacting with the
> outside world would work. Granted, networking should work, USB connectivity
> may work depending.
>
> As stated several times. Rasbian is just RaspberryPI(hardware) specific
> Debian. Well I do believe there is also an Ubuntu branch, but again . . .
> Ubuntu is based on Debian.
>
> Now is you're wanting someone to setup Debian for you, with all the bells
> and whistles that comes with Rasbian. Be prepared to pay someone tens, if
> not hundreds of thousands of dollars. It is however doable.
>
> On Tue, Sep 17, 2019 at 3:09 AM Jason Kridner  wrote:
>
>> Reading this back encouraged a couple of clarifications
>>
>> On Tue, Sep 17, 2019 at 8:59 AM Jason Kridner  wrote:
>>
>>>
>>>
>>> On Tuesday, September 10, 2019 at 1:29:31 PM UTC-4, Josiah Akinloye
>>> wrote:
>>>>
>>>> Ok
>>>> So what is the cost of the board
>>>>
>>>
>>> FAQ mentions that the price is around US$100.
>>>
>>
>> Excluding any applicable tariffs.
>>
>>
>>>
>>>
>>>> And can you manufacture based on my requirements??
>>>>
>>>
>>> See https://beagleboard.org/support and
>>> https://beagleboard.org/resources. BeagleBoard.org Foundation does not
>>> do customizations, but the open hardware design is at
>>> https://github.com/beagleboard/beaglebone-ai already (and OSHWA
>>> certified) and can be customized by developers familiar with the AM5729
>>> SoC, such as those listed on the resources page.
>>>
>>
>>
>> We are open hardware and will make changes to the design that benefit the
>> developer community. These would strictly be open source updates and with
>> sufficient demand to justify the board spins/testing.
>>
>>
>>
>>>
>>>
>>>>
>>>> On Tue, Sep 10, 2019 at 5:27 PM Jason Kridner 
>>>> wrote:
>>>>
>>>>> On Tuesday, September 10, 2019 at 12:19:35 PM UTC-4, Josiah Akinloye
>>>>> wrote:
>>>>>>
>>>>>> can the beaglebone AI run raspbian operating system?
>>>>>>
>>>>>
>>>>> What features are you looking for by running Raspbian?
>>>>>
>>>>> You can run Debian.
>>>>>
>>>>> It is possible to patch a Raspbian image to boot, but many of the
>>>>> custom aspects of Raspian won't work or won't do anything useful. If there
>>>>> is a software feature you are looking for that you use in Raspbian today,
>>>>> best to request that in the Debian images we assemble as a suitable
>>>>> starting point.
>>>>>
>>>>> --
>>>>> 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/0a030485-f048-4745-888c-67aaaec79f3d%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/beagleboard/0a030485-f048-4745-888c-67aaaec79f3d%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>> --
>>>>
>>>>
>>>>
>>>>
>>>> *Josiah Akinloye+2348135010778ceo at Hubtecs Technological
>>>> InstituteRobotic and AutomationEgalitarian TranshumanistFuturist"Mindset
>>>> powered by hard work equals unbeatable Achievement"--OLUWEST*
>>>>
>>> --
>>> 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

Re: [beagleboard] Re: Can this beaglebone AI run raspbian OS?

[William Hermans]

There is absolutely zero point to running "rasbian" on any beagle hardware.
None of the software that is used for interacting with the outside world
would work. Granted, networking should work, USB connectivity may work
depending.

As stated several times. Rasbian is just RaspberryPI(hardware) specific
Debian. Well I do believe there is also an Ubuntu branch, but again . . .
Ubuntu is based on Debian.

Now is you're wanting someone to setup Debian for you, with all the bells
and whistles that comes with Rasbian. Be prepared to pay someone tens, if
not hundreds of thousands of dollars. It is however doable.

On Tue, Sep 17, 2019 at 3:09 AM Jason Kridner  wrote:

> Reading this back encouraged a couple of clarifications
>
> On Tue, Sep 17, 2019 at 8:59 AM Jason Kridner  wrote:
>
>>
>>
>> On Tuesday, September 10, 2019 at 1:29:31 PM UTC-4, Josiah Akinloye wrote:
>>>
>>> Ok
>>> So what is the cost of the board
>>>
>>
>> FAQ mentions that the price is around US$100.
>>
>
> Excluding any applicable tariffs.
>
>
>>
>>
>>> And can you manufacture based on my requirements??
>>>
>>
>> See https://beagleboard.org/support and https://beagleboard.org/resources.
>> BeagleBoard.org Foundation does not do customizations, but the open
>> hardware design is at https://github.com/beagleboard/beaglebone-ai
>> already (and OSHWA certified) and can be customized by developers familiar
>> with the AM5729 SoC, such as those listed on the resources page.
>>
>
>
> We are open hardware and will make changes to the design that benefit the
> developer community. These would strictly be open source updates and with
> sufficient demand to justify the board spins/testing.
>
>
>
>>
>>
>>>
>>> On Tue, Sep 10, 2019 at 5:27 PM Jason Kridner 
>>> wrote:
>>>
 On Tuesday, September 10, 2019 at 12:19:35 PM UTC-4, Josiah Akinloye
 wrote:
>
> can the beaglebone AI run raspbian operating system?
>

 What features are you looking for by running Raspbian?

 You can run Debian.

 It is possible to patch a Raspbian image to boot, but many of the
 custom aspects of Raspian won't work or won't do anything useful. If there
 is a software feature you are looking for that you use in Raspbian today,
 best to request that in the Debian images we assemble as a suitable
 starting point.

 --
 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/0a030485-f048-4745-888c-67aaaec79f3d%40googlegroups.com
 
 .

>>> --
>>>
>>>
>>>
>>>
>>> *Josiah Akinloye+2348135010778ceo at Hubtecs Technological
>>> InstituteRobotic and AutomationEgalitarian TranshumanistFuturist"Mindset
>>> powered by hard work equals unbeatable Achievement"--OLUWEST*
>>>
>> --
>> 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/c9b83700-ed45-4ee0-bcd4-0f3d5e69a6d0%40googlegroups.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/CAK8RMs2JEqKGb7beh%3Dn7pY46jkDFvWCTGnwnrS3Pn7J_J1JKmQ%40mail.gmail.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/CALHSORp8CA7H7C-bmKnVBsvahOWf-zcrf8tBWnxyw1DoAUMAmA%40mail.gmail.com.

Re: [beagleboard] Indiegogo launched using BeagleBone AI for private, trusted NAS

[William Hermans]

Potential Downside. What will availability be for us normal "joes" ?

On Tue, Sep 17, 2019 at 9:42 AM Jason Kridner  wrote:

> This looks interesting to me as it provides a trusted, open-source
> software/hardware solution for network-accessible storage:
>
> https://privacysafe.ai/
>
> https://www.indiegogo.com/projects/privacysafe-privacy-by-design/x/7085817#/
>
>
> --
> https://beagleboard.org/about
>
> --
> 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/CA%2BT6QPmeZAspxg7i4V1u8a3BgTnjgWFhsauBfyFoB4t6LspK4Q%40mail.gmail.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/CALHSORpyxKJmWcCw%3Dx1Zt0WRB61D9ZMCoVWQ6PHa_AHP74kOwA%40mail.gmail.com.

Re: [beagleboard] Re: Where to order the BeagleBone AI?

[William Hermans]

100 bux sounds like a good deal. Furthermore, for me, and people like me.
This platform makes
 more sense than the x15 full sized board. For a credit card sized board
this thing sure will pack some muscle. .

On Tue, Sep 17, 2019 at 9:50 AM Jason Kridner  wrote:

> Thought I already replied to this, but I don't see it
>
> Price will be around US$100, not including any related tariffs.
>
> You know what, it was on a totally dumb thread name about Raspbian where
> the price question shouldn't have been asked.
>
> On Tuesday, September 17, 2019 at 3:28:27 PM UTC-4, William Hermans wrote:
>>
>> price ?
>>
>>
>> On Tue, Sep 17, 2019 at 8:24 AM Jason Kridner wrote:
>>
>>> No pre-orders. Orders available soon.
>>>
>>> On Tuesday, September 10, 2019 at 12:22:26 PM UTC-4, deeler
>>>  wrote:
>>>>
>>>> can we preorder?
>>>>
>>>> On Thursday, September 5, 2019 at 1:09:06 AM UTC+2, Jason Kridner wrote:
>>>>>
>>>>> Stay tuned. Did you sign up for the e-mail notification via
>>>>> https://beagleboard.org/ai ?
>>>>>
>>>>> On Wednesday, September 4, 2019 at 7:02:50 PM UTC-4, someone wrote:
>>>>>>
>>>>>> As Title
>>>>>
>>>>>
>>> --
> 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/0cf281b7-7c3d-4ca6-8f2d-5f330d94d179%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/0cf281b7-7c3d-4ca6-8f2d-5f330d94d179%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CALHSORrdUAARQysfz1MNVvsWOkRfAH6SpX5Q_pjhMVh%2BOkbpNg%40mail.gmail.com.

Re: [beagleboard] Re: Where to order the BeagleBone AI?

[William Hermans]

price ?


On Tue, Sep 17, 2019 at 8:24 AM Jason Kridner  wrote:

> No pre-orders. Orders available soon.
>
> On Tuesday, September 10, 2019 at 12:22:26 PM UTC-4, dee...@gmail.com
> wrote:
>>
>> can we preorder?
>>
>> On Thursday, September 5, 2019 at 1:09:06 AM UTC+2, Jason Kridner wrote:
>>>
>>> Stay tuned. Did you sign up for the e-mail notification via
>>> https://beagleboard.org/ai ?
>>>
>>> On Wednesday, September 4, 2019 at 7:02:50 PM UTC-4, someone wrote:

 As Title
>>>
>>> --
> 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/f23bd16b-c93c-410f-bea7-e205470f463c%40googlegroups.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/CALHSORqrj5-F4Kv8f9nNLDTvXK%3DiM6dCboFFoO%3D%2BHQo3hek6Pg%40mail.gmail.com.

Re: [beagleboard] Re: Cape Manager for U-Boot

[William Hermans]

I've noticed that sometimes the order in which you load device files can
play a factor on if they will load or not. May be worth checking out.

On Tue, Mar 27, 2018, 8:52 AM  wrote:

> They are a bit large to post as source.   I'll try attaching them...
>
> On Monday, March 26, 2018 at 6:27:56 PM UTC-7, RobertCNelson wrote:
>>
>> On Mon, Mar 26, 2018 at 5:56 PM,   wrote:
>> > Sorry, please disregard the uBoot output posted previously--that was
>> with
>> > our workaround of loading one big dtbo file.
>> >
>> > HERE IS THE OUTPUT FROM OUR MULTIPLE DTBOs...
>> >
>> >
>> > U-Boot SPL 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29)
>> > Trying to boot from MMC1
>> >
>> >
>> > U-Boot 2018.01-2-g9aa111a004 (Jan 20 2018 - 12:45:29 -0600), Build:
>> > jenkins-github_Bootloader-Builder-32
>> >
>> > CPU  : AM335X-GP rev 2.1
>> > I2C:   ready
>> > DRAM:  512 MiB
>> > No match for driver 'omap_hsmmc'
>> > No match for driver 'omap_hsmmc'
>> > Some drivers were not found
>> > Reset Source: Power-on reset has occurred.
>> > MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
>> > Using default environment
>> >
>> > Board: BeagleBone Black
>> >  not set. Validating first E-fuse MAC
>> > BeagleBone Black:
>> > BeagleBone: cape eeprom: i2c_probe: 0x54:
>> > BeagleBone: cape eeprom: i2c_probe: 0x55:
>> > BeagleBone: cape eeprom: i2c_probe: 0x56:
>> > BeagleBone: cape eeprom: i2c_probe: 0x57:
>> > Net:   eth0: MII MODE
>> > cpsw, usb_ether
>> > Press SPACE to abort autoboot in 2 seconds
>> > board_name=[A335BNLT] ...
>> > board_rev=[00C0] ...
>> > switch to partitions #0, OK
>> > mmc0 is current device
>> > SD/MMC found on device 0
>> > ** Bad device 0:2 0x8200 **
>> > ** Bad device 0:2 0x8200 **
>> > switch to partitions #0, OK
>> > mmc0 is current device
>> > Scanning mmc 0:1...
>> > gpio: pin 56 (gpio 56) value is 0
>> > gpio: pin 55 (gpio 55) value is 0
>> > gpio: pin 54 (gpio 54) value is 0
>> > gpio: pin 53 (gpio 53) value is 1
>> > switch to partitions #0, OK
>> > mmc0 is current device
>> > gpio: pin 54 (gpio 54) value is 1
>> > Checking for: /uEnv.txt ...
>> > 2094 bytes read in 30 ms (67.4 KiB/s)
>> > gpio: pin 55 (gpio 55) value is 1
>> > Loaded environment from /uEnv.txt
>> > Importing environment from mmc ...
>> > Checking if uenvcmd is set ...
>> > Checking if client_ip is set ...
>> > Checking for: /boot.scr ...
>> > Checking for: /boot/boot.scr ...
>> > Checking for: /boot/uEnv.txt ...
>> > gpio: pin 55 (gpio 55) value is 1
>> > 2246 bytes read in 28 ms (78.1 KiB/s)
>> > Loaded environment from /boot/uEnv.txt
>> > debug: [dtb=am335x-boneblack-overlay.dtb] ...
>> > Using: dtb=am335x-boneblack-overlay.dtb ...
>> > Checking if uname_r is set in /boot/uEnv.txt...
>> > gpio: pin 56 (gpio 56) value is 1
>> > Running uname_boot ...
>> > loading /boot/vmlinuz-4.4.91-ti-r133 ...
>> > 8886912 bytes read in 579 ms (14.6 MiB/s)
>> > uboot_overlays: dtb=am335x-boneblack-overlay.dtb in /boot/uEnv.txt,
>> unable
>> > to use [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...
>> > loading /boot/dtbs/4.4.91-ti-r133/am335x-boneblack-overlay.dtb ...
>> > 54603 bytes read in 84 ms (634.8 KiB/s)
>> > uboot_overlays: [fdt_buffer=0x6] ...
>> > uboot_overlays: loading /lib/firmware/maps_bbb_gpio-00A0.dtbo ...
>> > 1039 bytes read in 145 ms (6.8 KiB/s)
>> > uboot_overlays: loading /lib/firmware/maps_bbb_pwm-00A0.dtbo ...
>> > 1599 bytes read in 296 ms (4.9 KiB/s)
>> > uboot_overlays: loading /lib/firmware/maps_bbb_i2c-00A0.dtbo ...
>> > 1312 bytes read in 300 ms (3.9 KiB/s)
>> > uboot_overlays: loading /lib/firmware/maps_bbb_eqep-00A0.dtbo ...
>> > 2055 bytes read in 396 ms (4.9 KiB/s)
>>
>> Okay these loaded fine..
>>
>>
>> > uboot_overlays: uboot loading of
>> [/lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo]
>> > disabled by /boot/uEnv.txt [disable_uboot_overlay_emmc=1]...
>> > uboot_overlays: uboot loading of
>> [/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo]
>> > disabled by /boot/uEnv.txt [disable_uboot_overlay_video=1]...
>> > uboot_overlays: uboot loading of [/lib/firmware/BB-ADC-00A0.dtbo]
>> disabled
>> > by /boot/uEnv.txt [disable_uboot_overlay_adc=1]...
>> > uboot_overlays: loading /lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo
>> ...
>> > 2402 bytes read in 356 ms (5.9 KiB/s)
>> > uboot_overlays: cape universal disabled, external cape enabled or
>> > detected...
>> > loading /boot/initrd.img-4.4.91-ti-r133 ...
>> > 5416133 bytes read in 361 ms (14.3 MiB/s)
>> > debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1
>> > root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait coherent_pool=1M
>> > net.ifnames=0 quiet cape_universal=enable] ...
>> > debug: [bootz 0x8200 0x8808:52a4c5 8800] ...
>> > ## Flattened Device Tree blob at 8800
>> >Booting using the fdt blob at 0x8800
>> >Loading Ramdisk to 8fad5000, end 84c5 ... OK
>> >reserving fdt memory region: addr=8800 size=6e000
>> >Loading Device Tree to 8fa64000, end 8fad4fff ... OK
>> >
>> > 

Re: [beagleboard] BBB Wireless frequently drops connection

[William Hermans]

For what it's worth. The rpi3 does this as well. Granted perhaps not as
much. I've used mine as an ap for my phones, and would get dropped
connections at random times. Sometimes days, other times hours.

On Tue, Mar 27, 2018, 2:06 PM Robert Nelson  wrote:

> On Tue, Mar 27, 2018 at 5:22 PM, ags  wrote:
> > I’m experiencing random drops of wirelesss connectivity with BBBW. I
> have several other wired & wireless SBCs BBB, RPi, etc. and don’t see this
> with them. This is my only BBBW though. I believe I’ve experienced it since
> first installing - but am not certain.
> >
> > Symptoms are simply not being able to connect (with ssh or other means)
> or having an open ssh session terminated. Sometimes I can re-establish
> immediately, sometimes I let ping run for dozens of packets and it is
> eventually found back online, and sometimes I have to power-cycle to
> (re)gain access. When inaccessible the power and heartbeat leds are
> indicating normal operation.
> >
> > Is this a known issue? Is there a fix?
> >
> > Running 4.4.11x ti
>
> Let's check a few things:
>
> sudo /opt/scripts/tools/version.sh
>
> 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/CAOCHtYi9Nwd%3D4qNf2uFmxVw8YR3zqHKcgwEAyhzCVSn2UYc4Yw%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/CALHSORpXWrpKSUByDuPAqnbeju1iDwK-%3DAN0%2BiaheEXkHGf6Eg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Debian 9.3 - BBB ver 5AC repeatedly doesn't boot on µSD card unless boot button is pushed each time.

[William Hermans]

Probably an Old MLO / uboot.img on the eMMC. If the newer is flashed to the
eMMC, this problem would probably go away. I've experienced this on many
boards myself as / when I forget to update the eMMC.



On Fri, Feb 23, 2018 at 8:15 AM, Robert Nelson 
wrote:

> On Fri, Feb 23, 2018 at 12:12 PM, Michel Gerin 
> wrote:
> > Hello Robert,
> > Thank you for your help.
> > Here is the result:
> >
> > ~$ sudo /opt/scripts/tools/version.sh
> > git:/opt/scripts/:[89f2e9309c2322c15e2bb6b55afd214313d94842]
> > eeprom:[A335BNLT0A5C2713BBBK4830]
> > model:[TI_AM335x_BeagleBone_Black]
> > dogtag:[BeagleBoard.org Debian Image 2018-02-18]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> > 2018.01-2-g60ae27e116]:[location: dd MBR]
>
> Okay, i was expecting a 2nd entry here..
>
> For kicks try this to clear out the first 10mb of the eMMC..
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 bs=1M count=10
>
> if that doesn't solve it, do you have a serial cable to plug into j1?
>
> i'd like to see what's up on bootup, when the boot button is not pressed..
>
> 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/CAOCHtYhmDeG%3DdWoOYOaD8jDNGff38K4hppsnOcs%
> 3DZXMbVWqO%3DQ%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/CALHSORr_of%2BitFh-Ma4gP5ZD6NSwhVpX0JB-xJD6QJkKoMfPkg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] display driver

[William Hermans]

Apparently, the driver was compiled with debug symbols, and in debug mode.

On Thu, Feb 22, 2018 at 7:48 AM, evilwulfie  wrote:

> The more i learn the more i don't know
>
> Got most everything working with a spi display but one last issue i cant
> seem to figure out.
>
> if i load the module
>
> modprobe -v fbtft_device busnum=1 cs=0 speed=1600 name=er_tftm070_5
> gpios=reset:60,dc:24,led:50
>
> it loads with no errors
>
> i can display a jpg on the monitor
>
> fbi -noverbose -T 1 -a -d /dev/fb0 Mystery-100x100.jpg
>
> it displays the image on display just fine proving that the module is
> functioning fine
>
> ok this is good i say but if i tail -f /var/log/messages OR view dmesg
> OR tail -f /var/log/syslog
>
> it spams the below messages over and over.  If i read the logs it inits
> the display fine but the repeating messages baffle me.
>
> when i modprobe -r fbtft_device
>
> the errors go away
>
> I am SO over my head in kernel land i just need a little help here if
> anybody knows what might be going on.
>
> Feb 22 09:55:32 bone kernel: [37927.179998] fb_ra8875 spi1.0: Display
> update: 739 kB/s, fps=3
> Feb 22 09:55:32 bone kernel: [37927.350235] fb_ra8875 spi1.0:
> fbtft_update_display(start_line=0, end_line=15)
> Feb 22 09:55:32 bone kernel: [37927.350264] fb_ra8875 spi1.0:
> write_reg8_bus8: 30 00
> Feb 22 09:55:32 bone kernel: [37927.350276] fb_ra8875 spi1.0:
> write_spi(len=2): 80 30
> Feb 22 09:55:32 bone kernel: [37927.350474] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.350615] fb_ra8875 spi1.0:
> write_reg8_bus8: 31 00
> Feb 22 09:55:32 bone kernel: [37927.350623] fb_ra8875 spi1.0:
> write_spi(len=2): 80 31
> Feb 22 09:55:32 bone kernel: [37927.350762] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.350900] fb_ra8875 spi1.0:
> write_reg8_bus8: 32 00
> Feb 22 09:55:32 bone kernel: [37927.350908] fb_ra8875 spi1.0:
> write_spi(len=2): 80 32
> Feb 22 09:55:32 bone kernel: [37927.351046] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.351184] fb_ra8875 spi1.0:
> write_reg8_bus8: 33 00
> Feb 22 09:55:32 bone kernel: [37927.351192] fb_ra8875 spi1.0:
> write_spi(len=2): 80 33
> Feb 22 09:55:32 bone kernel: [37927.351330] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.351468] fb_ra8875 spi1.0:
> write_reg8_bus8: 34 1f
> Feb 22 09:55:32 bone kernel: [37927.351476] fb_ra8875 spi1.0:
> write_spi(len=2): 80 34
> Feb 22 09:55:32 bone kernel: [37927.351614] fb_ra8875 spi1.0:
> write_spi(len=2): 00 1f
> Feb 22 09:55:32 bone kernel: [37927.351752] fb_ra8875 spi1.0:
> write_reg8_bus8: 35 03
> Feb 22 09:55:32 bone kernel: [37927.351760] fb_ra8875 spi1.0:
> write_spi(len=2): 80 35
> Feb 22 09:55:32 bone kernel: [37927.351898] fb_ra8875 spi1.0:
> write_spi(len=2): 00 03
> Feb 22 09:55:32 bone kernel: [37927.352036] fb_ra8875 spi1.0:
> write_reg8_bus8: 36 0f
> Feb 22 09:55:32 bone kernel: [37927.352044] fb_ra8875 spi1.0:
> write_spi(len=2): 80 36
> Feb 22 09:55:32 bone kernel: [37927.352182] fb_ra8875 spi1.0:
> write_spi(len=2): 00 0f
> Feb 22 09:55:32 bone kernel: [37927.352320] fb_ra8875 spi1.0:
> write_reg8_bus8: 37 00
> Feb 22 09:55:32 bone kernel: [37927.352328] fb_ra8875 spi1.0:
> write_spi(len=2): 80 37
> Feb 22 09:55:32 bone kernel: [37927.352466] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.352604] fb_ra8875 spi1.0:
> write_reg8_bus8: 46 00
> Feb 22 09:55:32 bone kernel: [37927.352612] fb_ra8875 spi1.0:
> write_spi(len=2): 80 46
> Feb 22 09:55:32 bone kernel: [37927.352750] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.352888] fb_ra8875 spi1.0:
> write_reg8_bus8: 47 00
> Feb 22 09:55:32 bone kernel: [37927.352896] fb_ra8875 spi1.0:
> write_spi(len=2): 80 47
> Feb 22 09:55:32 bone kernel: [37927.353034] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.353172] fb_ra8875 spi1.0:
> write_reg8_bus8: 48 00
> Feb 22 09:55:32 bone kernel: [37927.353180] fb_ra8875 spi1.0:
> write_spi(len=2): 80 48
> Feb 22 09:55:32 bone kernel: [37927.353318] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.353456] fb_ra8875 spi1.0:
> write_reg8_bus8: 49 00
> Feb 22 09:55:32 bone kernel: [37927.353464] fb_ra8875 spi1.0:
> write_spi(len=2): 80 49
> Feb 22 09:55:32 bone kernel: [37927.353602] fb_ra8875 spi1.0:
> write_spi(len=2): 00 00
> Feb 22 09:55:32 bone kernel: [37927.353740] fb_ra8875 spi1.0:
> write_reg8_bus8: 02
> Feb 22 09:55:32 bone kernel: [37927.353748] fb_ra8875 spi1.0:
> write_spi(len=2): 80 02
> Feb 22 09:55:32 bone kernel: [37927.357784] fb_ra8875 spi1.0:
> write_vmem16_bus8(offset=0, len=25600)
> Feb 22 09:55:32 bone kernel: [37927.357838] fb_ra8875 spi1.0:
> fbtft_write_spi(len=4093): 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00 00 0
> 0 00 00 00 00 00 00 00 00 00 ...
> Feb 22 09:55:32 bone 

Re: [beagleboard] Re: SPI on beagle bone black and beagle bone black wireless

[William Hermans]

Clay, a bit of advice for you. Stop worrying about how you perceive someone
over the internet, whom by the way doesn't know you, and you do not know
them yourself. I'm not here to hand hold anyone, and I do answer question
for those who ask questions in a way that makes sense to me. But if you've
got a problem with how I say something. You know what, keep it to yourself.
You're not paying me, or anyone else to help you for that matter. So ask
your questions, then maybe they'll get answered. Otherwise, keep the
personal opinion( which is wrong by the way ) out of it.

-- 
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/CALHSORpE5ycpbvuNMXu%3DN%2B8284oFxTwGH%3D6sA%3Ds%2BhJT%2BEZehdg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: SPI on beagle bone black and beagle bone black wireless

[William Hermans]

On Sat, Dec 9, 2017 at 1:01 PM, Dennis Lee Bieber <wlfr...@ix.netcom.com>
wrote:

>
> The following is just my viewpoint, and is not meant to be an
> attack on
> any person. I've not done enough with the BBB (other than running a nasty
> benchmark on it and an RPi3 -- and I think the benchmark wore out the
> original RPi3 SD card, before I obtained a small USB hard drive for swap)
>
> On Sat, 9 Dec 2017 12:10:23 -0700, William Hermans
> <yyrk...@gmail.com> declaimed the following:
>
> >
> >You need to slow down, and learn things. Seriously, when I first had a BBB
> >in hand, I knew nothing about embedded Linux, and had to learn everything
> >from the ground up. Since this was also when the beaglebone black first
> >came out, there were no articles on the web. However, what I did not
> >understand at the time, was the BBW was pretty much the same hardware from
> >an embedded linux users standpoint. There were a lot of article out there
> .
>
> The biggest hindrance currently is that practically everything
> that IS
> "out there' for the BBB is based upon cape-manager and run-time device tree
> overlays. There doesn't seem to be anything that firmly lays out how to
> convert a cape-manager/overlay example into the u-Boot overlay scheme
> (would be nice if such example actually used some major documentation --
> say a side-by-side of Molloy's lessons).
>
> Consider how many questions over the last few months have had
> answers
> on the order of "... no longer create a separate FAT partition" or "... now
> use u-Boot overlays". Neither of which actually explain how to go from some
> now-outdated guide to equivalent functionality. Heck, I've even seen images
> vary from auto-mounting an SD card (when booting from eMMC) to requiring
> one to figure out how to perform a mount, and to some intermediate
> condition.
>

This just tells me that either a) the person asking the question isn't
willing to look, or doesn't know where to look. Both of the examples youve
given above are explained on the elinux documentation pages. Of whcih I'm
assuming wrote those guides. Robert at least links to them all the time,
for question asked here. Not to mention in the case of uboot overlays, it's
clearly mentioned, and linked to in the uEnv.txt file for every image I've
seen to date.

As for the rest, yeah, IDK maybe it's just me( I doubt it ) but very seldom
do I have issues following an older guide, and converting to a modern file
system arrangement. I'd say, that perhaps more time needs to be invested in
order to "get it" ?

Adapting overlays, source, etc is a matter of experience, and perhaps those
who do not understand them should study, and experiment more ? Worked for
me.

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

Re: [beagleboard] Re: Beaglebone time runs slow despite starting /lib/systemd/systemd-timesyncd

[William Hermans]

On Sat, Dec 9, 2017 at 12:08 PM,  wrote:

> Thanks, glad to see I'm not the only one with the issue.  Did some more
> searching and it seems it only logs the sync that happens at daemon start
> up, but is supposed to resync at some compiled in interval.  Check the most
> recent sync time with the times from stat /var/lib/systemd/clock
>
> On my Debian 8.9 Beaglebone Green I changed /etc/systemd/timesyncd.conf to
> have a line:
> NTP=pool.ntp.org
> This is the server that I know is being used by the Lorex DVR device which
> is the most important wrt the time sync with  my Beaglebone Green.
>
> I then did:
> sudo systemctl stop systemd-timesyncd
> sudo systemctl start systemd-timesyncd
>
> and sudo systemctl status  systemd-timesyncd showed I was apparently now
> using the pool.ntp.org server.
>
>
> Using: stat /var/lib/systemd/clock
> Mine seems to be updating every 35 seconds, although apparently the
> interval will change as sync gets better/worse.
>
> After doing this about 45 minutes ago my Beaglebone is now within 1 second
> of the Lorex, where it was about 5 seconds off before.  Is it possible that
> extra jitter in the time functions is caused by a fairly heavy and variable
> workload?  tops shows load averages: 0.20 .010. 0.07
>
> OTOH my BBW Debian 9.2 system, which has been up about a day longer than
> the BBG (did a test reboot yesterday) now seems well synced, but it is very
> lightly loaded basically just running my ssh session to make these tests.
> The systemd-timesyncd update interval seems to be about 34 minutes.
>
> So I'm not sure what is really going on here, but as long as the BBG and
> the Lorex stay synced to +/- 1 second I don't need to understand it :)
>

If you're serious about keeping time. Then get an accurate real time clock,
and sync your system clock off that. Then update the real time clock once
every month, or however often you need in order to keep time as close to
dead on, as you need it.

-- 
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/CALHSORpA%2B2t9ZDRW-MTB5YTQW%2BQHQ6dQXKY5ji536FhMJxV%2Bxg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: SPI on beagle bone black and beagle bone black wireless

[William Hermans]

On Fri, Dec 8, 2017 at 10:57 PM,  wrote:

> So, this is what so (fun?) about the BB ecosystem.
>
> I'm updating to the most recent image, trying to run code that has been
> working great for a good long time now, and it fails utterly with the same
> issue Nuno is experiencing.
>
> I understand William Herman's point of view - for him, this is blaringly
> obvious. Why so hard? I'm sure he wonders. I'm willing to bet that William
> is an expert at embedded linux, and perhaps does it as a day job. That's
> admirable, and I think it would be fun to do that too.
>
> But I don't.
>
> I like making blinky lights. https://www.facebook.
> com/claytongulick/videos/pcb.10155266610164779/10155266622269779/?type=3&
> theater
>
> My point here, is that if the BB community expects folks like me to stick
> around and not just use a raspberry pi for everything, we need to make this
> stuff easier.
>
> I'm using the same documented SPI pins that Nuno is using, and on the
> latest image, it just doesn't work. Not only that, but the commands in
> uEnv.txt have changed.
>
> Where is the documentation on this? How are we expected to figure this out?
>
> And now, according to Robert, I just simply can't use the pins I was using
> before without using something called dtb-rebuilder?
>
> Look guys, I know this stuff is like breathing to you and not a big deal.
> But changes like this without clear documentation are going to lose the
> hobbyist/maker community.
>
> Sorry for the rant, I'm a bit frustrated, it's midnight and I've been
> working on this for hours without success, just to get SPI working the same
> way it used to.
>
> For now, I'm going to revert to an older image. I'd love to update my
> github doc with some clear instructions on how to get SPI up and going on
> all of the documented SPI pins if someone can point me to a place where I
> can figure it out.
>

You need to slow down, and learn things. Seriously, when I first had a BBB
in hand, I knew nothing about embedded Linux, and had to learn everything
from the ground up. Since this was also when the beaglebone black first
came out, there were no articles on the web. However, what I did not
understand at the time, was the BBW was pretty much the same hardware from
an embedded linux users standpoint. There were a lot of article out there .
. .

Additionally, you should understand no one here gets paid to help anyone.
So this comment "if you guys want to keep me . . ." comment is going to
fall on deaf ears. The embedded Linux community is huge, but no one wakes
up early morning thinking "gee, I hope there are a bunch of questions to
answer today . . ."

Anyway, you probably have a lot to learn, just so you can form a proper
question. Which by the way, was how it was with me a little under 5 years
ago.

-- 
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/CALHSORqj9q0TT-_b2%3DW9kpe6w0w0Dd88%2BQ-7PMWdBeCuAj9PPg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Is cape manager obsolete? What about device tree overlays?

[William Hermans]

On Wed, Nov 29, 2017 at 7:27 AM, Mark A. Yoder 
wrote:

> That fixed it.  Thanks...
>
> Now I see all sorts of gpios are already exported.
> export   gpio114  gpio13  gpio22  gpio30  gpio46  gpio50  gpio66  gpiochip0
> gpio110  gpio115  gpio14  gpio23  gpio31  gpio47  gpio51  gpio67
> gpiochip32
> gpio111  gpio116  gpio15  gpio26  gpio4   gpio48  gpio60  gpio68
> gpiochip64
> gpio112  gpio117  gpio2   gpio27  gpio44  gpio49  gpio61  gpio69
> gpiochip96
> gpio113  gpio12   gpio20  gpio3   gpio45  gpio5   gpio65  gpio7   unexport
>
> I want to unexport a couple (14, 113 and 115) so the *fbtft_device*
> kernel driver and access them.  But I get and error
> echo: write error: Invalid argument
>
> How do I unexport them?
>
>>
>>
as root:

echo xxx > /sys/class/gpio/unexport

Where xxx == the gpioxxx value you wish to reclaim.

So in the example case of gpio112 . . .

echo 112 > /sys/class/gpio/unexport

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

Re: [beagleboard] How to boot on a custom Linux built with Buildroot?

[William Hermans]

On Tue, Nov 28, 2017 at 5:47 PM, Robert Nelson 
wrote:

> On Tue, Nov 28, 2017 at 5:32 PM, RPGamer  wrote:
> > OK so what's the official kernel sources for the Blue?
> >
> > I tried different sources, the one provided by Buildroot and this one :
> > https://github.com/beagleboard/linux.
> > I've seen that you use an other more repository you host on GitHub that
> you
> > patch with dozen of patches from an other repository you host to build an
> > Debian/Ubuntu based distro.
> > Is there any "kernel only" repository with working source for the Blue
> or a
> > list of patches needed to make it works?
>
> For the Blue:
>
> 1: Pure Mainline:
>
> 2:
> https://github.com/beagleboard/linux
>
> All these branches:
>
> 4.4 4.4-rt
> 4.9 4.9-rt
> 4.14 4.14-rt
>
> 3: lots more..
>
> Yakbuild ?

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

Re: [beagleboard] Is cape manager obsolete? What about device tree overlays?

[William Hermans]

On Tue, Nov 28, 2017 at 7:06 PM, Robert Nelson 
wrote:

> On Tue, Nov 28, 2017 at 8:02 PM, Mark A. Yoder 
> wrote:
> > bone$ dpkg --list | grep cape
> > ii  bb-cape-overlays
> > 4.4.20171120.0-0rcnee1~stretch+20171120   armhfDevice tree
> > overlays for Beaglebone.
> > ii  roboticscape
> > 0.3.4-git20170602-0rcnee4~stretch+20171108armhfRobotics Cape
> > Library and Examples
> >
> > Mine looks recent.  Any suggestions on a fix?
> >
> > --Mark
> >
> > This might help...
> > bone$ sudo /opt/scripts/tools/version.sh
> > git:/opt/scripts/:[e5c23dc2a45f5c9ace291dd32e7c3d79edc1932d]
> > eeprom:[A335BNLT000C3114BBBK1969]
> > model:[TI_AM335x_BeagleBone_Black]
> > dogtag:[BeagleBoard.org Debian Image 2017-11-26]
> > bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot
> > 2017.11-2-g7b415acfc1]
> > bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot
> 2015.01-1-gb2412df]
>
> There's the issue, old u-boot in eMMC, so all teh U-Boot stuff is
> ignored.. and thus nothing is in sync.. ;)
>
> sudo dd if=/dev/zero of=/dev/mmcblk1 count=1 seek=1 bs=128k
>


So I'm seeing this as the biggest problem most people are having. It's
bitten me more than once too. Just got to remember people. Get into the
habit of pressing the boot button when flashing newer images.

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

Re: [beagleboard] Linux Kernel tree for porting to mailine and basic support.

[William Hermans]

Any video of that workshop ? All I saw from hackaday was Sammy Kamkar etc,
regurgitated video . . .

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

Re: [beagleboard] Are there more details on the function of the battery and power management?

[William Hermans]

On Fri, Nov 3, 2017 at 8:32 PM, Kellen Lundry  wrote:

> What all does the power management handle?  Can it manage safely charging
> a lipo battery and supplying power to the board? Can it be used for
> projects that may have power intermittently? Like say a solar powered clock
> with a battery connected that charges the battery when there is sun and
> continues running from battery when there isn't?
>

In short. Yes, and no.

Yes, the battery can hold the beaglebone up for a limited amount of time,
while there is an "ac power" outage.

No, the beaglebone will not be fully functional if you require USB
functionality at all. As USB requires 5v, and a typical lithium battery is
3.7-4.1v. So you lose USB on a power outage, and it will not come back
until after a reboot. Assuming "ac power" is back when the board comes back
up.

Without the debian package acpid installed, the battery functionality
varies. With some versions the board will stay up, other versions the board
will unceremoniously  immediately shutoff( non clean power off ). Just as
if there were no battery.

Additionally, there is a PMIC register that can be toggled to keep the
board from shutting down while there is a battery connected correctly
through the board test points. I've tested this, and it works as expected.

As far as I can tell from my limited experimentation. You can not change
the charge aspects of the PMIC, it all seems to be hard coded in the
firmware. However, with that said, we've done extensive testing as far as
physically checking the battery voltage, and it seems that the voltage
rarely if ever goes above 4.0xx voltage. So it's pretty close to an 80%
charge, where many lithium people like to keep their batteries for the most
longevity.

Passed that, I probably can not talk much more about our design. However, I
can say that sometimes, the board will get put into a state, where it hangs
at reset. In these cases, one must disconnect the power, reconnect the
power, then toggle the reset pin on the board. Otherwise the board will
hang indefinitely. So, when I say disconnect power, I mean all power. DC
in, and battery alike. The only way to do this automatically, is design a
proper circuit, and use some form of micro-controller. That is, for
locations where physical interaction could be difficult.

All the technical information you need, is in the PMIC datasheet. The rest
will be learned through experimentation, and experience with using it.
Including knowing how I2C in Linux is used.

-- 
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/CALHSORro%3DYT%2B7dO-X3Zw9RaGV3HpBqVZ%3DtP8tP-JEzaGfgNHBQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 11:28 AM, Robert Nelson 
wrote:

> On Wed, Nov 1, 2017 at 1:24 PM, Tracy Smith  wrote:
> > The need to use E18 and E19 For CAN1 comes from the TI pinmux tool.
>
> Umm, on the ZCZ package used on the BBB
>
> E18: dcan1_tx
> E19: not available for can0/can1...
>
> Want to try again?
>

Yeah tx, and rx are staggered two pins apart in the pdf file I have here.
what are the Px header assignments, or gpioxx_yy nomenclature assignments ?

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

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 11:19 AM, Robert Nelson 
wrote:

> On Wed, Nov 1, 2017 at 1:14 PM, Tracy Smith  wrote:
> > E17 and E18 we want to use that are designated as possible CAN1 pins on
> the
> > BeagleBone Black schematic.
> >
> > Not using a different overlay, using the existing 4.14 kernel and 2017 I
> > boot that Robert Nelson suggests using for the BBB. But we need to pinmux
> > for E17 and E18 because the TI pinmuxing tool finds no conflict with
> these
> > two pins on our custom board. I’ll go back and check the CAN1 but prior
> to
> > Roberts changes last week that did not use the P9 expansion header, the
> unit
> > pinmux used different pins CAN1 I believe.  With the P9 expansion header,
> > can’t use Roberts overlay because there is no P9 expansion header on our
> BBB
> > board. I’ll go back look at the pins for CAN1 prior to then P9 overlay
> > changes from last week by Robert.
>
> What i suggested, assumed you were using a BBB.  Thus since you have a
> custom board, it's all null and void..
>
> Use TI's pinmux tool and properly route your can signals.
>

What Robert said, but in addition, it might be handy if you let us know
what hardware( everything ) you're using to help us, help you spot
potential hardware conflicts. I've worked on a project that did in fact use
one CAN interface a couple or three years ago. It works, but I only used
one bus. Not two. Additionally, I was using an older kernel, so I've not
the same on a current kernel. At some point I think I did test a semi
recent kernel, just to get the interface up and running, but I did not test
the C code I wrote a while back on that interface.

So how do you know it's not working. Just saying it doesn't work does not
give us the steps you taken to get where you are. or the error messages
you're getting, that could help us troubleshoot your issue for you. Nor
does it tell us if the driver for a given CAN interface is even loaded. You
see where I'm going ? There are many places for this process to go wrong.

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

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 11:01 AM, Tracy Smith  wrote:

> Ok look this custom board is based on the BeagleBone Black. For all
> intense and purposes it is the BBB. The pins for the AM3358 are the same.
> The primary difference is no P9 expansion header. What you are suggesting
> below is exactly what I’m doing and why I have the questions I do because
> your CAN support will not work on our custom BeagleBone Black.
>
> Customers will use the BBB as a reference platform and will actually have
> to do pinmuxing. When I do mention custom board, you do ignore me. But you
> shouldn’t because not all companies that use the BBB as a reference
> platform will use the P9 expansion and they will want to have CAN support
> in the kernel even without the P9 expansion header. You don’t have to use
> the P9 and the overlay being used to support CAN0 and CAN1
>
> You seem to be limiting CAN support to those using the P9 expansion
> header?  Why is that? Does it allow for four or more CANS?
>
> Really appreciate the assistance and it has been and continues to be
> extremely helpful.
>
> What limitations or constraints are causing you to have to use the P9
> expansion header for CAN?  Knowing this help justify adding an expansion
> header to the design.
>
> I need to look closer at the overlay. But knowing these constraints could
> justify adding the P9 expansion header to our custom BBB board.
>
> Thx, Tracy
>

First, I am not affiliated with beagleboard.org, cicuitco or any other
organization related directly to the beaglebone, or beagleboard products.
Or anyone who sells said products. I am just your average community member,
whose been using the beaglebone products since it's release date

Second, I never said I was ignoring anyone.

Third, you're delving into territory that myself, and most others have not
gone into. So if someone does say they're ignoring you, it could very well
be that they have not done what you're doing, and do not want to give you
incorrect information.

Lastly, be more verbose with your information. Just saying "wont work for
us" doesn't tell us what the underlying problem is, or how to help you
solve your issue.

So . .. tell us EXACTLY what you've done, and EXACTLY the errors your
experiencing. Then perhaps, if you're verbose enough, someone on this list
can help 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/CALHSORr5DDcmH2O5VydO9b8%3DWX4yKhtW9jm5q4PqaFnzrSc8%3Dg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Cannot get BBB to flash new OS image

[William Hermans]

Long story short.

When the eMMC has the first, and second stage bootloader installed on it.
The board will always load these from the eMMC, and then load the rest from
the sdcard when one is inserted.

The result is that one can be put into a non working state, because there
would be a MLO / uboot / kernel conflict.

There are two ways to solve this, Robert already mentioned one. The other
would be to press, and continue to hold the boot button on the board so
that it loads MLO, and uboot form teh sdcard instead. I've heard mention of
some people having difficulties with this, and instead short the boot
button. BUt I've not done that personally.

In the end, it would probably be easier to do as Robert suggests above.

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

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 10:17 AM, William Hermans <yyrk...@gmail.com> wrote:

>
>
> On Wed, Nov 1, 2017 at 10:12 AM, William Hermans <yyrk...@gmail.com>
> wrote:
>
>>
>>
>> On Wed, Nov 1, 2017 at 10:05 AM, Tracy Smith <tlsmith3...@gmail.com>
>> wrote:
>>
>>> We have no P9expansion header.  I’ve already discussed this with Robert
>>> Nelson.  We are using the AM3358 pins I sent previously.  Any can using the
>>> P9and this overlay will not work for our custom board.
>>>
>>
>> Ok, good, that doesn't make a bit of difference at all. Those pin names
>> in the overlay are just variables used by the file, and initially by cape
>> manager. cape manager translates those variable names into addresses when
>> the overlay file is compiled.
>>
>> Passed that, the software that is provided could stll use the Px header
>> designation for the pins, and it'll still work fine if you're using
>> something like universal IO + config-pin, so long as you all have not done
>> something drastically different in your layout. I do recall that some
>> devices can be done using multiple pin configurations, and one in fact is
>> still like that with the beaglebone design as is.
>>
>> Anyway, I do not remember if CAN1 has the potential to be on different
>> pins or not. Out of the processor. But working with the file I sent you a
>> link to all that can easily be changed.
>>
>
> Well technically, I'm not 100% positive on this. There could be hooks, etc
> I'm not aware of, and I have not done this hands on personally. But so long
> as you're using the same pins the bealgebone is using. It should work.
>
> Are you, or are you not using he same pins as the beaglebone for CAN1 ?
>

Another thing I did not consider is that it sounds like you could be using
a completely different board file overlay for your hardware, at which point
all bets are off.

-- 
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/CALHSORpUw6vhmD7CtNRhA1R1aL2zhkVcpXaELo%3DS%2BS%3DAL3057g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 10:12 AM, William Hermans <yyrk...@gmail.com> wrote:

>
>
> On Wed, Nov 1, 2017 at 10:05 AM, Tracy Smith <tlsmith3...@gmail.com>
> wrote:
>
>> We have no P9expansion header.  I’ve already discussed this with Robert
>> Nelson.  We are using the AM3358 pins I sent previously.  Any can using the
>> P9and this overlay will not work for our custom board.
>>
>
> Ok, good, that doesn't make a bit of difference at all. Those pin names in
> the overlay are just variables used by the file, and initially by cape
> manager. cape manager translates those variable names into addresses when
> the overlay file is compiled.
>
> Passed that, the software that is provided could stll use the Px header
> designation for the pins, and it'll still work fine if you're using
> something like universal IO + config-pin, so long as you all have not done
> something drastically different in your layout. I do recall that some
> devices can be done using multiple pin configurations, and one in fact is
> still like that with the beaglebone design as is.
>
> Anyway, I do not remember if CAN1 has the potential to be on different
> pins or not. Out of the processor. But working with the file I sent you a
> link to all that can easily be changed.
>

Well technically, I'm not 100% positive on this. There could be hooks, etc
I'm not aware of, and I have not done this hands on personally. But so long
as you're using the same pins the bealgebone is using. It should work.

Are you, or are you not using he same pins as the beaglebone for CAN1 ?

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

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 10:02 AM, Tracy Smith  wrote:

> Hi William,
>
> These overlays from Robert Nelson are associated with the P9 expansion
> header.  We don’t have a P9 expansion header on the custom BBB we are
> using. So we can’t use this overlay.
>
> Thx, Tracy
>

You're not making any sense. Just because you can mux pins, doesn't mean
you can also reassign pins to something they're not intended.

-- 
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/CALHSORq-n4tFUDB0JKcP80fA%3D_g7nvkcu-JQDBWYTq4S%3D5GNzg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

On Wed, Nov 1, 2017 at 5:44 AM, Tracy Smith  wrote:

> Hi William,
>
> Thanks for the email and here is what I’m trying to do.
>
> The CANUSB from Lawicel is a standard USB device that looks like a serial
> port since it can use the FTDI driver.
>
>
>
> On the MachineKit Debian Beagle the CANUSB is a dev/ttyUSB0 device.
>
>
> On our *custom* BeagleBone Black, we want both CAN0 and CAN1 accessible
> USB devices.  We don’t want to have to add a P9 expansion header on the
> custom board for I2C and we have specific pins E17 and E18 we want to use
> that are designated as possible CAN1 pins on the BeagleBone Black
> schematic.
>
>
> These two pins for CAN1 are tstpt1 pin E17 and TP9 pin E18.  Just need to
> see if there is a pad name associated with these pins so I can use them for
> the pinmux file and device tree to make CAN1 available as a USB device for
> uboot and the kernel.  This is what I need.
>
>
> Looking through the pinmux files for any pad names associated with these
> two pins.
>
>
> Thx, Tracy
>
> Just use the file I sent you, no worries about anything. If you NEED to
put it all into one large overlay file, you can pretty much just copy paste
what's in that file into your existing overlay. WIth some caveats of
course. You'll need to make sure the file is organized correctly.

Personally, I'd just leave the file as is, and load it standalone.

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

Fwd: [beagleboard] Re: u-boot support for pins

[William Hermans]

-- Forwarded message --
From: William Hermans <yyrk...@gmail.com>
Date: Wed, Nov 1, 2017 at 9:58 AM
Subject: Re: [beagleboard] Re: u-boot support for pins
To: Tracy Smith <tlsmith3...@gmail.com>


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

Pad name is on the beaglebone schematic. Which for the purpose of using
overlays is useless.

On Wed, Nov 1, 2017 at 5:44 AM, Tracy Smith <tlsmith3...@gmail.com> wrote:

> Hi William,
>
> Thanks for the email and here is what I’m trying to do.
>
> The CANUSB from Lawicel is a standard USB device that looks like a serial
> port since it can use the FTDI driver.
>
>
>
> On the MachineKit Debian Beagle the CANUSB is a dev/ttyUSB0 device.
>
>
> On our *custom* BeagleBone Black, we want both CAN0 and CAN1 accessible
> USB devices.  We don’t want to have to add a P9 expansion header on the
> custom board for I2C and we have specific pins E17 and E18 we want to use
> that are designated as possible CAN1 pins on the BeagleBone Black
> schematic.
>
>
> These two pins for CAN1 are tstpt1 pin E17 and TP9 pin E18.  Just need to
> see if there is a pad name associated with these pins so I can use them for
> the pinmux file and device tree to make CAN1 available as a USB device for
> uboot and the kernel.  This is what I need.
>
>
> Looking through the pinmux files for any pad names associated with these
> two pins.
>
>
> Thx, Tracy
>
> On Oct 31, 2017, at 7:55 PM, William Hermans <yyrk...@gmail.com> wrote:
>
> SO what is it that you're trying to do ? I've read your posts, but am
> still mystified. Just sayin' . . . I've been working with this hardware for
> around 5 years now,  have written many device tree overlays for various
> hardware configurations. Including GPIO, I2C, UART, CAN, SPI, etc.
>
> I'm willing to give you some guidance, but need to understand what it is
> you're trying to do . . .
>
> I2C really isn't that hard to get working. Nor is most of it.
>
> --
> 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/dE1bIym6rDg/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/CALHSORrdO87s1J7uKrJ%2BEvRKQRmKhahZBq%3DmtK1
> ktk4sChsbkA%40mail.gmail.com
> <https://groups.google.com/d/msgid/beagleboard/CALHSORrdO87s1J7uKrJ%2BEvRKQRmKhahZBq%3DmtK1ktk4sChsbkA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/CALHSORoStvWHYsRVk_z_rE-pMNMvVv_MRviyEeH-FqJco1gfTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: u-boot support for pins

[William Hermans]

SO what is it that you're trying to do ? I've read your posts, but am still
mystified. Just sayin' . . . I've been working with this hardware for
around 5 years now,  have written many device tree overlays for various
hardware configurations. Including GPIO, I2C, UART, CAN, SPI, etc.

I'm willing to give you some guidance, but need to understand what it is
you're trying to do . . .

I2C really isn't that hard to get working. Nor is most of it.

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

Re: [beagleboard] Can't locate /sys/class/leds folder

[William Hermans]

On Sat, Oct 21, 2017 at 2:39 PM, William Hermans <yyrk...@gmail.com> wrote:

> wgd@wgd:~$ uname -a
> Linux wgd 4.4.68-ti-r111 #1 SMP Wed Jun 28 10:06:34 UTC 2017 armv7l
> GNU/Linux
> wgd@wgd:~$ ls /sys/class/leds/
> beaglebone:green:usr0  beaglebone:green:usr2
> beaglebone:green:usr1  beaglebone:green:usr3
> wgd@wgd:~$ cat /etc/dogtag
> BeagleBoard.org Debian Image 2017-07-01
>

The point is this. If you require something the standard factory images
need. Don't screw around with someone elses build guide, or images. The
beagleboard.org site has links to all factory, and custom images built by
the same people who build the factory images. Then if you want to get
"crazy, google "eewiki debian on beaglebone black", and Follow Roberts
guide that he uses in part, or whole to build the factory images.

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

Re: [beagleboard] Can't locate /sys/class/leds folder

[William Hermans]

wgd@wgd:~$ uname -a
Linux wgd 4.4.68-ti-r111 #1 SMP Wed Jun 28 10:06:34 UTC 2017 armv7l
GNU/Linux
wgd@wgd:~$ ls /sys/class/leds/
beaglebone:green:usr0  beaglebone:green:usr2
beaglebone:green:usr1  beaglebone:green:usr3
wgd@wgd:~$ cat /etc/dogtag
BeagleBoard.org Debian Image 2017-07-01

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

Re: [beagleboard] Re: PocketBeagle workshop at Hackaday Supercon

[William Hermans]

Just a note, all workshops already sold out.

On Mon, Oct 16, 2017 at 2:47 PM, Robert Nelson 
wrote:

> On Mon, Oct 16, 2017 at 4:30 PM, CJA  wrote:
> > Hi Drew,
> > Awesome, I just received my PocketBeagle today from arrow.com.  Is this
> > going to be a full day workshop ? And are there any prerequisites, in
> terms
> > of getting acquainted to certain topic's before attending the workshop..
> > Thanks for the help - Carmelito
>
> What would you like us to talk about? ;)
>
> aka, i'm still writing everything up..  Definitely be going over
> u-boot, kernel, u-boot overlays, config-pin, adafruit-io... ;)
>
> 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/CAOCHtYh9XY%2B5WPhyhjAHquzjqs8N200v%
> 2BR30ORNe3QzCBdGtng%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/CALHSORr4LhecHbngkQ2db2o3hQ6zDQ2t5Ci8%3DkjbeFMDYGUP1g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Adding a USB Port to PocketBeagle

[William Hermans]

On Sat, Oct 14, 2017 at 10:30 AM, Graham Haddock 
wrote:

> I am just reporting what "speedtest-cli" says.
>
> I note that watching "htop" at the same time, on the USB-2 to Ethernet
> tests, the CPU is maxing out at 100 percent, so the speed is not
> necessarily constrained by the network interface, but the CPU's ability to
> feed it, through the USB stack.
>
> I don't know how speedtest-cli works. If it runs a random number
> continuously, then we might be testing the speed of the random number
> generator, rather than the network.  If it builds a large data table in
> advance and just streams the table, then it is probably representative of
> the fastest the system can run.
>
> A long winded way of agreeing with you.
>
> But, there is no doubt in my mind that the USB-2 to Ethernet interface is
> about an order of magnitude faster than the SPI to Ethernet interface.
>
> One conclusion is that putting a 1Gb Ethernet interface on a PocketBeagle
> is a waste of money and power.  A 10/100 Mb USB-2 to Ethernet interface
> would be cheaper, just as fast for throughput, and about one fourth the
> power.
>
> --- Graham
>

As far as using the gether gadget driver for USB, I was kind of thinking
the same thing, but I did not comment at that time. e.g. should be a lot
faster than "slow" SPI ethernet. But while on the subject, I'm thinking the
PRU's could be used as well. Either as "software" SPI interface, or perhaps
something else I'm unaware of.

When I tested gether, I tested using iperf, which seems to be "the
standard" for old school linux admins. However, with that said, I usually
prefer real world tests, as that tells me what I can expect when I use an
interface as such. Not some "mumbo jumbo" that may, or may not have
anything to do with what I'm trying to accomplish.

As far as the pocketbeagle goes . . . I do not own one, and do not
currently plan on having one any time soon. But I have tested the "bejesus"
out of the blacks, and the greens. They actually achieve better networking
speeds than most Windows based desktops / laptops. On a PC, under windows,
you'd be doing good to get 10-10.5MB/s through put over a fast ethernet
connection. On GbE, the fastest I can think of personally, was around
60MB/s and that was not constant. Do note, that I used Intel Pro NiC's . .
.but the bottleneck was, I'm thinking in the PCIe lanes of the motherboards
. . .

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

Re: [beagleboard] I need a tutorial for how to boot prepare a sd card boot image

[William Hermans]

On Sat, Oct 14, 2017 at 9:14 AM, Mrigendra Chaubey <
mrigendra.chau...@gmail.com> wrote:

> Why i asked this because except I am downloading kernel from Robert's
> repository I don't know where beaglebone configs are
> selected.
> I can only see the soc name like am3xx but no where in configs beaglebone
> or anything that does not confuse a first timer
> sure that he is doing the right thing.
>

#1 You WERE talking to Robert

#2 There is no question if Robert did "the right thing". The question is if
YOU did the right thing.

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

Re: [beagleboard] Re: Adding a USB Port to PocketBeagle

[William Hermans]

On Fri, Oct 13, 2017 at 8:39 AM, Graham  wrote:

> I hacked a "quick and dirty" second USB port as described.
> Then connected a LAN7500 USB-2 to Gb-Ethernet board.
> Came right up, drivers are already in the kernel, no device tree changes.
> Connected to the network at 1 Gb.
>
> speedtest-cli results (on a 1 Gb up/down network)
> Download 27 Mbps, Upload 41 Mbps.
>
> And it has a legitimate MAC address.  :-)
>
> (for comparison, BBB Rev.C is download 60 Mbps, upload 70 Mbps, which
> is about all I would expect out of a 100 Mbps connection.)
>
>
> So, I'm not going ot argue about this, and I'm only going to say this
once.

I've real world tested ethernet on several A5A's, several C's, and a
boatload of green's.  Down speeds 11.6MB/s( that's megabyte ), up speed
11.4-11.5MB/s.

Real world test was a NFS share, reading / writing 1GB of data, or more.

Additionally, I've benchmarked USB networking, Down speeds 105 Mbit/s, and
uploads were a bit shy at around 85Mbit/s.

You may want to check to make sure your speed test is accurate.

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

Re: [beagleboard] Re: Announcing $25 PocketBeagle

[William Hermans]

On Wed, Oct 11, 2017 at 11:43 AM, Robert Nelson 
wrote:

> On Wed, Oct 11, 2017 at 1:33 PM, Jason Kridner
>  wrote:
> > Robert,
> >
> > Can you add the .bmap file?
>
> Oh i had stopped generating those by default, i'll quickly add one..
>
> I've completely switched to using etcher's command line version..
>


It's that fast ?

-- 
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/CALHSORr9%3DdgyBiV%2BMmRgD_SupnXRWZLn%2Bbc9DO9DNH2FiBipJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Serial Baudrates

[William Hermans]

On Tue, Oct 10, 2017 at 9:04 AM, Paul Van den Bergh 
wrote:

> Hi all,
>
> I'm implementing an interface to a commercial product that communicates
> over an asynchronous interface at 62500 Baud.  Looking at the 
> files on the BBB I cannot find this setting.  Is it at all possible to set
> up a u(s)art to communicate at this speed?  Is it possible with ioctl()?
> Where can I find more info on the later ?
>
> Thanks for your replies.
>

Read Peter Hurley's second post. From he link below. He he wrote / linked
code that will do any baud rate. A gist on github I believe it is. Then
it's just a gcc -Wall  -o 

https://groups.google.com/forum/#!searchin/beagleboard/serial$20baud$20rate$205760|sort:relevance/beagleboard/GC0rKe6rM0g/13c1ngXF7owJ

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

Re: [beagleboard] Slow boot times on PocketBeagle

[William Hermans]

There are options if you're running grub. So, perhaps there is a kernel
parameter that can be passed ? Not really a lot of info out there, at least
for current web search.

And yeah that minute and a half boot is getting old here too.

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

Re: [beagleboard] PRU

[William Hermans]

On Fri, Oct 6, 2017 at 11:38 PM,  wrote:

> Hi,
>
> Hi, I am new to beaglebone black PRU can anybody help me to use PRU in
> c-language.
>
> Thank you
> Ashok
>

http://lmgtfy.com/?q=beaglebone+PRU+in+C

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

Re: [beagleboard] Re: ENC28J60 Click on PocketBeagle

[William Hermans]

On Sat, Oct 7, 2017 at 4:02 PM, Robert Nelson 
wrote:

>
> How fast can you push the spi bus? I've just used the 12 mhz, as it was
> the default for one of the device tree in the docs..
>
> Regards,
>
> --
> 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/CAOCHtYi2bg8xZOt4yBaG9%3D6h5pVKv%2BRpGBPcrKZMa1wru%
> 3DbHSg%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

Yeah what Graham said. I seem to recall that the SPI bus could potentially
handle faster speeds too. But I've also read that above ~48Mhz the bus can
get noisy.

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

Re: [beagleboard] Stretch pwm difference

[William Hermans]

I think I have it figured out. If you  disable the ecap devices, the dual
channel populate normally. e.g. 0,2,4. But when you do have ecap enabled,
that's when things start to get squirrely. But at least it's not completely
random. There are or seem to be patterns when you have both ecap enabled.
My file structure looked exactly the same as your above where you had ecap
enabled.

On Fri, Sep 29, 2017 at 2:17 PM, Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Fri, Sep 29, 2017 at 3:19 PM, William Hermans <yyrk...@gmail.com>
> wrote:
> > Robert,
> >
> > Ok I think I see what you mean now( fully ). With universal IO and the
> > generic startup script enabled. I did see something similar to what you
> were
> > saying. However, if one disables both universal IO, and the generic
> startup
> > script, then writes their own custom overlay for all 3 of the PWM chips
> that
> > are dual channel. You get a structure like this:
> >
> > root@wgd:~# ls /sys/class/pwm/pwmchip*/ |grep pwm
> > /sys/class/pwm/pwmchip0/:
> > npwm
> > /sys/class/pwm/pwmchip2/:
> > npwm
> > /sys/class/pwm/pwmchip4/:
> > npwm
> >
> > This is consistent across multiple images on the same board. In this
> case a
> > 4G beaglebone black( rev C ). But at the same time as you can see from
> the
> > output above. The two PWM channels for each PWM chip are not enabled. In
> > Jessie, these are populated automatically at boot. How can I make that
> > happen in stretch ? I could write a script, but I think that is done
> > automatically through cape_manager in Jessie ?
>
> What's happening in v4.4.x, the pwm's are now in the correct order, if
> you look at v4.4.x: (pwm came before ecap)
>
> #4.4.88-ti-r129
> pwmchip0 -> ../../devices/platform/ocp/4830.epwmss/48300200.pwm/
> pwm/pwmchip0
> pwmchip2 -> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/
> pwm/pwmchip2
> pwmchip4 -> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/
> pwm/pwmchip4
> pwmchip6 -> ../../devices/platform/ocp/4830.epwmss/48300100.ecap/
> pwm/pwmchip6
> pwmchip7 -> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/
> pwm/pwmchip7
>
> In v4.9.x: (since ecap are considered pwm's) they are now in the order
> of the register address:
>
> pwmchip0 -> ../../devices/platform/ocp/4830.epwmss/48300100.ecap/
> pwm/pwmchip0
> pwmchip1 -> ../../devices/platform/ocp/4830.epwmss/48300200.pwm/
> pwm/pwmchip1
> pwmchip3 -> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/
> pwm/pwmchip3
> pwmchip5 -> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/
> pwm/pwmchip5
> pwmchip6 -> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/
> pwm/pwmchip6
>
> In your case, you only want the dual mode "pwm", (48300200.pwm,
> 48302200.pwm, 48304200.pwm), you shouldn't blindly enable the
> "pwmchip0,2,4" as they are dynamic.  You should grep the symlink
> first.
>
> Ps, watch out for v4.11.x too:
>
> #v4.4.x/v4.9.x
> /sys/class/pwm/pwmchip1/:
> drwxr-xr-x 3 root root0 Sep 29 21:06 pwm0
> drwxr-xr-x 3 root root0 Sep 29 21:06 pwm1
>
> #v4.11.x+
>
> /sys/class/pwm/pwmchip1/:
> drwxrwxr-x 3 root pwm 0 Sep 29 21:10 pwm-1:0
> drwxrwxr-x 3 root pwm 0 Sep 29 21:10 pwm-1:1
>
> (ps, this last change is good thing, notice that udev correctly added
> the "root:pwm" rule.. ;) )
>
> 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/CALHSORpeFHTD5q2WrPaQeLwCQ4D0D%2B_Yr0fTL4FuEZ_hvx%2BwLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Debian 9.1.0 with VirtualBox unable to "sudo apt-get install crossbuild-essential-armhf"

[William Hermans]

On Fri, Sep 29, 2017 at 1:54 PM, Jose Valenzuela San Juan <
javal...@gmail.com> wrote:

> Were you able to do this?
> The guide from Derek is a bit outdated.
> You don't have to use the source from embedian (as its deprecated). In
> debian 9 the cross compiling packages are in the standard repository.
> Follow this steps instead - Installation for unstable  - from
> https://wiki.debian.org/CrossToolchains - :
>
> You must enable the appropriate (HOST) foreign architecture before
>> installing the cross-compiler.
>>
>> dpkg --add-architecture armhfapt-get update
>>
>> It is recommended to install the cross environment like this as that
>> pulls in all the necessary components:
>>
>> apt-get install crossbuild-essential-
>>
>> i.e
>>
>> apt-get install crossbuild-essential-armhf
>>
>> But you can install just the compiler with
>>
>> apt-get install gcc-arm-linux-gnueabihf
>>
>> Note that gcc-arm-linux-gnueabihf is (like the native 'gcc') just a
>> metapackage, which brings int he current version of the actual compiler
>> gcc-4.9-arm-linux-gnueabihf (c.f. gcc-4.9)
>>
>
> Everything else form the guide should be ok to follow. You could even try
> to install a newer eclipse version if you want, it works fine.
>
> PD. The step in which you get the error is optional. Derek uses it only to
> show how easy is to get the versions of the libraries you need for either
> architecture
>

You should be aware that Stretch uses a newer gcc: gcc version 6.3.0
20170516 (Debian 6.3.0-18)

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

Re: [beagleboard] Stretch pwm difference

[William Hermans]

I mean this hack fix is fairly trivial. Without the qep's being enabled.

debian@wgd:~$ sudo su
root@wgd:/home/debian# cd ~
root@wgd:~# nano pwm-enable.sh









*#!/bin/bashecho '0' > /sys/class/pwm/pwmchip0/exportecho '1' >
/sys/class/pwm/pwmchip0/exportecho '0' >
/sys/class/pwm/pwmchip2/exportecho '1' >
/sys/class/pwm/pwmchip2/exportecho '0' >
/sys/class/pwm/pwmchip4/exportecho '1' >
/sys/class/pwm/pwmchip4/exportexit 0*

root@wgd:~# chmod +x pwm-enable.sh
root@wgd:~# ./pwm-enable.sh

root@wgd:~# ls /sys/class/pwm/pwmchip*/ |grep pwm
/sys/class/pwm/pwmchip0/:
npwm
pwm0
pwm1
/sys/class/pwm/pwmchip2/:
npwm
pwm0
pwm1
/sys/class/pwm/pwmchip4/:
npwm
pwm0
pwm1

-- 
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/CALHSORojNm6u5Eb%3DSrWvO%2BBcuVGFBO%3D_UTdjMa%2B-Wnh1V8TBrw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Stretch pwm difference

[William Hermans]

Robert,

Ok I think I see what you mean now( fully ). With universal IO and the
generic startup script enabled. I did see something similar to what you
were saying. However, if one disables both universal IO, and the generic
startup script, then writes their own custom overlay for all 3 of the PWM
chips that are dual channel. You get a structure like this:

root@wgd:~# ls /sys/class/pwm/pwmchip*/ |grep pwm
/sys/class/pwm/pwmchip0/:
npwm
/sys/class/pwm/pwmchip2/:
npwm
/sys/class/pwm/pwmchip4/:
npwm

This is consistent across multiple images on the same board. In this case a
4G beaglebone black( rev C ). But at the same time as you can see from the
output above. The two PWM channels for each PWM chip are not enabled. In
Jessie, these are populated automatically at boot. How can I make that
happen in stretch ? I could write a script, but I think that is done
automatically through cape_manager in Jessie ?

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

Re: [beagleboard] Stretch pwm difference

[William Hermans]

On Wed, Sep 27, 2017 at 1:31 PM, Robert Nelson 
wrote:

>
> Don't compare "pwmchipX's" directly, you need to dig into the symlink:
>
> root@beaglebone:/sys/class/pwm# ls -lh
> total 0
> lrwxrwxrwx 1 root root 0 Oct 13 17:14 pwmchip0 ->
> ../../devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip0
> lrwxrwxrwx 1 root root 0 Oct 13 17:14 pwmchip2 ->
> ../../devices/platform/ocp/4830.epwmss/48300100.ecap/pwm/pwmchip2
> lrwxrwxrwx 1 root root 0 Oct 13 17:14 pwmchip3 ->
> ../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip3
> lrwxrwxrwx 1 root root 0 Oct 13 17:14 pwmchip5 ->
> ../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip5
> lrwxrwxrwx 1 root root 0 Oct 13 17:14 pwmchip7 ->
> ../../devices/platform/ocp/48304000.epwmss/48304100.ecap/pwm/pwmchip7
>
> https://github.com/RobertCNelson/bb.org-overlays/
> blob/master/examples/cape-unversal-pwm.txt#L3-L9
>
> Regards,
>

So I get what you're saying, and get what the link is stating as well.
However, I'm not seeing how the pwmchipX value is changing at all. More to
the point, I really do not care if the underlying path changes, so long as
I do not have to completely rewrite a library in order to use the sysfs pwm
objects. Moreover, what good is loading a uboot overlay, if that overlay
does not do what it is supposed to do ?  It would be really nice to have
the pwm channels functioning before the OS is loaded.

*Jessie:*
root@wgd:~# ls -lh /sys/class/pwm
total 0
lrwxrwxrwx 1 root pwm 0 Sep 24 19:18 pwmchip0 ->
../../devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip0
lrwxrwxrwx 1 root pwm 0 Sep 24 19:18 pwmchip2 ->
../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip2
lrwxrwxrwx 1 root pwm 0 Sep 24 19:18 pwmchip4 ->
../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip4

*Stretch:*
root@wgd:~#  ls -lh /sys/class/pwm
total 0
lrwxrwxrwx 1 root pwm 0 Sep 26 21:20 pwmchip0 ->
../../devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip0
lrwxrwxrwx 1 root pwm 0 Sep 26 21:20 pwmchip2 ->
../../devices/platform/ocp/48302000.epwmss/48302200.pwm/pwm/pwmchip2
lrwxrwxrwx 1 root pwm 0 Sep 26 21:20 pwmchip4 ->
../../devices/platform/ocp/48304000.epwmss/48304200.pwm/pwm/pwmchip4

Seriously, I can run a script at boot, then run all the echo's I need in
order to populate the entire pwm subsystem for each "duel channel" pwm chip
I need to use. But it was my hope I did not have to.

With all of that said, this structure is all I care about.
root@wgd:~# uname -r
4.4.68-ti-r111
root@wgd:~# ls /sys/class/pwm/pwmchip*/ |grep pwm
/sys/class/pwm/pwmchip0/:
npwm
pwm0
pwm1
/sys/class/pwm/pwmchip2/:
npwm
pwm0
pwm1
/sys/class/pwm/pwmchip4/:
npwm
pwm0
pwm1

I would like Stretch to be the same at boot, without the need to run a
script if possible. But it's not.

root@wgd:~# uname -r
4.9.50-ti-r61
root@wgd:~# ls /sys/class/pwm/pwmchip*/ |grep pwm
/sys/class/pwm/pwmchip0/:
npwm
pwm0
/sys/class/pwm/pwmchip2/:
npwm
/sys/class/pwm/pwmchip4/:
npwm


Did I miss something in what you were saying ?

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

[beagleboard] Stretch pwm difference

[William Hermans]

So a few things to note about pwm behavior on the latest stretch image 
versus Jessie.
Obviously, Jessie by default runs an older kernel. 4.4.x versus 4.9.x.


First,

Jessie:
root@wgd:~# uname -r
4.4.68-ti-r111
root@wgd:~# lsmod |grep pwm
pwm_tiehrpwm 

Stretch:
root@wgd:~# uname -r
4.9.50-ti-r61
root@wgd:~# lsmod |grep pwm /* No output */

Here, I'm thinking the PWM module is built into the kernel. Because I'm 
running the same custom overlay on both boards, and both have a populated 
sysfs entry for pwm. However there is a difference.

Jessie:
root@wgd:~# ls /sys/class/pwm/pwmchip0
device  export  npwm  power  pwm0  pwm1  subsystem  uevent  unexport

Stretch:
root@wgd:~# ls /sys/class/pwm/pwmchip0
device  export  npwm  power  pwm0  subsystem  uevent  unexport

Here, initially, there was no pwm0 substructure. This populated after I ran 
echo '0' > /sys/class/pwm/pwmchip0/export as root. Further examination 
seems to indicate that pwm0 channel A is fully functional.

root@wgd:~# ls /sys/class/pwm/pwmchip0/pwm0/
capture  duty_cycle  enable  period  polarity  power  uevent

But I have not physically tested the hardware just yet.

So my questions are this. What's the difference ? Does this have something 
to do with the module being built into the kernel. or is there some kind of 
overlay change I'm not currrently aware of ?

config-pin for my project here is not an option . . . And in fact, 
cape_universal is disabled via the uboot envrorinment file.

Everything else seems to be exactly the same as far as I can tell, but I 
have not poured over the whole system just yet. Seems to be pretty stable 
too, but I've only been running the latest console stretch image for a few 
days now.


-- 
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/04056bac-16ec-4bba-b0c7-453df7efd228%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: PocketBeagle U-Boot Overlays [naming???]

[William Hermans]

On Tue, Sep 26, 2017 at 9:02 PM, Robert Nelson 
wrote:

> On Tue, Sep 26, 2017 at 9:55 PM, Graham  wrote:
> > The interface names seem much more self explanatory.
> > The U/M option is workable.
>
> They list 381 varients:
>
> https://shop.mikroe.com/click
>
> So 381 * 2 dtb overlays..
>
> 99% of them use one interface, SPI/I2C/UART
>
> So if we had to use the interface name, i'd probably simplify it to just:
>
> PB-I2C1-RTC-6-CLICK-00A0.dtbo
> PB-I2C2-RTC-6-CLICK-00A0.dtbo
>
> Maybe that'll be good enough to help users know which side to plug in?
>
> Regards,
>

Looks good to me.

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

Re: [beagleboard] Announcing $25 PocketBeagle

[William Hermans]

On Thu, Sep 21, 2017 at 10:42 AM, Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Thu, Sep 21, 2017 at 12:30 PM, William Hermans <yyrk...@gmail.com>
> wrote:
> > Thanks Robert. So pretty much still a work in progress I take it ?
>
> Works out of the box.. With any "2017-09-19" or later images...
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

Ok, cool, thanks 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/CALHSORp4cSHyY4C3%3DFgS7NeD4DNyUg-JLYvA-50vNSOWPx-uvQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Announcing $25 PocketBeagle

[William Hermans]

Thanks Robert. So pretty much still a work in progress I take it ?

On Thu, Sep 21, 2017 at 10:17 AM, Robert Nelson <robertcnel...@gmail.com>
wrote:

> On Thu, Sep 21, 2017 at 11:41 AM, William Hermans <yyrk...@gmail.com>
> wrote:
> > The board is bootble / usable right now ? The FAQ could be taken both
> ways.
> > e.g. because of the board overlay file.
>
> https://rcn-ee.net/rootfs/bb.org/testing/2017-09-19/
> stretch-iot/bone-debian-9.1-iot-armhf-2017-09-19-4gb.img.xz
>
>
> U-Boot SPL 2017.09-3-g02f3fd3962 (Sep 20 2017 - 14:09:02)
> Trying to boot from MMC1
>
>
> U-Boot 2017.09-3-g02f3fd3962 (Sep 20 2017 - 14:09:02 -0500)
>
> CPU  : AM335X-GP rev 2.1
> I2C:   ready
> DRAM:  512 MiB
> No match for driver 'omap_hsmmc'
> No match for driver 'omap_hsmmc'
> Some drivers were not found
> Reset Source: Power-on reset has occurred.
> MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
> Using default environment
>
> Model: BeagleBoard.org PocketBeagle
>  not set. Validating first E-fuse MAC
> Net:   eth0: RGMII MODE
> Could not get PHY for cpsw: addr 0
> cpsw
> Press SPACE to abort autoboot in 2 seconds
> board_name=[A335PBGL] ...
> switch to partitions #0, OK
> mmc0 is current device
> SD/MMC found on device 0
> ** Bad device 0:2 0x8200 **
> ** Bad device 0:2 0x8200 **
> switch to partitions #0, OK
> mmc0 is current device
> Scanning mmc 0:1...
> gpio: pin 56 (gpio 56) value is 0
> gpio: pin 55 (gpio 55) value is 0
> gpio: pin 54 (gpio 54) value is 0
> gpio: pin 53 (gpio 53) value is 1
> switch to partitions #0, OK
> mmc0 is current device
> gpio: pin 54 (gpio 54) value is 1
> Checking for: /uEnv.txt ...
> Checking for: /boot.scr ...
> Checking for: /boot/boot.scr ...
> Checking for: /boot/uEnv.txt ...
> gpio: pin 55 (gpio 55) value is 1
> 2595 bytes read in 27 ms (93.8 KiB/s)
> Loaded environment from /boot/uEnv.txt
> Checking if uname_r is set in /boot/uEnv.txt...
> gpio: pin 56 (gpio 56) value is 1
> Running uname_boot ...
> loading /boot/vmlinuz-4.4.88-ti-r122 ...
> 8665976 bytes read in 572 ms (14.4 MiB/s)
> loading /boot/dtbs/4.4.88-ti-r122/am335x-pocketbeagle.dtb ...
> 71821 bytes read in 145 ms (483.4 KiB/s)
> uboot_overlays: add [enable_uboot_overlays=1] to /boot/uEnv.txt to
> enable...
> loading /boot/initrd.img-4.4.88-ti-r122 ...
> 5514927 bytes read in 368 ms (14.3 MiB/s)
> debug: [console=ttyO0,115200n8 root=/dev/mmcblk0p1 ro rootfstype=ext4
> rootwait coherent_pool=1M net.ifnames=0 quiet] ...
> debug: [bootz 0x8200 0x8808:5426af 0x8800] ...
> ## Flattened Device Tree blob at 8800
>Booting using the fdt blob at 0x8800
>Loading Ramdisk to 8fabd000, end 86af ... OK
>Loading Device Tree to 8faa8000, end 8fabc88c ... OK
>
> Starting kernel ...
>
> [0.001144] clocksource_probe: no matching clocksources found
> [2.118518] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
> [2.227684] omap_voltage_late_init: Voltage driver support not added
> [2.238761] PM: Cannot get wkup_m3_ipc handle
> [2.776365] musb-hdrc musb-hdrc.1.auto: VBUS_ERROR in a_wait_vrise
> (80, <SessEnd), retry #3, port1 0008010c
>
> Debian GNU/Linux 9 beaglebone ttyS0
>
> BeagleBoard.org Debian Image 2017-09-19
>
> Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian
>
> default username:password is [debian:temppwd]
>
> beaglebone login:
>
> 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/CAOCHtYh-CjPoTELw_RqVzu_YF5eR27c9yMnCUxcaSAs-zA981g%
> 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/CALHSORryJ4sFHbNYstNYarTk13faxWJfypQDt_qCk5qZCP800w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Announcing $25 PocketBeagle

[William Hermans]

The board is bootble / usable right now ? The FAQ could be taken both ways.
e.g. because of the board overlay file.

On Thu, Sep 21, 2017 at 8:35 AM, Jason Kridner 
wrote:

> https://beagleboard.org/pocket
>
> Trying to get a few things documented at https://github.com/
> beagleboard/pocketbeagle/wiki/FAQ, so feel free to start throwing out
> questions here, on IRC or on the github site.
>
>
> --
> https://beagleboard.org/about
>
> --
> 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/CA%2BT6QPmwE7Pri0_Jyx1Wp8n40rHJF_
> CziJj%2B0nceNkL%2B2RH24w%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/CALHSORp%2BALo-LqoQPyVKb9u_K6dwCGZ4nWK4xcJogEuFe-%3DF7g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RTC reset after Beaglebone boot

[William Hermans]

You could also set time on the second rtc during setup after updating the
time via nap date then just run a script at boot, and occasionally  (once a
day?) Using a system timer.

With the new fix Robert implemented.  .
Probably more hassle than it's worth , but it's  not that difficult, and it
works.

On Sep 14, 2017 10:03 AM, "Robert Nelson"  wrote:

> On Thu, Sep 14, 2017 at 11:50 AM, Robert Nelson 
> wrote:
> > On Thu, Sep 14, 2017 at 12:59 AM,   wrote:
> >> Hello,
> >> I have intefaced RTC DS1307 with Beaglbone. However, after the
> beaglebone
> >> boots up, its time is reset and RTC takes this reset time. Use of NTP
> would
> >> not be feasible since Beaglebone would be used in a remote location
> with no
> >> internet connection. What would be the solution to this issue ?
> >
> > As of this week, we have an easy solution. (using u-boot overlays of
> > course), the trick is the rtc "aliases", so that the ds1307 gets rtc0
> >
> > Seee either :
> >
> > https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-I2C1-MCP7940X-00A0.dts
> >
> > or:
> >
> > https://github.com/beagleboard/bb.org-overlays/
> blob/master/src/arm/BB-I2C2-PCF8523-00A0.dts
>
> and here's it working: (eth is disconnected)
>
> debian@beaglebone:~$ dmesg | grep rtc
> [1.594096] omap_rtc 44e3e000.rtc: already running
> [1.594335] omap_rtc 44e3e000.rtc: rtc core: registered 44e3e000.rtc as
> rtc1
> [1.776976] rtc-ds1307 1-0068: registered as rtc0
> [1.795900] rtc-ds1307 1-0068: setting system clock to 2017-09-14
> 17:01:12 UTC (1505408472)
>
> 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/CAOCHtYjZ3hbMsv7QUYw0A3TtKYr-
> dmEGENJa5U9kDzYomr4QBQ%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/CALHSORoB%3DGXS37v06fspJTfJvpuWhG7nixNcnMVM_FCNNTUXOg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] JTAG Debugging - 2 Code Composers on the Same Machine - One under Ubuntu - The Other under Windows

[William Hermans]

If you're serious about your work. Buy a cheap laptop, and install Ubuntu
on it.

On Wed, Aug 9, 2017 at 6:23 AM, Jeff Andich  wrote:

> Hi,
>
> We're not yet able to setup Ubuntu native on PC's at work, so we're using
> Ubuntu under VBOX.
>
> I'm attempting to do JTAG debugging via CCS 7.2 to the BB-X15/am572xEVM,
> but when I run CCS in debug mode under an Ubuntu/VirtualBox, CCS hangs.
> I'm able to view registers on the A15_0 core, but I haven't been able to
> successfully load u-boot-spl.bin built in CCS on Ubuntu.  When I load, CCS
> never comes back, and I haven't been able to specify the "load address" for
> the SPL.  From what I understand from reading an older version of TI's CCS
> wiki, JTAG debugging doesn't work well through a virtual machine.
>
> So I'm trying a strange approach:  2, CCS 7.2 installations on the same
> machine, 1 under the Ubuntu VM to build the SPL in Linux and another under
> Windows to manage the JTAG debugging process (e.g. load u-boot-spl.bin via
> JTAG, view memory, step, etc).  But I'm having some issues using a
> Windows/VBOX shared folder to contain the u-boot tree so that both the
> Windows and Ubuntu CCS's can look at the same tree/project.
>
> Has anyone on this forum successfully tried this kind of thing before or
> are there obvious reasons why this is a bad idea??
>
> I think the person in the following thread may have tried something like
> this??
>
> https://e2e.ti.com/support/development_tools/code_
> composer_studio/f/81/t/117880?tisearch=e2e-quicksearch&
> keymatch=virtualbox%20shared%20folder
>
> I may post up on TI/E2E, but we're working with the BB-X15 image, not the
> TI SDK image.  I'll try to annotate this thread with any useful information
> that's thrown our way.
>
> Thanks!!
>
> Jeff
>
> --
> 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/5f061151-4d0a-4633-b601-767a32a9c47b%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/CALHSORpdoi4VaLaJq1-QwU3GkyND-B%3Drr3qWy3yy%2Bz-fmqH4ZA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Reading analog in on the stretch (9.1) images

[William Hermans]

On Fri, Jul 28, 2017 at 3:18 PM, evilwulfie  wrote:

> Shame on him.
>

Just for the record,I did not write that. Ethon Hayon did back in 2012, I'm
thinking probably for the white. Same hardware though . . . I know this,
because I have a duplicate of his repo on my git, but it was an excellent
learning tool. However, no one in their right mind, is going to map the
whole hardware address space into memory, UNLESS they were doing exactly
what Ethon was doing in his project. Which was making a general purpose
"library" to access any GPIO pin, and ADC's.

SO when you see something like this:

map[(ADCSTEPCONFIG1-MMAP_OFFSET)/4] = 0x00<<19 | ADC_AVG8 | ADC_SW_ONESHOT;
Versus
map[(ADCSTEPCONFIG1-MMAP_OFFSET)/4] = 0x00<<19 | ADC_AVG16;

Obvious copy paste ripoff.

Anyway I'm not saying no one can use Ethon's code, I'm saying if you're
obviously copy pasting code from his repo, you need to give him credit for
it. No matter how much you butcher / move stuff around.

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

Re: [beagleboard] Reading analog in on the stretch (9.1) images

[William Hermans]

On Fri, Jul 28, 2017 at 2:55 PM, Robert Nelson 
wrote:

> On Fri, Jul 28, 2017 at 4:40 PM, Mark A. Yoder 
> wrote:
> > How do I read AIN on the latest images?  I don't know where to find it in
> > /sys/
>
> Hi Mark,
>
> This is with the Blue right?
>
> James' got the ADC tied up in mmap for the Robotic's cape library..
>
> https://github.com/StrawsonDesign/Robotics_Cape_Installer/blob/master/
> libraries/mmap/rc_mmap_gpio_adc.c
>
> We need to convert his library to use libiio, then we can just enable
> the ADC's as an iio device and share usage with the library..
>
> https://analogdevicesinc.github.io/libiio/
>
> Regards,
>

That's just swell, as Strawson didn't write that code either, and gave no
attribution to whom did.
https://github.com/wphermans/BeagleBone-GPIO/blob/master/src/gpio.c

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

Re: [beagleboard] Re: RTC's SDA and SCL Resistors

[William Hermans]

Well, rtc0 is most likely the on AM335x on die real time clock, which will
not persist time across reboots.

On Thu, Jul 27, 2017 at 7:54 PM, William B <wbbena...@gmail.com> wrote:

> Finally I got ... the last hint from William Hermans indicated me
> something about the device name, which could be "rtcX", which made me
> execute: "ls -la /dev/rtc*":
>
> root@beaglebone:~# ls -la /dev/rtc*
> lrwxrwxrwx 1 root root  4 May 21  2016 /dev/rtc -> rtc0
> crw--- 1 root root 254, 0 May 21  2016 /dev/rtc0
>
> 1) Replace "rtc1" with "rtc0" in the commands and everything works! (the
> system date and time were already correct):
>
> hwclock -w -f /dev/rtc0
>
> 2) To test if it worked and if the date and time were actually adjusted, I
> changed the system time, restarted the BBB and disconnected it from the
> internet to ensure the date and time would not be auto-tuned. After
> restarting it, I checked if the system time was still wrong and then read
> the RTC time (which must be correct!).
>
> hwclock -r -f /dev/rtc0
>
> It works!!! RTC date and time were correct.
>
> I don't even know how to thank everyone for their help. It should be
> simple to solve this problem, but it takes a lot of time, especially for
> those who don't have experience like me.
>
> Thank you very much!
>
>
>
>
> --
> 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/9c2b0a36-e70d-4fec-a904-6a0f6b5e0a49%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/9c2b0a36-e70d-4fec-a904-6a0f6b5e0a49%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CALHSORrnv9o8x6kTfvKJpXCkQNQOUNKz3eN2Cf9syXOibW3%2B9A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RTC's SDA and SCL Resistors

[William Hermans]

William,

Also to save you from future grief. Make sure you load the proper drivers
for your hardware,then if you're going to write your own software to read
from the RTC. Use /dev/rtcx( probably /dev/rtc1 ), and do not try to read
directly from the RTC over I2C. Trust me . . .

On Thu, Jul 27, 2017 at 4:46 PM, William Hermans <yyrk...@gmail.com> wrote:

>
>
> On Thu, Jul 27, 2017 at 4:24 PM, William B <wbbena...@gmail.com> wrote:
>
>> Is there any other difference in this latest version of Debian? I'm
>> following a tutorial below, but the command "hwclock -r -f /dev/rtc1" is
>> indicating failure to communicate with the new device:
>>
>> *TUTORIAL*:
>> https://learn.adafruit.com/adding-a-real-time-clock-to-beagl
>> ebone-black/set-rtc-time
>>
>> *ERROR*:
>> root@beaglebone:~# hwclock -r -f /dev/rtc1
>> hwclock: Cannot access the Hardware Clock via any known method.
>>
>> *DEVICES*:
>> root@beaglebone:/# ls -la /sys/bus/i2c/devices
>> total 0
>> drwxr-xr-x 2 root root 0 Jul 27 20:19 .
>> drwxr-xr-x 4 root root 0 Jul 27 20:19 ..
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0024 ->
>> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0034 ->
>> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0034
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0050 ->
>> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0070 ->
>> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0070
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0054 ->
>> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0054
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0055 ->
>> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0055
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0056 ->
>> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0056
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0057 ->
>> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0057
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-0 ->
>> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-1 ->
>> ../../../devices/platform/ocp/4802a000.i2c/i2c-1
>> lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-2 ->
>> ../../../devices/platform/ocp/4819c000.i2c/i2c-2
>>
>>
> You have to write to the RTC before you can read from it. Something that
> guide confuses . . . So actually the first steps you need to take is like
> this:
> root@wgd:~# apt-get install ntpdate
> root@wgd:~# ntpdate pool.ntp.org
> 27 Jul 16:39:29 ntpdate[1903]: adjust time server 199.223.248.101 offset
> 0.004123 sec
>
> Then if it's important to be on the right timezone . . .
> ( optional )
> root@wgd:~# dpkg-reconfigure tzdata
>
> Current default time zone: 'America/Phoenix'
> Local time is now:  Thu Jul 27 16:40:54 MST 2017.
> Universal Time is now:  Thu Jul 27 23:40:54 UTC 2017.
>
> Then you can write to the RTC:
> root@wgd:~# hwclock -w -f /dev/rtc1
>
> So what all this does is update the system time, configures the timezone,
> so that system time can be written to the real time clock. You could in
> fact just write to the real time clock without doing all the above. But the
> RTC will not be accurate.
>
> Now we should be able to read from the RTC.
> root@wgd:~# hwclock -r -f /dev/rtc1
> Thu Jul 27 16:45:41 2017  -0.646341 seconds
>
>
>

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

Re: [beagleboard] Re: RTC's SDA and SCL Resistors

[William Hermans]

On Thu, Jul 27, 2017 at 4:24 PM, William B  wrote:

> Is there any other difference in this latest version of Debian? I'm
> following a tutorial below, but the command "hwclock -r -f /dev/rtc1" is
> indicating failure to communicate with the new device:
>
> *TUTORIAL*:
> https://learn.adafruit.com/adding-a-real-time-clock-to-
> beaglebone-black/set-rtc-time
>
> *ERROR*:
> root@beaglebone:~# hwclock -r -f /dev/rtc1
> hwclock: Cannot access the Hardware Clock via any known method.
>
> *DEVICES*:
> root@beaglebone:/# ls -la /sys/bus/i2c/devices
> total 0
> drwxr-xr-x 2 root root 0 Jul 27 20:19 .
> drwxr-xr-x 4 root root 0 Jul 27 20:19 ..
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0024 ->
> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0024
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0034 ->
> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0034
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0050 ->
> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0050
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 0-0070 ->
> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0/0-0070
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0054 ->
> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0054
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0055 ->
> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0055
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0056 ->
> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0056
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 2-0057 ->
> ../../../devices/platform/ocp/4819c000.i2c/i2c-2/2-0057
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-0 ->
> ../../../devices/platform/ocp/44e0b000.i2c/i2c-0
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-1 ->
> ../../../devices/platform/ocp/4802a000.i2c/i2c-1
> lrwxrwxrwx 1 root root 0 Jul 27 20:19 i2c-2 ->
> ../../../devices/platform/ocp/4819c000.i2c/i2c-2
>
>
You have to write to the RTC before you can read from it. Something that
guide confuses . . . So actually the first steps you need to take is like
this:
root@wgd:~# apt-get install ntpdate
root@wgd:~# ntpdate pool.ntp.org
27 Jul 16:39:29 ntpdate[1903]: adjust time server 199.223.248.101 offset
0.004123 sec

Then if it's important to be on the right timezone . . .
( optional )
root@wgd:~# dpkg-reconfigure tzdata

Current default time zone: 'America/Phoenix'
Local time is now:  Thu Jul 27 16:40:54 MST 2017.
Universal Time is now:  Thu Jul 27 23:40:54 UTC 2017.

Then you can write to the RTC:
root@wgd:~# hwclock -w -f /dev/rtc1

So what all this does is update the system time, configures the timezone,
so that system time can be written to the real time clock. You could in
fact just write to the real time clock without doing all the above. But the
RTC will not be accurate.

Now we should be able to read from the RTC.
root@wgd:~# hwclock -r -f /dev/rtc1
Thu Jul 27 16:45:41 2017  -0.646341 seconds

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

Re: [beagleboard] recommendation for a symbolic debugger

[William Hermans]

On Thu, Jul 27, 2017 at 4:13 PM, William Hermans <yyrk...@gmail.com> wrote:

> This is probably the best guide you're going to find on the subject.
>
> https://www.youtube.com/watch?v=T9yFyWsyyGk
>
> Never used it myself( I do not cross compile ), but I'm confident DR
> Molly's instructions work.
>

Just in case it's not clear, R Molly shows how to setup remote debugging
towards the end I think. Been a while since I've watched this.

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

Re: [beagleboard] recommendation for a symbolic debugger

[William Hermans]

This is probably the best guide you're going to find on the subject.

https://www.youtube.com/watch?v=T9yFyWsyyGk

Never used it myself( I do not cross compile ), but I'm confident DR
Molly's instructions work.

-- 
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/CALHSORrj%3D7YCkk7f0ipJ2QyQ1P%3DUBRtT-h-4qrXuTopcLMnbOA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: RTC's SDA and SCL Resistors

[William Hermans]

On Thu, Jul 27, 2017 at 3:02 PM, William B <wbbena...@gmail.com> wrote:

> *Grahan:*
> You're 100% correct. Running "i2cdetect -y -r 2" instead of "1" at the
> end, it detected the RTC at address 0x68, as we can see in the available
> tutorials.
> Answering your question, I'm using the latest available Debian release
> (bone-debian-8.8-iot-armhf-2017-07-01-4gb.img) available here:
> https://rcn-ee.net/rootfs/bb.org/testing/2017-07-01/iot/
>
> *William Hermans: *
> When I run the command "i2cdetect -l", I get this information:
>
> root@beaglebone:~# i2cdetect -l
> i2c-0   i2c OMAP I2C adapterI2C adapter
> i2c-1   i2c OMAP I2C adapterI2C adapter
> i2c-2   i2c OMAP I2C adapterI2C adapter
>
>
> Now I can continue with the process normally and as soon as it works I
> report here.
>
> Thank you again!!!
>

Sounds about right . ..
root@wgd:~# cat /sys/bus/i2c/devices/2-0068/name
ds3232

Funny, I'm actually using an i2c RTC, forgot, and confused the temp sensor
I'm using over one wire. By the way, the DS3232 is also an accurate RTC,
but it does cost like $8.xx per. So not exactly cheap.

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

Re: [beagleboard] Re: RTC's SDA and SCL Resistors

[William Hermans]

It's not so much the debian version, as it is the kernel. kernel 3.8.x is
different from kernel 4.x. The easiest way to see what is attached it this:
root@wgd:~# i2cdetect -l
i2c-0   i2c OMAP I2C adapterI2C adapter
i2c-1   i2c OMAP I2C adapterI2C adapter
i2c-2   i2c OMAP I2C adapterI2C adapter

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

Re: [beagleboard] Re: RTC's SDA and SCL Resistors

[William Hermans]

On Thu, Jul 27, 2017 at 1:24 PM, William B  wrote:

> Hi!
> I bought the I2C logic converter 3.3V => 5v and I've connected the RTC to
> the BBB, but running "i2cdetect -y -r 1" doesn't find the RTC device. I've
> checked the wiring of the connections and I repeated the process a few
> times, but it doesn't detect the RTC.
>
> Any suggestion?
>

#1 You're sure you're connected to I2C-1 ?
#2 Did you load the device tree to get I2C-1 active ? It's not enabled by
default.

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

Re: [beagleboard] Battery

[William Hermans]

On Thu, Jul 13, 2017 at 1:35 PM, Robert Nelson 
wrote:

> On Thu, Jul 13, 2017 at 3:26 PM, Sri Ram  wrote:
> >
> > Hi,
> >
> > Is 3S battery compatible with Beaglebone blue?
>
> no, 2s only..
>
> https://github.com/beagleboard/beaglebone-blue/wiki/Accessories#Batteries
>
> Regards,
>

So here's the problem.
https://github.com/beagleboard/beaglebone-blue/blob/master/docs/BeagleBone_Blue_ShortSpec.pdf

*Page 3 states:*

> e. Power management:
> i. TPS65217C PMIC is used along with a separate LDO to provide power to the
> system (Integrated in the OSD3358)
> ii. 2 cell (2S) LiPo battery charger (powered by 9 – 18VDC DC Jack)
>

The problem is this. I think I understand  what the documentation is trying
to say, but this can be misleading. The voltage should be left out of the
battery "section" and perhaps mention that the system must be powered by
the DC jack. Because 2s batteries are 7.4v nominal, and fully charged 2s
batteries are 8.4v

You see what I'm getting at ? When you include the DC jack voltage into the
battery spec section, you're confusing the issue, and almost making the
documentation contradictory. e.g. it almost makes it seem like a 3s, or
maybe even a 4s pack would work.

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

Re: [beagleboard] Re: spi / shiftout.js in 2017-03-19 image

[William Hermans]

On Tue, Jul 11, 2017 at 8:17 PM, William Hermans <yyrk...@gmail.com> wrote:

> SPI is notoriously finicky when it comes to high speed, and noise. Since
> I'm not an EE, I could not say much more than that. Typically though, from
> what I understand, traces can not be very long.
>

Additionally, this could very well be a Nodejs bottleneck. I've personally
experienced first hand how slow Nodejs really is when working with fast
moving code. I notice the title "shiftout.js" but you're also talking about
C too. So maybe you're using a hybrid of the two ? A bit confusing, but
maybe some clarity on the subject is deserved ?

Using my own  javascript library, which pretty much just encapsulates the
sysfs file entries. When toggling GPIO, I've noticed it peters off at about
1Khz, or slightly less. That's just using a simple XOR binary operation.
Arguably, using /dev/mem/ and mmap() would be faster, but the speed of
scripting language code is alway going ot be a bottle neck. First, because
it's an interpreted language, and second, because the "binary" size is huge
compared to something like C. It's going ot be a lot slower.

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

Re: [beagleboard] Re: spi / shiftout.js in 2017-03-19 image

[William Hermans]

SPI is notoriously finicky when it comes to high speed, and noise. Since
I'm not an EE, I could not say much more than that. Typically though, from
what I understand, traces can not be very long.

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

Re: [beagleboard] Re: Windows 10 Bone_D64.exe Failing

[William Hermans]

Well, this is like a 2 year old post . . . Let me just say this. I'm
running Windows 10 pro on a Lenovo Thinkpad, and I happened to have a BBG
plugged into a USB 3.0 port off this laptop for power( using ethernet for
networking ), and Windows update automatically installed the NDIS driver
for it the update after . . . So, I have not used it, but no problems with
it installing at all. Also, I did not run the Bone_D64 installer either . .
.

On Tue, Jul 11, 2017 at 6:52 PM, Nathan Holder 
wrote:

> I had the same issue, I disabled signature requirement for drivers.
>
> On Wednesday, August 12, 2015 at 11:13:13 PM UTC-4, mscleavite wrote:
>>
>> I have just upgraded to Windows 10 on a machine that I have not
>> previously connected my BBB to.  I had success on other windows 8 machines
>> as well as SSHing using Putty.  I have spent SOME time searching forums and
>> not finding much at all on Windows 10.  During the install of the
>> Bone_D64.exe, the driver the status returned on all the drivers is "Install
>> Failed".  Let the flaming begin.  Or hopefully there is someone out
>> there that has encountered and concurred this.
>>
> --
> 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/a77d0884-5748-4362-aa94-368ee4381609%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/CALHSORo9MO8f2DwNzPPaTi%3D3%3DUbrbG%2B3VGj%3D2oSjHXRxfHMcrA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] How to protect scripts and codes?

[William Hermans]

What Robert said. There is nothing you can write code wise that can not be
done by someone else.

On Fri, Jul 7, 2017 at 8:25 PM, Robert Nelson 
wrote:

> On Fri, Jul 7, 2017 at 3:27 PM,   wrote:
> > Hi everyone!
> > How can I protect my scripts and nodejs codes on my Beaglebone? Example:
> > when I program and sell a Beaglebone to anyone, It's possible someone
> wants
> > to copy all scripts and codes. How to protect it?
>
> The money isn't in the scripts, it's in the support of the scripts and
> the infrastructure the scripts utilize..
>
> 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/CAOCHtYj%3D0SjyXoproNd3OzZf2CE5jC5-7%
> 3D-OXjGUOMAX%3DhrqFg%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/CALHSORokg%2B1rdM2CxLs0pHjieF8Q1ggE%3DnQTWRX_5%3DGkd14Kww%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] spi / shiftout.js in 2017-03-19 image

[William Hermans]

SO just glancing at the code here:
https://github.com/derekmolloy/exploringBB/blob/master/chp08/spi/spi595Example/spi595.c

I notice in fact he does have the path hard coded for the device: #define
SPI_PATH "/dev/spidev1.0"

So, after checking to make sure the spidev kernel module has loaded through
your overlay files, and in fact it's configured correctly for this kernel.
I'd double check the above path is actually still pointing to the correct
hardware SPI module you're trying to use.

On Fri, Jul 7, 2017 at 4:38 PM, William Hermans <yyrk...@gmail.com> wrote:

> SO Derrek's book is based on kernel 3.8.x where as you're now using a 4.x
> kernel. Chances are very likely you'll need to chance a few things in
> relation to SPI. NO hands on with SPI on the beaglebone yet personally. But
> first, you're going need to make sure your overlay file is correct for this
> kernel.  Also, file pathing for hardware has changed too. So unless you've
> adjusted the code to work with this kernel, it likely will not work.
>
> Can you show us the output of the lsmod command? First it would be good to
> make sure the SPIdev driver is actually loaded.
>

-- 
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/CALHSORpMeifTxj%2BnSPT_50cGjQEzZVg3zvHL6J%3DUmUa%2BL_5U6g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] spi / shiftout.js in 2017-03-19 image

[William Hermans]

SO Derrek's book is based on kernel 3.8.x where as you're now using a 4.x
kernel. Chances are very likely you'll need to chance a few things in
relation to SPI. NO hands on with SPI on the beaglebone yet personally. But
first, you're going need to make sure your overlay file is correct for this
kernel.  Also, file pathing for hardware has changed too. So unless you've
adjusted the code to work with this kernel, it likely will not work.

Can you show us the output of the lsmod command? First it would be good to
make sure the SPIdev driver is actually loaded.

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

Re: [beagleboard] BBGW crash

[William Hermans]

Well, considering the wireless beaglebone require a 4.4+ kernel, and 4.4+
kernels were not developed for this platform until the Jessie image was
used . . . Yes you need to use Jessie. I suppose you could *try* compiling
your own version of of the kernel for Wheezy. . . but god that would be a
nightmare.

On Mon, Jul 3, 2017 at 2:57 PM, Sebastián Sáez <otra...@gmail.com> wrote:

> Williams, I already did the update, apparently it's just for Jessie
>
> https://github.com/rcn-ee/repos/tree/master/seeed-wificonfig-installer
>
> On Monday, July 3, 2017 at 5:36:14 PM UTC-4, William Hermans wrote:
>>
>> sudo apt-get update <--- before apt-get install
>>
>> On Mon, Jul 3, 2017 at 2:09 PM, Sebastián Sáez <otr...@gmail.com> wrote:
>>
>>> Hi Robert, I can't find wifidog package for Stretch image.
>>>
>>> image test: bone-debian-9.0-iot-armhf-2017-06-25-4gb.img
>>>
>>>
>>> debian@beaglebone:~$ sudo apt install seeed-wificonfig-installer
>>> wifidog-gateway
>>> Reading package lists... Done
>>> Building dependency tree
>>> Reading state information... Done
>>> E: Unable to locate package seeed-wificonfig-installer
>>> E: Unable to locate package wifidog-gateway
>>>
>>>
>>>
>>> On Thursday, June 29, 2017 at 5:00:26 PM UTC-4, RobertCNelson wrote:
>>>
>>>> On Thu, Jun 29, 2017 at 3:49 PM, Sebastián Sáez <otr...@gmail.com>
>>>> wrote:
>>>> > Good tips Greg, thank you.
>>>> > I would like to use one of these IOT images but I need wifidog so my
>>>> users
>>>> > can configure the home wifi.
>>>> >
>>>> > I tried installing wifidog with these instructions without luck
>>>> > Https://github.com/Pillar1989/wifidog-server
>>>>
>>>> sudo apt update
>>>> sudo apt install seeed-wificonfig-installer wifidog-gateway
>>>>
>>>> (that's what converts an iot image to a seeed-iot image)
>>>>
>>>> > Is there any alternative to wifidog ?, my users do not know linux how
>>>> to use
>>>> > connmanctl
>>>>
>>>> I'd like to find a "simpler" nodejs app to talk from a web-browser and
>>>> connman..
>>>>
>>>> >
>>>> > Robert, I have another question for you,
>>>> > Is it convenient to remotely update the kernel on a machine that I do
>>>> not
>>>> > have physical access, is it possible to block it?
>>>>
>>>> I do all the time. ;)
>>>>
>>>> but i have a network pwr relay i can ping to reset the board's power..
>>>>
>>>> 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...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/beagleboard/9bc9c3e6-1924-4128-b0ff-cdc636ea9acc%40googlegroups.com
>>> <https://groups.google.com/d/msgid/beagleboard/9bc9c3e6-1924-4128-b0ff-cdc636ea9acc%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> 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/93ba0f40-fc88-45dc-825a-828498a1d9bb%40googlegroups.com
> <https://groups.google.com/d/msgid/beagleboard/93ba0f40-fc88-45dc-825a-828498a1d9bb%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CALHSORoHCbXEkjNwe1L%3DWXkNTd80f%3DoQM5mCobHZTNg45XLZyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBGW crash

[William Hermans]

sudo apt-get update <--- before apt-get install

On Mon, Jul 3, 2017 at 2:09 PM, Sebastián Sáez  wrote:

> Hi Robert, I can't find wifidog package for Stretch image.
>
> image test: bone-debian-9.0-iot-armhf-2017-06-25-4gb.img
>
>
> debian@beaglebone:~$ sudo apt install seeed-wificonfig-installer
> wifidog-gateway
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> E: Unable to locate package seeed-wificonfig-installer
> E: Unable to locate package wifidog-gateway
>
>
>
> On Thursday, June 29, 2017 at 5:00:26 PM UTC-4, RobertCNelson wrote:
>
>> On Thu, Jun 29, 2017 at 3:49 PM, Sebastián Sáez 
>> wrote:
>> > Good tips Greg, thank you.
>> > I would like to use one of these IOT images but I need wifidog so my
>> users
>> > can configure the home wifi.
>> >
>> > I tried installing wifidog with these instructions without luck
>> > Https://github.com/Pillar1989/wifidog-server
>>
>> sudo apt update
>> sudo apt install seeed-wificonfig-installer wifidog-gateway
>>
>> (that's what converts an iot image to a seeed-iot image)
>>
>> > Is there any alternative to wifidog ?, my users do not know linux how
>> to use
>> > connmanctl
>>
>> I'd like to find a "simpler" nodejs app to talk from a web-browser and
>> connman..
>>
>> >
>> > Robert, I have another question for you,
>> > Is it convenient to remotely update the kernel on a machine that I do
>> not
>> > have physical access, is it possible to block it?
>>
>> I do all the time. ;)
>>
>> but i have a network pwr relay i can ping to reset the board's power..
>>
>> 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/9bc9c3e6-1924-4128-b0ff-cdc636ea9acc%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/CALHSORoAunsztGsj9hF_m4G7RS0%3DqXruDvne_N63yn8A6S%2Bwiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: DPRAM interface with BBB

[William Hermans]

I'm kind of late to the post here but I remember Tom King doing some work
maybe for a cape years ago, So, I did a quick search, and found this post.
Maybe some useful information for you ?
https://groups.google.com/forum/#!category-topic/beagleboard/gpmc/QENqyIYTlO0

On Fri, Jun 30, 2017 at 9:47 PM, sajeevan k  wrote:

> Hi Gerald and Jason,
>
> Thank You for the reply.
> I got doubt because GPMC_AX lines were utilized for some other purposes.
> So first I thought that BBB is not designed to have external parallel
> interface. But later I found that GPMC_AD0-AD16 are  freely available and
> with ALE signal, Data and Address bus can be multiplexed.
>
>
>
>
> Also I think, even though AD0-AD7 lines are connected to MMC1, since
> Address, Data lines may be connected to many devices, and one particular
> device will be selected only when its CS signal is active, there won't be
> any issues.
>
>
>
> Thank You very much.
>
>
> Thanks & Regards,
> Sajeevan.K
>
>
> On Friday, June 30, 2017 at 5:56:23 PM UTC+5:30, Jason Kridner wrote:
>>
>> There is a peripheral called the GPMC -- general purpose memory
>> controller -- which is pretty good at SRAM-style interfaces.
>>
>> On Jun 30, 2017, at 7:46 AM, Gerald Coley  wrote:
>>
>> It is feasible.
>>
>>
>>
>> Gerald
>>
>>
>>
>> *From:* beagl...@googlegroups.com [mailto:be...@googlegroups.com] *On
>> Behalf Of *sajeevan k
>> *Sent:* Thursday, June 29, 2017 11:48 PM
>> *To:* BeagleBoard 
>> *Subject:* [beagleboard] Re: DPRAM interface with BBB
>>
>>
>>
>> Hi all,
>>
>> Any comments about the feasibility of DPRAM interface with BeagleBone
>> Black will be highly appreciated? Please...
>>
>>
>> Thanks & Regards,
>> Sajeevan.K
>>
>> On Tuesday, June 27, 2017 at 1:59:51 PM UTC+5:30, sajeevan k wrote:
>>
>> Hi all,
>>
>>
>>
>> Is it possible to interface an Asynchronous DPRAM (with 16 address lines
>> and 16 data lines) with BBB?
>>
>>
>>
>> Is there any block diagram (circuit diagram), which shows the
>> connections, available?
>>
>>
>>
>> Can we use GPMC_ADO-GPMC-AD15 pins as Address and Data mux pins with
>> GPMC_ADVN_ALE?
>>
>>
>>
>> Also I think GPMC_Ax pins are not required, since we can use Address-Data
>> multiplexing with ALE signal.
>>
>>
>>
>> I think all the required pins are coming out in P8 connector.
>>
>> 1) GPMC_ADO-GPMC-AD15
>>
>> 2) GPMC_ADVN_ALE
>>
>> 3) GPMC_WEN
>>
>> 4) GPMC_OEN_REN
>>
>> 5) GPMC_BE1N
>>
>> 6) GPMC_CSN0
>>
>>
>>
>> But GMC_AD0-GPMC-AD7 are also connected to MMC1_D0 to MMC1_D7. Will this
>> cause any problem to the functoining of DPRAM? Or will the DPRAM
>> functioning cause any problem to MMC1.
>>
>>
>>
>> Have anybody interfaced DPRAM with BBB? Please share your experience.
>>
>>
>>
>> Thanks and Regards,
>>
>> Sajeevan.K
>>
>> --
>> 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...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/d01d7261-4cad-49b1-965f-4bc3a0e847c7%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...@googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/beagleboard/4bb8d3999eb34e8d8fff57fd094f9a3b%
>> 40winhexbeus11.winus.mail
>> 
>> .
>> 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/3dea8e8f-98c6-492e-ac15-df96fe45b56a%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 

Re: [beagleboard] How to enable USB power with u-boot?

[William Hermans]

On Fri, Jun 30, 2017 at 9:04 PM, Sergey Manucharian  wrote:

> Oh, thanks, William, I was inspired doing this by your post!
>

Oh, cool ! Glad someone reads my stuff now and then ;)

>
> The problem is that "usb start" starts *u-boot*'s USB subsystem, it
> (probably) has nothing to do with the CPU.
> You explicitly mentioned that used a USB HDD with external power supply,
> but I'm trying to boot off a USB flash drive. The CPU doesn't provide USB
> power at early stage. If I provide power from an external source,
> everything works fine.
>

Right so in that case, I explicitly mentioned using external power for a
hard drive. As many hard drives need at least 1-3A when spinning up, then
typically for a 3.5" HDD 1A after that. I just assumed that flash stick
would / should work, because most of them are pulling less than 500mA, or
is what I'd guess at any rate. However, you tested it seems, where I did
not.

>
> The latest u-boot supports loading overlays, I'm not sure whether it's
> possible to load an overlays with the correct configuration of that pin and
> *then* load kernel and stuff from USB flash drive.
>

So I do not know all the specifics, and quite honestly Robert would
probably know better than I. But *maybe* there is a way you can create a
new overlay, based on the board file, to get the USB power up. A lot of
overlays are already set in the board file by default, or more specifically
references to hardware are in the board file, and in some cases all you
need to do is write an overlay that targets the hardware in question, and
provide status="okay". With that said. . . I'm not 100% sure how soon the
overlays get loaded. As in if they're actually loaded in uboot, or if
they're somehow loaded just prior, or simotaneously when the kernel is
loaded via cmdline options.

It's a really interesting problem to solve, one that I'd like to figure out
myself - even.  If only I were not already busy with a ton of things at
work :/ Which, yeah, I'll probably be spending part of my weekend doing too
. . .

-- 
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/CALHSORpS-ATaFN8Dx-Gytn-RWF9oiyXUoHkx_8prmt2Ajt607g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] RE: Um...My Temp in F Degrees is the Same as the C Degrees/Dang!

[William Hermans]

On Fri, Jun 30, 2017 at 8:33 PM, Mala Dies  wrote:

> Mr. Rob,
>
> Why would I use the value 4096.0?
>
> Seth
>
> P.S. I have tried to suit the software to suit my needs and I keep coming
> up empty. I will try this value and I will get back to you.
>

Do you know anything about the hardware you're trying to use ? the onboard
ADC's report a value of 0-4095(4096 total ) depending on how much voltage
they're seeing at the pins. 1.8 would be fore the absolute maximum value in
voltage the ADC can read before failure. The reason why 4096.0 was probably
mentioned is that would indicate a float value, which strickly speaking is
not really necessary in Javascript. But in C, sometimes, it's necessary.

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

Re: [beagleboard] How to enable USB power with u-boot?

[William Hermans]

On Fri, Jun 30, 2017 at 7:50 PM, Sergey Manucharian  wrote:

> From this thread https://e2e.ti.com/support/arm/sitara_arm/f/791/t/270060:
> Modifying bit 0 of 8 bit register address 0x47401C60 it switch on/off
> USB1_DRVVBUS pin
>

But I don't think you have to do all that. Read my post from nearly 4 years
ago here: http://www.embeddedhobbyist.com/2013/07/beaglebone-black-usb-boot/

Scroll down where I talk about uEnv.txt. "usb start" should initiate power,
and the driver. Note that I'm calling it first before loading files over
USB. If you require in depth details, you'll have to read through the
source code. But I might be able to answer *some* questions. I'm by no
means a uboot expert.

-- 
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/CALHSORr9Me_7hnr%2BU%3Dmciv-RUi-Qu4YVG-MatjZJwAiYPsKGmw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Possible to remove eeprom?

[William Hermans]

https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-Bootloader:U-Boot
Link to the bootloader source there. Along with the whole build process.

Then I do believe what you're asking about removing the eeprom check is
possible. Seems you have already done that, but I do remember some
discussion about that being possible. However Robert would have to confirm
that is possible on the Linux side of things. That, I'm not sure of.

On Wed, Jun 28, 2017 at 3:05 PM,  wrote:

> Hello,
>
> I know this thread is a bit stale but I could use some assistance. So I
> built I customboard referenced about the beaglebone black wireless. I am
> also looking for help bypassing the eeprom check in u-boot. I was able to
> successfully build and bypass the eeprom check using your tutorial here.
>
> https://eewiki.net/display/linuxonarm/BeagleBone+Black
>
> I would like to generate an SD card image with the jessie iot image found
> on beaglebone.org. Is it possible to use the same MLO and u-boot
> generated from the above tutorial? Is not, is the source for the u-boot
> used in the jessie iot image available?
>
> Thanks in advance!
>
> On Friday, December 16, 2016 at 7:38:14 PM UTC-8, RobertCNelson wrote:
>>
>> On Fri, Dec 16, 2016 at 6:29 PM, ferdster  wrote:
>> > We have a custom board based on a BBB. It has the eeprom on it, but
>> we'd
>> > like to get rid of it.
>> >
>> > Initially, to bring up the board, we programmed the eeprom as a BBB.
>> Now we
>> > want to remove it. I patched it with:
>> > https://github.com/RobertCNelson/Bootloader-Builder/blob/
>> master/patches/v2016.03/0002-NFM-Production-eeprom-assume-
>> device-is-BeagleBone-Bl.patch
>> >
>> > Now it boots with an empty eeprom. I thought the patch would be enough,
>> but
>> > after removing the eeprom from the board, I get nothing at all on the
>> > console.
>> >
>> > Something must be failing very early on in u-boot for it not to print
>> > anything.
>>
>> Yeah, your going to have to dig deeper in u-boot, for beaglebone
>> clone's an eeprom on the i2c bus is expected..
>>
>> You'll need to disable all those calls..
>>
>> 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/12cb894b-447f-462d-897b-9e0d74801013%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/CALHSORpNhXZasghRydCyEQp2doAL7VnO0c69UK%2B7bAxDbqZ6%2Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

Missed a -o in there, but hopefully you get the point ;)

On Thu, Jun 29, 2017 at 10:36 AM, William Hermans <yyrk...@gmail.com> wrote:

>
> On Thu, Jun 29, 2017 at 10:12 AM, mzimmers <mzimm...@gmail.com> wrote:
>
>> Hey, William...thanks for the pointers. I actually do already have
>> cross-development working (for user space programs). I'm using Qt Creator,
>> and a Linaro toolchain and sysroot. I built Qt for the armhf in order to
>> get the right qmake.conf file, and I can cross-debug using gdbserver on the
>> BBB. So, I've got that going already.
>>
>> But, as you're aware, cross building for kernel stuff is more involved,
>> and I'm inclined to agree with you that I'm making this a bigger deal than
>> it is. I'm prepared to move on, though I'd really like to know why this
>> example program isn't working. But, as I mentioned, this isn't a BBB
>> problem, so I'm not going to pursue it here.
>>
>> Right. You want to know how much I personally cross compile ? Zero. When
> I was toying around with compiling my own kernel was about the only time.
> At one point I did setup the Linaro cross tool chain, with code::blocks(
> IDE ) on Windows and got that working. But IMHO time is much better spent
> learning how to compile natively, from the command line. Because that
> information can be used anywhere. Knowing your tool chain from the command
> line is a must in my opinion. After that, learning a build tool such as
> make is a must too. Quite honestly though, I hardly ever even use make.
> Most of my projects are modular in nature, and small applications that
> communicate with each other through files. Or other means like mqtt
> outbound to a server somewhere. So basically my whole process starts with
> writing the code then . . . $ gcc -Wall 
> 
>
> Keeping things modular and small makes life for me much easier . . .Not to
> be confused with kernel modules of course ;)
>

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

On Thu, Jun 29, 2017 at 10:12 AM, mzimmers  wrote:

> Hey, William...thanks for the pointers. I actually do already have
> cross-development working (for user space programs). I'm using Qt Creator,
> and a Linaro toolchain and sysroot. I built Qt for the armhf in order to
> get the right qmake.conf file, and I can cross-debug using gdbserver on the
> BBB. So, I've got that going already.
>
> But, as you're aware, cross building for kernel stuff is more involved,
> and I'm inclined to agree with you that I'm making this a bigger deal than
> it is. I'm prepared to move on, though I'd really like to know why this
> example program isn't working. But, as I mentioned, this isn't a BBB
> problem, so I'm not going to pursue it here.
>
> Right. You want to know how much I personally cross compile ? Zero. When I
was toying around with compiling my own kernel was about the only time. At
one point I did setup the Linaro cross tool chain, with code::blocks( IDE )
on Windows and got that working. But IMHO time is much better spent
learning how to compile natively, from the command line. Because that
information can be used anywhere. Knowing your tool chain from the command
line is a must in my opinion. After that, learning a build tool such as
make is a must too. Quite honestly though, I hardly ever even use make.
Most of my projects are modular in nature, and small applications that
communicate with each other through files. Or other means like mqtt
outbound to a server somewhere. So basically my whole process starts with
writing the code then . . . $ gcc -Wall 


Keeping things modular and small makes life for me much easier . . .Not to
be confused with kernel modules of course ;)

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

Ah, something I unintentionally left out. The arch you'll need is armhf.
Granted, I'm not 100% sure that even applies to the kernel, or kernel
modules.

On Thu, Jun 29, 2017 at 9:58 AM, William Hermans <yyrk...@gmail.com> wrote:

> Then later, once you understand native module development much better,
> you'll be able to apply that information towards cross compiling much
> easier. Just be aware, this is not an overnight sort of situation. It could
> take years to grasp, but if you apply yourself, it'll probably take a lot
> less time.
>
>
>

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

Then later, once you understand native module development much better,
you'll be able to apply that information towards cross compiling much
easier. Just be aware, this is not an overnight sort of situation. It could
take years to grasp, but if you apply yourself, it'll probably take a lot
less time.

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

mz,

You know what I'd do in your shoes ? I'd just setup a development sdcard
for your bb, and compile modules natively. on the bb. Much simpler, no
hassle, no pain in the butt. Compiling a kernel on a bb may take a few
days, but a kernel module should not take very long.

Another thing you should be aware of when it comes to DR Molloy's book. Is
that the information is dated, and not how one would go about doing things
with current versions of Debian. For instance, with Jessie there are some
mechanisms built in now. That allow for much easier cross compiling. With
that said, asking anyone on the group here to help you with that process,
would be asking too much. But suffice it to say, multi arch on Debian is
much better than with previous versions of debian. The best way to start
learning with that in my mind is to create, and use an x64 debian virtual
machine from something like virtual box. Then just start experimenting with
instructions off the web. Until you find a process that works.

Anyway, you just start getting your hands dirty, and experimenting. Then
things should eventually start working out. google "cross compile kernel
module deb" Then just start reading guides that only talk about armhf, and
Debian Jessie. Things to be aware of, is that you'll need to apt-get
install , and you'll need to be able to compile
those sources from your version of gcc ( gcc --version). The only
additional package you'll need to install on that image aside from the
kernel headers is build-essential. Unless you need something specific like
libusb-dev for USB development, or the like.

-- 
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/CALHSORoRG-hQjoXcJQ4cU1oLgQLp644nd%2Brq0nz%3DCThMUx_Ytg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] EduMIP BeagleBone Blue on the loose

[William Hermans]

On Thu, Jun 22, 2017 at 8:32 PM, Robert Nelson 
wrote:

>
>
> On Thu, Jun 22, 2017 at 8:28 PM, Mark A. Yoder 
> wrote:
>
>> I turned an EduMIP BeagleBone Blue loose near my laptop and where is what
>> happened.
>>
>>
>> 
>>
>> --Mark
>>
>
> That's close! Humanity was only 5 key rows away from the Blue hitting the
> enter key, thus initiating a robot revolution...
>
> Regards
>
> --
> Robert Nelson
> https://rcn-ee.com/
>

Looks like it did it's best to take out the screen though, to keep us form
seeing what it was up to.

-- 
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/CALHSORqjPhN-SZTmm_DQX%3DeJm%3DSN2_u%2B0va3Eby9rySeaC-rZw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

On Thu, Jun 22, 2017 at 12:54 PM, mzimmers  wrote:

> Hey, I'm open to any and all ideas. It seems so strange that I'm getting a
> seg fault in the client code, though...that does make me suspicious of the
> compiler version vs. the headers, etc.
>
> How do people go about debugging kernel code, anyway? I gather that gdb
> isn't much of an option. Do we just litter the code with printk statements
> like we did when we were freshmen in college?
>
> mz
>

Naw, theres a special way to compile a kernel that will allow it to be run
as though it's just another executable. This way, you can run the kernel on
top of the Linux you're already running in order to debug it.

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

Yeah, ok, seemed like the obvious question to ask, but maybe too obvious ;)

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

mzimmers, Which version of gcc are you using ?

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

On Wed, Jun 21, 2017 at 7:34 PM, mzimmers  wrote:

> Hi, William -
>
> I have no (current) interest in building my own kernel. I'm trying to do
> Dr. Molloy's tutorials because I want to learn about writing device drivers
> for Linux (you may recall an earlier discussion where you encouraged me to
> go this route in favor of doing bare-metal bit-banging). I'm just trying to
> get his program to work. I wasn't aware that I was doing anything in the
> kernel building area. (Still new to much of this stuff.)
>
> mz
>

Yeah ok, my bad. I think I misread your initial post. Where you mention
kernel MODULES and not just the kernel.

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

Re: [beagleboard] which "arch" subdirectory to use?

[William Hermans]

mzimmers, additionally, aside from getting hands on experience. Why do you
feel compelled to build your own kernel ? If it's for the learning process,
ok I get that. But if you need to build something in . . maybe, but  if
you're looking to build a driver module . . . you do not need to rebuild
the kernel for that.

On Wed, Jun 21, 2017 at 5:54 PM, William Hermans <yyrk...@gmail.com> wrote:

> Just in case you do not know already. https://eewiki.net/display/
> linuxonarm/BeagleBone+Black That guide is for the black, there is one for
> the white, but don't know if there is one for the blue, or any of the
> wireless variants.
>
> On Wed, Jun 21, 2017 at 5:52 PM, William Hermans <yyrk...@gmail.com>
> wrote:
>
>> mzimmers,
>>
>> You know, I tried a few different guides when building the kernel and
>> none of them worked until I found Robert's build guide( 4+ years ago ). In
>> your shoes, I would probably forget about trying to follow DR Molloy's book
>> in this case, and just use Robert's guide. Because no one is going to know
>> how to build a kernel for this hardware as well as 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/CALHSORrFfGCFGU7Fpb5TOSZXabhS3zb7b7gCiODNWKex%2Btoc%2BQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.