date:20170524

Re: [beagleboard] Multicore Support for Beagle

2017-05-24 Thread Aaron

You haven't seen the x15 yet?

https://beagleboard.org/x15



On 24 May 2017 at 21:42,  wrote:

> Hi all,
>
> I see this was asked a few years ago, are there still no further plans to
> add a multicore board to the lineup?
>
> I ask as its very likely the company I work for would have ordered one if
> there was, we use the PI 3 and its not 100% ideal, we would love an RTC, I
> know the BBB CPU has an internal one and that would have helped us,
> especially with the onboard battery charger.
>
> I have a strong suspicion that the PI 3 etc are more in demand than boards
> from beagleboard.org due to multiple cores.
>
> I know the 2 different boards (pi and BBB) are targeted to different uses,
> BBB is great for lots of sensors and robotics etc, but I think it comes
> across out dated these days in comparison to the pi especially how the pi
> has evolved a lot with a more powerful processor every couple of years.
>
> The new Octavia package is a great idea, I hope it help propel custom
> designs.
>
> Any more thoughts?
>
> Fisher
>
> --
> 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 beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/7f4d0c8b-82fe-45de-83cc-8d4077f182b1%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CALw-AjNODPu15JVEom4G179GEfqUr3NB-_LN%3Da1ys_8dAFz%3DiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Multicore Support for Beagle

2017-05-24 Thread fisher . grubb

Hi all,

I see this was asked a few years ago, are there still no further plans to add a 
multicore board to the lineup?

I ask as its very likely the company I work for would have ordered one if there 
was, we use the PI 3 and its not 100% ideal, we would love an RTC, I know the 
BBB CPU has an internal one and that would have helped us, especially with the 
onboard battery charger.

I have a strong suspicion that the PI 3 etc are more in demand than boards from 
beagleboard.org due to multiple cores.

I know the 2 different boards (pi and BBB) are targeted to different uses, BBB 
is great for lots of sensors and robotics etc, but I think it comes across out 
dated these days in comparison to the pi especially how the pi has evolved a 
lot with a more powerful processor every couple of years.

The new Octavia package is a great idea, I hope it help propel custom designs.

Any more thoughts?

Fisher

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7f4d0c8b-82fe-45de-83cc-8d4077f182b1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Can't get wifi to work on BBBW.

2017-05-24 Thread Robert Nelson

On Wed, May 24, 2017 at 4:22 PM,   wrote:
> I can't seem to get anywhere with setting up wifi on my BBBW. I installed
> latest image (Debian 8.7 2017-03-19 4GB SD IoT )
>
> Whenever i try to any wifi related command with connmanctl i get: Error
> disabling wifi tethering: Method "SetProperty" with signature "sv" on
> interface "net.connman.Technology" doesn't exist

Just grab:

http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Jessie_Snapshot_iot

i'm pretty sure what your seeing is fixed..

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYh5wx%3DwQV_T30UYq4FUAy3oztqQTWxPE8Ot8ahekK%3DjVQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] systemd question ?

2017-05-24 Thread Riko Ho


Hello everyone,

I tried to start with systemd initialization and got this message below:

=

You are in emergency mode. After logging in, typ/bin/sh: 
/home/bianchi77/buildrd

You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to
try again to boot into default mode.
/bin/sh: /home/bianchi77/buildroot/output/host/usr/sbin/sulogin: not found
You are in emergency mode. After logging in, type "journalctl -xb" to view
system logs, "systemctl reboot" to reboot, "systemct/bin/sh: 
/home/bianchi77/bud



What do you reckon I missed here ? thanks

--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*

--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/c7e83312-e932-a499-9972-875dd72b2f1e%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Can't get wifi to work on BBBW.

2017-05-24 Thread skonakov

I can't seem to get anywhere with setting up wifi on my BBBW. I installed 
latest image (Debian 8.7 2017-03-19 4GB SD IoT  

)

Whenever i try to any wifi related command with connmanctl i get: *Error 
disabling wifi tethering: Method "SetProperty" with signature "sv" on 
interface "net.connman.Technology" doesn't exist*

Here is what i get from ifconfig:

debian@beaglebone:~$ sudo ifconfig -a
can0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
  NOARP  MTU:16  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:10 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:210 

can1  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
  NOARP  MTU:16  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:10 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:211 

eth0  Link encap:Ethernet  HWaddr 50:65:83:e7:96:82  
  UP BROADCAST MULTICAST DYNAMIC  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
  Interrupt:173 

loLink encap:Local Loopback  
  inet addr:127.0.0.1  Mask:255.0.0.0
  inet6 addr: ::1/128 Scope:Host
  UP LOOPBACK RUNNING  MTU:65536  Metric:1
  RX packets:568 errors:0 dropped:0 overruns:0 frame:0
  TX packets:568 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1 
  RX bytes:43659 (42.6 KiB)  TX bytes:43659 (42.6 KiB)

usb0  Link encap:Ethernet  HWaddr 50:65:83:e7:96:84  
  inet addr:192.168.7.2  Bcast:192.168.7.3  Mask:255.255.255.252
  inet6 addr: fe80::5265:83ff:fee7:9684/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:544 errors:0 dropped:0 overruns:0 frame:0
  TX packets:355 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:51090 (49.8 KiB)  TX bytes:67281 (65.7 KiB)

usb1  Link encap:Ethernet  HWaddr 50:65:83:e7:96:87  
  inet addr:192.168.6.2  Bcast:192.168.6.3  Mask:255.255.255.252
  inet6 addr: fe80::5265:83ff:fee7:9687/64 Scope:Link
  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
  RX packets:106 errors:0 dropped:0 overruns:0 frame:0
  TX packets:57 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000 
  RX bytes:16310 (15.9 KiB)  TX bytes:12855 (12.5 KiB)



Have you guys seen this problem, or have any idea on what i can try to fix 
it?

Thanks,
Sergey Konakov

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/2ec699ee-778a-42bd-85e4-9ce6d5fa1bd0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] See if I understand setting up a device tree for the PRU

2017-05-24 Thread Charles Steinkuehler

On 5/17/2017 9:37 PM, Clark Sann wrote:
> 
> Signal  Signal name on  Mode from Data
>  Octavo per BB Blue   Sheet Table 4-1
>  schematic
> 
> MDIR 1A GPIO2_0_T13  7
> MDIR 1B UART4_TX0_U176
> MDIR 2A CP101_16_R137
> MDIR 2B LCD_DATA14_V40
> PWM 1A  EHRPWM1A_U14   6
> 
> The mode setting I have chosen is the mode that causes the pin to have the 
> signal name shown on the BB Blue schematic.
> 
> Do I have my mode settings correct?

Probably not, unless you plan to use the UART, PWM, and LCD hardware
to drive your motor coils.

You probably want to set all the pins to mode 7 (GPIO).  The PRU can
write to the GPIO control registers with minimal delay and latency.

-- 
Charles Steinkuehler
char...@steinkuehler.net

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/bfc90fcf-e962-d70c-615a-185fb683f189%40steinkuehler.net.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: UART5 not working on Beaglebone Black

2017-05-24 Thread Graham Haddock

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 connectors?

Do you have a serial debug cable plugged in?  Is it giving you any boot
errors or conflicts?

==

Why are you planning to mess with I2C-1 ?  On Debian jessie, that is an
internal control bus you should not touch, unless you really know what you
are doing.


I suspect that:
BB-BONELT-HDMI,BB-BONELT-HDMIN
only disables the HDMI, not the LCD drivers, and you should only disable
the HDMI once, not twice.

I am guessing that you still need to disable the LCD drivers.


--- Graham


---



On Wed, May 24, 2017 at 10:04 AM,  wrote:

> I tried uncommenting the lines in /boot/uEnv.txt about disabling HDMI, but
> it did not help. I also tried typing in
> *optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3,BB-UART5* at
> the end of that file.
> Then I was trying to type optargs=quiet 
> capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN
> in order to explicitly disable the HDMI in the /boot/uEnv.txt, but it
> didn't help either.
>
> It appears that HDMI is not enabled there whatsoever since in the slots
> file I don't have anything dedicated to it:
> *root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots*
> * 0: PF  -1*
> * 1: PF  -1*
> * 2: PF  -1*
> * 3: PF  -1*
> * 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-I2C1*
> * 6: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-UART1*
> * 7: P-O-L-   2 Override Board Name,00A0,Override Manuf,BB-UART2*
> * 8: P-O-L-   3 Override Board Name,00A0,Override Manuf,BB-UART4*
> * 9: P-O-L-   4 Override Board Name,00A0,Override Manuf,BB-UART5*
> *10: P-O-L-   5 Override Board Name,00A0,Override Manuf,BB-UART3*
>
> Are there any other possible sources of UART5 not working, aside from it
> interfering with HDMI? I tried several different boards and SD cards, but
> the port did not work on any of them.
>
>
>
> On Monday, May 22, 2017 at 9:47:08 PM UTC-4, Graham wrote:
>>
>> The IO pins used by UART5 are, by default, assigned to driving an LCD
>> screen.
>> You will need to reconfigure the IO, so that LCD/video is disabled, and
>> the pins are re-assigned as UART I/O pins.
>> You will need to modify the boot file and device tree.
>> Start searching about how to edit the /boot/uEnv.text file, and your
>> different options for re-configuring the necessary pins.
>>
>> --- Graham
>>
>> ==
>>
>> On Monday, May 22, 2017 at 8:04:06 PM UTC-5, sspo...@bu.edu wrote:
>>>
>>> I am using a Beaglebone Black on a student project. In order to activate
>>> the UART5 port, I type in “echo BB-UART5 > 
>>> /sys/devices/platform/bone_capemgr/slots”
>>> every time I power the board on. However, even though the port does seem to
>>> be activated, uart5 never works for any of the BBB’s I try (other UART
>>> ports on them work as well as usual) . What can cause such problems
>>> specifically with UART5? How can I fix it?
>>>
>> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to a topic in the
> Google Groups "BeagleBoard" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/
> topic/beagleboard/3Rby6pdTUCg/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> beagleboard+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/beagleboard/54415aca-e655-4107-9c36-da720d79a5d5%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CANN_KV5S3LVUEfQCpjUy-kJU94axR9uvX6SCWO_cYWNuWg94dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: UART5 not working on Beaglebone Black

2017-05-24 Thread ssposnov

I tried uncommenting the lines in /boot/uEnv.txt about disabling HDMI, but 
it did not help. I also tried typing in 
*optargs=capemgr.enable_partno=BB-UART1,BB-UART2,BB-UART3,BB-UART5* at the 
end of that file.
Then I was trying to type optargs=quiet 
capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN in order to 
explicitly disable the HDMI in the /boot/uEnv.txt, but it didn't help 
either.

It appears that HDMI is not enabled there whatsoever since in the slots 
file I don't have anything dedicated to it:
*root@beaglebone:~# cat /sys/devices/platform/bone_capemgr/slots*
* 0: PF  -1*
* 1: PF  -1*
* 2: PF  -1*
* 3: PF  -1*
* 4: P-O-L-   0 Override Board Name,00A0,Override Manuf,BB-I2C1*
* 6: P-O-L-   1 Override Board Name,00A0,Override Manuf,BB-UART1*
* 7: P-O-L-   2 Override Board Name,00A0,Override Manuf,BB-UART2*
* 8: P-O-L-   3 Override Board Name,00A0,Override Manuf,BB-UART4*
* 9: P-O-L-   4 Override Board Name,00A0,Override Manuf,BB-UART5*
*10: P-O-L-   5 Override Board Name,00A0,Override Manuf,BB-UART3*

Are there any other possible sources of UART5 not working, aside from it 
interfering with HDMI? I tried several different boards and SD cards, but 
the port did not work on any of them.



On Monday, May 22, 2017 at 9:47:08 PM UTC-4, Graham wrote:
>
> The IO pins used by UART5 are, by default, assigned to driving an LCD 
> screen.
> You will need to reconfigure the IO, so that LCD/video is disabled, and 
> the pins are re-assigned as UART I/O pins.
> You will need to modify the boot file and device tree.
> Start searching about how to edit the /boot/uEnv.text file, and your 
> different options for re-configuring the necessary pins.
>
> --- Graham
>
> ==
>
> On Monday, May 22, 2017 at 8:04:06 PM UTC-5, sspo...@bu.edu wrote:
>>
>> I am using a Beaglebone Black on a student project. In order to activate 
>> the UART5 port, I type in “echo BB-UART5 > 
>> /sys/devices/platform/bone_capemgr/slots” every time I power the board on. 
>> However, even though the port does seem to be activated, uart5 never works 
>> for any of the BBB’s I try (other UART ports on them work as well as usual) 
>> . What can cause such problems specifically with UART5? How can I fix it?
>>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/54415aca-e655-4107-9c36-da720d79a5d5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: Development environment for BBB and Win 7 64 bit for C-programming

2017-05-24 Thread Graham

I have used the same tool chain (in various versions) for Angstrom, wheezy 
and jessie on the BBB without problems.

I think some of the recent security changes in BBB jessie might need to be 
loosened during development, 
(I like to develop in root on the BBB) but once the application is running 
you can move it wherever you want 
and set the security back to maximum.

--- Graham

On Tuesday, May 23, 2017 at 10:12:07 PM UTC-5, William Hermans wrote:
>
> He's got 4-5 videos all on the same topic. Well . . .at least 3 anyway. I 
> still think Ubuntu is the best option, because I know how temperamental 
> Debian can be( for this purpose ). But it does look better with Jessie 
> perhaps ? I'm still using Wheezy on my support system but the only cross 
> compiling I do is with the kernel, and that will change soon when I get my 
> ODROID XU4 development support system up and running. "Building" the case 
> as we speak . . .
>
> On Tue, May 23, 2017 at 7:49 PM, Graham Haddock  > wrote:
>
>> William:
>> Great.  Derek did update his video, although he still refers to the 
>> original one on his website.
>> --- 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, send an email 
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/1769f94c-45bc-43b1-b72f-c8bc24285626%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] pru-rproc failing on boot, working manually

2017-05-24 Thread Greg

This behavior started, I think when the Debian Jessie distribution appeared.
Prior to that, the PRUs started up at boot perfectly as far as I could tell.

Later, post-Jessie, I worked around it with similar methods to what you are 
doing.
I didn't consider it a serious problem since I could start up with either 
.profile or .bashrc.  
My projects are hobby/learning so not for serious embedded deployment.  It 
would be good to understand what is going on!

You can also try this:

echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/bind
echo "4a338000.pru1" > /sys/bus/platform/drivers/pru-rproc/bind

and this

echo "4a334000.pru0" > /sys/bus/platform/drivers/pru-rproc/unbind
echo "4a338000.pru1"  > /sys/bus/platform/drivers/pru-rproc/unbind

If the above commands work, this might provide an additional clue as to 
what is going on at boot.

I'm hoping to get back on another PRU project soon, would be nice to get 
this mystery resolved!

Regards,
Greg

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/dd125e46-9c99-4d95-a9b7-ac79c40274a8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] pru-rproc failing on boot, working manually

2017-05-24 Thread Hugh Frater

Looks like this kind-of works now... dmesg doesn't show any errors, but a 
/dev entry for rpmsg_pru31 is only created if I manually cycle an rrmod -f 
pru_rproc, modprobe pru_rproc...

Is this because the pru's are booting before the /dev filesystem kernel 
modules are loaded?

On Thursday, 18 May 2017 15:27:34 UTC+1, RobertCNelson wrote:
>
> On Thu, May 18, 2017 at 5:54 AM, Hugh Frater  > wrote: 
> > Despite googling the heck out of this simple problem, I can't find 
> > anything... 
> > 
> > Problem is: 
> > 
> > [   34.358783]  remoteproc1: 4a338000.pru1 is available 
> > [   34.358802]  remoteproc1: Note: remoteproc is still under development 
> and 
> > considered experimental. 
> > [   34.358811]  remoteproc1: THE BINARY FORMAT IS NOT YET FINALIZED, and 
> > backward compatibility isn't yet guaranteed. 
> > [   34.359092]  remoteproc1: Direct firmware load for am335x-pru1-fw 
> failed 
> > with error -2 
> > [   34.359113]  remoteproc1: failed to load am335x-pru1-fw 
> > [   34.371827] pru-rproc 4a338000.pru1: booting the PRU core manually 
> > [   34.371857]  remoteproc1: powering up 4a338000.pru1 
> > [   34.371968]  remoteproc1: Direct firmware load for am335x-pru1-fw 
> failed 
> > with error -2 
> > [   34.371985]  remoteproc1: request_firmware failed: -2 
> > [   34.377200] pru-rproc 4a338000.pru1: rproc_boot failed 
> > [   34.493128]  remoteproc1: releasing 4a338000.pru1 
> > [   34.493310] pru-rproc: probe of 4a338000.pru1 failed with error -2 
> > 
> > The firmware file is present, it works - I just have to load it manually 
> > once I've booted with: 
> > 
> > sudo rmmod -f pru_rproc 
> > sudo modprobe pru_rproc 
> > 
> > Is there a known issue with enabling the PRU's at boot? 
>
> Thanks for the bug, the firmware wasn't getting copied to the 
> initramfs, just pushed a fix, and should hit the apt repo shortly: 
>
>
> https://github.com/rcn-ee/repos/commit/2922f56ce8ab70771944f7eb99d7fd10f8a52b6a
>  
>
> [   10.478212] ti-pruss 4a30.pruss: creating PRU cores and other 
> child platform devices 
> [   10.478410] irq: no irq domain found for 
> /ocp/pruss@4a30/intc@4a32 ! 
> [   10.499594] irq: no irq domain found for 
> /ocp/pruss@4a30/intc@4a32 ! 
> [   10.562246]  remoteproc1: 4a338000.pru1 is available 
> [   10.599505] pru-rproc 4a338000.pru1: booting the PRU core manually 
> [   10.599538]  remoteproc1: powering up 4a338000.pru1 
> [   10.599836]  remoteproc1: Booting fw image am335x-pru1-fw, size 35392 
> [   10.599913]  remoteproc1: remote processor 4a338000.pru1 is now up 
> [   10.599951] pru-rproc 4a338000.pru1: PRU rproc node 
> /ocp/pruss@4a30/pru1@4a338000 probed successfully 
> [   10.602814]  remoteproc2: 4a334000.pru0 is available 
> [   10.604856] pru-rproc 4a334000.pru0: booting the PRU core manually 
> [   10.604883]  remoteproc2: powering up 4a334000.pru0 
> [   10.605156]  remoteproc2: Booting fw image am335x-pru0-fw, size 36296 
> [   10.605225]  remoteproc2: remote processor 4a334000.pru0 is now up 
> [   10.605260] pru-rproc 4a334000.pru0: PRU rproc node 
> /ocp/pruss@4a30/pru0@4a334000 probed successfully 
>
> Regards, 
>
> -- 
> Robert Nelson 
> https://rcn-ee.com/ 
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/39afa0bc-9140-4173-9f0e-fb253867ccfe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] avahi question ?

2017-05-24 Thread Riko Ho


Hi Robert,

Where can I find avahi setting ? Is that the service that giving me "ssh 
to 192.168.7.2" ?


Thanks

--
*

/***/
Sent by Ubuntu LTS 16.04,
谢谢,
Regards,
Riko Ho
/***/

*

--
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/e81cad26-49ba-30ae-707d-ca30d4946f94%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Flashing eMMC memory from SD card with Chipsee Debian Jessie

2017-05-24 Thread Radovan Chovan

I saw the thread https://sourceforge.net/p/win32diskimager/tickets/9/ 
before, but nothing helped to me.
I 've used Win32DiskImager v0.8. I see, it exists v1.0 on sourgeforge.net. 

Dňa utorok, 23. mája 2017 16:33:31 UTC+2 Dennis Lee Bieber napísal(-a):
>
> On Mon, 22 May 2017 23:36:28 -0700 (PDT), Radovan Chovan 
>  declaimed the following: 
>
> >Thanks for your time. 
> >I tried your instructions, I have 
> > 
> >Disk 1 
> >Removable (F:\) 
> >No Media 
> > 
> >But still no success with Win32DiskImager. I got Lock Error: An error 
> >occurred when attempting to lock the volume. Error 5: Access is denied. I 
> >tried to reboot my PC but it didn't help. 
> > 
> Sounds like some other program is running in the background that 
> has 
> taken ownership of the drive. Though a Google search seems to blame the 
> card reader itself: 
> https://openenergymonitor.org/forum-archive/node/3240.html 
> while others blame music players and anti-virus: 
> https://answers.launchpad.net/win32-image-writer/+question/205161 
> (though that is old enough that the author claims a change in processing 
> at 
> the end). A more up-to-date thread is: 
> https://sourceforge.net/p/win32diskimager/tickets/9/ 
> which had updates in December... How old is your copy of the program? The 
> current download appears to be only 2.5 months old. 
>
>
>
>
> >As I wrote in my last post I solved this problem using VirtualBox with 
> >Ubuntu, so please consider the problem resolved. 
> > 
> >D?a pondelok, 22. mája 2017 17:27:56 UTC+2 Dennis Lee Bieber napísal(-a): 
> >> 
> >> On Sun, 21 May 2017 23:12:20 -0700 (PDT), Radovan Chovan 
> >>  declaimed the following: 
> >> 
> >> >I used MiniTool Partition Wizard for finding out partition 
> rootfs(ext4). 
> >> >But I  cannot add drive letter to this partiton. 
> >> 
> >> It does not surprise me -- Windows really only works with NTFS 
> and 
> >> (ex)FAT formats. 
> >> 
> >> However, the card reader slot itself should have a drive letter 
> >> (mine 
> >> show up even with no card inserted). If you have NO drive letters for 
> the 
> >> card reader slots then you may need to use the disk management console 
> >> ("my 
> >> computer"/"this computer" -- right click/manage... Storage/Disk 
> >> Management). 
> >> 
> >> The top will only show mounted "drives" (those with a file 
> system 
> >> Windows recognizes). The bottom will show each physical drive with 
> regions 
> >> indicating the partitioning. For a Windows format, the drive letter 
> will 
> >> be 
> >> in the partition area -- for empty card reader slots, the drive letter 
> is 
> >> on the left side, such as: 
> >> 
> >> Disk 4 (G:) 
> >> Removable 
> >> No Media 
> >> 
> >> Disk 5 (H:) 
> >> Removable 
> >> No Media 
> >> 
> >> Disk 6 
> >> Removable 
> >> No Media 
> >> 
> >> 4 is my SD card slot, 5 is my CF card slot. 6 (and 7) are 
> Memory 
> >> Stick 
> >> and some other little used card format. There is a reason they do not 
> have 
> >> drive letters -- I removed them so they wouldn't show up, as I do not 
> have 
> >> any cards in those formats. 
> >> 
> >> If your SD card slot has no drive letter, right click on the 
> "disk 
> >> #" 
> >> and select "Change drive letter and paths". [ADD], (it should present 
> the 
> >> next available drive letter by default), [OK], [OK] 
> >> 
> >> -- 
> >> Wulfraed Dennis Lee Bieber AF6VN 
> >> wlf...@ix.netcom.com 
> HTTP://wlfraed.home.netcom.com/ 
> >> 
> >> 
> -- 
> Wulfraed Dennis Lee Bieber AF6VN 
> wlf...@ix.netcom.com HTTP://wlfraed.home.netcom.com/ 
>
>

-- 
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 beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/ee806b51-f33b-4408-877d-b85498082b8d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Multicore Support for Beagle

Re: [beagleboard] Multicore Support for Beagle

Re: [beagleboard] Can't get wifi to work on BBBW.

[beagleboard] systemd question ?

[beagleboard] Can't get wifi to work on BBBW.

Re: [beagleboard] See if I understand setting up a device tree for the PRU

Re: [beagleboard] Re: UART5 not working on Beaglebone Black

[beagleboard] Re: UART5 not working on Beaglebone Black

Re: [beagleboard] Re: Development environment for BBB and Win 7 64 bit for C-programming

Re: [beagleboard] pru-rproc failing on boot, working manually

Re: [beagleboard] pru-rproc failing on boot, working manually

[beagleboard] avahi question ?

[beagleboard] Re: Flashing eMMC memory from SD card with Chipsee Debian Jessie

13 matches

Site Navigation

Mail list logo

Footer information