On Thu, 23 Apr 2015 20:02:03 -0400, you wrote:
inputs are not inputs are not inputs as far as loading goes.
if I connect an instrument with a 50 ohm impedance to a TTL/CMOS gate,
then it's going to see low at that gate input, even though they are
all inputs. Different logic series gates look lik
Hi,
I am using BB Black to work with a motion sensor through SPI.
By doing
*echo BB-SPIDEV0 > /sys/devices/bone_capemgr.9/slots*
I am able to get */dev/spidev1.0* and */dev/spidev1.1,* which are supposed
to be output and input PIN of SPI0 in mode0. I wire P9 pin 18 and 21, and
tested spidev_
dont you prototype your very first one and test it before you order
production boards ?
If you would have searched this forum for boot mode or you may have
found your issue.
test a proto first. the information is there for the reading.
On 4/23/2015 5:02 PM, Kenneth Martin wrote:
> If they cau
Those pins are the LCD pins also. Please read the tables for the pin outs
and you will see signals labeled LCD. That is why they wee brought out.
Sorry for the poorly written sentence. Sorry for your bad experience. I
would have been happy to review your design before you went to that expense.
I
If they cause the BBB to not boot, by hooking an input to them, I would
argue they should never have been brought out to the header, and that
examples of how to handle this sensitivity while still making use of the
header pins should be more readily available. The documentation on this
sensitiv
Don't get me started on that. Tried that for years and never could get it
through.
So, we are doing a custom BBB design for a customer, and it is there.
Gerald
On Thu, Apr 23, 2015 at 4:30 PM, William Hermans wrote:
> Well in our case ntpdate + ntp.pool.org works fine. Most of the time.
> But
Well in our case ntpdate + ntp.pool.org works fine. Most of the time. But
I've also thought about many external work arounds, which really renders my
gripe moot. An msp430g2553 for instance doesn't cost much more than an RTC,
and can serve multiple purposes . . .
On Thu, Apr 23, 2015 at 2:18 PM,
On Thu, Apr 23, 2015 at 4:14 PM, William Hermans wrote:
> The only real thing that bothers me that I can think of offhand. Is having
> an on-die RTC that effectively can not be used. However, there *are* both
> hardware, and software work arounds. Depending on how early you need the
> clock to be
The on die RTC has been rendered unusable. It has no clock. External RTC is
available.
Gerald
On Thu, Apr 23, 2015 at 4:14 PM, William Hermans wrote:
> The only real thing that bothers me that I can think of offhand. Is having
> an on-die RTC that effectively can not be used. However, there *ar
The only real thing that bothers me that I can think of offhand. Is having
an on-die RTC that effectively can not be used. However, there *are* both
hardware, and software work arounds. Depending on how early you need the
clock to be accurate.
Not even sure if that is listed as an errata item, but
Non of that has had much if any effect on any of our projects. Which my
buddy ( the EE in our projects ) read the errata prior to release. He
expressed some concerns early on, but in the end they have had no effect on
our projects.
On Thu, Apr 23, 2015 at 1:06 PM, wrote:
> I never meant to imply
On Thu, Apr 23, 2015 at 3:06 PM, wrote:
> I never meant to imply they "don't work", it really depends on your
> definition of "work".
> ...bottom line read the errata ..especially be wary of the words "no
> workarounds".
You realize, the errata list is pretty small right now.. But i
guarantee,
On Thu, Apr 23, 2015 at 3:56 PM, rh_ wrote:
> On Wed, 22 Apr 2015 13:25:26 -0500
> Robert Nelson wrote:
>
>> On Wed, Apr 22, 2015 at 3:58 AM,
>> wrote:
>> > Hi all.
>> > Is dtb-rebuilder
>> > git clone https://github.com/RobertCNelson/dtb-rebuilder
>> > and
>> > git checkout origin/3.19.x -b tmp
I never meant to imply they "don't work", it really depends on your
definition of "work".
...bottom line read the errata ..especially be wary of the words "no
workarounds".
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscrib
It's my understanding that you can access peripherals from the PRU. I can
do this by reading/writing the appropriate addresses in the L4_PER memory
map, correct?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Gr
Just as a note to those wondering . . .
We have two "early" A5A BBB's here. Both still working perfectly . . .
On Thu, Apr 23, 2015 at 7:59 AM, Gerald Coley
wrote:
> They are what are called X versions. As was the case on the BBB, these are
> the same devices as the production release versions.
>
> *(the PRUSS's can write anywhere in memory - they could be a significant
> security risk - for example changing some bytes loaded at PRUSS startup
> could be used to take over the BBB).*
Only if you're incompetent where system security is concerned.
On Thu, Apr 23, 2015 at 9:18 AM, Bit Pushe
Excellent write-up ... I knew there was a reason I liked Windows CE so
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 fr
ANY load can affect how they are read. These pins are already well loaded
as it is. If you want to use them, use a buffer to isolate them until after
the processor is running.
Gerald
On Thu, Apr 23, 2015 at 12:20 PM, Bit Pusher wrote:
> This is not clear as they are connected to other inputs w
Hello there,
I was wondering either it is possible to compile user applications for
BeagleBone Black, that require lprussdrv linker flag? So far I have copied
the libs:
libprussdrv.a
you are messing with the boot pins. its been stated here 100s of times
you cannot do anything to these pins before board boots.
check the BBB schematic and the using the bbb board guide.,
On 4/23/2015 9:09 AM, Bit Pusher wrote:
> I have found a reproducible boot freeze (on two boards); could some
We have been using the PRUSS's extensively on bone70; with mostly success,
but every so often, memory gets corrupted, and we have to reboot. This
behavior is aperiodic and we have not been able to track it down yet (the
PRUSS's can write anywhere in memory - they could be a significant security
I have found a reproducible boot freeze (on two boards); could someone else
possibly check; it's very easy to try.
No connections besides power plug and one (or two) wires from header P8 to
P9
Scenario 1: connect P8-43 to P9-30, plug in power, only power light comes
on and BBB does not boot up
S
Hello there,
I am following Derek Molloy's book on pru programming and I have run into a
problem. I have my user space c++ application build on a remote x86 linux
pc. I am using cross compiler there to deploy executables to the BeagleBone
Black. So far it was working great but it does not with p
They are what are called X versions. As was the case on the BBB, these are
the same devices as the production release versions.The same devices will
be used on the TI EVM.
All issues are listed in the process errata. Any issues that may be fixed
have HW workarounds already in the design.
Gerald
>
> One note of caution: If its like previous BB releases the early boards
> will probably contain processor "Engineering samples".
>
These are usually buggy early silicon. Actually the community is a great
outlet for TI to dump its engineering stock and still charge for it.
--
For more optio
Thank you for the replies. We will look closer at the GCC compiler, and
check out a copy of the "Exploring BeagleBone" - Rodney
On Tuesday, April 21, 2015 at 6:35:32 PM UTC-5, Graham wrote:
>
> Rodney:
>
> I highly recommend this book. The answers to all your questions with
> examples are eit
David Goodenough writes:
> searching on the net I think I may have found what you are using. It is not
> an AM2320, but rather an AM2321. This DOES have an I2C interface unlike
> the AM2320.
According to sellers who offer AM2320 (e.g. on AliExoress), it supports
both, I2C and Aosong's propriet
Hi Friends,
I am trying to display an image in a label, using QT - QImage.
The image does get displayed in the label , but there are no colors , I
have tried various images with different depths and formats (I am not
trying jpeg) , I tried with bmp & png formats.
The result is always the same
29 matches
Mail list logo
