[beagleboard] Re: libpruio (fast and easy D/A - I/O)

2020-09-16 Thread TJF 
PS:

If somebody knows a good protection circuity for the ADC inputs (ie OP-amp 
working with ADC Vref), please let me know.

Regards

-- 
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/36a108ce-e55c-4e00-8be6-482a88363fe1o%40googlegroups.com.

[beagleboard] Re: libpruio (fast and easy D/A - I/O)

2020-09-16 Thread TJF 
Hi Andrew!

I've also seen frozen ADC. I guess (not confirmed yet) it's coming from 
negative Voltage on the input line.

I tried to disable and re-enable only the TSC_ADC_SS (while the rest of the 
system is running), to no avail. But after a system reset (warm-start) the 
ADC always runs well.

Regards

-- 
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/45191737-96c5-43e2-8506-d3cbb59a740eo%40googlegroups.com.

Re: [beagleboard] Device Tree Overlay for BeagleBone-AI

2020-09-16 Thread Robert Nelson 
On Wed, Sep 16, 2020 at 7:15 PM 어지수  wrote:
>
> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz
>
> (v4.19.x-ti based kernel..)
>
> Does the dbt_overlay (kernel overlay) work properly on this kernel(v4.19.x-ti 
> based kernel)?
>  I succeeded in u-boot overlay. However, dtb_overlay was not successful. 
> (kernel overlay on 4.19-x version.
>
> I don't know the difference between kernel overlay and uoot overlay.
> Are these two the same thing?
>
>  My uEnv.txt is the following list.
>   ###Custom Cape
> dtb_overlay=/lib/firmware/BBORG_SERVO-00A2.dtbo-> kernel overlay ( i said 
> it as kernel overlay)
>
>   uboot_overlay_addr4=/lib/firmware/BBORG_SERVO-00A2.dtbo -> uboot overlay ( 
> i mean it as uboot-overlay)
>
> #Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
>
> uname_r=4.19.94-ti-r50
> #uuid=
> #dtb=
>
> ###U-Boot Overlays###
> ###Documentation: 
> http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays
> ###Master Enable
> enable_uboot_overlays=1
> ###
> ###Overide capes with eeprom
> #uboot_overlay_addr0=.dtbo
> #uboot_overlay_addr1=.dtbo
> #uboot_overlay_addr2=.dtbo
> #uboot_overlay_addr3=.dtbo
> ###
> ###Additional custom capes
> uboot_overlay_addr4=/lib/firmware/BBORG_SERVO-00A2.dtbo

Use:

uboot_overlay_addr4=BBORG_SERVO-00A2.dtbo

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/CAOCHtYg5qDFKSka43e4ye8nmu0qvX8y%3Di0hBg5Waf-fwrrSPpg%40mail.gmail.com.

Re: [beagleboard] Starting kdump-tools: kdump is not supported by this kernel ... failed! at BeagleBone AI

2020-09-16 Thread 어지수 
At the time, it was noted as follows:

enable kexec support in the kernel.  =>  What environment file should I
change?

I thank you for your help.
Regards


2020년 9월 16일 (수) 오후 10:34, Robert Nelson 님이 작성:

> On Wed, Sep 16, 2020 at 7:02 AM  wrote:
> >
> > I have a kernel panic happening and I want to analyze the core dump.
> However, the following error occurs during booting at BeagleBone AI
> >
> > [7.758681] kdump-tools[1024]: Starting kdump-tools: kdump is not
> supported by this kernel ... failed!
> > [   10.728480] kdump-tools[1210]: Stopping kdump-tools: kexec unload
> failed: Function not implemented
> > [   10.744723] kdump-tools[1210]: failed to unload kdump kernel ...
> failed!
> > [   11.158265] kdump-tools[1235]: Starting kdump-tools: kdump is not
> supported by this kernel ... failed!
> >
> > How do I fix this problem?
>
> enable kexec support in the kernel.
>
> Can you share your panic, it's probably a known one..
>
> Regards,
>
> --
> Robert Nelson
> https://rcn-ee.com/
>
> --
> 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/E71E7YvQ7tI/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/CAOCHtYgF3_11obvSDDKGfBXQAOtOQqoJgAe0FuTWAQ6AvczPwg%40mail.gmail.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/CAKyOz5h5cBWLoyzdo181L%2BnSgyW53%3DkNBs8xOdLFFi_phGwd0Q%40mail.gmail.com.

[beagleboard] Re: Servo control: pulse width working range ?

2020-09-16 Thread Dennis Lee Bieber 
On Wed, 16 Sep 2020 10:27:17 -0700, in gmane.comp.hardware.beagleboard.user
jonnymo  wrote:

>Actually 360 degree Continuous Rotation Servers are quite common. There are
>basically two types of servos: 360 degree Continuous Rotation and 90 degree
>Standard Rotation.  Each has a different purpose.

>On Wed, Sep 16, 2020 at 8:54 AM Dennis Lee Bieber 
>
>wrote:
>
>> Very few servos have a 360 rotation range... +/- 90 degree is more
>> common (the exception being servos that have had the position feed back
>> logic removed and act as variable speed continuous motors).


I'd have though I'd covered those with the "act as variable speed
continuous motors".

However, the OP asked about setting specific angles of 0, 90, 180, 270
(I'm assuming the 270, they went 0, 90, 180, 360). Continous rotation types
do not have feed-back for positions, so could not be commanded to rotate to
any particular angle.

That leaves us back with common positioning servos which normally run
-90 to +90 (or 0 to 180, if one prefers... +/- 90 makes for sense if being
used for a steering servo on a robot, where 0 is "straight ahead". It may
also make sense for throttle control, where 0 is stopped, -90 is full
reverse, +90 is full forward).



-- 
Dennis L Bieber

-- 
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/dd55mf5trjrj5ska4s34vdcichqgdc89i4%404ax.com.

Re: [beagleboard] Re: Servo control: pulse width working range ?

2020-09-16 Thread jonnymo 
Actually 360 degree Continuous Rotation Servers are quite common. There are
basically two types of servos: 360 degree Continuous Rotation and 90 degree
Standard Rotation.  Each has a different purpose.

As far as manufacturers not providing datasheets for their products, I
would suspect this depends on where you are purchasing the servers from.
If you stick with manufacturers such as Hitec, Tower, Futaba, or Parallax
you should be fine.  If you are purchasing cheap off brand servers, then
you may run into an issue with each being different as far as how they
react to a PWM signal. Also, depending on the application, there could be a
difference between plastic and metal gears.  I tend to like metal gear
servos though.

Cheers,

Jon


On Wed, Sep 16, 2020 at 8:54 AM Dennis Lee Bieber 
wrote:

> On Wed, 16 Sep 2020 07:36:14 -0700 (PDT), in
> gmane.comp.hardware.beagleboard.user Pavel Yermolenko
>  wrote:
>
> >I noticed that many servo motor manufacturers don't provide datasheets
> for
> >their products (for example for my servo it's the case)
> >Generic values that can be found on the web don't work for every servo.
> >For example what should be pulse width for 0/90/180/360 degrees.
> >I suppose the value of pulse widths depends on a particular model.
> >
>
> Very few servos have a 360 rotation range... +/- 90 degree is more
> common (the exception being servos that have had the position feed back
> logic removed and act as variable speed continuous motors).
>
>
> https://www.jameco.com/jameco/workshop/howitworks/how-servo-motors-work.html
>
> 1.5mS pulse should be the "neutral" position (middle of the range).
>
> https://learn.adafruit.com/adafruit-motor-selection-guide/rc-servos
>
> https://learn.adafruit.com/adafruit-motor-selection-guide/continuous-rotation-servos
>
> >For example I noticed that if pulse width in quite low, the servo heats
> up
> >as an iron.
>
> Likely you are over (under) driving the position, and the servo
> can not
> physically move to the position you are requesting -- this leaves the coils
> energized with the servo pushing against the internal end-stop.
>
> My suggestion would be that you write a short calibration program
> with
> which you adjust the pulse width from neutral, one step at a time, until
> the servo reaches an end point (ie; the control "horn" stopped moving while
> you changed the pulse width), then back up until you just detect the horn
> has moved off the end-stop. Record that value and repeat for the other
> direction. Maybe put a sticker on the servo with the values of the
> end-point pulse widths -- neutral position should be the average of those
> two values.
>
> Do that for all your servos, and either use the minimum span for
> all,
> or program the limits per servo (if using Python, install Adafruit Blinka
> and libraries for CircuitPython -- the servo class allows override of
> min/max pulse width; they default to 0.5 - 2.5ms, but do state that
> "standard" servos are supposed to work with 1.0 - 2.0ms width).
>
> https://learn.adafruit.com/circuitpython-essentials/circuitpython-servo
> https://learn.adafruit.com/circuitpython-on-raspberrypi-linux (ignore the
> R-Pi, it works for BBB also)
>
> https://learn.adafruit.com/using-servos-with-circuitpython/high-level-servo-control
>
>
>
>
> --
> Dennis L Bieber
>
> --
> 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/nkb4mfd0pbjeigumqjvhb0k8gur9qql2ed%404ax.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/CAG99bkpb_a%2B8RUCggcgWF-fGBcrgFY4VYGA2CEygfPTR8GM%3DAQ%40mail.gmail.com.

Re: [beagleboard] Device Tree Overlay for BeagleBone-AI

2020-09-16 Thread Robert Nelson 
On Wed, Sep 16, 2020 at 11:10 AM 어지수  wrote:
>
> What is the difference between kenel overlay (device tree) and u-boot overlay?
> Are they the same thing?
>
> I have succeeded with u-boot overlay.
> How do I get the kernel overlay (dtb_overlay) to load successfully?
>
> I add my uEnv.txt for loading kernel overlay(dtb_overlay).

I'm sorry, v4.14.x-ti in your /boot/uEnv.txt is NOT compatible with
overlays for BBAI, this is brand new for the BBAI..

YOU much start with:

https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz

(v4.19.x-ti based kernel..)

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/CAOCHtYhP2M5sN1SWVPFaPHucTzA9xAg_WwEmXzZmE8_JUEFSew%40mail.gmail.com.

Re: [beagleboard] Device Tree Overlay for BeagleBone-AI

2020-09-16 Thread 어지수 
What is the difference between kenel overlay (device tree) and u-boot
overlay?
Are they the same thing?

I have succeeded with u-boot overlay.
How do I get the kernel overlay (dtb_overlay) to load successfully?

I add my uEnv.txt for loading kernel overlay(dtb_overlay).

2020년 9월 14일 (월) 오후 6:26, 어지수 님이 작성:

> I send uEnv.txt to you.
> I success but i have a question
>
>   Are uboot_overlay and dtb_overlay the same?
>
>
> 2020년 9월 14일 (월) 오후 6:16, 어지수 님이 작성:
>
>> I have some questions.
>> Are dtb_overlay and uboot_overlay_addr4 the same thing?
>> Are uboot_overlay and dtb_overlay the same?
>>
>> thank you for a lot help
>> regards
>> jisu
>>
>> 2020년 9월 12일 (토) 오전 3:15, Robert Nelson 님이 작성:
>>
>>> On Fri, Sep 11, 2020 at 12:30 PM debian  wrote:
>>> >
>>> > Could i use overlay (Device Tree) in BeagleBone AI?
>>> > Could i know how to use overlay (DT) in BeagleBone AI?
>>> >
>>> > First, I dont know to modify uEnv.txt ?
>>> > I don't know what to edit in uEnv.txt.
>>> >
>>> > Can I know which part I need to fix?
>>>
>>> Either start with this image (unless you need xorg)
>>>
>>>
>>> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/am57xx-debian-10.5-iot-armhf-2020-09-07-4gb.img.xz
>>>
>>> Here is the list of overlays:
>>>
>>>
>>> https://github.com/beagleboard/BeagleBoard-DeviceTrees/tree/v4.19.x-ti-overlays/src/arm/overlays
>>>
>>> Regards,
>>> --
>>> Robert Nelson
>>> https://rcn-ee.com/
>>>
>>> --
>>> 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/-7xASl-oqic/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/CAOCHtYi9NwNJNOQbkZLCJk_-LApGN-VRTVPQuuzTtuTX10sNew%40mail.gmail.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/CAKyOz5h_h0HU6G%2Bx047owg-KdGuaDVcPSkTsw2uvo677JDduHg%40mail.gmail.com.
#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.14.108-ti-r136
#uuid=
#dtb=
cmdline=coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet

#In the event of edid real failures, uncomment this next line:
#cmdline=coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet 
video=HDMI-A-1:1024x768@60e

#Use an overlayfs on top of a read-only root filesystem:
#cmdline=coherent_pool=1M net.ifnames=0 rng_core.default_quality=100 quiet 
overlayroot=tmpfs

##enable x15: eMMC Flasher:
##make sure, these tools are installed: dosfstools rsync
#CMDLINE=INIT=/OPT/SCRipts/tools/eMMC/init-eMMC-flasher-v3-no-eeprom.sh

dtb_overlay=/lib/firmware/.dtb

dtb=am5729-beagleboneai-custom.dtb

[beagleboard] Re: omap2_mcspi 48030000.spi: chipselect 0 already in use

2020-09-16 Thread Dennis Lee Bieber 
On Wed, 16 Sep 2020 08:22:52 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Mark Mitchell
 wrote:


>Is there a guide to show how to set up the uEnv.txt file and any others to 
>use Uboot to load the device trees? I dont quite understand how or what 
>cape universal is doing or when to use it or not.
>

This relies upon the version of u-boot being used also... (which is why
it was suggested that you blank the eMMC, so there is no boot attempt from
it -- I prefer to flash the eMMC with a modern image)

Old BBB (Debian Wheezy era, maybe early Jessie) have a u-boot in the
eMMC that assumes the kernel will load device trees. Updating the eMMC with
a modern image should install a u-boot that does device tree loading. Note
that newer u-boot also detect the uSD card, and transition to it
automatically (so, booting from eMMC u-boot to uSD card device tree [I
believe] followed by uSD kernel) -- no need to hold down the boot-select to
get it to boot from uSD.

If you have the old u-boot in eMMC, you MUST use the boot-select button
to force it to load u-boot from the uSD card instead.


-- 
Dennis L Bieber

-- 
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/jbd4mf5cg70i8r0infcajgv147ru0444a4%404ax.com.

Re: [beagleboard] Starting kdump-tools: kdump is not supported by this kernel ... failed! at BeagleBone AI

2020-09-16 Thread 어지수 
i run make for snull
snull is simple network device driver

 snull.zip



sudo insmod snull.ko

sometimes it is okay , it have no kernel panic.
but sometimes i have a kernel panic when i run sudo insmod snull.ko. at
Beaglbone AI (  4.19.94-ti-r50)

i have kernel panic
I use 4.19.94-ti-r50 at Beaglebone AI


root@beaglebone:/home/debian/LDD/snull# sudo insmod snull.ko
root@beaglebone:/home/debian/LDD/snull# [ 4026.234112] Pool empty
[ 4027.008435] [ cut here ]
[ 4027.013118] WARNING: CPU: 0 PID: 0 at net/sched/sch_generic.c:466
dev_watchdog+0x258/0x25c
[ 4027.021453] NETDEV WATCHDOG: sn0 (): transmit queue 0 timed out
[ 4027.027421] Modules linked in: snull(O) sbull(O+) hello_1(O) xt_state
xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nft_compat
pru_rproc irq_pruss_intc rpmsg_rpc pruss bnep virtio_rpmsg_bus
uio_pruss_shmem pruss_soc_bus ti_vip ti_vpe btsdio ti_sc
videobuf2_dma_contig ti_csc bluetooth ti_vpdma v4l2_fwnode v4l2_mem2mem
v4l2_common videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media
ecdh_generic brcmfmac brcmutil cfg80211 omap_remoteproc remoteproc virtio
virtio_ring usb_f_ncm usb_f_mass_storage usb_f_rndis u_ether libcomposite
uio_pdrv_genirq uio gpio_pisosr spidev [last unloaded: snull]
[ 4027.081808] CPU: 0 PID: 0 Comm: swapper/0 Tainted: G  D W  O
 4.19.94-ti-r50 #1buster
[ 4027.090371] Hardware name: Generic DRA74X (Flattened Device Tree)
[ 4027.096513] [] (unwind_backtrace) from []
(show_stack+0x20/0x24)
[ 4027.104299] [] (show_stack) from []
(dump_stack+0x8c/0xa0)
[ 4027.111562] [] (dump_stack) from []
(__warn.part.3+0xcc/0xe8)
[ 4027.119085] [] (__warn.part.3) from []
(warn_slowpath_fmt+0x78/0x94)
[ 4027.127217] [] (warn_slowpath_fmt) from []
(dev_watchdog+0x258/0x25c)
[ 4027.135439] [] (dev_watchdog) from []
(call_timer_fn+0x3c/0x210)
[ 4027.143222] [] (call_timer_fn) from []
(expire_timers+0xcc/0x174)
[ 4027.151090] [] (expire_timers) from []
(run_timer_softirq+0xbc/0x1bc)
[ 4027.159308] [] (run_timer_softirq) from []
(__do_softirq+0x16c/0x438)
[ 4027.167529] [] (__do_softirq) from []
(irq_exit+0xd8/0xec)
[ 4027.174792] [] (irq_exit) from []
(__handle_domain_irq+0x90/0xfc)
[ 4027.182663] [] (__handle_domain_irq) from []
(gic_handle_irq+0x4c/0x88)
[ 4027.191054] [] (gic_handle_irq) from []
(__irq_svc+0x6c/0xa8)
[ 4027.198569] Exception stack(0xc1501ed8 to 0xc1501f20)
[ 4027.203644] 1ec0:
 007c7460
[ 4027.211861] 1ee0: fe60  e000 c1506e34 c1506e7c 0001
0001 c15de2ba
[ 4027.220078] 1f00: c10e6414 c1501f34 c1501f14 c1501f28 c012cdd4 c010a6f4
60010013 
[ 4027.228297] [] (__irq_svc) from []
(arch_cpu_idle+0x30/0x4c)
[ 4027.235732] [] (arch_cpu_idle) from []
(default_idle_call+0x38/0x3c)
[ 4027.243863] [] (default_idle_call) from []
(do_idle+0x11c/0x158)
[ 4027.251643] [] (do_idle) from []
(cpu_startup_entry+0x28/0x30)
[ 4027.259251] [] (cpu_startup_entry) from []
(rest_init+0xd4/0xd8)
[ 4027.267036] [] (rest_init) from []
(start_kernel+0x490/0x4c0)
[ 4027.274579] ---[ end trace 0152fed7b0e69663 ]---
[ 4027.279905] Unable to handle kernel NULL pointer dereference at virtual
address 
[ 4027.288098] pgd = 2f826f0f
[ 4027.290843] [] *pgd=
[ 4027.294466] Internal error: Oops: 5 [#2] PREEMPT SMP ARM
[ 4027.299804] Modules linked in: snull(O) sbull(O+) hello_1(O) xt_state
xt_conntrack nft_counter nft_chain_nat_ipv4 ipt_MASQUERADE nft_compat
pru_rproc irq_pruss_intc rpmsg_rpc pruss bnep virtio_rpmsg_bus
uio_pruss_shmem pruss_soc_bus ti_vip ti_vpe btsdio ti_sc
videobuf2_dma_contig ti_csc bluetooth ti_vpdma v4l2_fwnode v4l2_mem2mem
v4l2_common videobuf2_memops videobuf2_v4l2 videobuf2_common videodev media
ecdh_generic brcmfmac brcmutil cfg80211 omap_remoteproc remoteproc virtio
virtio_ring usb_f_ncm usb_f_mass_storage usb_f_rndis u_ether libcomposite
uio_pdrv_genirq uio gpio_pisosr spidev [last unloaded: snull]
[ 4027.354148] CPU: 0 PID: 9 Comm: ksoftirqd/0 Tainted: G  D W  O
 4.19.94-ti-r50 #1buster
[ 4027.362884] Hardware name: Generic DRA74X (Flattened Device Tree)
[ 4027.369016] PC is at snull_tx+0xf4/0x234 [snull]
[ 4027.373660] LR is at dev_hard_start_xmit+0xd4/0x2cc
[ 4027.378560] pc : []lr : []psr: 000f0013
[ 4027.384854] sp : d4197d28  ip :   fp : d4197d9c
[ 4027.390102] r10:   r9 : bf7b7280  r8 : 006e
[ 4027.395349] r7 : 006e  r6 : c1506e08  r5 : d1cdf800  r4 : d1ce6002
[ 4027.401905] r3 : 0020  r2 : d1cdf800  r1 : 6674692a  r0 : 02ff
[ 4027.408462] Flags: nzcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment
none
[ 4027.415629] Control: 10c5387d  Table: 9196806a  DAC: 0051
[ 4027.421401] Process ksoftirqd/0 (pid: 9, stack limit = 0xf5db9d5e)
[ 4027.427609] Stack: (0xd4197d28 to 0xd4198000)
[ 4027.431988] 7d20:   0400  002a 0400
02aa 0400
[ 4027.440204] 7d40: d4197d6c c0b6a16c 4008 d18c0240

[beagleboard] Re: Servo control: pulse width working range ?

2020-09-16 Thread Dennis Lee Bieber 
On Wed, 16 Sep 2020 07:36:14 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Pavel Yermolenko
 wrote:

>I noticed that many servo motor manufacturers don't provide datasheets for 
>their products (for example for my servo it's the case)
>Generic values that can be found on the web don't work for every servo.
>For example what should be pulse width for 0/90/180/360 degrees.
>I suppose the value of pulse widths depends on a particular model.
>

Very few servos have a 360 rotation range... +/- 90 degree is more
common (the exception being servos that have had the position feed back
logic removed and act as variable speed continuous motors).

https://www.jameco.com/jameco/workshop/howitworks/how-servo-motors-work.html

1.5mS pulse should be the "neutral" position (middle of the range).

https://learn.adafruit.com/adafruit-motor-selection-guide/rc-servos
https://learn.adafruit.com/adafruit-motor-selection-guide/continuous-rotation-servos

>For example I noticed that if pulse width in quite low, the servo heats up 
>as an iron.

Likely you are over (under) driving the position, and the servo can not
physically move to the position you are requesting -- this leaves the coils
energized with the servo pushing against the internal end-stop.

My suggestion would be that you write a short calibration program with
which you adjust the pulse width from neutral, one step at a time, until
the servo reaches an end point (ie; the control "horn" stopped moving while
you changed the pulse width), then back up until you just detect the horn
has moved off the end-stop. Record that value and repeat for the other
direction. Maybe put a sticker on the servo with the values of the
end-point pulse widths -- neutral position should be the average of those
two values.

Do that for all your servos, and either use the minimum span for all,
or program the limits per servo (if using Python, install Adafruit Blinka
and libraries for CircuitPython -- the servo class allows override of
min/max pulse width; they default to 0.5 - 2.5ms, but do state that
"standard" servos are supposed to work with 1.0 - 2.0ms width).

https://learn.adafruit.com/circuitpython-essentials/circuitpython-servo
https://learn.adafruit.com/circuitpython-on-raspberrypi-linux (ignore the
R-Pi, it works for BBB also)
https://learn.adafruit.com/using-servos-with-circuitpython/high-level-servo-control




-- 
Dennis L Bieber

-- 
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/nkb4mfd0pbjeigumqjvhb0k8gur9qql2ed%404ax.com.

[beagleboard] Re: Servo control: pulse width working range ?

2020-09-16 Thread robert.sty...@gmail.com 
My memory is a little rusty, but IIRC

With remote control (RC) servos, there is a pulse width between 1ms and 2ms 
to give minimum to maximum angle.  
There is pulse repetition rate of 20ms.

I found these 
 


Pulse width cycle time 20ms, repetition 50Hz
Pulse width duty 5% to 10%

On Wednesday, 16 September 2020 at 15:36:14 UTC+1 py.o...@sunrise.ch wrote:

> Hello,
>
> I noticed that many servo motor manufacturers don't provide datasheets for 
> their products (for example for my servo it's the case)
> Generic values that can be found on the web don't work for every servo.
> For example what should be pulse width for 0/90/180/360 degrees.
> I suppose the value of pulse widths depends on a particular model.
>
> For example I noticed that if pulse width in quite low, the servo heats up 
> as an iron.
>
> Any comments ?
>
> 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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/4601daa7-3863-46ec-8b39-34e7dfff3125n%40googlegroups.com.

Re: [beagleboard] omap2_mcspi 48030000.spi: chipselect 0 already in use

2020-09-16 Thread Mark Mitchell 
Hi Robert -
Thanks so much for your quick reply.  
We initially did try the most recent version but could not get that to work 
so stepped back to earlier versions as that is a very large jump as you 
said.  we also tried the uboot approach but that did not work either.  now 
I am suspicious that it is because we were not using ver. 4.14 or newer.

Is there a guide to show how to set up the uEnv.txt file and any others to 
use Uboot to load the device trees? I dont quite understand how or what 
cape universal is doing or when to use it or not.

Thanks for your help.

Mark


On Tuesday, September 15, 2020 at 3:47:56 PM UTC-7 RobertCNelson wrote:

> On Tue, Sep 15, 2020 at 5:43 PM markmi...@cynmark.com
>  wrote:
> >
> > Hi All -
> > I am not very familiar with using this chat so please have patience with 
> me.
> >
> > I am working on a beaglebone black based system that we are trying to 
> move from kernel Ver 3.8 to 4.4.
> >
> > We have a working code base that runs on ver 3.8 but when I try to run 
> it on ver 4.4 I get the message
> > 11.682162] omap2_mcspi 4803.spi: chipselect 0 already in use
> > [ 11.688461] spi_master spi1: spi_device register error 
> /ocp/spi@4803/channel@0
> > [ 11.696131] of_spi_notify: failed to create for 
> '/ocp/spi@4803/channel@0'
> > [ 11.703325] __of_changeset_entry_notify: notifier error 
> @/ocp/spi@4803/channel@0
> > [ 11.884030] omap2_mcspi 4803.spi: chipselect 1 already in use
> > [ 11.890275] spi_master spi1: spi_device register error 
> /ocp/spi@4803/channel@1
> > [ 11.897937] of_spi_notify: failed to create for 
> '/ocp/spi@4803/channel@1'
> > [ 11.905139] __of_changeset_entry_notify: notifier error 
> @/ocp/spi@4803/channel@1
> > [ 12.215468] omap2_mcspi 481a.spi: chipselect 0 already in use
> > [ 12.221776] spi_master spi2: spi_device register error 
> /ocp/spi@481a/channel@0
> > [ 12.229461] of_spi_notify: failed to create for 
> '/ocp/spi@481a/channel@0'
> > [ 12.236658] __of_changeset_entry_notify: notifier error 
> @/ocp/spi@481a/channel@0
> > [ 12.642142] omap2_mcspi 481a.spi: chipselect 1 already in use
> > [ 12.648433] spi_master spi2: spi_device register error 
> /ocp/spi@481a/channel@1
> > [ 12.656098] of_spi_notify: failed to create for 
> '/ocp/spi@481a/channel@1'
> > [ 12.663293] __of_changeset_entry_notify: notifier error 
> @/ocp/spi@481a/channel@1
> >
> >
> > This appears in the dmesg log and at boot up.
> >
> > during boot I get the message
> >
> > loading /boot/dtbs/4.4.113-ti-r145/am335x-boneblack-uboot.dtb ...
> >
> > so It seems there is a conflict between this file and my device tree 
> which uses the same settings as BB-SPIDEV0-00A0.dts and BB-SPIDEV1-00A0.dts
> >
> > I have tried using the BB-SPIDEV0 dtbo files instead and get same 
> problem.
> >
> > The SPI ports (0 and 1) both work correctly except that the spi0 chip 
> select line functions correctly on program startup but when I call it for a 
> specific function it goes low and stays low.
> >
> > so really ther are 2 questions -
> > Why is this not allowing my normal functioning of the device tree like 
> it was.
> >
> > 2 - Is there something that changed with the way ioctl() handles the spi 
> accesses that is now broken in ver 4.4 but worked ok in ver 3.8
> >
> >
> > the complete version I am using is
> > Linux beaglebone 4.4.113-ti-r145 #1 SMP Mon Jan 29 19:44:54 UTC 2018 
> armv7l GNU/Linux
> >
> > Please let me know if there is specific information I can supply to help 
> resolve this question?
>
>
> Whenever i read users moving from v3.8.x to -> xyz... i have to ask,
> are you still using "load device tree overlays while booting the
> kernel"???
>
> That is no longer supported..
>
> We really recommend all users switch to u-boot overlays with at least
> the v4.14.x-ti based kernel.
>
> This is a pretty drastic change for anyone running a 3.8.x based setup.
>
> So i'd advise you take a new microsd card, blank out the eMMC, and
> test with a newer buster-iot image:
>
> https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-iot/
>
> and just see if you can get your application working on that..
>
> 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/64bed642-aa2a-42af-a552-b74a9266507an%40googlegroups.com.

[beagleboard] Re: Beaglebone Black - Network Manager & VNC

2020-09-16 Thread Dennis Lee Bieber 
On Wed, 16 Sep 2020 05:09:05 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Michael Coulton
 wrote:

>Hello
>I've flashed an 8 GB micro SD card with the Debian (4 GB) version found on 
>the BB site. I now want a GUI to use the built in network manager and VNC. 

I would presume you mean an image from
http://beagleboard.org/latest-images

>What desktop do you recommend I use i.e Gnome, KDE etc. Also I have an 

It might be faster to pull a non-production image from
https://rcn-ee.net/rootfs/bb.org/testing/ that has LXQT in the name. Those
already have a desktop defined. The most recent would be
https://rcn-ee.net/rootfs/bb.org/testing/2020-09-07/buster-lxqt/ (I
wouldn't bother with the flasher images for LXQT at all -- they leave
barely enough free space to even log into the device )
{Heck, even an 8GB uSD card could be uncomfortable with an LXQT image, if
one is adding enough application stuff [GNAT, etc., your VNC]!

| BeagleBoard.org Debian Buster LXQt Image 2020-08-19

debian@beaglebone:~$ df
Filesystem 1K-blocksUsed Available Use% Mounted on

/dev/mmcblk0p1   7572696 3318996   3894940  47% /

}

>Archer T2U Nano V1 WiFi doggle that I'd like to use. Does anyone know the 
>commands I needed to download and install the driver for that? 
>

https://suraj.dev/blog/configuring-wireless-usb-adapter-archer-t2u-nano-on-linux


-- 
Dennis L Bieber

-- 
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/4s94mfd9ro3fpn0mrfttq2noo5sfb48ik9%404ax.com.

[beagleboard] Servo control: pulse width working range ?

2020-09-16 Thread Pavel Yermolenko 
Hello,

I noticed that many servo motor manufacturers don't provide datasheets for 
their products (for example for my servo it's the case)
Generic values that can be found on the web don't work for every servo.
For example what should be pulse width for 0/90/180/360 degrees.
I suppose the value of pulse widths depends on a particular model.

For example I noticed that if pulse width in quite low, the servo heats up 
as an iron.

Any comments ?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/7177fb2f-ec1f-4638-92e2-55e1c97bc7a3o%40googlegroups.com.

Re: [beagleboard] bone script written for PocketBeagle doesn't work on BBB

2020-09-16 Thread Pavel Yermolenko 
Works fine !
Thanks.

On Wednesday, September 16, 2020 at 3:45:07 PM UTC+2, RobertCNelson wrote:

> bonescript is being scrapped, use adafruit-beaglebone-io-python... 
>
>
> https://github.com/adafruit/adafruit-beaglebone-io-python 
>
> 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/3506f7a5-d10e-443a-bcb2-1ba903d9beeeo%40googlegroups.com.

Re: [beagleboard] bone script written for PocketBeagle doesn't work on BBB

2020-09-16 Thread Pavel Yermolenko 
Thanks Robert,

BBB seems blocked when I tried to disable pwm one more time:

debian@beaglebone:/sys/class/pwm/pwmchip1/pwm-1:1$ echo 0 > enable 
^C
^C

Hot reboot ?

Sincerely,

Pavel

On Wednesday, September 16, 2020 at 3:45:07 PM UTC+2, RobertCNelson wrote:
>
> On Wed, Sep 16, 2020 at 8:33 AM Pavel Yermolenko  > wrote: 
> > 
> >  Hello, 
> > 
> > I modified bone script pwm.js from Derek Molloy book, adapting pin for 
> BBB (in bold): 
> > 
> > var b = require('bonescript'); 
> > var pin = "P9_21";   // Use P1.08 or P1.36 by default on PocketBeagle 
> > var dutyCycle = 0.75; 
> > var frequency = 1; 
> > 
> > b.pinMode(pin, b.OUTPUT); 
> > b.getPinMode(pin, printPinMux); 
> > b.analogWrite(pin, dutyCycle, frequency, display); 
> > 
> > function printPinMux(val){ 
> >console.log('mux = '+val.mux); 
> >console.log('name = '+val.name); 
> > } 
> > 
> > function display(val){ 
> >console.log(val); 
> > } 
> > 
> > Doesn't work: 
> > 
> > debian@beaglebone:~/exploringbb/chp06/bone$ sudo nodejs pwm.js 
> > error: error updating PWM freq and value: 
> /sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1/pwm-1:1, 
> Error: EINVAL: invalid argument, write 
> > { err: 
> >'error updating PWM freq and value: 
> /sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1/pwm-1:1, 
> Error: EINVAL: invalid argument, write' } 
> > warning: single argument callbacks will be deprecated.please use 
> node-style error-first callbacks: callback(err,response) 
> > mux = undefined 
> > name = UART2_TXD 
> > 
> > Any suggestions ? 
>
> bonescript is being scrapped, use adafruit-beaglebone-io-python... 
>
>
> https://github.com/adafruit/adafruit-beaglebone-io-python 
>
> 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/5ac23de7-8f70-4201-9c77-52dbf250bfcdo%40googlegroups.com.

[beagleboard] Re: bone script written for PocketBeagle doesn't work on BBB

2020-09-16 Thread Pavel Yermolenko 
Then I tried to disable a pwm channel:

debian@beaglebone:/sys/class/pwm/pwmchip1/pwm-1:1$ echo 0 > enable

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11581.921142] Internal error: : 1028 [#1] PREEMPT SMP ARM

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.013693] Process bash (pid: 1968, stack limit = 0xca6774a9)

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.019553] Stack: (0xdb4b9e18 to 0xdb4ba000)

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.023931] 
9e00:   db4b9e6c 
da8ab330

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.032148] 9e20: 0fa0 da8ab350 07d0  db4b9e64 
db4b9e40 c079ef58 c07a1ec4

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.040364] 9e40: c1506e08 dc5e519c  da8ab330 0002 
dc73a440 db4b9ea4 db4b9e68

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.048582] 9e60: c079f8dc c079edf8  0fa0 07d0 
  754b2d89

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.056800] 9e80: db4b9ed4 c079f824 db18c380   
db4b9f60 db4b9ebc db4b9ea8

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.065018] 9ea0: c08d69d8 c079f830 c08d69b0 db18c380 db4b9ed4 
db4b9ec0 c03abb1c c08d69bc

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.073236] 9ec0: 0002 db18c380 db4b9f0c db4b9ed8 c03ab10c 
c03abae0  

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.081453] 9ee0: dac3b988 c03ab014 db0bd540 01fd5128 db4b9f60 
  0004

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.089671] 9f00: db4b9f24 db4b9f10 c0319564 c03ab020 0002 
db0bd540 db4b9f54 db4b9f28

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.097888] 9f20: c031976c c0319548  c033bd58 db0bd540 
c1506e08 db0bd540 01fd5128

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.106106] 9f40:   db4b9f94 db4b9f58 c0319a4c 
c03196c4  

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.114324] 9f60:   db4b9f94 754b2d89 0074 
01fd5128 b6f01db0 0004

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.122542] 9f80: c0101204 db4b8000 db4b9fa4 db4b9f98 c0319ad8 
c03199e4  db4b9fa8

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.130760] 9fa0: c0101000 c0319acc 0074 01fd5128 0001 
01fd5128 0002 

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.138977] 9fc0: 0074 01fd5128 b6f01db0 0004 0002 
0002  

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.147194] 9fe0: 0004 bec31770 b6e995b3 b6e22746 6030 
0001  

Message from syslogd@beaglebone at Sep 16 13:35:27 ...
 kernel:[11582.259598] Code: 13a07004 03a07001 13e0400c 03e04003 (e1d350b0) 
Connection to 10.42.0.39 closed.
pavel@ALABAMA:~$

-- 
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/5df709bb-5603-4baa-8493-ecd3ba44026co%40googlegroups.com.

Re: [beagleboard] bone script written for PocketBeagle doesn't work on BBB

2020-09-16 Thread Robert Nelson 
On Wed, Sep 16, 2020 at 8:33 AM Pavel Yermolenko  wrote:
>
>  Hello,
>
> I modified bone script pwm.js from Derek Molloy book, adapting pin for BBB 
> (in bold):
>
> var b = require('bonescript');
> var pin = "P9_21";   // Use P1.08 or P1.36 by default on PocketBeagle
> var dutyCycle = 0.75;
> var frequency = 1;
>
> b.pinMode(pin, b.OUTPUT);
> b.getPinMode(pin, printPinMux);
> b.analogWrite(pin, dutyCycle, frequency, display);
>
> function printPinMux(val){
>console.log('mux = '+val.mux);
>console.log('name = '+val.name);
> }
>
> function display(val){
>console.log(val);
> }
>
> Doesn't work:
>
> debian@beaglebone:~/exploringbb/chp06/bone$ sudo nodejs pwm.js
> error: error updating PWM freq and value: 
> /sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1/pwm-1:1, 
> Error: EINVAL: invalid argument, write
> { err:
>'error updating PWM freq and value: 
> /sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1/pwm-1:1, 
> Error: EINVAL: invalid argument, write' }
> warning: single argument callbacks will be deprecated.please use node-style 
> error-first callbacks: callback(err,response)
> mux = undefined
> name = UART2_TXD
>
> Any suggestions ?

bonescript is being scrapped, use adafruit-beaglebone-io-python...


https://github.com/adafruit/adafruit-beaglebone-io-python

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/CAOCHtYhFz%3DYoxnPayUOW9VeJrum2kJtAzZisYVZWjNsGKxGqKg%40mail.gmail.com.

Re: [beagleboard] Beaglebone Black - Network Manager & VNC

2020-09-16 Thread Robert Nelson 
On Wed, Sep 16, 2020 at 7:09 AM Michael Coulton  wrote:
>
> Hello
> I've flashed an 8 GB micro SD card with the Debian (4 GB) version found on 
> the BB site. I now want a GUI to use the built in network manager and VNC. 
> What desktop do you recommend I use i.e Gnome, KDE etc. Also I have an Archer 
> T2U Nano V1 WiFi doggle that I'd like to use. Does anyone know the commands I 
> needed to download and install the driver for that?
>
> Thanks in advance for any help that can be provided.

Grab one of the "lxqt" testing images,

https://elinux.org/Beagleboard:Latest-images-testing

it will be released as official..

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/CAOCHtYj%2BasHo9X5xuis1rWSD1kGj8LFomtRzjY0RDYXM4yuonQ%40mail.gmail.com.

Re: [beagleboard] Starting kdump-tools: kdump is not supported by this kernel ... failed! at BeagleBone AI

2020-09-16 Thread Robert Nelson 
On Wed, Sep 16, 2020 at 7:02 AM  wrote:
>
> I have a kernel panic happening and I want to analyze the core dump. However, 
> the following error occurs during booting at BeagleBone AI
>
> [7.758681] kdump-tools[1024]: Starting kdump-tools: kdump is not 
> supported by this kernel ... failed!
> [   10.728480] kdump-tools[1210]: Stopping kdump-tools: kexec unload failed: 
> Function not implemented
> [   10.744723] kdump-tools[1210]: failed to unload kdump kernel ... failed!
> [   11.158265] kdump-tools[1235]: Starting kdump-tools: kdump is not 
> supported by this kernel ... failed!
>
> How do I fix this problem?

enable kexec support in the kernel.

Can you share your panic, it's probably a known one..

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/CAOCHtYgF3_11obvSDDKGfBXQAOtOQqoJgAe0FuTWAQ6AvczPwg%40mail.gmail.com.

[beagleboard] bone script written for PocketBeagle doesn't work on BBB

2020-09-16 Thread Pavel Yermolenko 
 Hello,

I modified bone script *pwm.js *from Derek Molloy book, adapting pin for 
BBB (in bold):

var b = require('bonescript');
var pin = "*P9_21*";   // Use P1.08 or P1.36 by default on PocketBeagle
var dutyCycle = 0.75;
var frequency = 1;

b.pinMode(pin, b.OUTPUT);
b.getPinMode(pin, printPinMux);
b.analogWrite(pin, dutyCycle, frequency, display);

function printPinMux(val){
   console.log('mux = '+val.mux);
   console.log('name = '+val.name);
}

function display(val){
   console.log(val);
}

Doesn't work:

debian@beaglebone:~/exploringbb/chp06/bone$ sudo nodejs pwm.js
error: error updating PWM freq and value: 
/sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1/pwm-1:1, 
Error: EINVAL: invalid argument, write
{ err:
   'error updating PWM freq and value: 
/sys/devices/platform/ocp/4830.epwmss/48300200.pwm/pwm/pwmchip1/pwm-1:1, 
Error: EINVAL: invalid argument, write' }
warning: single argument callbacks will be deprecated.please use node-style 
error-first callbacks: callback(err,response)
mux = undefined
name = UART2_TXD

Any suggestions ?

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.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/0ee2a7ee-f815-42ea-9a77-4d71cc7fe017o%40googlegroups.com.

Re: [beagleboard] Re: pygame displaying on /dev/fb0 - Solved

2020-09-16 Thread Mark A. Yoder 
Jon:
  Thanks...

I'm thinking of getting rid of reset.sh since on.sh effectively does a 
reset when you rerun it.

--Mark

On Sunday, September 13, 2020 at 7:32:53 PM UTC-4 jonn...@gmail.com wrote:

> I was able to resolve the issue I was having with your fb and pygame 
> examples.  I had to ensure the BUS was set to '0' and the pin GPIO values 
> were set properly in 'on.sh'. The same was true in reset.sh with 'busnum=0'
>
> Also, it seemed that if I ran the examples in 'usr', I had to reboot the 
> board for the 'fb' examples to work.
>
> It's all working now.
> Nice job.
>
> Jon
>
> On Sat, Sep 12, 2020 at 5:05 PM jonnymo  wrote:
>
>> Cool.
>>
>>   I am unable to get your pygame or other fb examples to work but I can 
>> get the 'usr' examples to work. 
>>  
>> Perhaps this is for another post, but in your examples, are you using 
>> SPI0 or SPI1?  It seems some of the setup for the examples are set for SPI0 
>> and some are set for SPI1 yet the wiring listing in "EBC Exercise 12a 2.4 
>> TFT LCD display via SPI" seems to indicate SPI0.  
>>
>>
>> Cheers,
>>
>> Jon 
>>
>> On Sat, Sep 12, 2020 at 1:20 PM Mark A. Yoder  
>> wrote:
>>
>>> I now have it working with sudo.  I just added 
>>> https://github.com/MarkAYoder/BeagleBoard-exercises/blob/a531dca3a5f52813623bd40ea42bc733decfc70d/displays/ili9341/fb/pygame/clock.py#L26
>>>
>>> I needed to set SDL_NOMOUSE to 1.
>>>
>>> --Mark
>>>
>>> On Saturday, September 12, 2020 at 3:33:23 PM UTC-4 Mark A. Yoder wrote:
>>>
 Jon:
   Well.  su does give different results than sudo.  I tried su 
 again and it works!

 So, how can I set permissions so I don't have to su or sudo?

 --Mark

 p.s.  Thanks for all the suggestions.

 On Friday, September 11, 2020 at 6:23:45 PM UTC-4 jonn...@gmail.com 
 wrote:

> In my config, BBAI running 4.14 kernel, I found two instances of fbcon:
> $ sudo find / -name fbcon
>
> * /sys/devices/virtual/graphics/fbcon*
> * /sys/class/graphics/fbcon*
>
>
> The framebuffer console seems to be attached to the console layer. 
>
> *$ cat /sys/class/vtconsole/vtcon1/bind*
> *1*
> *$ cat /sys/class/vtconsole/vtcon0/bind*
> *0*
>
>
> Info on fbcon:
> https://www.kernel.org/doc/html/latest/fb/fbcon.html
>
>
> Not sure if this helps at all.
>
> Cheers,
>
> Jon
>
>
> On Fri, Sep 11, 2020 at 11:24 AM Robert Nelson  
> wrote:
>
>> On Fri, Sep 11, 2020 at 12:56 PM Dennis Lee Bieber
>>  wrote:
>> >
>> > On Fri, 11 Sep 2020 04:56:42 -0700 (PDT), in
>> > gmane.comp.hardware.beagleboard.user "Mark A. Yoder"
>> >  wrote:
>> >
>> >
>> > >
>> > >Are you sure there is a fbcon module?
>> >
>> > 
>> https://www.kernel.org/doc/html/latest/fb/fbcon.html#a-configuration
>> >
>> > ... seems to imply it may not have been built for the standard 
>> release BBB
>> > kernels.
>>
>> It's enabled:
>>
>> │ 
>> ┌───┐
>>  │
>>   │ │[*] Framebuffer Console support
>>  │ │
>>   │ │-*-   Map the console to the primary display device
>>  │ │
>>   │ │[*]   Framebuffer Console Rotation
>>  │ │
>>   │ │[ ]   Framebuffer Console Deferred Takeover  
>>   │
>>
>> 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...@googlegroups.com.
>>
> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/beagleboard/CAOCHtYgkXSOoJQ%3D_iBLcYBuFc4Q0%3D%2B6y29EXzABPn5uK-Qbqdw%40mail.gmail.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...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/beagleboard/ea2cc40d-aa9e-462e-a454-b0bea9a7da4cn%40googlegroups.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

[beagleboard] Beaglebone Black - Network Manager & VNC

2020-09-16 Thread Michael Coulton 
Hello
I've flashed an 8 GB micro SD card with the Debian (4 GB) version found on 
the BB site. I now want a GUI to use the built in network manager and VNC. 
What desktop do you recommend I use i.e Gnome, KDE etc. Also I have an 
Archer T2U Nano V1 WiFi doggle that I'd like to use. Does anyone know the 
commands I needed to download and install the driver for that? 

Thanks in advance for any help that can be provided.

Michael

-- 
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/a0319ba9-0898-4bb8-b0a9-23045c6d90edo%40googlegroups.com.

[beagleboard] Starting kdump-tools: kdump is not supported by this kernel ... failed! at BeagleBone AI

2020-09-16 Thread jisu . au 
I have a kernel panic happening and I want to analyze the core dump. 
However, the following error occurs during booting at BeagleBone AI 

[7.758681] kdump-tools[1024]: Starting kdump-tools: kdump is not 
supported by this kernel ... failed!
[   10.728480] kdump-tools[1210]: Stopping kdump-tools: kexec unload 
failed: Function not implemented
[   10.744723] kdump-tools[1210]: failed to unload kdump kernel ... failed!
[   11.158265] kdump-tools[1235]: Starting kdump-tools: kdump is not 
supported by this kernel ... failed!

How do I fix this problem?

-- 
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/638ae16a-9955-4392-8670-c6b15cd9e2c2o%40googlegroups.com.

[beagleboard] kdump is not supported by this kernel ... failed! at 4.19.94-ti-r50

2020-09-16 Thread debian 
debian@beaglebone:~/uartC$  sudo kdump-config load
[sudo] password for debian:
kdump is not supported by this kernel ... failed!

I am developing a device driver.
I have a kernel panic in the driver module and want to install sudo apt-get 
install kdump-tools and analyze the core dump.

However, I get the following error.  => kdump is not supported by this 
kernel ... failed!

Also, if you run sudo kdump-config load command
kdump is not supported by this kernel ... failed! Error message is 
displayed.

How do I analyze a core dump using kdump?
I don't know how to analyze the core dump.
Please explain in detail.

thank you a lot for your help

-- 
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/ef2b034e-4ef1-41c3-9b37-f9360c82b321o%40googlegroups.com.