I had to look up what such a letter would be.
I found http://howtowritealetter.net/letter-of-volatility.html
I'm not sure of the value as the detailed specifications are already public.
How would this be put to practical use? What liability are we opening ourselves
to?
> On Mar 3, 2017, at 9:
Special Computing routinely provides Letter of Volatility with our "NoLogo"
boards for commercial use and are treated as proprietary information. Our
customer tends to issue their own form letter for their vendors to fill
out. Letters of Volatility are used to assist in defining procedures to
safel
http://www.elinux.org/Beagleboard:BeagleBoneBlack#Terms_of_Use
Gerald
On Sat, Mar 4, 2017 at 5:38 AM, Bill Mar wrote:
> Special Computing routinely provides Letter of Volatility with our
> "NoLogo" boards for commercial use and are treated as proprietary
> information. Our customer tends to iss
On 3/3/2017 10:04 PM, ags wrote:
>
> 1) pin configuration ultimately boils down to two steps, for every pin (ball
> on
> the SoC): what is it internally connected to (and operationally configured),
> and
> separately, controlling that function once connected.
Yes. The physical pin is connect
On Saturday, March 4, 2017 at 5:56:04 AM UTC-8, Charles Steinkuehler wrote:
>
> On 3/3/2017 10:04 PM, ags wrote:
> ...
> > *I haven't tried it (don't want to damage hardware) but does this mean
> that
> > directly poking at the GPIO registers from userspace with /dev/mem &
> mmap()
> > won't
@RobertCNelson
I found and followed (mostly) the instructions you previously provided
here: https://groups.google.com/forum/#!msg/beagleboard/l59Dx8ygxNg/GvIzOJSzDAAJ
and I am now able to mmap the PRU memory and read/write to it. Loading PRU
instructions comes next, and then finally pinmuxing an
Hello Robert,
On Sun, Feb 26, 2017 at 4:23 PM, Robert Nelson
wrote:
>
> try:
>
> sudo depmod -a
> sudo modprobe mt7601Usta
>
> then dmesg so we can see what happened..
>
>
I'm getting back to this. I now have an official UWN100. I have a fresh
install, with 7601 installed via aptitude. I'm atte
Hi All,
I am trying to read a second I2C bus but it gives "controller timed out"
message.
below is the log for same.
[root /]# i2cdetect -y -r 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: [ 1188.831062] omap_i2c 4802a000.i2c: controller timed out
-- [ 1189.831029] omap_i2c
