date:20160229

Re: [beagleboard] 4.1.16-bone18 #26 PREEMPT & CPU stuck for 90 second

2016-02-29 Thread Micka

But the CPU is stuck for 90 second, is that normal ?

Micka,

Le mar. 1 mars 2016 à 08:56, John Syne  a écrit :

> It is not a bug.
>
> https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt
>
> Regards,
> John
>
>
>
>
> On Feb 29, 2016, at 11:15 PM, Micka  wrote:
>
> Hi,
>
> I run 3 process doing serial test ( write on ttyO with a 5ms sleep between
> each send ) and i got this yesterday :
>
> [28744.255809] INFO: rcu_preempt self-detected stall on CPU
> [28744.255852]  0: (1 ticks this GP) idle=af5/1/0 softirq=1389832/1389832
> fqs=0
> [28744.255862]   (t=9593 jiffies g=880748 c=880747 q=3814)
> [28744.255874] rcu_preempt kthread starved for 9593 jiffies!
> [28744.255881] Task dump for CPU 0:
> [28744.255889] swapper R running  0 0  0 0x0002
> [28744.255962] [] (unwind_backtrace) from []
> (show_stack+0x11/0x14)
> [28744.255990] [] (show_stack) from []
> (rcu_dump_cpu_stacks+0x6b/0xac)
> [28744.256011] [] (rcu_dump_cpu_stacks) from []
> (rcu_check_callbacks+0x3fb/0x704)
> [28744.256030] [] (rcu_check_callbacks) from []
> (update_process_times+0x2f/0x54)
> [28744.256051] [] (update_process_times) from []
> (tick_sched_handle+0x21/0x4c)
> [28744.256065] [] (tick_sched_handle) from []
> (tick_sched_timer+0x3f/0x68)
> [28744.256078] [] (tick_sched_timer) from []
> (__run_hrtimer+0x61/0x1e0)
> [28744.256090] [] (__run_hrtimer) from []
> (hrtimer_interrupt+0xcb/0x220)
> [28744.256109] [] (hrtimer_interrupt) from []
> (omap2_gp_timer_interrupt+0x23/0x28)
> [28744.256136] [] (omap2_gp_timer_interrupt) from []
> (handle_irq_event_percpu+0x5b/0x174)
> [28744.256151] [] (handle_irq_event_percpu) from []
> (handle_irq_event+0x39/0x58)
> [28744.256168] [] (handle_irq_event) from []
> (handle_level_irq+0x8b/0xd8)
> [28744.256183] [] (handle_level_irq) from []
> (generic_handle_irq+0x23/0x2c)
> [28744.256195] [] (generic_handle_irq) from []
> (__handle_domain_irq+0x57/0xac)
> [28744.256208] [] (__handle_domain_irq) from []
> (omap_intc_handle_irq+0x85/0x8c)
> [28744.256236] [] (omap_intc_handle_irq) from []
> (__irq_svc+0x3b/0x80)
> [28744.256245] Exception stack(0xc0a4ff50 to 0xc0a4ff98)
> [28744.256255] ff40: 0001 
>  c001c041
> [28744.256265] ff60: c0a4e000 c0a510f8   c0b01a48 0001
> c0aebb70 c0a51104
> [28744.256275] ff80: c0a4e03c c0a4ff98 c000efff c000f000 4033 
> [28744.256294] [] (__irq_svc) from []
> (arch_cpu_idle+0x28/0x2c)
> [28744.256314] [] (arch_cpu_idle) from []
> (cpu_startup_entry+0x1e1/0x248)
> [28744.256346] [] (cpu_startup_entry) from []
> (start_kernel+0x33f/0x348)
> [28744.256441] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 90s!
> [swapper:0]
> [28744.256450] Modules linked in: tda998x usb_f_acm u_serial usb_f_rndis
> g_multi usb_f_mass_storage u_ether libcomposite ti_am335x_adc rtc_ds1307
> tmp102 mma8452 snd_soc_tlv320aic3x snd_soc_davinci_mcasp snd_soc_edma
> snd_soc_omap snd_soc_core ad799x industrialio_triggered_buffer kfifo_buf
> snd_compress snd_pcm_dmaengine industrialio gpio_mcp23s08 snd_pcm snd_seq
> snd_seq_device uio_pruss tilcdc snd_timer omap_aes omap_sham omap_rng
> drm_kms_helper rng_core snd spi_omap2_mcspi ti_am335x_tsc soundcore
> ti_am335x_tscadc uio_pdrv_genirq leds_gpio uio
> [28744.256588] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.16-bone18 #26
> [28744.256594] Hardware name: Generic AM33XX (Flattened Device Tree)
> [28744.256603] task: c0a552f0 ti: c0a4e000 task.ti: c0a4e000
> [28744.256615] PC is at arch_cpu_idle+0x28/0x2c
> [28744.256624] LR is at arch_cpu_idle+0x27/0x2c
> [28744.256633] pc : []lr : []psr: 4033
> [28744.256633] sp : c0a4ff98  ip : c0a4e03c  fp : c0a51104
> [28744.256642] r10: c0aebb70  r9 : 0001  r8 : c0b01a48
> [28744.256649] r7 :   r6 :   r5 : c0a510f8  r4 : c0a4e000
> [28744.256657] r3 : c001c041  r2 :   r1 :   r0 : 0001
> [28744.256667] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb
>  Segment kernel
> [28744.256675] Control: 50c5387d  Table: 9deb0019  DAC: 0015
> [28744.256684] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.16-bone18 #26
> [28744.256690] Hardware name: Generic AM33XX (Flattened Device Tree)
> [28744.256707] [] (unwind_backtrace) from []
> (show_stack+0x11/0x14)
> [28744.256732] [] (show_stack) from []
> (watchdog_timer_fn+0x191/0x1c4)
> [28744.256747] [] (watchdog_timer_fn) from []
> (__run_hrtimer+0x61/0x1e0)
> [28744.256759] [] (__run_hrtimer) from []
> (hrtimer_interrupt+0xcb/0x220)
> [28744.256773] [] (hrtimer_interrupt) from []
> (omap2_gp_timer_interrupt+0x23/0x28)
> [28744.256791] [] (omap2_gp_timer_interrupt) from []
> (handle_irq_event_percpu+0x5b/0x174)
> [28744.256804] [] (handle_irq_event_percpu) from []
> (handle_irq_event+0x39/0x58)
> [28744.256819] [] (handle_irq_event) from []
> (handle_level_irq+0x8b/0xd8)
> [28744.256832] [] (handle_level_irq) from []
> (generic_handle_irq+0x23/0x2c)
>

Re: [beagleboard] 4.1.16-bone18 #26 PREEMPT & CPU stuck for 90 second

2016-02-29 Thread John Syne

It is not a bug.

https://www.kernel.org/doc/Documentation/RCU/stallwarn.txt 


Regards,
John




> On Feb 29, 2016, at 11:15 PM, Micka  wrote:
> 
> Hi,
> 
> I run 3 process doing serial test ( write on ttyO with a 5ms sleep between 
> each send ) and i got this yesterday :
> 
> [28744.255809] INFO: rcu_preempt self-detected stall on CPU
> [28744.255852]  0: (1 ticks this GP) idle=af5/1/0 softirq=1389832/1389832 
> fqs=0
> [28744.255862]   (t=9593 jiffies g=880748 c=880747 q=3814)
> [28744.255874] rcu_preempt kthread starved for 9593 jiffies!
> [28744.255881] Task dump for CPU 0:
> [28744.255889] swapper R running  0 0  0 0x0002
> [28744.255962] [] (unwind_backtrace) from [] 
> (show_stack+0x11/0x14)
> [28744.255990] [] (show_stack) from [] 
> (rcu_dump_cpu_stacks+0x6b/0xac)
> [28744.256011] [] (rcu_dump_cpu_stacks) from [] 
> (rcu_check_callbacks+0x3fb/0x704)
> [28744.256030] [] (rcu_check_callbacks) from [] 
> (update_process_times+0x2f/0x54)
> [28744.256051] [] (update_process_times) from [] 
> (tick_sched_handle+0x21/0x4c)
> [28744.256065] [] (tick_sched_handle) from [] 
> (tick_sched_timer+0x3f/0x68)
> [28744.256078] [] (tick_sched_timer) from [] 
> (__run_hrtimer+0x61/0x1e0)
> [28744.256090] [] (__run_hrtimer) from [] 
> (hrtimer_interrupt+0xcb/0x220)
> [28744.256109] [] (hrtimer_interrupt) from [] 
> (omap2_gp_timer_interrupt+0x23/0x28)
> [28744.256136] [] (omap2_gp_timer_interrupt) from [] 
> (handle_irq_event_percpu+0x5b/0x174)
> [28744.256151] [] (handle_irq_event_percpu) from [] 
> (handle_irq_event+0x39/0x58)
> [28744.256168] [] (handle_irq_event) from [] 
> (handle_level_irq+0x8b/0xd8)
> [28744.256183] [] (handle_level_irq) from [] 
> (generic_handle_irq+0x23/0x2c)
> [28744.256195] [] (generic_handle_irq) from [] 
> (__handle_domain_irq+0x57/0xac)
> [28744.256208] [] (__handle_domain_irq) from [] 
> (omap_intc_handle_irq+0x85/0x8c)
> [28744.256236] [] (omap_intc_handle_irq) from [] 
> (__irq_svc+0x3b/0x80)
> [28744.256245] Exception stack(0xc0a4ff50 to 0xc0a4ff98)
> [28744.256255] ff40: 0001  
>  c001c041
> [28744.256265] ff60: c0a4e000 c0a510f8   c0b01a48 0001 
> c0aebb70 c0a51104
> [28744.256275] ff80: c0a4e03c c0a4ff98 c000efff c000f000 4033 
> [28744.256294] [] (__irq_svc) from [] 
> (arch_cpu_idle+0x28/0x2c)
> [28744.256314] [] (arch_cpu_idle) from [] 
> (cpu_startup_entry+0x1e1/0x248)
> [28744.256346] [] (cpu_startup_entry) from [] 
> (start_kernel+0x33f/0x348)
> [28744.256441] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 90s! 
> [swapper:0]
> [28744.256450] Modules linked in: tda998x usb_f_acm u_serial usb_f_rndis 
> g_multi usb_f_mass_storage u_ether libcomposite ti_am335x_adc rtc_ds1307 
> tmp102 mma8452 snd_soc_tlv320aic3x snd_soc_davinci_mcasp snd_soc_edma 
> snd_soc_omap snd_soc_core ad799x industrialio_triggered_buffer kfifo_buf 
> snd_compress snd_pcm_dmaengine industrialio gpio_mcp23s08 snd_pcm snd_seq 
> snd_seq_device uio_pruss tilcdc snd_timer omap_aes omap_sham omap_rng 
> drm_kms_helper rng_core snd spi_omap2_mcspi ti_am335x_tsc soundcore 
> ti_am335x_tscadc uio_pdrv_genirq leds_gpio uio
> [28744.256588] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.16-bone18 #26
> [28744.256594] Hardware name: Generic AM33XX (Flattened Device Tree)
> [28744.256603] task: c0a552f0 ti: c0a4e000 task.ti: c0a4e000
> [28744.256615] PC is at arch_cpu_idle+0x28/0x2c
> [28744.256624] LR is at arch_cpu_idle+0x27/0x2c
> [28744.256633] pc : []lr : []psr: 4033
> [28744.256633] sp : c0a4ff98  ip : c0a4e03c  fp : c0a51104
> [28744.256642] r10: c0aebb70  r9 : 0001  r8 : c0b01a48
> [28744.256649] r7 :   r6 :   r5 : c0a510f8  r4 : c0a4e000
> [28744.256657] r3 : c001c041  r2 :   r1 :   r0 : 0001
> [28744.256667] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb  Segment 
> kernel
> [28744.256675] Control: 50c5387d  Table: 9deb0019  DAC: 0015
> [28744.256684] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.16-bone18 #26
> [28744.256690] Hardware name: Generic AM33XX (Flattened Device Tree)
> [28744.256707] [] (unwind_backtrace) from [] 
> (show_stack+0x11/0x14)
> [28744.256732] [] (show_stack) from [] 
> (watchdog_timer_fn+0x191/0x1c4)
> [28744.256747] [] (watchdog_timer_fn) from [] 
> (__run_hrtimer+0x61/0x1e0)
> [28744.256759] [] (__run_hrtimer) from [] 
> (hrtimer_interrupt+0xcb/0x220)
> [28744.256773] [] (hrtimer_interrupt) from [] 
> (omap2_gp_timer_interrupt+0x23/0x28)
> [28744.256791] [] (omap2_gp_timer_interrupt) from [] 
> (handle_irq_event_percpu+0x5b/0x174)
> [28744.256804] [] (handle_irq_event_percpu) from [] 
> (handle_irq_event+0x39/0x58)
> [28744.256819] [] (handle_irq_event) from [] 
> (handle_level_irq+0x8b/0xd8)
> [28744.256832] [] (handle_level_irq) from [] 
> (generic_handle_irq+0x23/0x2c)
> [28744.256844] [] (generic_handle_irq) from []

[beagleboard] 4.1.16-bone18 #26 PREEMPT & CPU stuck for 90 second

2016-02-29 Thread Micka

Hi,

I run 3 process doing serial test ( write on ttyO with a 5ms sleep between
each send ) and i got this yesterday :

[28744.255809] INFO: rcu_preempt self-detected stall on CPU
[28744.255852]  0: (1 ticks this GP) idle=af5/1/0 softirq=1389832/1389832
fqs=0
[28744.255862]   (t=9593 jiffies g=880748 c=880747 q=3814)
[28744.255874] rcu_preempt kthread starved for 9593 jiffies!
[28744.255881] Task dump for CPU 0:
[28744.255889] swapper R running  0 0  0 0x0002
[28744.255962] [] (unwind_backtrace) from []
(show_stack+0x11/0x14)
[28744.255990] [] (show_stack) from []
(rcu_dump_cpu_stacks+0x6b/0xac)
[28744.256011] [] (rcu_dump_cpu_stacks) from []
(rcu_check_callbacks+0x3fb/0x704)
[28744.256030] [] (rcu_check_callbacks) from []
(update_process_times+0x2f/0x54)
[28744.256051] [] (update_process_times) from []
(tick_sched_handle+0x21/0x4c)
[28744.256065] [] (tick_sched_handle) from []
(tick_sched_timer+0x3f/0x68)
[28744.256078] [] (tick_sched_timer) from []
(__run_hrtimer+0x61/0x1e0)
[28744.256090] [] (__run_hrtimer) from []
(hrtimer_interrupt+0xcb/0x220)
[28744.256109] [] (hrtimer_interrupt) from []
(omap2_gp_timer_interrupt+0x23/0x28)
[28744.256136] [] (omap2_gp_timer_interrupt) from []
(handle_irq_event_percpu+0x5b/0x174)
[28744.256151] [] (handle_irq_event_percpu) from []
(handle_irq_event+0x39/0x58)
[28744.256168] [] (handle_irq_event) from []
(handle_level_irq+0x8b/0xd8)
[28744.256183] [] (handle_level_irq) from []
(generic_handle_irq+0x23/0x2c)
[28744.256195] [] (generic_handle_irq) from []
(__handle_domain_irq+0x57/0xac)
[28744.256208] [] (__handle_domain_irq) from []
(omap_intc_handle_irq+0x85/0x8c)
[28744.256236] [] (omap_intc_handle_irq) from []
(__irq_svc+0x3b/0x80)
[28744.256245] Exception stack(0xc0a4ff50 to 0xc0a4ff98)
[28744.256255] ff40: 0001 
 c001c041
[28744.256265] ff60: c0a4e000 c0a510f8   c0b01a48 0001
c0aebb70 c0a51104
[28744.256275] ff80: c0a4e03c c0a4ff98 c000efff c000f000 4033 
[28744.256294] [] (__irq_svc) from []
(arch_cpu_idle+0x28/0x2c)
[28744.256314] [] (arch_cpu_idle) from []
(cpu_startup_entry+0x1e1/0x248)
[28744.256346] [] (cpu_startup_entry) from []
(start_kernel+0x33f/0x348)
[28744.256441] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 90s!
[swapper:0]
[28744.256450] Modules linked in: tda998x usb_f_acm u_serial usb_f_rndis
g_multi usb_f_mass_storage u_ether libcomposite ti_am335x_adc rtc_ds1307
tmp102 mma8452 snd_soc_tlv320aic3x snd_soc_davinci_mcasp snd_soc_edma
snd_soc_omap snd_soc_core ad799x industrialio_triggered_buffer kfifo_buf
snd_compress snd_pcm_dmaengine industrialio gpio_mcp23s08 snd_pcm snd_seq
snd_seq_device uio_pruss tilcdc snd_timer omap_aes omap_sham omap_rng
drm_kms_helper rng_core snd spi_omap2_mcspi ti_am335x_tsc soundcore
ti_am335x_tscadc uio_pdrv_genirq leds_gpio uio
[28744.256588] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.16-bone18 #26
[28744.256594] Hardware name: Generic AM33XX (Flattened Device Tree)
[28744.256603] task: c0a552f0 ti: c0a4e000 task.ti: c0a4e000
[28744.256615] PC is at arch_cpu_idle+0x28/0x2c
[28744.256624] LR is at arch_cpu_idle+0x27/0x2c
[28744.256633] pc : []lr : []psr: 4033
[28744.256633] sp : c0a4ff98  ip : c0a4e03c  fp : c0a51104
[28744.256642] r10: c0aebb70  r9 : 0001  r8 : c0b01a48
[28744.256649] r7 :   r6 :   r5 : c0a510f8  r4 : c0a4e000
[28744.256657] r3 : c001c041  r2 :   r1 :   r0 : 0001
[28744.256667] Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA Thumb
 Segment kernel
[28744.256675] Control: 50c5387d  Table: 9deb0019  DAC: 0015
[28744.256684] CPU: 0 PID: 0 Comm: swapper Not tainted 4.1.16-bone18 #26
[28744.256690] Hardware name: Generic AM33XX (Flattened Device Tree)
[28744.256707] [] (unwind_backtrace) from []
(show_stack+0x11/0x14)
[28744.256732] [] (show_stack) from []
(watchdog_timer_fn+0x191/0x1c4)
[28744.256747] [] (watchdog_timer_fn) from []
(__run_hrtimer+0x61/0x1e0)
[28744.256759] [] (__run_hrtimer) from []
(hrtimer_interrupt+0xcb/0x220)
[28744.256773] [] (hrtimer_interrupt) from []
(omap2_gp_timer_interrupt+0x23/0x28)
[28744.256791] [] (omap2_gp_timer_interrupt) from []
(handle_irq_event_percpu+0x5b/0x174)
[28744.256804] [] (handle_irq_event_percpu) from []
(handle_irq_event+0x39/0x58)
[28744.256819] [] (handle_irq_event) from []
(handle_level_irq+0x8b/0xd8)
[28744.256832] [] (handle_level_irq) from []
(generic_handle_irq+0x23/0x2c)
[28744.256844] [] (generic_handle_irq) from []
(__handle_domain_irq+0x57/0xac)
[28744.256857] [] (__handle_domain_irq) from []
(omap_intc_handle_irq+0x85/0x8c)
[28744.256873] [] (omap_intc_handle_irq) from []
(__irq_svc+0x3b/0x80)
[28744.256880] Exception stack(0xc0a4ff50 to 0xc0a4ff98)
[28744.256889] ff40: 0001 
 c001c041
[28744.256900] ff60: c0a4e000 c0a510f8   c0b01a48 0001
c0aebb70 c0a51104
[28744.256909] ff80: c0a4e03c c0a4ff98

[beagleboard] Re: can't boot from eMMC; can't flash eMMC

2016-02-29 Thread joelk

 I think I should trash this BBB.  Tonight while installing packages with 
apt-get there were a few errors while decompressing downloaded packages.  
This was fixable, but still ... generally shouldn't happen.  Also, while 
building libvpx from sources there were two internal compiler errors.  The 
first one said just

> : internal compiler error: Segmentation fault
>
>
The next one said:

> vp8/encoder/encodemb.c: In function ‘optimize_b.constprop’:
> vp8/encoder/encodemb.c:412:1: internal compiler error: Bus error
>  }
>  ^
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See  for instructions.
> The bug is not reproducible, so it is likely a hardware or OS problem.
> Makefile:152: recipe for target 'vp8/encoder/encodemb.c.o' failed
> make[1]: *** [vp8/encoder/encodemb.c.o] Error 1
> Makefile:17: recipe for target '.DEFAULT' failed
> make: *** [.DEFAULT] Error 2
>
>
So it looks like there is more wrong with this BBB besides the eMMC.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB enable i2c2 on chipsee debian 3.8.13 kernel

2016-02-29 Thread Damian Nahmiyas

thank robert!

i install this image

https://rcn-ee.com/rootfs/bb.org/testing/2016-02-21/lxqt-4gb/bone-debian-8.3-lxqt-4gb-armhf-2016-02-21-4gb.img.xz

update & upgrade

git clone https://github.com/beagleboard/bb.org-overlays
cd ./bb.org-overlays
./dtc-overlay.sh
./install.sh


dtc --version
Version: DTC 1.4.1-g1e75ebc9

but dont have this files... 
/sys/devices/bone_capemgr.8/slots

/sys/devices/platform/bone_capemgr/slots

i try to enable with cape_enable=bone_capemgr.enable_partno=BB-I2C2
but it does not work.

any idea?

uname -a
Linux beaglebone 4.1.18-ti-r49

ls -l /sys/bus/i2c/devices/i2c-*
lrwxrwxrwx 1 root root 0 Mar  1 06:10 /sys/bus/i2c/devices/i2c-0 -> 
../../../devices/platform/ocp/44e0b000.i2c/i2c-0
lrwxrwxrwx 1 root root 0 Mar  1 06:10 /sys/bus/i2c/devices/i2c-1 -> 
../../../devices/platform/ocp/4802a000.i2c/i2c-1

thanks for your responses!


El lunes, 29 de febrero de 2016, 15:57:18 (UTC-3), RobertCNelson escribió:
>
> On Mon, Feb 29, 2016 at 12:45 PM, Damian Nahmiyas  > wrote: 
> > hi! i need some help to enable pins P9 19,20 to use i2c2 with te 
> precompiled 
> > kernel of chipsee screen.I dont found the cape manager: 
> > 
> > /sys/devices/bone_capemgr.8/slots: No such file or directory 
>
> The people who designed the chipsee cape messed up... They have a can 
> phy connected to those i2c pins needed for cape-manager.. 
>
> Use any of the v4.x kernels where both the chipsee r/c are fully 
> supported: 
>
> dtb=am335x-boneblack-bbb-exp-r.dtb 
> dtb=am335x-boneblack-bbb-exp-c.dtb 
>
>
> 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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Root NFS

2016-02-29 Thread John Syne

You don’t have to delete connman for NFS to work. Just tell connman to stop 
managing eth0. This is required when using systemd. 

Regards,
John




> On Feb 29, 2016, at 2:42 PM, eli.jo...@gmail.com wrote:
> 
> 
> Wow.
> 
> I was dealing with issues trying to boot an NFS exported nfsroot with 
> Angstrom Linux.. and was having this exact same issue.  It would hang after 
> booting to the login and display:
> 
> nfs: server  not responding, still trying
> 
> removing /lib/systemd/system/conman.service does fix this problem.
> 
> I am replying here as this is the only place I saw this mentioned.
> 
> So, if you are having trouble booting from barebox into a custom kernel via 
> tftp and attempting to mount the rootfs over nfs using Ångström linux.. 
> (either don't use angstrom or delete the connman.service)
> 
> On Sunday, January 19, 2014 at 6:12:28 PM UTC-5, michele...@gmail.com 
>  wrote:
> "If your NFS root freezes during boot with a message similar to:
> 
> nfs: server 192.168.0.251 not responding, still trying
> Then it is possible the network connection used by the NFS connection has 
> been re-configured. On Angstrom, this connection is re-established by the 
> Connection Manager (ConnMan. ) To quickly overcome 
> this problem, remove /lib/systemd/system/connman.service from your rootFS."
> 
> 
> From Beyondlogic
> 
> 
> 
> Il giorno venerdì 2 agosto 2013 04:31:52 UTC+2, Marcel Claro ha scritto:
> I got sucessfully the boot-up of angstrom by NFS, but after appears 
> "beaglebone login: ", appears: "nfs: server server.domain.name 
>  not responding, still trying"  and then kernel 
> panic after few seconds, anyone knows why?
> 
> ps.: I try to follow this tutorial: 
> http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-network-boot/
>  
> 
> 
> -- 
> 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 
> .
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] can't boot from eMMC; can't flash eMMC

2016-02-29 Thread joelk


The BBB that I was working on 2-3 weeks ago seemingly died.  All attempts 
to boot it ended with various unusual led patterns, e.g. all 4 on for maybe 
a minute, then off, then all 4 on, and so on ... or, alternatively, led2 on 
permanently, or, alternatively, none at all.  I tried reflashing it with 
one of the Jessie console flasher images, which appeared to flash 
successfully but after removing the sd card it failed to complete booting.  
I used beaglebone-black-make-microSD-flasher-from-eMMC.sh to make a flasher 
image from a brand-new BBB, and again,  flashing seemed to go well but it 
still wouldn't boot.

I was about to toss it in the trash, but today I realized that it actually 
would boot from an ordinary sd card image 
(bone-debian-8.3-lxqt-4gb-armhf-2016-01-24-4gb.img), and seems to function 
normally that way.  So I edited /boot/uEnv.txt to make it a flasher, and 
tried to flash that image, but after about 10 minutes it stopped with all 4 
leds flashing together.  So I hooked it up to my pc with a usb-to-serial 
adapter and watched as I tried to flash that filesystem to the eMMC again.  
Twice.  Both times it failed to complete. 

The first time it falied almost immediately after it started writing to the 
eMMC:
rsync: [sender] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(820) [sender=3.1.1]
writing to [/dev/mmcblk1] failed...


The second time it wrote for about 5 minutes before quitting again with the 
same error message:
rsync: [sender] write error: Broken pipe (32)
rsync error: error in socket IO (code 10) at io.c(820) [sender=3.1.1]
writing to [/dev/mmcblk1] failed...

although this time there was a lot more error and warning messages (not 
very meaningful to me but maybe informative to you experts).  I will attach 
the full output that I got in my screen as flash_emmc.log.2.


I obviously don't know what caused this problem, although maybe it's worth 
mentioning that
1. for a day or 2 before it stopped booting from the emmc, I noted (even 
mentioned in one of my posts here) that I was seeing a surprising amount of 
activity on led2.  At the time I thought that was caused by 1 or more of 
the kernels I was trying out, but maybe it was just an early warning that 
something was getting ready to fail.

2. the last thing that I was doing before it stopped working was 
configuring a mini-wifi adapter (adafruit product #814).  (Prior to that I 
had been working with a ethernet cable.)  I didn't suspect the wifi adapter 
at the time but a few days later, while I was using that adapter connected 
to a Raspberry Pi, the Pi started acting flaky (cursor movement in the 
terminal lagging for a few seconds and then jumping suddenly) so I stopped 
using that adapter and the Pi has seemed normal, with a different wifi 
adapter, since then.

3. I did, once or twice, pull the power plug out without shutting down 
properly when my wifi failed to connect -- at the time I was unaware that I 
should have hit the power button first.  Maybe that damaged the eMMC?   
(Although that was after the excessively-flashing led2 mentioned above.)

Sorry if this is too much information.  I just thought it might be useful 
to somebody sometime.

Anyway, do you think there's any hope for reviving the eMMC on this BBB or 
should I just be happy that it works from the sd card?

-- 
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.
For more options, visit https://groups.google.com/d/optout.


flash_emmc.log.2
Description: Binary data

Re: [beagleboard] Re: Driver for Adafruit BMP280 Barometric Pressure & Temperature Sensor

2016-02-29 Thread Nuno Sucena Almeida

On 02/29/2016 08:28 PM, AV8TOR wrote:
> Update:
> I anticipate someone will want to know how the sensor is interfaced:
> Again, using the BMP085 as a reference for my BMP280
> The actual BMP280 pinout BMP280 Pinout
> 
> the below steps snipped from this link: BMP On the Beaglebone Black
> 
> 
>  1. Connect GND from the BMP085 to P9.1 of your BBB.
>  2. Connect VIN from the BMP085 to P9.3 of your BBB.
>  3. Connect SCL from the BMP085 to P9.19 of your BBB.
>  4. Connect SDA from the BMP085 to P9.20 of your BBB.  (NOTE: the BMP280
> does not have SDA, so I'm using SDI instead)

You might want to make sure that you are using the BMP280 in I2C mode,
instead of SPI mode, as it supports both.

Before assigning a driver to it (your echo command), you can try to see
if it's actually being detected on the i2c bus and dump its registers
using the i2c tools (i2cdetect, i2cdump)

You also didn't mention what linux/kernel versions you are running.
There's support for BMP280 on newer linux kernels within the kernel iio
framework as of 2014/2015.

regards,
Nuno

-- 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Driver for Adafruit BMP280 Barometric Pressure & Temperature Sensor

2016-02-29 Thread AV8TOR

Update:
I anticipate someone will want to know how the sensor is interfaced: Again, 
using the BMP085 as a reference for my BMP280
The actual BMP280 pinout BMP280 Pinout 

the below steps snipped from this link: BMP On the Beaglebone Black 


   1. Connect GND from the BMP085 to P9.1 of your BBB.
   2. Connect VIN from the BMP085 to P9.3 of your BBB.
   3. Connect SCL from the BMP085 to P9.19 of your BBB.
   4. Connect SDA from the BMP085 to P9.20 of your BBB.  (NOTE: the BMP280 
   does not have SDA, so I'm using SDI instead)


On Monday, February 29, 2016 at 8:17:40 PM UTC-5, AV8TOR wrote:
>
> Hello, 
> My first time ever using a BB platform. ID10T newbie.
>
> I'm trying to use the board along with a BMP280 sensor for Pressure and 
> Temperature.
> I'm having no skill or luck with it. I've sprungboard off of a post 
> showing how to implement a driver for the BMP085 which is an earlier 
> version of the same sensor.
> The link: BMP_on_the_Beagle_Bone_Black 
> 
>
> I've tried the command line commands as such.
> echo bmp280 0x77 > /sys/class/i2c-adapter/i2c-1/new_device
> root@beaglebone:~# dmesg | grep bmp
> [  785.694384] i2c i2c-1: new_device: Instantiated device bmp280 at 0x77
> root@beaglebone:~# cat /sys/bus/i2c/drivers/bmp280/1-0077/temp0_input
> root@beaglebone:~# cat /sys/bus/i2c/drivers/bmp280/1-0077/temp0_input: No 
> such file or directory
> Not working as you can see.
>
>
> Then I tried to modify and re-use Juan Corez example. Also, the same 
> output. No such file or directory.
> ***BMP280.js
> ***
> * Created on: 6-12-2013
> * Revised on: 6-13-2013
> * BMP085 Author: Juan Cortez, Modified by me for the BMP280.
> * Works on: 06-08-12 image or later on both BeagleBone and BeagleBone 
> Black
> * Reads temperature and pressure from the BMP280 Sensor
> * Input: Sensors on the BMP280 Sensor
> * Output: Outputs the readings on the console.
> * Special Instructions: Run code once as it is. You will get an error but 
> it is OK. 
> * Comment out the b.writeTextFile(bmp280); line, save and run the 
> code again.
>
> ***/
>  
> var b = require('bonescript');
> var bmp280= '/sys/class/i2c-adapter/i2c-1/'; 
>
> //Sensor Locations on the BeagleBone Black
> var temperature= '/sys/bus/i2c/drivers/bmp280/1-0077/temp0_input';
> var pressure= '/sys/bus/i2c/drivers/bmp280/1-0077/pressure0_input';
>
> /* We will initialize the driver for the BMP280 sensor located at I2C 
> location 0x77.*/
> /* !NOTE!: You only have to initialize the driver once. Once you run the 
> code once, comment out the next line. (i.e. b.writeTextFile) */
> //b.writeTextFile(bmp280 + 'new_device', 'bmp280 0x77');
> /Comment out the line above after you 
> run the code once***/
>
> /* Opens,reads, and prints pressure and temperature. */
> b.readTextFile(pressure, printPressure);
> b.readTextFile(temperature,printTemperature); 
>
> /* Prints Pressure */
> function printPressure(x) {
>   console.log("Pressure: ", x.data/100 + " millibar");
> }
>
> /* Prints Temperature */
> function printTemperature(x){
>   console.log("Temperature: ", x.data/10 + '\xB0' + " Celcius"); // 
> '\xB0' is decimal in hexademical
>   x.data /= 10;
>   x.data *= 1.8;
>   x.data += 32;
>   console.log("or: ", x.data + '\xB0' + " Fahrenheit"); 
> }
>
> Could someone please gently point me in the right direction?
>
> Thanks in advance,
> Mike
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Driver for Adafruit BMP280 Barometric Pressure & Temperature Sensor

2016-02-29 Thread AV8TOR

Hello, 
My first time ever using a BB platform. ID10T newbie.

I'm trying to use the board along with a BMP280 sensor for Pressure and 
Temperature.
I'm having no skill or luck with it. I've sprungboard off of a post showing 
how to implement a driver for the BMP085 which is an earlier version of the 
same sensor.
The link: BMP_on_the_Beagle_Bone_Black 


I've tried the command line commands as such.
echo bmp280 0x77 > /sys/class/i2c-adapter/i2c-1/new_device
root@beaglebone:~# dmesg | grep bmp
[  785.694384] i2c i2c-1: new_device: Instantiated device bmp280 at 0x77
root@beaglebone:~# cat /sys/bus/i2c/drivers/bmp280/1-0077/temp0_input
root@beaglebone:~# cat /sys/bus/i2c/drivers/bmp280/1-0077/temp0_input: No 
such file or directory
Not working as you can see.


Then I tried to modify and re-use Juan Corez example. Also, the same 
output. No such file or directory.
***BMP280.js***
* Created on: 6-12-2013
* Revised on: 6-13-2013
* BMP085 Author: Juan Cortez, Modified by me for the BMP280.
* Works on: 06-08-12 image or later on both BeagleBone and BeagleBone Black
* Reads temperature and pressure from the BMP280 Sensor
* Input: Sensors on the BMP280 Sensor
* Output: Outputs the readings on the console.
* Special Instructions: Run code once as it is. You will get an error but 
it is OK. 
* Comment out the b.writeTextFile(bmp280); line, save and run the code 
again.
***/
 
var b = require('bonescript');
var bmp280= '/sys/class/i2c-adapter/i2c-1/'; 

//Sensor Locations on the BeagleBone Black
var temperature= '/sys/bus/i2c/drivers/bmp280/1-0077/temp0_input';
var pressure= '/sys/bus/i2c/drivers/bmp280/1-0077/pressure0_input';

/* We will initialize the driver for the BMP280 sensor located at I2C 
location 0x77.*/
/* !NOTE!: You only have to initialize the driver once. Once you run the 
code once, comment out the next line. (i.e. b.writeTextFile) */
//b.writeTextFile(bmp280 + 'new_device', 'bmp280 0x77');
/Comment out the line above after you 
run the code once***/

/* Opens,reads, and prints pressure and temperature. */
b.readTextFile(pressure, printPressure);
b.readTextFile(temperature,printTemperature); 

/* Prints Pressure */
function printPressure(x) {
  console.log("Pressure: ", x.data/100 + " millibar");
}

/* Prints Temperature */
function printTemperature(x){
  console.log("Temperature: ", x.data/10 + '\xB0' + " Celcius"); // '\xB0' 
is decimal in hexademical
  x.data /= 10;
  x.data *= 1.8;
  x.data += 32;
  console.log("or: ", x.data + '\xB0' + " Fahrenheit"); 
}

Could someone please gently point me in the right direction?

Thanks in advance,
Mike

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: Root NFS

2016-02-29 Thread eli . jones


Wow.

I was dealing with issues trying to boot an NFS exported nfsroot with 
Angstrom Linux.. and was having this exact same issue.  It would hang after 
booting to the login and display:

nfs: server  not responding, still trying

removing /lib/systemd/system/conman.service does fix this problem.

I am replying here as this is the only place I saw this mentioned.

So, if you are having trouble booting from barebox into a custom kernel via 
tftp and attempting to mount the rootfs over nfs using Ångström linux.. 
(either don't use angstrom or delete the connman.service)

On Sunday, January 19, 2014 at 6:12:28 PM UTC-5, michele...@gmail.com wrote:
>
> "If your NFS root freezes during boot with a message similar to: 
>
> nfs: server 192.168.0.251 not responding, still trying
>
> Then it is possible the network connection used by the NFS connection has 
> been re-configured. On Angstrom, this connection is re-established by the 
> Connection Manager (ConnMan. ) To quickly 
> overcome this problem, remove /lib/systemd/system/connman.service from your 
> rootFS."
>
> From Beyondlogic
>
>
> Il giorno venerdì 2 agosto 2013 04:31:52 UTC+2, Marcel Claro ha scritto:
>>
>> I got sucessfully the boot-up of angstrom by NFS, but after appears 
>> "beaglebone login: ", appears: "nfs: server server.domain.name not 
>> responding, still trying"  and then kernel panic after few seconds, anyone 
>> knows why?
>>
>> ps.: I try to follow this tutorial: 
>> http://www.embeddedhobbyist.com/debian-tips/beaglebone-black/beaglebone-black-network-boot/
>>
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

2016-02-29 Thread dariush . abbasinezhad



On Sunday, September 28, 2014 at 6:44:24 PM UTC+3:30, Andrew Henderson 
wrote:
>
> Hello all. I have released a new port of Android for the BBB.  This 
> version uses AOSP 4.4.4 (KitKat) and the 3.8 Linux kernel. I have made 
> build instructions and a pre-made image available at 
> http://www.bbbandroid.org.  I use a combination of AOSP repos and Rowboat 
> build scripts, and I have a few custom repos for the kernel, bootloader, 
> and additional "external" tools (such as i2c-tools).  You can view the repo 
> manifest XML file for the project here:
>
>
> https://github.com/hendersa/bbbandroid-manifest/blob/master/bbbandroid-aosp-4.4.4_r1-3.8.xml
>
> Because this Android image uses the 3.8 kernel, you should be able to just 
> plug in your capes and go without any hassle:
>
> Built-in HDMI cape:
> http://i.imgur.com/q4AZQ95.jpg
>
> 4D Systems LCD capes:
> 4DCAPE-43T: http://i.imgur.com/6qHmgqX.jpg
> 4DCAPE-70T: http://i.imgur.com/UZLG7Or.jpg
>
> CircuitCo LCD capes:
> LCD3: http://i.imgur.com/LC7SrBB.jpg 
> LCD4: http://i.imgur.com/1xBQ8R6.jpg
> LCD7: http://i.imgur.com/vxoqROE.jpg
>
> Andrew
>

Hi Andrew.
Thanks a lot for your great work.
I'm trying to flash BBBAndroid to eMMC but using fastboot.
the problem is it does not boot with kernel 3.8, just boots with kernel 3.2.
I'm using the u-boot with fastboot support "U-Boot SPL 
2013.01.01-bbb-fb-2-gf7d94e6 ".
It complains about not supported machin ID.
Any suggestion? 

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Cosmic rays measured with BeagleBone-based data acquisition

2016-02-29 Thread Drew Fustini

Thanks for sharing.  That sounds very exciting!  I'm from Batavia,
Illinois where Fermilab is and believe Open Source Hardware is a great
fit for physics exeperiments.

Is there a specific URL that talks about your project that uses the
BBB?   Maybe a repo with the source code and/or design files (like
GitHub)?

thanks,
drew

On Mon, Feb 29, 2016 at 4:54 PM, wojtekskulski via BeagleBoard
 wrote:
> Hello everyone:
> last week we started a website CosmicRayNet.net showing a measurement of
> cosmic ray mu-meson capture-and-decay. We developed an instrument which is
> performing signal digitization and data acquisition of such rare decay
> events. The instrument is using the BeagleBone Black, upon which we stacked
> an ADC+FPGA board. I am inviting all of you to visit the new website. I also
> point out that this work was supported by the Office of Science of the
> Department of Energy. It is a cool scientific project with a lot of further
> potential.
>
> I want to thank the BeagleBone creators and the entire community for such a
> fantastic tool.
> Regards,
> Wojtek
>
> --
> 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.
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] Cosmic rays measured with BeagleBone-based data acquisition

2016-02-29 Thread wojtekskulski via BeagleBoard

Hello everyone:
last week we started a website CosmicRayNet.net showing a measurement of 
cosmic ray mu-meson capture-and-decay. We developed an instrument which is 
performing signal digitization and data acquisition of such rare decay 
events. The instrument is using the BeagleBone Black, upon which we stacked 
an ADC+FPGA board. I am inviting all of you to visit the new website. I 
also point out that this work was supported by the Office of Science of the 
Department of Energy. It is a cool scientific project with a lot of further 
potential.

I want to thank the BeagleBone creators and the entire community for such a 
fantastic tool.
Regards,
Wojtek

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] BBB enable i2c2 on chipsee debian 3.8.13 kernel

2016-02-29 Thread Robert Nelson

On Mon, Feb 29, 2016 at 12:45 PM, Damian Nahmiyas  wrote:
> hi! i need some help to enable pins P9 19,20 to use i2c2 with te precompiled
> kernel of chipsee screen.I dont found the cape manager:
>
> /sys/devices/bone_capemgr.8/slots: No such file or directory

The people who designed the chipsee cape messed up... They have a can
phy connected to those i2c pins needed for cape-manager..

Use any of the v4.x kernels where both the chipsee r/c are fully supported:

dtb=am335x-boneblack-bbb-exp-r.dtb
dtb=am335x-boneblack-bbb-exp-c.dtb


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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] BBB enable i2c2 on chipsee debian 3.8.13 kernel

2016-02-29 Thread Damian Nahmiyas

hi! i need some help to enable pins P9 19,20 to use i2c2 with te 
precompiled kernel of chipsee screen.I dont found the cape manager:

/sys/devices/bone_capemgr.8/slots: No such file or directory

thanks!

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] What is the purpose of eMMC_RSTn?

2016-02-29 Thread Gerald Coley

That is what it is there for. However, it does not work until you enable it
in the eMMC itself.

Gerald


On Mon, Feb 29, 2016 at 10:30 AM, Geoff L.  wrote:

> On the BBB there is a gpio that is connected through a open collector
> buffer to the emmc reset line.  It seems that this is there for the purpose
> of allowing capes to use the processor pins that are otherwise connected to
> the eMMC, by holding the eMMC in reset.I'm considering removing feature
> on a derivative board - just want to confirm that it is not necessary for
> any other function.If the reset is removed, is it recommended that the
> eMMC reset be connected to SYS_RESETn, or some other reset source instead?
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Gerald

ger...@beagleboard.org
http://beagleboard.org/

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] Re: BBB USB0 change from client to host

2016-02-29 Thread Antonio Garcia Oteros

Hi ,
 I would like to know if you have the solution to convert this USB0 port to
periferical port.

I have the same problem like you.

Thanks in advanced.

2015-11-05 14:24 GMT+01:00 Ison Thomas :

> Hi Robert,
>
> I am trying to acheive a similar goal here. I want to change my USB0 to
> host and USB1 to device. I tried to make this change in
> arch/arm/boot/dts/am335x-bone-
> common.dtsi file but the file structure has changed significantly. It is
> now having :
>
> " _otg_hs {
> interface_type = <1>;
> power = <250>;
> status = "okay";
> }; " instead of what is posted in the original querry.
>
> Also the am33xx.dtsi file is changed in the usb part as:
>
>  " usb_otg_hs: usb@4740 {
> compatible = "ti,musb-am33xx";
> reg = <0x4740 0x1000/* usbss */
>0x47401000 0x800 /* musb instance 0
> */
>0x47401800 0x800>;   /* musb instance 1
> */
> interrupts = <17/* usbss */
>   18/* musb instance 0
> */
>   19>;  /* musb instance 1
> */
> multipoint = <1>;
> num-eps = <16>;
> ram-bits = <12>;
> port0-mode = <3>;
> port1-mode = <1>;
> power = <250>;
> ti,hwmods = "usb_otg_hs";
> status = "disabled";
> }; "
>
> Do you have any idea on how to make the USB0 to work as host and USB1 to
> work as device with the latest files?
>
> Also do we have to make any change in the 'menuconfig' for achieving this
> or the default configuration used for beaglebone is sufficient?
>
>
> On Friday, 19 December 2014 00:15:38 UTC+5:30, RobertCNelson wrote:
>>
>> On Thu, Dec 18, 2014 at 12:43 PM, Siddhiq Ahmed 
>> wrote:
>> > Dear All,
>> >
>> > I am also working with a Clone of BBB.  In which I need to Convert USB0
>> as
>> > Host.  I need to use both the USB0 and USB1 has Host.  Kindly,
>> suggest.  How
>> > to Convert the USB0 Port to Host.
>>
>> I suggest you take a look at the schematic and compare usb0 & usb1..
>>
>> Regards,
>>
>> --
>> Robert Nelson
>> http://www.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.
> 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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard] What is the purpose of eMMC_RSTn?

2016-02-29 Thread Geoff L.

On the BBB there is a gpio that is connected through a open collector 
buffer to the emmc reset line.  It seems that this is there for the purpose 
of allowing capes to use the processor pins that are otherwise connected to 
the eMMC, by holding the eMMC in reset.I'm considering removing feature 
on a derivative board - just want to confirm that it is not necessary for 
any other function.If the reset is removed, is it recommended that the 
eMMC reset be connected to SYS_RESETn, or some other reset source instead?

-- 
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.
For more options, visit https://groups.google.com/d/optout.

[beagleboard]: how to flash only uboot on emmc

2016-02-29 Thread Ritu Sharma

Hi,

I am building uboot from source with robert nelson's instructions here:
https://eewiki.net/display/linuxonarm/BeagleBone+Black

But I do not want to upgrade emmc with rootfs and kernel... only uboot I
want to upgrade.


Is it possible to generate flasher image just for uboot on BBB ?

regards
Ritu

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [beagleboard] 4.1.16-bone18 #26 PREEMPT & CPU stuck for 90 second

Re: [beagleboard] 4.1.16-bone18 #26 PREEMPT & CPU stuck for 90 second

[beagleboard] 4.1.16-bone18 #26 PREEMPT & CPU stuck for 90 second

[beagleboard] Re: can't boot from eMMC; can't flash eMMC

Re: [beagleboard] BBB enable i2c2 on chipsee debian 3.8.13 kernel

Re: [beagleboard] Root NFS

[beagleboard] can't boot from eMMC; can't flash eMMC

Re: [beagleboard] Re: Driver for Adafruit BMP280 Barometric Pressure & Temperature Sensor

[beagleboard] Re: Driver for Adafruit BMP280 Barometric Pressure & Temperature Sensor

[beagleboard] Driver for Adafruit BMP280 Barometric Pressure & Temperature Sensor

[beagleboard] Re: Root NFS

[beagleboard] Re: BBBAndroid: AOSP 4.4.4 (KitKat) with 3.8 kernel

Re: [beagleboard] Cosmic rays measured with BeagleBone-based data acquisition

[beagleboard] Cosmic rays measured with BeagleBone-based data acquisition

Re: [beagleboard] BBB enable i2c2 on chipsee debian 3.8.13 kernel

[beagleboard] BBB enable i2c2 on chipsee debian 3.8.13 kernel

Re: [beagleboard] What is the purpose of eMMC_RSTn?

Re: [beagleboard] Re: BBB USB0 change from client to host

[beagleboard] What is the purpose of eMMC_RSTn?

[beagleboard]: how to flash only uboot on emmc

20 matches

Site Navigation

Mail list logo

Footer information