Have you tried plugging ia serial cable into the local serial port?
That should work as long as you still know the password.
No network links involved.
---Graham
==
On Saturday, September 19, 2020 at 6:30:17 AM UTC-5 pietb...@gmail.com
wrote:
> Hi
>
> I'm a Linux blockhead.
>
> I just got a
Another choice:
Adafruit USB C Breakout Board - Downstream Connection PRODUCT ID: 4090
Digi-Key Part Number 1528-2873-ND
Instructions at
https://www.adafruit.com/product/4090
It already has the two resistors on it, that Robert referred to.
--- Graham
On Monday, August 17, 2020 at 8:43:21
3.3 Volts is generated inside the OSD3358 by a TI TPS65217C PMIC die
PMIC stands for Power Management IC
You can read the TI data sheet on the TPS65217C
But the OSD3358 is a multi-chip module, so not too much you can do, other
than replace the entire OSD3358, if damaged.
And that would require
The answers is that the BeagleBone can address the entire 16GB micro-SD
card.
I have used cards up to 128 GB in size.
BUT
if you installed the OS image on the card for either direct use, or for
writing to the EMMC, then the partition size has been set to 4 GB, and you
can not see the rest of
>>> Does anyone have any input as to why the PocketBeagle design fails and
>>> why the BBBW works ?
Robert Nelson is really the right person to answer that.
>From what I understand, during boot, uBoot examines the configuration
EEPROM and decides which files/modules to load. Even though the
t;) escribió:
>
>> On Sat, Aug 10, 2019 at 9:50 PM Graham Haddock
>> wrote:
>>
>>> What I would do is some minor surgery on the PocketBeagle, disconnecting
>>> the +5V lead coming in the microUSB connector.
>>> The easiest way to do this would be to
What I would do is some minor surgery on the PocketBeagle, disconnecting
the +5V lead coming in the microUSB connector.
The easiest way to do this would be to remove FB1 (ferrite bead in series
with USB +5).
Easy with "hot tweezers", or a pair of small soldering irons.
To restore the Pocketbeagle
As I said, P1-Pin-1 and the microUSB connector power are two different
inputs to two different power supplies. Having power on both of them is
not a problem, and in fact, will prevent the problem of instability I was
concerned about.
So, no problem powering both.
The concern with the random
Does Etcher install the image and verify without errors?
Did you try Dennis' suggestion to hold down the boot-select button while
plugging in the USB/power cable?
--- Graham
==
On Fri, Jun 28, 2019 at 11:29 AM wrote:
> i tried but i'm faild again. i could write any os image for example
>
Detailed discussion on Apr 17 2017.
--- Graham
==
On Wed, Oct 31, 2018 at 10:15 AM Graham Haddock
wrote:
> I think there is a detailed discussion as to what is supposed to be inside
> the cape EEPROMs in the
> "BeagleBone Black System Reference Manual"
>
> It looks
I think there is a detailed discussion as to what is supposed to be inside
the cape EEPROMs in the
"BeagleBone Black System Reference Manual"
It looks like there is a live Wiki version at
https://github.com/beagleboard/beaglebone-black/wiki/System-Reference-Manual
But since that address has
did you install smbus?
It is a prerequisite.
--- Graham
On Thu, Oct 4, 2018 at 10:34 AM Dennis Lee Bieber
wrote:
> On Wed, 3 Oct 2018 20:15:04 -0700 (PDT), Chris Bohler
> declaimed the
> following:
>
> >
> >When attempt to execute Adafruit_BBIO.I2C as I2C:
> > "Adafruit_BBIO.I2C deprecated.
No, I only connected it with the USB-tether "gadget" via a Windows 10 PC.
I also got tired of the instability of the "gadget" and moved to either SPI
or USB2 interfaced wired Ethernet, both of which work well, if they are
fast enough for your application.
--- Graham
On Tue, Sep 18, 2018 at 3:30
Please do not use "TinyUrl" when distributing information.
It forces the receiver to open an unknown website on their computer.
Might be innocent, might be malicious.
If you want help, please provide the part number, and any URL should be the
full and exact URL.
--- Graham
==
On Mon, Sep 17,
Fred:
The temperature coefficient is only important if you are going to use them
as temperature monitors, and you are going to thermally/mechanically attach
them to the battery.
If you are just trying to get the battery power supply to run, and are not
concerned about battery temperatures, a
Mark:
Well, I suspect it would take a deep dive into the drivers to answer that.
I agree with what you would expect, but there is software involved.
I obviously does not like to be configured twice?
The configuration depends on some assumed initial states that are no longer
true when it has
Mark:
That bus is configured by default, so you should not have to configure it
to use it.
It is the bus used to probe for and talk to the memory chip on equipped
capes.
Try using the I2C-2 bus without configuration. It should just work.
--- Graham
==
On Wed, Sep 5, 2018 at 3:04 PM Mark A.
Ethernet
On Wed, Aug 8, 2018 at 11:15 AM, wrote:
> Hey guys,
> I'm trying to transfer video to raspberry pi.
>
> Which one should i use? the fastest? GPIO I2C SPI UART?
>
> I want to send video data from BBB to raspberry pi and receive data from
> Raspberry pi to BBB.
> I'm going to stream live
The console will not have Python installed. But apt-get can install Python2
or Python3 or both and all dependencies, and a minimum set of Python
modules. Other modules are available with pip.
example:
sudo apt install git build-essential tree htop i2c-tools python3
python3-pip python3-smbus
I don't use node.js, so I am not familiar with it.
The name of the function suggests that it does a 'sync' after the write,
which is what you want.
In Linux, the 'sync' command flushes all the buffers to disk.
I would just read the manual on the function to make sure it is doing what
you want.
---
It works fine on the PocketBeagle running Debian.
You do need to connect it to USB1, which is pinned out on the accessory
connectors, and not USB0, which is on the micro-USB connector.
--- Graham
==
On Thu, Feb 15, 2018 at 7:04 AM, wrote:
> Hello,
>
> I'm trying to
On the PocketBeagle, both I2C-1 and I2C-2 are both brought out to the
headers and both enabled by default.
I don't know that there is any reason to prefer one over the other on the
PocketBeagle.
--- Graham
==
On Sat, Feb 10, 2018 at 7:55 PM, Stuart Longland wrote:
I'l look at it with both a Voltmeter and an oscilloscope.
I have a B bench supply that when you turn it on, with a BBB already
attached, did an overshoot up to around 5.7 Volts before settling back to
5.0 Volts.
It would trip the self protect on the PMIC almost every time you tried to
start the
Works fine. As long as power/Vusb is on Vi (P1-pin 7)
--- Graham
On Sun, Dec 10, 2017 at 12:18 PM, Patrick Poirier <
patrickpoirie...@gmail.com> wrote:
> Hello, I am planning to use this setup, Have you successfully implemented
> and completed tests ?
>
> Regards
>
>
> Le vendredi 17 novembre
P1-pin7 is the 5V power input normally associated with power coming in the
USB connectors.
In the case of the PocketBeagle, it is the input from the USB0 connector.
It can be used as either a 5V input or, if there is power coming in USB
port0, as a power output for USB port 1.
It is just a
Yes, try some other power supplies. and if they stay between 4.75 and 5.25
under all the different load conditions a BBB can create, it will work fine.
USB power is highly variable from computer to computer. Sometimes it works
fine, sometimes it does not.
USB-1 was 0.5 Amps max, not enough to
All of your description points at a power supply problem.
If the USB power, even for a millisecond, drops below 4.5 Volts AT THE BBB,
the PMIC (Power Management IC) will shutdown.
If you have a computer with a USB port on the low side of the USB Voltage
range (4.5 to 5.5 Volts) then what you
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
The possible bus frequencies are integer divisors of 48 MHz, so only option
above 24 MHz is 48 MHz.
Spec on the W5500 chip says it will run up to 80 MHz.
So, I will recompile the ".dtbo' for 48 and report.
--- Graham
==
On Sat, Oct 7, 2017 at 6:02 PM, Robert Nelson
And they are a cool Blue, rather than industrial Black.
--- Graham
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it,
> On Mon, Oct 2, 2017 at 8:20 AM, Alex Bagehot <ceea...@gmail.com> wrote:
>
>>
>>
>> On Fri, Sep 29, 2017 at 1:55 PM, Graham Haddock <gra...@flexradio.com>
>> wrote:
>>
>>> You use the "USB-tether-gadget", which, when your USB cable is connec
You use the "USB-tether-gadget", which, when your USB cable is connected to
a Windows host computer, allows you to bridge and share the Ethernet port
on the Windows host.
I have it working on Windows 10.
See
Will the same Ethernet overlay work for both the ETH Click and the ETH-WIZ
Click?
Since the 10/100 Mb Ethernet (ETH WIZ) Click board is $19, and the 10 Mb
only ETH Click board is $24, I bought the 10/100 ETH WIZ click board.
--- Graham
==
On Wed, Sep 27, 2017 at 1:56 PM, Robert Nelson
If you start with a "microSD/standalone" image, then you are ready to boot
and run from the card.
If you start with a "flasher" image, then you will need to edit the
/boot/uEnv.txt file to keep it from flashing your eMMC.
The other thing to know is that you may need to expand the partitions on
Sounds like you can move ahead, and learn a little python.
--- Graham
==
On Fri, Jun 16, 2017 at 4:01 PM, wrote:
> now I can read :)
>
> this script works
>
> import smbus
>
> # General i2c device class so that other devices can be added easily
> class i2c_device:
> def
Sebastián:
Is your Arduino 3.3V or 5.0 V I/O?
What clock speed are you running the I2C bus in the Beaglebone?
With the time distortion in the level translator, I would not go above 100
kHz until proven good at higher speeds.
I note that your schematic shows VDDP connected to 5V.
This should be
Torsten:
Great job.
--- Graham
==
On Mon, May 29, 2017 at 9:32 AM, 'Torsten K.' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> FYI: It's working now. The PIC code that came with the motor controller
> was not I²C re-start aware.
>
> I re-implemented the ISR to accept both stop/start
Let's start with a few clues.
What board and revision level are you using? (example: BeagleBone Black,
Rev C.)
What OS, version, release date and kernel are you using?
What other changes, if any, have you made to the system software?
What hardware / I-O do you have plugged into the accessory
William:
Great. Derek did update his video, although he still refers to the
original one on his website.
--- Graham
==
On Tue, May 23, 2017 at 5:16 PM, William Hermans wrote:
> https://www.youtube.com/watch?v=T9yFyWsyyGk
>
> . . .
>
> On Tue, May 23, 2017 at 3:11 PM, Graham
compliant/conforming, although you could still screw up the response time
servicing it slowly internally.
If they are "bit-banging" the I2C interface, then anything can happen,
depending on the quality of the programmer.
--- Graham
On Mon, May 15, 2017 at 11:33 AM, Graham Ha
What part number PIC?
--- Graham
==
On Mon, May 15, 2017 at 9:36 AM, 'Torsten K.' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> Hi Graham,
>
> just for reference: The guys who built the motor controller confirmed that
> they are having trouble with newer kernels on the Raspberry PI,
I take back what I said about a non standard read sequence. I re-read the
data sheet, and they describe a standard concatenated write/read sequence
for a single byte read. But I do note that they do not describe a simple
read only sequence, where the part would start reading from the last
It looks like the MPU9250 has a non standard (to my way of thinking) I2C
read sequence that requires you to resend the register address as part of a
consolidated write/read sequence. The default tool i2cget does not deal
with this, and only deals with simple (standard to my way of thinking) read
So, the COM port on Windows is talking to a virtual serial port in the BBB
USB widget.
There is no hardware UART involved, and no hardware clocks anywhere to
throttle or pace anything.
Then, you push this for transfer rate, while running it under a non
realtime OS.
I guess I am not surprised that
Justin:
>From your questions, you seemed to have an over-simplified view as to how
the clocks are generated in the Sitara.
It is not your grandfather's PIC.
It is a very modern, sophisticated, clock system, with many of the clock
subsystems being variable rate.
A "Clock Tree" is the generic
What OS/kernel is ithinu running?
"shutdown -P now" works on all my BBB/BBG boards.
But, I run from external +5V, without anything on the battery connections.
--- Graham
==
> I usually tell everyone to use:
>
> sudo systemctl poweroff
>
> as systemd knows how to tell the external tps65217 to
Robert:
Looks like exactly what I want. I'll implement that.
William:
Thanks for your comments.
--- Graham
==
On Mon, Apr 17, 2017 at 5:03 PM, Robert Nelson
wrote:
> On Mon, Apr 17, 2017 at 1:42 PM, Graham wrote:
> > I would like to build a
Luther:
I have no explanation for that.
Only the most universal, uSD resident version is posted for the 'release'
versions.
I personally find the console version is the most useful for building much
smaller custom applications.
--- Graham
==
On Sun, Mar 19, 2017 at 7:38 AM, 'Luther Goh Lu
If you want the latest "release" version, use the 11-06 version, as
referenced on
https://beagleboard.org/latest-images
I told you where the "console version" corresponding to that "release"
version was.
==
If you are comfortable using a "testing" version, then I would only use the
ones that
I am glad it is running now.
It is not a chip I have used, so you will have to sort it out, now that you
are communicating with it.
If you do need to remote it in the future, you should use shielded cable
with a good ground, increase the size of the bypass / filter cap at the IC,
from the 0.1 uF
Under Debian 8, the external I2C bus is now I2C-2.
I2C-1 is internal only, and used for talking to the PMIC and things like
that.
Don't use it, unless you really understand what you are doing.
--- Graham
==
On Fri, Mar 10, 2017 at 8:08 AM, christ christ
wrote:
> Hi
Hi David:
I am glad to hear that you got it fixed.
I am posting your reply back to the Beaglebone reflector, so others can
benefit from the discussion.
If you are talking about RAM in the PRU, perhaps some PRU expert can answer
your question. (I am not a PRU expert.)
If you are talking about
On Mon, Jan 30, 2017 at 12:24 PM, 'woody stanford' via BeagleBoard <
beagleboard@googlegroups.com> wrote:
> You are obviously knowledgeable, Graham, so we'll pose these questions to
> you then.
>
> (1) Is serial (ie. UART) communication on a BBBW (Rev C) Angstrom "distro"
> (ie. stock) done with
The ADC can be set up to run audio format TDM. You have two MCASP, which
are high speed multi-channel TDM engines to play with.
(Although I think they only did a real good job of pinning out MCASP0, need
to investigate, but one might be enough.)
Each are relatively independent bi-directional.
Hi William:
For an expert, you are totally correct.
For a newbie, the Raspberry Pi images seem to be designed to limit how much
tinkering you can do with Linux itself.
The tools and examples for modifying Linux itself are much better supported
on the Beaglebone.
Both are good for blinking LEDs
that are on the uSD card?
> Thanks...Arnie
>
> On Fri, Jul 8, 2016 at 1:19 PM, Graham Haddock <gra...@flexradio.com>
> wrote:
>
>> Arnie:
>>
>> Simple answer: No.
>>
>> Although it is possible to have the OS running on the eMMC and an
>> app
t;> *On Debian 8 and later, this usually means that you do not have the
>>>> "boot bit" set on the card.*
>>>>
>>>
>>> No . ..as I said. It means there is an older bootloader on the emmc. If
>>> you remove the bootloader, said problem goes
It should automatically boot from the card without having to push the boot
button.
On Debian 8 and later, this usually means that you do not have the "boot
bit" set on the card.
If you created the card by installing the resident version of Debian, then
expanding the partition, the "boot bit"
My personal favorite C/C++ IDE is Eclipse, with the C/C++ Development and
Remote System Explorer (RSE) environment packages. I use the GCC cross
compiler.
A reference on how to set this up, although needing some updating, due to
newer current versions of Debian and Eclipse, is Derek Molloy's
The PMIC in the BeagleBone will go into shutdown, if the DC supply voltage
goes below 4.5 Volts, or above 5.5 Volts, even for a few milliseconds.
In use it should be held between 4.75 and 5.25, so you have some margin.
If the "lights flickered" then the power supply for the BBB did not have to
William:
That would work.
The only "edge case" I might see as a problem would be if your ping target
went off line. Then the BBB would reboot itself every ten minutes even
though nothing was wrong with the BBB. I guess you could ping several
different targets in rotation and only reboot if
Hm.
Both "Major League Electronics" and Samtec are located in New Albany,
Indiana.
What are the chances ?
Sounds like there is a back-story there, somewhere.
--- Graham
On Wed, May 4, 2016 at 4:51 PM, evilwulfie wrote:
> I know about breakaway headers and
Well, in an emergency, you can make your own out of breakaway stock.
Or, if you are in the US and looking for manufacturing volumes,
then call your local Samtec rep. They can turn this kind of stuff in days.
They normally don't use stocking reps. Factory direct. Very fast response.
David:
The whole button press thing is old information.
Even then, you needed to have either a "flasher" or a uSD card resident
package.
The software installation process has evolved a lot. (for the better.)
The good news is that the Beaglebone and embedded Linux are rapidly
evolving.
The bad
The problem is, that if it is not perfectly airtight, then the next time
you open it, you find the little silica gel packets floating in a puddle of
water. :-)
If it is not perfectly airtight, then every time it rains, or a cold front
passes, the box cools and it sucks in a little wet air (or
To Richard Cook:
My personal recommendation is Derek Molloy's:
Exploring BeagleBone: Tools and Techniques for Building with Embedded Linux
by Derek Molloy for John Wiley & Sons, 2014 -- ISBN 9781118935125
Book WebSite: includes errata, discussion
http://exploringbeaglebone.com/
Source Code:
Yes.
sudo chmod 755 myprogram
or
sudo chmod 755 myprogram.o
--- Graham
On Fri, Mar 25, 2016 at 9:50 AM, Seppo Nikkilä <
seppo.nikk...@innovativeideas.fi> wrote:
> myprogram.o
>
> On Fri, Mar 25, 2016 at 3:27 PM, Graham wrote:
>
>> And after you create the file for the
PCB rework skills are very useful, and not explicitly taught in college.
Good luck with your project.
--- Graham
==
On Wed, Mar 23, 2016 at 3:13 AM, Christopher Earley
wrote:
> That bit about only being able to mux a specific mode's signal (e.g.
> I2C2_SDA or I2C2_SCL) to
Do you have a terminal plugged into the command line serial port?
What does it say is happening?
--- Graham
On Sun, Feb 28, 2016 at 3:14 PM, Graham wrote:
>
> Alex:
>
> You are probably trying to draw too much power through the USB port from
> the BBB.
> I would try the
So, tell me again what the market is for a $250 "embedded" processor card.
I understand that TI is using it for an eval board for the AM572x.
OK, I get that. And they add an LCD and double the price. (?!?)
A pair of DSPs brings a lot of crunch power to the party.
OK, cool. RF transceivers,
I have installed right angle connectors on most of my BBB, so that the
serial console connector comes out the bottom of the board.
Works fine. You do need to know how to solder to do this, without hurting
the board. It will no longer fit in a case when you bring
the right angle serial console
Bill:
I don't think the PRU clocks are externally available.
I don't know what your interface looks like, but if there was a clock line
involved in the data transfer, or marking when data is valid, I would look
at inverting or adding some delay in that line going to the receiving PRU.
If your
I found another one:
http://www.nextwarehouse.com/item/?2221755_g10e
Claims they have one in stock.
I am sure they will say they have just sold it to someone else if you order
it, and your waiting time for the next delivery is 8 weeks.
Except that they will keep forgetting to take that one
Do you have the option to lock it in the basic ASCII 7 bit character set?
That would likely solve the problem.
The problem with Teraterm is that the BBB will sometimes put out some
gibberish or perhaps some non-printing control characters at the start of
the console output (don't know why) and it
Well, by definition, the boot programming pins are going to have the
pull-ups / pull-downs, so you know what they are going to be doing, until
over-ridden.
Most processors start up with the programmable pins as inputs, then move to
the configured state.
Anything else can be dangerous to the pins.
I think the VDD_3V3B rail is deliberately held off until the unit has
started booting,
and has already read the boot instructions. It is not a rise time issue.
I suspect it was done deliberately to help with the "don't drive the rest
of the pins" issue.
A little 5V to 3.3V regulator to power
>
> What is the minimum voltage I should have on the GPIO input so it is read
> as 1 logic?
>
>
> For most CMOS the minimum input voltage guaranteed to be read as a one is
0.7 times Vcc.
But not always. Read the spec sheet for the part in use. For instance, the
transmission gate you found was
Hi Frederic:
You could make the 74HC541 work, since it has a CMOS input and should not
load the BBB during boot, provided that it has power supplied the entire
time the BBB is booting.
I was thinking more of something like the 74CBTLV3126 bus switch which
would disconnect your existing circuits
It is not a flakey DC jack. But yes the symptoms do mimic that kind of
failure.
Same hardware works fine with Debian 8.1/kernel 3.14 and prior.
It happens under all loading /activity, but easy to reproduce with the
board idling, minimum console software load.
It does not happen with the board
I will add anecdotal comment in support of Guenter's comment about a serial
port problem.
Three times, I have had the ttyS0 port hardware serial console port stop
working in advance
of the reboot, while I could still sign in on SSH via Ethernet, and the BBB
seemed to be
otherwise still working.
Agreed. But at the same time, the same hardware, right or wrong, works
fine under 3.14 and prior. So there has been some software change since
3.14 in the way that the hardware is managed.
--- Graham
==
On Tue, Jul 28, 2015 at 5:47 PM, Dennis Cote denn...@harding.ca wrote:
On Monday, July
William:
OK. I plan to let it run for at least two days, perhaps three.
--- Graham
On Mon, Jul 20, 2015 at 11:34 AM, William Hermans yyrk...@gmail.com wrote:
*William/Wulfman: So far, running on USB Power module (no USB
communications) the BBB is staying up. It has been 18 hours or so now.
William/Wulfman: So far, running on USB Power module (no USB
communications) the BBB is staying up. It has been 18 hours or so now.
Running the same software that rebooted twice in 24 hours on +5V barrel
connector input. I have seen the 'bad' configuration run as long as 36
hours between reboots,
.
Easy enough to test anyway . . .
On Sun, Jul 19, 2015 at 9:00 AM, Graham Haddock gra...@flexradio.com
wrote:
My advice to Erik is that, if he has something important to do, to go
back to an official release. He should use a Beta release only if he can
afford the additional problems it might
What version Debian, and which version kernel is your friend running?
On Sat, Jul 18, 2015 at 7:46 PM, evilwulfie evilwul...@gmail.com wrote:
My friend powers his from USB and all is fine.
sounds like its related to the Vusb line issue posted here recently
On 7/18/2015 5:34 PM, Nuno
I power off the 5Volt power connector.
The only other connection to the unit is Ethernet cable.
--- Graham
==
On Sat, Jul 18, 2015 at 7:21 PM, evilwulfie evilwul...@gmail.com wrote:
powered how
On 7/18/2015 5:14 PM, Graham wrote:
For what it is worth...
I loaded the console version
:41 AM, Graham Haddock gra...@flexradio.com
wrote:
OK.
I took my Rev.C unit (1c:ba:8c:d9:5e:dd) and loaded
bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img onto a
16 GB uSD card. Unit, power supply and card are trusted.
Absolutely no changes to the image, just install, boot, run. No updates
OK.
I took my Rev.C unit (1c:ba:8c:d9:5e:dd) and loaded
bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img onto a
16 GB uSD card. Unit, power supply and card are trusted.
Absolutely no changes to the image, just install, boot, run. No updates,
additions or modifications.
No cape, only connections
Hi William:
Doing nothing with the board. It is just sitting on the side connected to
+5V power and Ethernet.
So, for example, late last night (Central US time) I loaded
bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img
onto a trusted uSD card expanded the memory using gparted to the full 16GB,
I will try it by reloading a totally untouched
bone-debian-8.1-lxqt-4gb-armhf-2015-07-05-4gb.img,
and report back. No cape, trusted Rev.C hardware and power supply. All
communications via
Ethernet.
By my saying that 3.14 is rock solid, this includes up to
Well, some suggestions and thoughts.
1.) In kernel 3.8, I think I2C Pins P9.19 and P9.20 report as I2C-1, so you
should see the part on that bus.
2.) Make sure you have not swapped the SCL and SDA lines. Make sure that
you are really connected to P9.19 and P9.20.
You should see activity on both
The signal on the bus is the same.
Just the name is different.
So to talk to the part using Linux, use the address in 7-bit format,
which for your part is 0x21.
If you are writing in C, you will use i2c-dev and ioctl
If you are writing in Python 2.7, you will use SMbus and something like the
I thought that it would work on USB, and not on external power supply.
If the situation is that you get the one blink and no boot, is the same for
both USB power and external power, then there is a hard failure of the
Beaglebone. Either a damaged power supply chip, or a short circuit
downstream
BeagleBone Black SRM Version C.1
Section 6.7 Boot Configuration Design, Page 67.
See Page 68, Figure 38.
Yes, DNI means Do Not Insert.
Or some time the term NP , meaning No Pop or do not populate is used.
Section 6.8 Default Boot Options, Page 68.
It is covered again on page 106, Section
Rodney:
I highly recommend this book. The answers to all your questions with
examples are either
answered in this book, or Derek Molloy's website.
Exploring BeagleBone: Tools and Techniques for Building with Embedded Linux
Paperback - December 31, 2014
by Derek Molloy (Author)
ISBN-13:
You don't have to short anything out for what he is describing to happen.
The BBB-Sitara uses a field of 100K resistors, which are either pull-ups or
pull-downs
on 15 different lines, pinned out from P8-31 through P8-46, which instructs
it how to boot.
Any load on any of these pins, of lower
Brian:
Thanks for the pointers.
I will go read up on it.
Thanks,
--- Graham
==
On Fri, Mar 27, 2015 at 7:06 PM, Brian Anderson b...@nwlink.com wrote:
Since you are using Jessie images, have you tried using ConnMan to manage
the WiFi connection rather than resorting to all of this systemd
To get a reliable start of the WiFi service with jessie, I did the
following:
1.) do NOT uncomment the wireless enable/start lines in
/etc/network/interfaces.
This would try to start up the WiFi before USB is up and running and stable.
Apparently, once wpa_supplicant gets the error, it will not
, Nathaniel Johnson
gruyere.emmenta...@gmail.com wrote:
Graham, did you try Fredrik's solution? It works fine for me though left
the auto wlan0 line in the interfaces file.
-Nathaniel
On Thu, Mar 26, 2015 at 11:54 AM, Graham Haddock gra...@flexradio.com
wrote:
To get a reliable start
Robert:
Thank you.
--- Graham
==
On Sun, Mar 22, 2015 at 12:35 PM, Robert Nelson robertcnel...@gmail.com
wrote:
http://elinux.org/Beagleboard:Capes_3.8_to_3.14#Chipsee_bbb-exp-c
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are
1 - 100 of 126 matches
Mail list logo