So . . .
ioctl(3, RTC_WIE_ON or RTC_WKALM_SET, {enabled=1, pending=0, {tm_sec=56,
tm_min=20, tm_hour=5, tm_mday=4, tm_mon=4, tm$
fstat64(1, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 0), ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xb6f0b000
write(1,
william@beaglebone:~$ uname -r
4.4.8-ti-r22
william@beaglebone:~$ sudo su
root@beaglebone:/home/william# echo mem > /sys/power/state
bash: echo: write error: Invalid argument
Not sure if this is helpful.
root@beaglebone:/home/william# lsmod
Module Size Used by
bnep
Yeah I don't know . . . something seems to be terribly broken.
william@beaglebone:~$ uname -r
4.1.22-ti-r59
william@beaglebone:~$ sudo su
root@beaglebone:/home/william# echo mem > /sys/power/state
bash: echo: write error: Invalid argument
Next up, I'm going ot attempt to get it working with the
Ah, ok my bad i missed it. You used a 4.4 regular ( non rt ) kernel.
On Tue, May 3, 2016 at 8:03 PM, William Hermans wrote:
> Robert, did you test "mem" on an rt kernel or regular ?
>
> On Tue, May 3, 2016 at 8:02 PM, Robert Nelson
> wrote:
>
>>
>>
Robert, did you test "mem" on an rt kernel or regular ?
On Tue, May 3, 2016 at 8:02 PM, Robert Nelson
wrote:
>
>
> On Tue, May 3, 2016 at 9:59 PM, William Hermans wrote:
>
>> root@beaglebone:/home/william# echo mem > /sys/power/state
>> bash: echo:
On Tue, May 3, 2016 at 9:59 PM, William Hermans wrote:
> root@beaglebone:/home/william# echo mem > /sys/power/state
> bash: echo: write error: Invalid argument
> root@beaglebone:/home/william# uname -r
> 4.1.22-ti-rt-r59
>
> Replacing "mem", with "disk" pretends to work, but
root@beaglebone:/home/william# echo mem > /sys/power/state
bash: echo: write error: Invalid argument
root@beaglebone:/home/william# uname -r
4.1.22-ti-rt-r59
Replacing "mem", with "disk" pretends to work, but it does not.
william@beaglebone:~$ time sudo rtcwake -m disk -s 60 && ls
rtcwake:
On Tue, May 3, 2016 at 8:10 PM, wrote:
> Should power management functions (mem/standby) be working with 4.x TI
> kernels on the BeagleBone Black for at least some subset of hardware
> versions? Or was full support intentionally disabled due to hardware
> related
>
> I've just got caught out by this myself. I wanted to reproduce build
> 4.4.6-ti-r15. So I cloned
> https://github.com/RobertCNelson/ti-linux-kernel-dev.git and checked out
> the 4.4.6-ti-r15 tag. But I got a similar error with the patch.
>
> I think what I was trying to do was a reasonable
Should power management functions (mem/standby) be working with 4.x TI
kernels on the BeagleBone Black for at least some subset of hardware
versions? Or was full support intentionally disabled due to hardware
related issues?
I've been using 3.14 TI kernels with the rtcwake command (both mem
On Wednesday, 16 March 2016 13:01:02 UTC+11, RobertCNelson wrote:
>
> On Tue, Mar 15, 2016 at 2:25 PM, Carlo Zolfo > wrote:
> > I've actually already answered the question, as I found the TI kernel
> src
> > code under:
> > $ git clone
Misunderstanding Did
I'm sorry
--
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
Maybe this is a clue, to get node-red installed on Ubuntu 16.04 I had to
install nodejs-legacy, so I tried installing it on my BBW.
This is what I get:
~# apt-get install nodejs-legacy
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages
Well, it's not really the API's that's the problem, networking it's self.
You *could* test the output of ifconfig canX, then parse for "UP" or
"DOWN". Or you can perhaps test the /proc/ pseudo file system *somehow* to
check if the device is up or not. After that, you can continue, or attempt
to
I *think* I started with the wrong image (console) - it worked when I used
an lxqt image.
On Tue 3 May 2016 14:20 wrote:
> I have the same issue. Do you found the solution?
>
>
> On Saturday, April 2, 2016 at 1:43:59 AM UTC+3, James S wrote:
>>
>> Still not working, even
Is there a way to check if Linux networking API's are ready or not using
some command?
On Tuesday, May 3, 2016 at 4:05:01 PM UTC-4, William Hermans wrote:
>
> *Thank you very much. I will try to implement your suggested ways.*
>>
>> *Right now I am actually using service routine that executes
>
> *Thank you very much. I will try to implement your suggested ways.*
>
> *Right now I am actually using service routine that executes the script
> that initializes the CAN. *
> *At the start of script I have given delay of 20 seconds.*
>
No problem.
SO here is what I am guessing that
Thank you very much. I will try to implement your suggested ways.
Right now I am actually using service routine that executes the script
that initializes the CAN.
At the start of script I have given delay of 20 seconds.
On Tuesday, May 3, 2016 at 3:44:19 PM UTC-4, William Hermans wrote:
>
>
Thanks Robert.
I probably would not need SPI or I2C, as I'd implement my own library.
Which is really very easy, as nodejs has a filesystem class object.
I'll give this a go later as we're busy out doors taking care of spring
things today . . .
On Tue, May 3, 2016 at 12:17 PM, Robert Nelson
Ok, so how do you fix the problem ? manually bring the CANBUS interface up
? If that is te case, then you need to start your script later in the boot
process. Using rc.d may do the trick, but in case you're already using
rc.d, then you may need to setup a cron job to 30 seconds after boot, or
On Mon, May 2, 2016 at 7:49 PM, William Hermans wrote:
> By "installling" I mean I'll be compiling my own Nodejs 4.x from source,
> and creating a package.
>
There's only one deb* package in the base install that can't handle nodejs
v4.x.
bb-bonescript-installer-beta
remove
sorry, mean:
2. can´t used, right?
Am Dienstag, 3. Mai 2016 20:25:43 UTC+2 schrieb hoerting...@gmx.at:
>
> Hello!
>
> 1. Oh, so W1 control both Pins? I thought that each PIN is handle by his
> own ... sure, then a second bus did not help!
> 2. Not sure if I unterstand you. When this feature is
Hello!
1. Oh, so W1 control both Pins? I thought that each PIN is handle by his
own ... sure, then a second bus did not help!
2. Not sure if I unterstand you. When this feature is not supported by
Kernel driver, I can used, right?
Thank you!
--
For more options, visit
Check out man pages for
- lsmod: list loaded kernel modules
- modprobe: load or unload modules
BR
--
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
1.) The cable radius is the same, regardless if you use one or two pins for
the W1 bus. So it only makes a difference regarding the cable weight, wich
isn't as critical as the radius.
2.) To speed up the conversation time trigger all sensors by a broadcast
message. After a delay of 750 ms you
Ok Thanks guys,
Identified and fixed the effected pin and now getting consistent boots.
Cheers,
On Monday, May 2, 2016 at 2:33:54 PM UTC-7, CEinTX wrote:
>
> I have seen this too.
> It is as Gerald says. Your cape is loading one or more of the boot pins.
> I did a cape - even though all the
Have you solved the problem that you were having? I am unsure why you are
getting the error:
P9_42 pinmux file not found!
cape-universala overlay not found
I am currently trying to figure out how the PWM pins work in the 4.1+
Kernel and it appears that after each reboot the *pwmchip** links
I have script that runs at startup which initializes the CAN communication
on my BBB. Whenever I restart my BBB this script does work most of the
times, I would say 7 out of 10.
Once the CAN is up successfully it never stops in middle of working. Then I
generally use Candump to fetch all the
Next, step, which i do.
I followed by https://eewiki.net/display/linuxonarm/BeagleBoard with v4.5.x
kernel and debian-8.4-minimal-armhf-2016-04-22.tar.xz
Second, i upgraded uboot
http://elinux.org/BeagleBoardNAND#U-Boot_v2011.12_or_newer
>
> *Can you please tell me how does sometimes the CAN network goes down on
> rebooting the BBB?*
>
No, I can only guess because you're not giving enough information. But if I
had to guess right now I'd say you're having a script / driver module race
condition. But even that does not sound 100%
>
> *Yes. I do have a script that runs at startup. *
>
> *Even if I try to run that script manually it shows the same error.*
>
Ok, you're still not being very verbose. Tell us everything you can think
of, preferably in order. When does it not work ? when does it work ? Does
it ever stop working
Yes. I do have a script that runs at startup.
Even if I try to run that script manually it shows the same error.
Can you please tell me how does sometimes the CAN network goes down on
rebooting the BBB?
On Tuesday, May 3, 2016 at 12:58:11 PM UTC-4, William Hermans wrote:
>
> Of course the can
OK cool. I'm still wanting to stick with 4.1.x*bone* but since for the
given project I'm working on I do not need uio_pruss - Maybe I'll use the
TI kernel instead.
I had also noticed in the past that the TI kernels used slightly less
memory at boot too. But only because the *bone* kernel was
Yes. I do have a script that runs at startup.
Even if I try to run that script manually it shows the same error.
On Tuesday, May 3, 2016 at 12:58:11 PM UTC-4, William Hermans wrote:
>
> Of course the can network goes down when you reboot the system, but you
> need to be more clear as to what
Of course the can network goes down when you reboot the system, but you
need to be more clear as to what your problem is. Do you have a script that
runs on startup that is failing, or what ?
On Tue, May 3, 2016 at 9:48 AM, Akash Gajeshwar
wrote:
> Hello,
>
> I am using
On Tue, May 3, 2016 at 11:47 AM, William Hermans wrote:
> *sgx = no comment...*
>>
>> *Regards,*
>
>
> heh yeah, it's only been 3 years TI . . .just for the beaglebone black
> platform.
>
> Robert, TI kernel still has usable power management ? Or is this no longer
> a
>
> *sgx = no comment...*
>
> *Regards,*
heh yeah, it's only been 3 years TI . . .just for the beaglebone black
platform.
Robert, TI kernel still has usable power management ? Or is this no longer
a difference between the two ?
On Tue, May 3, 2016 at 9:23 AM, Robert Nelson
All these network managers are evil. I mean seriously how hard is it to use
/etc/network/interfaces ? /etc/resolv.conf ?
But I forget why you all are using connman, and it seemed like a good
reason, I just wont use that feature myself. static IP's and all . . .
On Tue, May 3, 2016 at 9:40 AM,
Hello,
I am using "Waveshare CAN Cape" for sending CAN messages from Beaglebone
Black. I communicate with Beaglebone using ethernet by making SSH
connection and I have latest Debian OS on BBB.
Sometimes when I restart the Beaglebone it shows an error message
saying "Network is down". Because
On Tue, May 3, 2016 at 11:34 AM, Micka wrote:
> Hi,
>
> I'm using debian 8 for the beaglebone black ...
>
> I discovered that the beaglebone switch to connman to manage the network ?
> why ? that more complicate than using the file /etc/network/interfaces
>
> I've
Hi,
I'm using debian 8 for the beaglebone black ...
I discovered that the beaglebone switch to connman to manage the network ?
why ? that more complicate than using the file /etc/network/interfaces
I've difficulties with the nameserver, normally it's in the file
/etc/resolv.conf, but with
On Tue, May 3, 2016 at 9:58 AM, wrote:
> Hello all,
>
> I've noticed some bad HDMI jitter/flickering when using the -bone kernel,
> which is present both in 3.14 and latest 4.1. However this flickering is
> not present when using the -ti kernel, regardless of the version; the
On Tue, May 3, 2016 at 9:55 AM, wrote:
> Hi,
>
> So my BBB recently arrived and I plugged it in for the first time today.
> When I connected the USB cable as expected the FAT partition popped up and
> I followed the instructions and clicked on the start.htm (opened in
Am Dienstag, 3. Mai 2016 16:41:57 UTC+2 schrieb TJF:
>
> What happens when you pass the parameter at module load time? (In order to
> test, unload the kernel driver and reload with option
> w1_max_slave_count=30 )
>
Hello!
Many thanks for your help, but I don´t know how to load at module
Hi,
So my BBB recently arrived and I plugged it in for the first time today.
When I connected the USB cable as expected the FAT partition popped up and
I followed the instructions and clicked on the start.htm (opened in chrome).
I got to the screen below and continued to install the drivers
Hello all,
I've noticed some bad HDMI jitter/flickering when using the -bone kernel,
which is present both in 3.14 and latest 4.1. However this flickering is
not present when using the -ti kernel, regardless of the version; the -ti
version is used by default in rcn's netinstall script.
Hello!
Because of 2 points:
a) wire length
b) different poll times
I want to poll temperature as fast as possible (now around 800ms) ... when
I use many temperatur sensors, it takes long to poll all sensors. So I want
to use a second bus to increase polling speed.
--
For more options, visit
On Tue, May 3, 2016 at 10:17 AM, Mian Tang wrote:
> Hi,
>
> I'm working on BeagleBone Black, and the kernel version is 3.8.13-bone70.
> I want to bring the BBB to sleep mode and then wake up by the following
> commands:
>
> echo mem > /sys/power/state, and results in
Hi,
I'm working on BeagleBone Black, and the kernel version is 3.8.13-bone70. I
want to bring the BBB to sleep mode and then wake up by the following
commands:
echo mem > /sys/power/state, and results in "echo: write error: No such
device"
On the other hand, when I configure RTC wakeup, such
What happens when you pass the parameter at module load time? (In order to
test, unload the kernel driver and reload with option w1_max_slave_count=30
)
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
On Mon, May 2, 2016 at 8:42 PM, Virendra wrote:
>
> Hi,
>
> I have an issue with the current custom image(kernel_version=4.1.20) where
> the image advertises itself as a disk image. I didn't have this issue in
> the previous version of image(3.8.13-bone74.2). The previous
On Tue, May 3, 2016 at 3:21 AM, Kazz wrote:
> Hi all
>
> Now
> The contents of Ubuntu-2016-04-07 prebuild image is Debian Wheezy ?
>
Care to try that again?
voodoo@hades:/opt/images/elinux/2016-04-07/microsd$ sudo bmaptool copy
I have the same issue. Do you found the solution?
On Saturday, April 2, 2016 at 1:43:59 AM UTC+3, James S wrote:
>
> Still not working, even tried rebooting.
>
> debian@beaglebone:/opt/gfxinstall$ sudo /etc/init.d/sgx-startup.sh start
> sgx: Starting PVR
> debian@beaglebone:/opt/gfxinstall$ lsmod
just use the bbb battery connector.
it works fine
then use a small micro for the watchdog/power monitoring
my hardware does this and then after a power down cuts the battery
with proper timing the bbb can stay up for ever
On 5/3/2016 4:54 AM, Yiannis Papelis wrote:
> Fair enough.
>
> I think what
check the schematic of this cape
http://www.logicsupply.com/cbb-serial/
On 5/3/2016 2:02 AM, hoerting.busin...@gmx.at wrote:
> Hello,
>
> I want to add RS485 on UART4.
>
> I found:
> https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART4-RS485-00A0.dts
>
> But can´t
Fair enough.
I think what I am leaning on doing is providing 5V directly to the VDD_5V
connector with a diode fused battery+external power through a controllable
regulator, and then using a tiny micro (most likely a PIC) to monitor power
loss and then trigger an interrupt on a pin to cause the
Hello!
the command "getenforce" are not available on my system.
--
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
Hello,
I want to add RS485 on UART4.
I found:
https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-UART4-RS485-00A0.dts
But can´t compile the dts.
root@c0a80090:/home/user/bb.org-overlays/src/arm# dtc -O dtb -o
BB-UART4-RS485-00A0.dtbo -b 0 -@ BB-UART4-RS485-00A0.dts
Error:
On 3 May 2016 at 09:21, Kazz wrote:
> Hi all
>
> Now
> The contents of Ubuntu-2016-04-07 prebuild image is Debian Wheezy ?
No
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
Hi friends,
I m using Beaglebone black in *android OS* , plz help me code for GPIO
(read, write & direction set) using *memory mapped*.
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard"
Hi all
Now
The contents of Ubuntu-2016-04-07 prebuild image is Debian Wheezy ?
--
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
Hi,
I flashed my beaglebone black with Debian Jessie 8.3 too. The LCD 7'0 (4D
System) works fine with the board. The LCD's manual mentions Angstrom but
doesn't mention Debian distribution (section 3.2). For my experience, it's
compatible with the beaglebone black.
For information:
*$ uname
Thanks! It compiles... testing in the morning. :)
-p
On Mon, May 2, 2016 at 4:24 PM, William Hermans wrote:
> https://groups.google.com/forum/#!searchin/beagleboard/Problemas$20para$20comunicar$20com$20o$20Baud$20Rate$205760/beagleboard/GC0rKe6rM0g/13c1ngXF7owJ
>
> Read the
>
> *Everyone keeps using the same sentence "you're asking for trouble" but
> without any more details on why that is the case. I get the file system
> corruption issue, just wanting to make sure there isn't anything else.*
>
I think Gerald already stated this, but I think it's worth repeating.
64 matches
Mail list logo