In future you may wish to run dmesg command to see what the kernel
registers the device as instead of "guessing". HTH
On Wednesday, January 16, 2019 at 11:37:14 AM UTC+8, Graham wrote:
>
> It looks like it does show up as a ttyACM0 device, rather than a ttyUSB0
> device.
> Now I need to get it
Please share their reply when you receive it. I have their direct email and
can share if they dont reply you
On Monday, January 7, 2019 at 10:24:05 PM UTC+8, mallets wrote:
>
> Their estimate shipping options has many countries missing, so that's what
> I was basing it on. Contacted them
Did they confirm that they only ship to limited countries?
On Saturday, January 5, 2019 at 2:42:33 PM UTC+8, mallets wrote:
>
> Ahh, doesn't ship to many countries. Wish they were sold through resellers
> like Arrow, element14 and such.
>
> On Friday, December 14, 2018 at 11:22:59 AM UTC+5:30,
Seems like there is an equivalent of BBB Industrial with 1GB ram available
for pre order from San Cloud, shipping 14th Jan 2019. I wonder if it can
run the images from Robert Nelson, though I am guessing that they probably
would
https://www.sancloud.co.uk/?p=2101
With regards to the customisations, they are in deb package
bb-customisations. So apt upgrade does the job
$ sudo dpkg -S /etc/udev/rules.d/60-omap-tty.rules
bb-customizations: /etc/udev/rules.d/60-omap-tty.rules
On Saturday, December 8, 2018 at 5:52:12 PM UTC+8, Luther Goh Lu Feng wrote:
>
>
I customise my own Debian Stretch image based off a console image dated 04
Apr 2018. I just stumbled upon bb-customisations in this repo:
https://github.com/rcn-ee/repos/tree/master/bb-customizations/suite/stretch/debian
Question: Do I get these customisations if I just simply do a sudo apt
May I ask if the BBB Industrial boards from Special Computing are identical
to the one from Element14[1]?
--Luther
[1]
https://www.element14.com/community/docs/DOC-78671/l/element14-beaglebone-black-industrial-4g-based-on-sitara-am3358-processor
On Wednesday, November 21, 2018 at 9:17:25 AM
Fwiw, this is running on a Beaglebone black, and running a customised
version of Debian 9 built off RCN's console image
--Luther
On Friday, November 16, 2018 at 10:47:14 AM UTC+8, Luther Goh Lu Feng wrote:
>
> Hi all,
>
> I have a kernel panic with 4.19.0-ti-r2. Any ideas how to address this ?
On Saturday, October 6, 2018 at 9:38:47 PM UTC+8, Luther Goh Lu Feng wrote:
>
> Is it appropriate to set vm.swappiness=0 for my BBB running on Debian on
> the microSD, since the OS doesnt have swap?
>
> --Luther
>
Seems like for a system with no swap, setting vm.swappiness has no effect
Is it appropriate to set vm.swappiness=0 for my BBB running on Debian on the
microSD, since the OS doesnt have swap?
--Luther
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To
I am unfamiliar with how the repo. But it may be helpful to give an idea
what sort of conflicts there are? Maybe in a gist?
--Luther
On Friday, October 5, 2018 at 12:22:26 PM UTC+8, Enoch wrote:
>
> Hi Robert Nelson & Friends,
>
> I have a local Linux kernel repository that tracks
>
Any idea who we can nudge to try and get the patch backported to the long
term kernels? Greg Kroah-Hartman says that there hasn't been any
backporting word done yet
--Luther
On Thursday, June 7, 2018 at 6:04:18 AM UTC+8, RobertCNelson wrote:
>
> On Tue, Jun 5, 2018 at 12:15 PM, Robert Nelson
What are the major differences between TI's kernel and v4.4.x-bone kernel?
--Luther
On Friday, April 13, 2018 at 9:30:01 PM UTC+8, RobertCNelson wrote:
>
> On Thu, Apr 12, 2018 at 11:40 PM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups.com > wrote:
> >
If i am not mistaken, latest version in the repos is 4.4.113-r149, while
kernel.org's latest version is 4.4.127. Is this intentional, ie a known issue?
--Luther
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
As shared by Robert [1], the command to retrieve the serial number is as
follows:
sudo hexdump -e '8/1 "%c"' /sys/bus/i2c/devices/0-0050/eeprom -n 28 |
cut -b 5-28
Is there anyway to get the serial number without using sudo? My use case is
that I wish to let other programs use the serial
Is there a way to get the serial number without using sudo?
--Luther
On Tuesday, February 20, 2018, 12:59:42 AM GMT+8, Robert Nelson
wrote:
On Mon, Feb 19, 2018 at 10:50 AM, Luther Goh Lu Feng wrote:
> For clarity, the difference is as
On Monday, February 19, 2018, 11:01:39 AM GMT+8, 'Luther Goh Lu Feng' via
BeagleBoard <beagleboard@googlegroups.com> wrote:
When available, the contents of
`/sys/devices/platform/bone_capemgr/baseboard/serial-number` and
`/sys/bus/i2c/devices/0-0050/eeprom` differ. Are they expecte
When available, the contents of
`/sys/devices/platform/bone_capemgr/baseboard/serial-number` and
`/sys/bus/i2c/devices/0-0050/eeprom` differ. Are they expected to be the same
or are they 2 different type of serial numbers altogether? And are both unique?
Thanks!
--Luther
On Friday,
I would also like to know when the U-boot overlays changed from being inactive
to being active. Is it specifically during the reboot into the new kernel?
--Luther
On Thursday, February 15, 2018, 1:33:38 PM GMT+8, 'Luther Goh Lu Feng' via
BeagleBoard <beagleboard@googlegroups.com>
On Wed, Feb 14, 2018 at 9:16 PM, 'Luther Goh Lu Feng' via BeagleBoard
<beagleboard@googlegroups.com> wrote:
> I am running a custom image of Debian Stretch on BBB, downgraded to
> 4.4.54-ti-r93. On this image,
> /sys/devices/platform/bone_capemgr/baseboard/serial-number exists. Howe
I am running a custom image of Debian Stretch on BBB, downgraded
to 4.4.54-ti-r93. On this
image, /sys/devices/platform/bone_capemgr/baseboard/serial-number exists.
However after I perform an upgrade to 4.4.113-ti-r146 using sudo
/opt/scripts/tools/update_kernel.sh --ti-channel --lts-4_4,
I like console as it is very minimal and allows me to just add on stuff I
need. So I skip any "bloat"
--Luther
On Thursday, January 18, 2018 at 5:54:52 AM UTC+8, Rick M wrote:
>
> Thanks. What’s “console” then?
>
> --
> Rick Mann
> rm...@latencyzero.com
>
> > On Jan 17, 2018, at 13:49,
I see. I am actually more inclined to use 4.4.x-ti as it is listed as being
supported till Feb 2022
On Thursday, January 18, 2018 at 1:07:16 AM UTC+8, RobertCNelson wrote:
>
> On Wed, Jan 17, 2018 at 12:38 AM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups
Downloading the Stretch IoT (non-GUI) from beagleboard.org[1] yields an image
with kernel 4.4.91-ti-r133. A Stretch IOT image from Robert Nelson[2] has
kernel 4.9.74-ti-r90. My question specifically is: why the difference, and is
one preferable over the other? Thanks
[1]
-image-4.4.110-ti-r142 using apt?
On Friday, January 12, 2018 at 2:06:48 AM UTC+8, RobertCNelson wrote:
>
> On Wed, Jan 10, 2018 at 9:48 PM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups.com > wrote:
> > I am running a stretch console image[1] on a BBB industrial. A
> What hardware are you running?
Beaglebone Black Industrial
> Where is power supply connected?
5V 1.25 A power supply
> Which specific Stretch image are you running?
https://rcn-ee.com/rootfs/bb.org/testing/2018-01-07/stretch-console/bone-debian-9.3-console-armhf-2018-01-07-1gb.img.xz
On a related note, I will also be curious of the longest uptimes that you
have for images based on Stretch. I have created images based on a console
image in Sep last year, and I realised recently that these images typically
dont have uptimes more than a week. Most will reboot once every few
I am running a stretch console image[1] on a BBB industrial. After letting it
run for about 24 hrs, the system rebooted. Inspecting syslog[2], it doesnt
seemed to explain the reboot.
The only thing that could be suspicious is cron.hourly. Any thoughts?
Jan 10 02:08:56 beaglebone systemd[1]:
I am under the impression that BBB is affected as it runs AM335x 1GHz ARM®
Cortex-A8. What are the mitigations/recommendations to address this, if any?
--Luther
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google
Console is the most minimal of them all. You can probably use that as a
base to install your other requirements
On Friday, December 22, 2017 at 6:31:17 PM UTC+8, Paul Van den Bergh wrote:
>
> Hi All,
>
> On https://elinux.org/BeagleBoard:BeagleBoneBlack_Debian there are four
> kind of 'flavors'
I have a multi paritioned microSD card as follows. P1 is the boot partition, P2
and P3 are rootfs partitions. Based on my investigations, I have ensured both
P2 and P3 are bootable rootfs. By default, the BBB will boot to P2. By adding
mmcpart=3 in /boot/uEnv.txt, I can let the BBB boot to P3.
I am trying to debug some reboot issues and noticed that the output from $ last
show the wrong timestamps as follows. It seems like this has been previously
highlighted on the mailing list[1]. The recommended solution seems to be to use
fake-hwclock[2]. I am wondering if there is a reason this
different drive geometries means that the 1MB of each storage medium
>> contains other drive specific stuff, together with the MLO and u-boot, and
>> therefore results in differences in the 1MB content for each drive?
>>
>>
>> --Luther
>> On Thursday,
19, 2017 at 3:45:14 AM UTC+8, RobertCNelson wrote:
>>
>> On Wed, Oct 18, 2017 at 2:41 PM, 'Luther Goh Lu Feng' via BeagleBoard
>> <beagl...@googlegroups.com> wrote:
>> > Given that the eMMC and microSD has different drive geometries[1], what
>> is
>>
In my experience, instead of relying on the indicator lights, I use a
serial console cable to see the progress on a BBB Industrial. I use a
console image to flash the eMMC and that works fine. This should translate
to the other images produced by Robert Nelson.
--Luther
On Wednesday, October
>
> On Wed, Oct 18, 2017 at 2:41 PM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups.com > wrote:
> > Given that the eMMC and microSD has different drive geometries[1], what
> is
> > the correct way of backing up and restoring the MLO and u-boot from o
Given that the eMMC and microSD has different drive geometries[1], what is the
correct way of backing up and restoring the MLO and u-boot from one medium to
another? eg from eMMC to microSD or from microSD to eMMC.
--Luther
[1] https://groups.google.com/d/msg/beagleboard/4HTJt7J2M8w/3qdig-7hBQAJ
I am assuming the answer is yes based on what was discussed in this thread[1].
Next question. If I flash the eMMC using the microSD card debian flasher
script, and then dd out 1MB from the eMMC and microSD, do I expect both to have
the same shasum? I expect yes, since they came from the same
I understand that in the default boot priority, which is the eMMC followed by
the microSD, the MLO and u-boot resides in the eMMC.In the case where the eMMC
does not contain a valid boot image, the microSD gets booted.
Question: does a bootable microSD contain a copy of the MLO and uboot?
I am new to imaged based systems. Am wondering if it is possible to use an OTA
update system like mender and use it on an debian image. Please share your
insights and experiences
https://mender.io/blog/porting-mender-to-a-non-yocto-build-system
I understand that even though BBB boots from the eMMC first, if a bootable
microSD is inserted, it will boot from the microSD[1]. I believe uboot is
responsible for this behaviour and would like modify uboot.
- How would I go about doing it?
- Is it a matter of modifying uEnv.txt or a
As above subject
--
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
1. I believe you can only install the armhf version of Ubuntu
2. In my general opinion, Debian Jessie is better supported on the
Beaglebone than Ubuntu. They are probably equally supported by Docker
On Tuesday, July 25, 2017 at 11:06:15 AM UTC+8, Bobby Schmidt wrote:
>
> I recently got a BBBlue
Given that a BBB has just booted from a microSD card, I am wondering if it is
possible to reversibly modify the microSD card on the BBB, while it is booted,
ie via the commandline, so that on reboot, it will no longer boot from the
microSD card but from the eMMC.
And upon booting from the eMMC,
This is more of an intellectual curiosity, as I am wondering if it is a
loophole to maliciously brick a BBB. Any idea if this is possible?
--Luther
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
On Tue, Jun 20, 2017 at 9:55 PM, 'Luther Goh Lu Feng' via BeagleBoard
<beagleboard@googlegroups.com> wrote:
> That's interesting. I was always under the impression that the console image
> was used as a base for the other images. Any rough rough forecast that I
> wont be holding y
I have customised a BBB image using the console image. This includes
configurations and additional software packages installed. I have written some
software tests as well.
Question: how should I have the BBB as part of a continuous integration and
auto test environment workflow where a new BBB
:
>
> On Tue, Jun 20, 2017 at 1:14 PM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups.com > wrote:
> > I was looking for the Stretch bone debian console image but did not find
> it[1]. Though there seems to be other stretch images available[2]. Is there
&
I was looking for the Stretch bone debian console image but did not find it[1].
Though there seems to be other stretch images available[2]. Is there any
specific reason why a Stretch console image isnt made available? Thanks.
--Luther
[1]
As an additional datapoint, I also see identical messages appearing in the
output of dmesg
--Luther
On Wednesday, May 10, 2017 at 3:39:49 AM UTC+8, Luther Goh Lu Feng wrote:
>
> I have connected a console session using a serial console cable[1], on a
> custom Debian Jessie console image.
Though obscure, I am unsure if this is related to the issue I highlighted
here[1]. I would suggest connecting a console cable and see if there is any
output during boot. Thanks.
--Luther
[1]https://groups.google.com/d/msg/beagleboard/ritwRgywoUY/9XCJFJ6aAgAJ
On Tuesday, April 25, 2017 at
I had a successful boot on my BBB, and then managed to login, but then device
started hanging. I plugged in the serial console cable and saw the below error
in the console. After some time, maybe about 5 min, the system un-hung. Kernel
version: 4.4.54-ti-r93. Appreciate if there are any
Based on my research, I believe that it is possible to get a temperature
reading from the built-in sensor[1]. But I also read that the temperature
reading obtained will be extremely unreliable. I would like to confirm that
effort to get readings from the builtin sensor wont be worth it as the
at I'm using
> this without connman.
>
> Micka,
>
> Le mer. 22 mars 2017 à 09:11, 'Luther Goh Lu Feng' via BeagleBoard <
> beagl...@googlegroups.com > a écrit :
>
>> I seek to understand why connman is included in the BBB image?
>>
>> Without going in
I seek to understand why connman is included in the BBB image?
Without going into details, generally it doesn't seem to be without issues.
It seems that there are other users[1] uninstalling and using the
/etc/network/interfaces.
Any issues that could possibly arise with connman
On Tuesday, March 21, 2017 at 10:00:44 PM UTC+8, RobertCNelson wrote:
>
> On Tue, Mar 21, 2017 at 2:43 AM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups.com > wrote:
> > I am trying to build an image using image builder[1].
> >
> >
> >
I am trying to build an image using image builder[1].
I seek clarity on the correct approach if I intend to only build a console
image. The steps I took are based on README.md in the repo
Running ./beagleboard.org_image.sh seems to generate all the images. Can I
clarify what is the best way
I seek clarity on the changelog between various snapshot releases of the
console image[1].
On a related note, I have built a console image using OMAP image builder[2] was
hoping to rebuild the console and tag it to a particular release/version. How
do I do that?
I understand that there is
Are you looking for multiple submissions for the same board?
On Monday, March 20, 2017 at 9:28:11 PM UTC+8, kiran.k...@gmail.com wrote:
>
> Hi,
>
> FYI,
> Jason, Christine (of BB) requested me to pass my message on to this
> community
> so that I get help from volunteers. Here is my
rg/Beagleboard:BeagleBoneBlack_Debian
>
> There are other intermediate builds that may or may not have completed
> testing.
>
> --- Graham
>
> ==
>
> On Sat, Mar 18, 2017 at 10:09 PM, 'Luther Goh Lu Feng' via BeagleBoard <
> beagl...@googlegroups.com > wrote:
&g
Thanks for sharing. I just discovered that the latest console image on that
domain is
https://debian.beagleboard.org/images/rcn-ee.net/rootfs/bb.org/testing/2017-02-26/console/.
I assume I should try that instead of
to help send a pull request if the
> site is on a github repo :)
>
> [1] https://beagleboard.org/latest-images
>
> On Thursday, March 16, 2017 at 9:42:40 PM UTC+8, RobertCNelson wrote:
>>
>> On Thu, Mar 16, 2017 at 8:21 AM, 'Luther Goh Lu Feng' via BeagleBoard
>> &l
is on a github repo :)
[1] https://beagleboard.org/latest-images
On Thursday, March 16, 2017 at 9:42:40 PM UTC+8, RobertCNelson wrote:
>
> On Thu, Mar 16, 2017 at 8:21 AM, 'Luther Goh Lu Feng' via BeagleBoard
> <beagl...@googlegroups.com > wrote:
> > The precise reason why I wi
The precise reason why I wish to use the console image is because I needed the
small footprint to minimise the attack interface. I have built up my own BBB
image on top of the console image. The IoT image does not meet my requirements
as it requires substantial effort to strip down.
Does
A few weeks ago, I was using the image I found at
https://rcn-ee.com/rootfs/bb.org/testing/2017-02-12/
Today, I found that the image has disappeared, which was not totally
unexpected. Since it is supposed to be a snapshot. My question: is there a
stable console image that we can refer to that
I also found this barefs and I am curious if that is relevant to me as well
https://eewiki.net/display/linuxonarm/BeagleBone+Black#BeagleBoneBlack-RootFileSystem(smallflash)
On Tuesday, February 28, 2017 5:10 PM, Luther Goh Lu Feng
wrote:
I attempted to find a minimal
I attempted to find a minimal console image and found the IoT image on the
latest firmware images page[1]. Subsequently, I discovered a console image[2].
Please correct me if I am wrong, but I believe that the console image is even
more striped down the the IoT image.
Questions:
- Is there a
Someone has offered to build for me an Ubuntu Core image with a kernel
build off the mainline Linux kernel. I would like to confirm that it will
be more optimal if the mainline kernel build have the patches listed
here[1] applied, ie the mainline kernel will have issues running off the
BBB.
I
I realised that there are constantly new Debian testing snapshosts[1]. I
would like to know where I can see the changelog of these snapshots.
Also, I would like to know how to apply those deltas to an existing image
that I have. Is it it a matter of just $ apt upgrade? Thanks.
-- Luther
[1]
c 18, 2016, at 7:37 PM, 'Luther Goh Lu Feng' via BeagleBoard
<beagleboard@googlegroups.com> wrote:
>
>
>
>On Monday, December 19, 2016 at 4:04:47 AM UTC+8, William Hermans wrote:
>
>>
>>On Sun, Dec 18, 2016 at 1:00 PM, 'Luther Goh Lu Feng' via BeagleBoard
>
On Monday, December 19, 2016 at 4:04:47 AM UTC+8, William Hermans wrote:
>
>
> On Sun, Dec 18, 2016 at 1:00 PM, 'Luther Goh Lu Feng' via BeagleBoard <
> beagl...@googlegroups.com > wrote:
>
>> Noted your comments. In case it isn't clear, I am referring to Ubuntu
>
Hi there,
I am having a conversation with the Ubuntu Core community to figure out how
to get BBB supported in the long run. I am posting the thread link here in
case anyone is interested in this as well
https://lists.ubuntu.com/archives/snapcraft/2016-December/002086.html
--
For more
Hi there,
I am trying to install Ubuntu Core 16 on the Beaglebone black. Is this the
right place to seek help? I cant seem to find the documentation on how to
utilise the beagleblack gadget snap. Will be grateful if someone can point
me to the relevant documentation.
Am aware of
73 matches
Mail list logo