The default install is Debian and includes quite a lot. They're just isn't
anything in your home directory.
As with everything it's much easier with internet, but you can copy files
to a cdr and then load them on the BB via your host computer that you SSH
from. It's a pain but I've done it.
y, I want to use the BBone Blue to drive some servos with PWM
> signals. I'm search for c program examples to toggle the onboard LEDs and
> use the servo motor pins.
>
> On Sun, Jan 20, 2019 at 8:20 AM Jim F wrote:
>
>> The default install is Debian and includes quite a lot.
The pocket beagle has no emmc. So you shouldn't uncomment that line in
/boot/uEnv.txt. It's probably the problem.
Jim
On Wed, Dec 12, 2018, 6:58 AM Marius Strom wrote:
>
> I'm trying to evaluate a PocketBeagle (rev A2) for use in an
> instrumentation class I'm teaching this Spring, however,
aceme.service
>
> [Unit]
> Description=to invoke aceme.py automatically
> Requires=graphical.target
>
> [Service]
> Type=simple
> ExecStart=/home/debian/eme/acemev35.py
>
> [Install]
> WantedBy=multi-user.target
>
> [
Hi Harke,
I am hoping to build up some good will to get an answer to my question, so
let me see if I can pitch in. Plus I wanted to get a systemd service
working anyway, which I did successfully this morning. Here are the steps I
took.
1) Create the application. I wrote a stupid python program:
Hi all,
Perhaps someone understands the device tree overlay file format better than
I do (I sure hope so). Again, my purpose here is to be able to use a 1-wire
interface on the Beaglebone Blue using one of the 6 GPIO pins connected to
a header. I have selected GPIO1_25 which seems to be otherwise
Hi Seth,
I'm glad to hear from you. I am already using the latest-images iot build.
But I'm trying to learn how to reconfigure the 1-wire interface which has a
dts file configured to use P9.22 on the beaglebone black, and move it to a
different GPIO pin on the beaglebone blue. P9.13 (which I
or my comments don't get you on track.
Jim
On Wed, Dec 5, 2018 at 12:23 AM Mala Dies wrote:
> Okay and Hello Once More,
>
> Seth here. I think (know) Jim F was on to something w/ your software and
> setting up .service files for running on boot.
>
> For example: Here is an
me here.
> I hope this helps in the analysis.
> Best regards,
> Harke
>
>
>
>
> On Wed, 5 Dec 2018 at 21:46, Jim F wrote:
>
>> Harke,
>>
>> You should try running your script from the cli using the exact same
>> command you use for the exec s
You'd have to read the data sheet of the sensor to know if it can work that
way. Most of the time the interrupt pins need to actually be connected to
the processor somehow to work. I'd suggest that you connect them to gpios,
configure the BB gpio pins as interrupts, and check the data sheet to see
gt; could you please correct me if i am wrong.
>
> Thanks
> Prakash
>
> On Sun, Nov 25, 2018 at 7:07 AM Jim F wrote:
>
>> You'd have to read the data sheet of the sensor to know if it can work
>> that way. Most of the time the interrupt pins need to actually be conne
You can just use dd and write an image file, then copy that wherever, if
you have a tuition that only takes up part of the card space. Like
dd if=/dev/mmcblk0p1 of=/mnt/data/image.iso
Obviously you'll need to customize that command and you should either use
the dd man page or the internet for
Log in as debian, then sudo whatever you need to do as root. If you don't
like that, sudo su, and then you will be root and can change its password
if you must.
Many systems will not let you log in as root over ssh. It's a bad practice
anyway. If you really must you can change that in
It's considered poor form to log in to root directly these days,
particularly over ssh. Instead you log into a user account and either sudo
or su to do what you require. It is wise to change the root password, so
just log in as debian, sudo -s and then set the root password. If you
choose to log
This really has nothing to do with the BB. You should look into python
flask or a similar framework since you're using python. There are many
options. You need something to replace what php be doing for you.
Regards
Jim
On Tue, Mar 5, 2019, 7:35 AM wrote:
> Hello..
> I want to
I haven't tried to do what you're asking, but the error message suggests it
wants a 4.19 kernel while you have a 4.14 one installed. There are
instructions on elixir how to upgrade kernels or you could see if there's
an older version of lxde available which doesn't need 4.19. Or I'm
completely
You have to apt-get update first.
On Thu, Mar 14, 2019, 2:48 PM Sardar Vayghannezgad
wrote:
> Thanks a lot for your reply. What I end up seeing on puTTY after typing
> sudo apt-get install [no matter what!]" is the following:
> Reading package lists... Done
> Building dependency tree
> Reading
You aren't pinging Google.com, you're pinging 8.8.8.8. You haven't got your
dns resolve configured properly. What's in /etc/resolv.conf? It needs to
have a line in there like
nameserver 8.8.8.8
Then the apt-get update and other commands will work... Better.
On Thu, Mar 14, 2019, 4:10 PM Sardar
Do you have the root password? If so you can su and then fix it. If not you
should look up how to break in to a Linux system, which is usually a mod to
the boot command. Search for single user mode. Probably you'll need a
serial to USB cable for your board. If you messed up the image on the mmc
For installing pandas, try apt-get instead. If that doesn't work, then as
Dennis said, just copy/paste the whole error message.
$ apt-cache search pandas
python-pandas - data structures for "relational" or "labeled" data
python-pandas-doc - documentation and examples for pandas
python3-pandas -
It's not so hard to do by eye if you have good markings on the board and a
decent stencil. I have done this myself countless times. Just make sure
there's enough room nearby to look and see if you lined it up properly to
match rows. I managed to be off by a row once and that was unfortunate.
OSH
Yes, same concept. Once you have the system booted, set your password then
copy the /etc/passwd file over to the other partition. I forget if the
default BB image uses shadow password file so if there's no password data
in the passwd file you might need to copy over the /etc/shadow file too.
Make
What Robert said is what we did. Upgraded to 4.19 that way, then added the
existing dtb for 1 wire. The device s just show up in the /sys tree, can't
remember exactly where. Maybe /sys/class/w1.
It was pretty easy, surprisingly so. The hard part is knowing that it
didn't work on 4.14.
Jim
On
We upgraded to 4.19, loaded the 1W dtb from /lib/firmware and things just
work. I think it's looking for the 1 W interface to be on P9. 12 which
works out to Gpio 1-28 which is also known as gpio 60. At this point it
shows up under /sys/bus and "just works". Couldn't say that for 4.14 and
I've no
There are some obvious places in /boot/uEnv.txt. If it doesn't load
though, usually the only way you can debug is to hook up a serial console
to UART0 because uboot loads before kernel logging starts.
On Wed, May 15, 2019, 8:27 PM Walter Cromer Hugh - I'm a real newbie. I compiled a device
Plug it in to your computer via its USB cable, and use your web browser to
go to either http://192.168.6.1 or http://192.168.7.1. I can't remember
which is the one for a windows host and which for linux host. Either way, a
webpage will come up and you can see some of the ways you can work with
For what it's worth, your message was sent 3 times, Google doesn't send you
a copy because it assumes you know you sent it.
Have you been updating things? If not, the troubleshooting steps are in
your hands, which makes it easier. Replace the SD card with a new one and
see if it works. SD cards
If you decide instead to try to get 1 W working with drivers, we failed at
it on 4.14. Something changed on the way to 4.19 and we got it working
there. If I had notes to share I would...if I find them.
Jim
On Tue, May 7, 2019, 10:46 AM TJF Hi!
>
> When using the libpruw1 driver
>
Dennis,
I'm afraid I'm taking this a bit off topic, but part of your answer
tantalized me:
...I also should see about setting up Buster (Debian 10) in VirtualBox
> first; I do have Stretch in VirtualBox already...
>
I'm pretty sure you don't mean what I hope you mean, but do you have a
I think you messed up in step 1.
/etc/resolv.conf should contain at least one line in the form :
nameserver 8.8.8.8
In order to separate the different components for debugging, recommend you
try ping 8.8.8.8 and see if that works, first.
J
On Tue, Aug 13, 2019, 11:42 AM anish kumar wrote:
Ahhh. I've had some of this pain. I did actually raise xmodem from the
dead, but had enough problems that I just got a secondary USB port working
and put a wifi dingle on it. Anyway what you want to do, sounds like it
will work.
On Fri, Aug 9, 2019, 9:07 PM Robert Heller wrote:
> At Fri, 9 Aug
systemd-analyze will help with that, google or read its man pages.
Like Jacob said, for faster boot choose an image with no gui. One of the
iot or console images should do. Boot time around 30 seconds to
multi-user.target.
On Tue, Sep 3, 2019, 11:45 AM Deepak Shetye wrote:
>
>
The first is a clue to the second. Your apt cache has no
cross-build-essential.
Try running apt-get update first, then the apt-cache command gain, if you
find a candidate install it and move on.
If not the problem is your DVD safe probably the only install source you
have installed. Try
What do the signals look like when you hook a scope up? How's your ground
and signal connection? Is your bypass capacitor installed as short as
possible between the vcc and ground? If you are actually using a
breadboard, I'm surprised you got that far. Throw it away and get a
surfboard that you
I have been using mobaxterm for this kind of application. It encapsulates
putty and an x server, and its free license has reasonable terms. It just
works, without configuration. I believe it can handle an XDMCP session as
well but I've never tried it.
Best
Jim
On Thu, Aug 8, 2019, 11:45 AM
Robert,
If you have a look at the Pocketbeagle schematic, you can see what happens
with the USB connector, which comes in on page 2. Power on that pin goes to
VIN.USB, which goes straight to (page 3) the Octavo OSD3358 VIN_USB pins.
You can look at the Octavo datasheet [1] - it's for the
Did you tie the pins of those peripherals together? You can't just send a
message to a serial port and expect something to happen. Rx1 needs to be
tied to tx2, etc.
Also you need to config-pin the correct pins to the correct modes, or do it
in the device tree.
Not sure what you were expecting to
Robert,
Do you expect the RT build to boot as slow as the current non mainline
ones? I guess I can just wait and see, but I am curious. Thanks for the
awesome news!
Best,
Jim
On Sat, Jul 20, 2019, 6:54 PM Robert Nelson wrote:
> Encase anyone watches the git tree, something amazing just
Congratulations to you on that ;we were completely unable to get 1w working
on 4.14. After upgrading to 4.19 and using the default 1w dtb, things
worked perfectly. Unfortunately we only use a single device so I can't say
whether 4.19 will help you in this case.
Best regards,
Jim
On Fri, Jul 19,
Is your user a member of the gpio group? If the pin is already an output
and you don't have permission it seems reasonable that it might not fail.
You could always sudo python to rule out a permissions problem, which is
what the error message says. Then solve the permissions problem.
Have fun
1w didn't work in that version of Linux. It works in 4.14 if you enable the
dtb file in uenv.txt. So I think you'll have to update.
It looks like it should support multiple devices, but we're only using one,
so I haven't tried.
Good luck.
-j
On Mon, Nov 18, 2019, 10:28 AM Fohnbit wrote:
>
Should be easy to do. Change the boot configuration so that you don't try
to boot from mmc1.
I think if it's a black, it should be r68 out, r93 in. Look up that
platform manual to see the boot options. Chip is Am3358.
Here a handy chunk of schematic to help with that.
You also have to config-pin P9.26 uart. If not that, could be you swapped
tx and rx, common serial problem.
J
On Mon, Oct 14, 2019, 8:05 AM Mridul Ahuja wrote:
>
> I have a BeagleBone Black running *Debian 9.9 2019-08-03 4GB SD IoT *(
> https://beagleboard.org/latest-images). I want to
On Fri, Mar 6, 2020, 2:02 PM Hugo van den Brand
wrote:
> It sounds like you are mounting folders in your /boot and /home
> directories on the BBB which you don't mount if you just mount the SD card
> in ubuntu.
>
> On your BBB you could use the mount command to show currently mounted
>
Looks like you're using too much power from the USB. Maybe you can run your
device from its own power instead of off the bus.
On Tue, Mar 24, 2020 at 8:11 PM Zeph wrote:
> I am using a BeagleBone Black with Ubuntu 18.04 and I am attempting to use
> an SLAMTEC RPLidar A3M1 which uses a UART to
We built and delivered over 1000 ocean buoys in a design cycle that lasted
about 9 months based on the pocketbeagle MCM. The original plan was to
build a PCA on which the pocketbeagle sat (in order to satisfy some "COTS"
spec) but the cost of doing so got prohibitive, so we just squished the
Mark,
I wish more tutorials looked like this. I should have started with
congratulations on a great job. Thanks for considering my suggestions.
Best,
Jim
On Fri, Aug 28, 2020, 5:33 PM Mark A. Yoder wrote:
> Jim:
> Thanks for the feedback. I like your suggestions. Responses below:
>
> On
Hi Mark,
Nice tutorial. Wish I'd had that quite some time ago, I had to pull all
those pieces together myself.
>From having read a bunch of posts here, I have a few suggestions for your
consideration.
1. User needs to be in the gpio group. This isn't mentioned.
2. People often ignore parts of
What you are describing is typical behavior for electronics and is
something you need to pay attention to. According to the OSD3358 vendor, if
power is not applied to the chip, voltage should not be applied to any of
its pins. You should either design a circuit to prevent this, or design
your
This is pretty common behavior. TTL 232 pins have a limited drive
capability and may be sufficient to power or partially power connected
loads such as your cutie board. Your 3v measurement on the TX line is
evidence that your doing that. You are powering the system up using the ESD
diodes inside
If that were the only change and there were no hardware changes and the
eeprom is configured, it should boot. Debugging hardware problems or
anything before boot absolutely requires the serial connection on ttyS0.
You'll find plenty of posts here or elsewhere about such a cable.
On Fri, Aug 7,
Octavo has an app note about this. Basically you have to either program the
EEPROM or modify the uboot to not care.
https://octavosystems.com/app_notes/osd335x-eeprom-during-boot/
If you have the serial cable you can program the eeprom from within uboot.
I never tried that, looks like fun.
J
It's basically impossible to diagnose further without a serial cable like I
described above. But you can keep feeling blindly and might get lucky. I
have no idea what the led indicates, but it changed something.
Good luck!
On Fri, Aug 7, 2020, 5:43 PM Samuel Park wrote:
> Ok so I followed the
Indeed. Remember the OSD3358 is a 40$ part while the whole board is 80$.
It's just not a practical repair. If you were sure of the problem and swung
by my lab with the replacement, I might fix it for ten bucks or free if you
were fun to talk to. But as a business if you have to add in shipping and
It should work on an original pocket beagle. Like I told Sam Park in a
separate thread, you basically must have a serial debug adapter connected
to the device to debug u-boot issues.
I can say that I have followed rcn's instructions for building and
installing u-boot and followed octavo's
I'm off work today so I can't say exactly what versions I was using, but I
recall following the instructions verbatim and everything worked perfectly.
I suppose if your modifications to the u-boot source were bad enough, you
could cause boot to fail. If I recall correctly, I started by allowing
You might be able to modify the shutdown script so that the last thing it
does is drive your gpio to unset the power supply. I've never done that
before; we in fact used an msp430 to do what you need and more.
You can probably find more information about modifying the shutdown
procedure
eeded. This is going in a place
> where there’s no energy to be harvested…
>
> Will look into the MSP430 as well.
>
> On Jun 19, 2020, at 10:06 AM, Jim F wrote:
>
> You might be able to modify the shutdown script so that the last thing it
> does is drive your gpio to unset the po
58 matches
Mail list logo
