Last time on "I can't get the %^*$%^* wifi to work", Robert Nelson pointed
out that the issue blocking wifi is connmand, and not systemd/rfkill. I've
fixed that but have run into another issue. Wifi starts, associates and
grabs a DHCP address during init. While init is coming up, wifi closes the
Hello all.
Asking here due to forums activity and the same vendor as I have.
We need to boot the signed u-boot image.
The initial ROM loader is checking whether the key is correct and continue
loading of the image (looking at flow chart in technical reference man).
All I found is signGP util
If I'm the only one with this issue don't worry about it, please move on to
more important things.
I did test my idea using node-red on the BBG. The mqtt stuff worked nicely
with the BBW as the broker, but my read of how the exec node worked from
the info pane description was wishful thinking.
On Fri, Apr 29, 2016 at 4:41 PM, Wally Bkg wrote:
> Thanks for the suggestion but it still didn't work:
>
> Setting up bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) ...
> bb-node-red-installer:npm: [2.15.0]
> bb-node-red-installer:node: [v0.12.13]
> bb-node-red-installer:Installing: sys
Thanks for the suggestion but it still didn't work:
Setting up bb-node-red-installer (0.13.4-0rcnee1~bpo80+20160321+1) ...
bb-node-red-installer:npm: [2.15.0]
bb-node-red-installer:node: [v0.12.13]
bb-node-red-installer:Installing: systemd-0.2.6 (for node-red)
npm WARN engine systemd@0.2.6: wanted
On Fri, Apr 29, 2016 at 3:03 PM, William Hermans wrote:
> I've had really good results with this:
> https://github.com/mark-webster/node-debian.git. But the last build I
> attempted on Wheezy, on a RevC BBB failed. The error was also rather
> cryptic, so I was unable to find a cure right off. The
I've had really good results with this:
https://github.com/mark-webster/node-debian.git. But the last build I
attempted on Wheezy, on a RevC BBB failed. The error was also rather
cryptic, so I was unable to find a cure right off. The same version
compiled just fine manually though . . .
On Fri, Ap
On Fri, Apr 29, 2016 at 2:50 PM, Wally Bkg wrote:
> So the question appears to become can this system be upgraded to node-js
> 0.12.x?
>
Yeap, as root:
wget -qO- https://deb.nodesource.com/gpgkey/nodesource.gpg.key | apt-key add -
apt-get update
apt-get install apt-transport-https
echo 'deb h
So the question appears to become can this system be upgraded to node-js
0.12.x?
If it can't, I can test my idea on the RPi2 or BBG and only put a new image
on the BBW to run it where it "belongs" if it pans out.
Physical accessibility of the BBW is less than convenient now that the
hardware as
On Fri, Apr 29, 2016 at 12:49 PM, Wally Bkg <* >
wrote:
> I'm still having issues with installing the node-red & bonescript stuff.
>
> I have a BBW that has been running my IOT application 24/7 with great
> success for about the last four or five months. Its running:
> cat /etc/dogtag
> BeagleBoa
>
> *I've never had these kinds of problems with apt-get install failures on
> other Ubuntu & Debian systems.*
>
I've seen several, and in fact when udev was new, and incorporated into
Ubuntu. You could apt-get install several "applications" that fell flat on
their faces. Xen, and iSCSI tools were
I'm still having issues with installing the node-red & bonescript stuff.
I have a BBW that has been running my IOT application 24/7 with great
success for about the last four or five months. Its running:
cat /etc/dogtag
BeagleBoard.org Debian Image 2015-11-12
uname -a
Linux alarmbone 4.1.18-ti-r
Thanks, for the responses, let me clarify the problem.
In 4.1.1 i have been using overlays from "
https://github.com/RobertCNelson/bb.org-overlays"; and everything was
working fine for the last year or so except the power button ( i gave up on
this and don't remember the details, but issue was som
On Fri, Apr 29, 2016 at 1:08 AM, wrote:
> root@c0a80090:/sys/bus/w1/devices/w1_bus_master1# echo 20 >
> w1_master_max_slave_count
> bash: w1_master_max_slave_count: Permission denied
>
>
>
> Could you provide the result of running
ls -lZ w1_master_max_slave_count
--
For more options, visit ht
On Fri, Apr 29, 2016 at 11:08 AM, Grzesiek Stawik wrote:
> So i had this other issue where the power button would not trigger
> poweroff, and from time to time i try new kernel versions to see if it
> works, and i have recently switched to 4.1.22 because it does work there.
>
> But.
>
> Strange t
On the console image if you want the power button to function you
install acpid
It will shutdown the bbb on power button press AND if a battery is
connected will shutdown the bbb as well
As far as spi goes have you tried BB-SPIDEV1-00A0.dtbo or
BB-SPIDEV0-00A0.dtbo?
On 4/29/2016 9:08 AM, Grzes
So i had this other issue where the power button would not trigger
poweroff, and from time to time i try new kernel versions to see if it
works, and i have recently switched to 4.1.22 because it does work there.
But.
Strange things happen with SPI in 4.1.22, spidev is now created as
/dev/spide
Thanks William,
But this didn't help me a lot.
I have notice that the gcc --version on the board was 4.9 while the gcc
used to compile the Kernel was 5.2, so I need to upadte the gcc in order to
compile the module.
Do you know how to to this?
Thanks,
--
For more options, visit http://beaglebo
On 29 April 2016 at 14:48, 'Florian Feldbauer' via BeagleBoard
wrote:
> Using the config 9600 8N1 for testing, I get a delay of about 29.2 us
> between the falling edge of the DE/RE signal and the end of the stop bit of
> the UART.
>
> For my tests I used this dts file:
> https://github.com/Rober
On 04/29/2016 03:08 PM, Taceant Omnes wrote:
On 29 April 2016 at 13:39, 'Florian Feldbauer' via BeagleBoard
wrote:
I have to apologize for my last two mails, because I made a stupid
mistake...
If you look at the source of my test program (6th message in this thread)
I only set the SER_RS485_EN
Hello,
In my modified AM3358 board based on BBB (kernel 4.1.18, filesystem Debian
8 ) when I plug the usb , following errors are given:
root@arm:~# [ 822.883615] usb 1-1: new high-speed USB device number 2
using musb-hdrc
[ 823.003706] usb 1-1: device descriptor read/64, error -71
[ 823.233
Thanks john. I had a feeling it was something like that but i still
don't understand why some overlays
change direction on some pins. Its tough to find much information on
writing overlays out there.
In the TI pinmux tool when you define the mcasp pins default is all set
to input but there is a ch
On 29 April 2016 at 13:39, 'Florian Feldbauer' via BeagleBoard
wrote:
> I have to apologize for my last two mails, because I made a stupid
> mistake...
> If you look at the source of my test program (6th message in this thread)
> I only set the SER_RS485_ENABLED flag in the struct serial_rs485.
>
The pinmux input/output setting are only relevant when using GPIO. When using a
peripheral like McASP, the input/output are defined by the pin function. Also,
the serializers directions are defined by:
serial-dir = < /* 0: INACTIVE, 1: TX, 2: RX */
2 0 1 0
0 0 0 0
0
On 04/29/2016 12:06 PM, Taceant Omnes wrote:
On 29 April 2016 at 10:18, 'Florian Feldbauer' via BeagleBoard
wrote:
Did I miss anything? I tried this with Kernel version 4.4.6-ti-r15 as well
as 4.4.8
I mounted the SD card and deleted the initrd.img-`uname -r` file. After
that, the BeagleBone w
Thanks but I found it by myself..!
On Thursday, April 28, 2016 at 4:51:50 PM UTC+5:30, Sujit Singh wrote:
>
> I downloaded qt4-embedded on my Beaglebone black to run a qt gui on my BBB
> and display it on a touchscreen but I'm having calibration issues such as:
> root@beaglebone:~# ts_calibrate
>
Dear all,
In my modified AM3358 board based on BBB (kernel 4.1.18 , filesystem Debian
8), when I plugeed USB I get the following errors:
root@arm:~# [ 822.883615] usb 1-1: new high-speed USB device number 2
using musb-hdrc
[ 823.003706] usb 1-1: device descriptor read/64, error -71
[ 823.23
Hello,
thank you for the infos. But I´m not able to write the max slave count
value.
Of course I´m root with "sudo su".
But:
root@c0a80090:/sys/bus/w1/devices/w1_bus_master1# echo 20 >
w1_master_max_slave_count
bash: w1_master_max_slave_count: Permission denied
Why I can´t increase the value?
On 04/29/2016 12:06 PM, Taceant Omnes wrote:
On 29 April 2016 at 10:18, 'Florian Feldbauer' via BeagleBoard
wrote:
Did I miss anything? I tried this with Kernel version 4.4.6-ti-r15 as well
as 4.4.8
I mounted the SD card and deleted the initrd.img-`uname -r` file. After
that, the BeagleBone w
Dear all,
Does anyone know of problems using the quadrature detector on BBB
*3.8.13-bone70* ? It working fine on a BBB with *3.8.13-bone47*. I'm using
the same overlay file for both BBB versions. My test program does not show
any counted pulses when using *bone70*. *bone47 *works fine. The ov
On 29 April 2016 at 10:18, 'Florian Feldbauer' via BeagleBoard
wrote:
> Did I miss anything? I tried this with Kernel version 4.4.6-ti-r15 as well
> as 4.4.8
>
> I mounted the SD card and deleted the initrd.img-`uname -r` file. After
> that, the BeagleBone was booting again.
> But: Loading the BB
On 04/29/2016 09:43 AM, Florian Feldbauer wrote:
On 04/28/2016 03:47 PM, Robert Nelson wrote:
On Thu, Apr 28, 2016 at 1:56 AM, florian.feldbauer85 via BeagleBoard
wrote:
Hey,
I had a look at the kernel source at github. From the code
I would say the 8250 driver supports RS485.
On 04/28/2016 03:47 PM, Robert Nelson wrote:
On Thu, Apr 28, 2016 at 1:56 AM, florian.feldbauer85 via BeagleBoard
mailto:beagleboard@googlegroups.com>>
wrote:
Hey,
I had a look at the kernel source at github. From the code
I would say the 8250 driver supports RS485. Only the
33 matches
Mail list logo
