[beagleboard] Re: BeagleBone Black (C) USB based touch not working

[Dennis Lee Bieber]

On Sun, 30 May 2021 16:13:00 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Kasimir
 wrote:

>But I'm hanging with touch. 
>Installed is: Linux beaglebone 4.19.94-ti-r64 #1buster SMP PREEMPT Fri May 
>21 23:57:28 UTC 2021 armv7l GNU/Linux
>Plan is to write directly into the framebuffer, no X no desktop.
>That works also fine, very fast.
>But with touch  I'm running out of ideas.
>Was expecting a conflict with USB Network, is now deactivated, no change.
>/dev/input/event0 is existing. But no events .

Could you be having a conflict with the native LCD system (which is
active in parallel with the HDMI). The native LCD system expects a
capacitive touchscreen on the P9 (I think) pins.

Might help if you identified WHICH product you are using. This one
https://www.amazon.com/GeeekPi-1024x600-Capacitive-Monitor-Raspberry/dp/B075QCXLPF/ref=asc_df_B075QCXLPF/?tag=hyprod-20=df0=309707619534==g=5324710204179150785c===9017241=pla-570706414713=1
mentions a "free driver" (I would hope so -- I doubt they'd sell many if
they said the driver was extra cost; though the best documentation I find
for it says "driver-free" -- meaning no driver needed).

I would note that the compatibility list on

does NOT mention beagle bone, though the body text does.

"""
Power Supply 5V/1A via USB port
"""
OUCH! Beagle USB maxes out at 500mA (which is the spec for USB2); you'll
need a powered USB hub with high-power ports.

"""
Please make sure the FPC cable is fastened and please connect the
MicroUSB cable to your device so that it can communicate with the touch
panel.
Please make sure the USB power cable is connected properly.
"""

Implies one needs to use a separate USB power supply

One port is power, the other is data.


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

[beagleboard] BeagleBone Black (C) USB based touch not working

[Kasimir]

Hi,
working on a new product, 7" HDMI display with optical touch should be used.
LCD works fine ( 1024x600).
But I'm hanging with touch. 
Installed is: Linux beaglebone 4.19.94-ti-r64 #1buster SMP PREEMPT Fri May 
21 23:57:28 UTC 2021 armv7l GNU/Linux
Plan is to write directly into the framebuffer, no X no desktop.
That works also fine, very fast.
But with touch  I'm running out of ideas.
Was expecting a conflict with USB Network, is now deactivated, no change.
/dev/input/event0 is existing. But no events .
Touch hardware is ok, works fine on WIN10 PC. 
I'm sure, I'm not the first one . need help on that.
Thanks in advance for every good hint :-)
Kasimir

PS I checked it with destop, also. Touch doesn't work.

-- 
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/b3f9feda-df28-4b64-a02b-ca537a0ec019n%40googlegroups.com.

[beagleboard] Re: Reducing Boottime in Beaglebone Black

[Dennis Lee Bieber]

On Sun, 30 May 2021 11:51:27 -0700 (PDT), in
gmane.comp.hardware.beagleboard.user Karishma Jaiswal
 wrote:


>Can u suggest any way to change my application as currently my application 
>is getting call from .bashrc file and now it's taking around 35 sec to get 
>execute.
>Some how can I call the .bashrc file bit faster?  
>this will really help to reduce the boot time.

Since .bashrc is a SHELL CONFIGURATION file, it gets run when a BASH
shell is opened. So how are you getting to a bash shell? (It is vaguely
possible you have some script being started by systemd, or a @reboot
crontab entry, which specifies that the bash shell is to be used).

Bash shell/command interpreter won't be available until most of the OS
has booted.


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

Re: [beagleboard] Re: Reducing Boottime in Beaglebone Black

[Karishma Jaiswal]

@Robet Nelson

Can u suggest any way to change my application as currently my application 
is getting call from .bashrc file and now it's taking around 35 sec to get 
execute.
Some how can I call the .bashrc file bit faster?  
this will really help to reduce the boot time.

Thanks
Karishma Jaiswal

On Monday, May 24, 2021 at 9:56:44 PM UTC+5:30 robert.sty...@gmail.com 
wrote:

> Can you start these services later?
>
> If you cannot just sleep, or hibinate to save power, and have to cold boot 
> quickly.
> I would hope for something like:
>
> Initially
> load the kernel loader
> load the kernel
> (load root file-system service)
> (load IPC or network service)
> load the turnkey application
>
> Then as Needed
> load device and file-system services
>
>
> For a screen based turnkey app, you can only display a splash screen for a 
> few seconds, before the user thinks it is broken, a bit longer for an 
> animated splash screen. Imagine a car radio, something has happen 
> immediately after power on (speaker click or LED indicator or screen 
> backlight), then less than half a second "Tuning..." before music appears.
>
> On Monday, 24 May 2021 at 16:42:08 UTC+1 RobertCNelson wrote:
>
>> On Sun, May 23, 2021 at 9:19 PM Karishma Jaiswal 
>>  wrote: 
>> > 
>> > @Dennis L Bieber Really thanks for your detailed explanation about the 
>> each services. 
>> > I also updated ubuntu from 16 to 18 and done some modification in the 
>> services. now my board's logs are as below 
>> > My system should be working as station mode but may be future, we will 
>> add AP mode also. 
>> > I will also remove nginx services. 
>> > 
>> > 
>> > ubuntu@beaglebone:~$ systemd-analyze blame 
>> > 51.048s dev-mmcblk1p1.device 
>> > 28.951s generic-board-startup.service 
>> > 6.550s led-status.service 
>> > 6.133s systemd-hwdb-update.service 
>> > 4.805s grub-common.service 
>> > 4.611s loadcpufreq.service 
>> > 3.244s nginx.service 
>> > 3.053s systemd-udev-trigger.service 
>> > 2.971s avahi-daemon.service 
>> > 2.099s ssh.service 
>> > 1.958s archive_log.service 
>> > 1.839s keyboard-setup.service 
>> > 1.548s rsyslog.service 
>> > 1.512s connman.service 
>> > 1.438s systemd-user-sessions.service 
>> > 1.404s wpa_supplicant.service 
>> > 1.315s ofono.service 
>> > 1.291s systemd-logind.service 
>> > 1.275s cpufrequtils.service 
>> > 1.253s tacread-keymap.service 
>> > 887ms systemd-timesyncd.service 
>> > 786ms us...@0.service 
>> > 685ms systemd-journald.service 
>> > 508ms kmod-static-nodes.service 
>> > 498ms dev-mqueue.mount 
>> > 487ms fake-hwclock.service 
>> > 469ms sys-kernel-config.mount 
>> > 459ms systemd-fsck-root.service 
>> > 422ms systemd-tmpfiles-setup-dev.service 
>> > 406ms systemd-modules-load.service 
>> > 401ms systemd-sysctl.service 
>> > 390ms systemd-tmpfiles-setup.service 
>> > 387ms setvtrgb.service 
>> > 350ms nvda.service 
>> > 341ms sys-fs-fuse-connections.mount 
>> > 
>> > 
>> > Also want to know that in ubuntu 18, why below two task taking so much 
>> time and how we can reduce it further to achieve the over all boot time as 
>> 30 sec. Any suggestion will help me. 
>> > 
>> > 51.048s dev-mmcblk1p1.device 
>> > 28.951s generic-board-startup.service 
>>
>> as long as you don't use usb-serial, usb-flash, or usb-networking on 
>> the "OTG" USB port, you can nuke generic-board-startup.service 
>>
>> 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/33fc689f-5f9e-403a-83b1-428fa27f90d0n%40googlegroups.com.

Re: [beagleboard] Re: PRU Assumptions - True or False

['Mark Lazarewicz' via BeagleBoard]

Hello AMF 
I have 5 year old quad core win 8.1 64 bit 8 G ram laptop running Ubuntu 16.04 
VM  I used it to build SDK kernel no problems and 
a new Debian 10 VM with a 64 bit GCC on same machine. The Debian VM is flaky 
last attempt  I just got memory calloc error on building 5.5 TI BSP from the 
instructions on Digikey.


I have a 10 year old win 7 quad core desktop I think it has 8 gig ram I never 
used I was contemplating either a dual boot or nuke win 7 a native Linux build 
box. Problem is it's probably 32 bit.
Which compiler are you using? 32 bit or 64 bit and a link to it would be great 
and Is this 5.x or 5.x 
I have several BBW, an am335x SK and two BBB for hardware. I'm also a JTAG user 
so I'd prefer nothing in EMC I don't know if that's possible?
I also probably need SD preparation instructions to go with kernel.
You know something like Robert has and the SDK has that even a college student 
can follow
Thanks alot!!
Mark


Sent from Yahoo Mail on Android 
 
  On Sun, May 30, 2021 at 11:02 AM, amf wrote:   Hi 
lazarman,on ubuntu 20.04, this builds ok
git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev
git checkout remotes/origin/ti-linux-rt-5.4.y -b ti-linux-rt-5.4.y
./build_kernel.sh

I've used VirtualBox before with Ubuntu 16/18/20 without any issues, what VM 
are you using?Several years ago a company that I worked for used some other VM, 
it was a pain in the azz to get to work, if i hear the name again i'll know if 
that was the one.I haven't used Debian for a desktop, so I can't help you with 
that. 

On Saturday, May 29, 2021 at 3:45:46 PM UTC-5 lazarman wrote:

 Hello 
I've failed to build following those instructions twice in Mainline  and twice 
using the TI BSP.version. the 2nd attempt of TI BSP is hung as we speak after 
resolving dependencies for several hours. Each attempt takes hours and the 
build_kernel script doesnt care you already cloned 2G of code it clones 
torvald.gitso I retried 4 times by running build_kernel.sh twice in both 
directories
The Mainline had some git branch errors today
I paid to upgrade my internet for this testing and was ready to buy a 64 bit 
box but am scared these instructions need a refresh and I will waste $$
what would be lovely is a 2 line like is in the instruction pasted below with 
something that will work for sure.the two directories I created are both on 
wrong branches and  dont complete a buil d
Be nice not keep downloading the 2G kernel source I know there is  a rebuild.sh 
but I am assuming that is used after a successful buildIf these instruction 
need I tweek I can understand I can test them. If it old and not supported a 
heads up would be appreciated. So I need something like this below with 
everything needed to build a kernel including the previous two steps as my two 
directories are on the wrong branches
Thanks

For TI v5.4.x: Real-Time#~/ti-linux-kernel-dev/
git checkout origin/ti-linux-rt-5.4.y -b tmp


Build:




Build:
#user@localhost:~/ti-linux-kernel-dev$
./build_kernel.s


Build:
#user@localhost:~/ti-linux-kernel-dev$
./build_kernel.s

Build:
#user@localhost:~/ti-linux-kernel-dev$
./build_kernel.sh



On Friday, May 28, 2021, 02:56:38 PM CDT, Robert Nelson 
 wrote:  
 
 On Fri, May 28, 2021 at 2:53 PM Robert Nelson  wrote:
>
> On Fri, May 28, 2021 at 2:45 PM Robert Nelson  wrote:
> >
> > On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz  wrote:
> > >
> > > Thanks!!
> > >
> > > Think of it as I'm validating the instructions I think having these is 
> > > something good. Unfortunately my VM blew up just now.
> > >
> > > I KNOW your adamant about not supporting VM.
> > >
> > > So I'll build a dedicated Debian 8 dev box.
> > >
> > > Any hints tips lessons learned what you use be appreciated.
> > >
> > > Have a great long weekend.
> >
> > VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the
> > failure point..
>
> I think mainline might work:
>
> debian@beaglebone:~$ uname -r
> 5.13.0-rc3-bone2.2
> debian@beaglebone:~$ dmesg | grep pru
> [    2.044506] remoteproc remoteproc1: 4a334000.pru is available
> [    2.045701] remoteproc remoteproc2: 4a338000.pru is available
> debian@beaglebone:~$ ls /dev/remoteproc/pruss-core*
> /dev/remoteproc/pruss-core0:
> coredump  device  firmware  name  power  recovery  state  subsystem  uevent
>
> /dev/remoteproc/pruss-core1:
> coredump  device  firmware  name  power  recovery  state  subsystem  uevent
>
> @Mark Yoder can you test? ;)

debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "start" > state
[  243.355728] remoteproc remoteproc1: powering up 4a334000.pru
[  243.366533] remoteproc remoteproc1: Booting fw image
am335x-pru0-fw, size 32456
[  243.374135] remoteproc remoteproc1: remote processor 4a334000.pru is now up

debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "stop" > state
[  296.981371] remoteproc remoteproc1: stopped remote processor 4a334000.pru

Regards,

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


-- 
For more options, 

Re: [beagleboard] Re: PRU Assumptions - True or False

[amf]

Hi lazarman,
on ubuntu 20.04, this builds ok

git clone https://github.com/RobertCNelson/ti-linux-kernel-dev.git
cd ti-linux-kernel-dev
git checkout remotes/origin/ti-linux-rt-5.4.y -b ti-linux-rt-5.4.y
./build_kernel.sh

I've used VirtualBox before with Ubuntu 16/18/20 without any issues, what 
VM are you using?
Several years ago a company that I worked for used some other VM, it was a 
pain in the azz to get to work, if i hear the name again i'll know if that 
was the one.
I haven't used Debian for a desktop, so I can't help you with that. 

On Saturday, May 29, 2021 at 3:45:46 PM UTC-5 lazarman wrote:

> Hello 
>
> I've failed to build following those instructions twice in Mainline  and 
> twice using the TI BSP.version. the 2nd attempt of TI BSP is hung as we 
> speak after resolving dependencies for several hours. Each attempt takes 
> hours and the build_kernel script doesnt care you already cloned 2G of code 
> it clones torvald.git
> so I retried 4 times by running build_kernel.sh twice in both directories
>
> The Mainline had some git branch errors today
>
> I paid to upgrade my internet for this testing and was ready to buy a 64 
> bit box but am scared these instructions need a refresh and I will waste $$
>
> what would be lovely is a 2 line like is in the instruction pasted below 
> with something that will work for sure.
> the two directories I created are both on wrong branches and  dont 
> complete a buil d
>
> Be nice not keep downloading the 2G kernel source I know there is  a 
> rebuild.sh but I am assuming that is used after a successful build
> If these instruction need I tweek I can understand I can test them. If it 
> old and not supported a heads up would be appreciated. So I need something 
> like this below with everything needed to build a kernel including the 
> previous two steps as my two directories are on the wrong branches
>
> Thanks
>
>
> For TI v5.4.x: Real-Time
>
> #~/ti-linux-kernel-dev/
> git checkout origin/ti-linux-rt-5.4.y -b tmp
>
> Build:
>
>
>
>
> Build:
>
> #user@localhost:~/ti-linux-kernel-dev$
> ./build_kernel.s
>
>
>
> Build:
>
> #user@localhost:~/ti-linux-kernel-dev$
> ./build_kernel.s
>
>
> Build:
>
> #user@localhost:~/ti-linux-kernel-dev$
> ./build_kernel.sh
>
>
>
>
>
> On Friday, May 28, 2021, 02:56:38 PM CDT, Robert Nelson <
> robert...@gmail.com> wrote: 
>
>
> On Fri, May 28, 2021 at 2:53 PM Robert Nelson  wrote:
> >
> > On Fri, May 28, 2021 at 2:45 PM Robert Nelson  
> wrote:
> > >
> > > On Fri, May 28, 2021 at 2:41 PM Mark Lazarewicz  
> wrote:
> > > >
> > > > Thanks!!
> > > >
> > > > Think of it as I'm validating the instructions I think having these 
> is something good. Unfortunately my VM blew up just now.
> > > >
> > > > I KNOW your adamant about not supporting VM.
> > > >
> > > > So I'll build a dedicated Debian 8 dev box.
> > > >
> > > > Any hints tips lessons learned what you use be appreciated.
> > > >
> > > > Have a great long weekend.
> > >
> > > VM's usually fail when using 'dd'.. so MLO/u-boot.img is usually the
> > > failure point..
> >
> > I think mainline might work:
> >
> > debian@beaglebone:~$ uname -r
> > 5.13.0-rc3-bone2.2
> > debian@beaglebone:~$ dmesg | grep pru
> > [2.044506] remoteproc remoteproc1: 4a334000.pru is available
> > [2.045701] remoteproc remoteproc2: 4a338000.pru is available
> > debian@beaglebone:~$ ls /dev/remoteproc/pruss-core*
> > /dev/remoteproc/pruss-core0:
> > coredump  device  firmware  name  power  recovery  state  subsystem  
> uevent
> >
> > /dev/remoteproc/pruss-core1:
> > coredump  device  firmware  name  power  recovery  state  subsystem  
> uevent
> >
> > @Mark Yoder can you test? ;)
>
> debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "start" > state
> [  243.355728] remoteproc remoteproc1: powering up 4a334000.pru
> [  243.366533] remoteproc remoteproc1: Booting fw image
> am335x-pru0-fw, size 32456
> [  243.374135] remoteproc remoteproc1: remote processor 4a334000.pru is 
> now up
>
> debian@beaglebone:/dev/remoteproc/pruss-core0$ echo "stop" > state
> [  296.981371] remoteproc remoteproc1: stopped remote processor 
> 4a334000.pru
>
>
> 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/6dcb2683-2d69-45fa-a4a8-62bb6c6e3ed0n%40googlegroups.com.

Re: [beagleboard] Re: PRU Assumptions - True or False

[Robert Nelson]

> Be nice not keep downloading the 2G kernel source I know there is  a 
> rebuild.sh but I am assuming that is used after a successful build
> If these instruction need I tweek I can understand I can test them. If it old 
> and not supported a heads up would be appreciated. So I need something like 
> this below with everything needed to build a kernel including the previous 
> two steps as my two directories are on the wrong branches

There is a variable in system.sh to set this up, most users use it
once and done..

https://github.com/RobertCNelson/ti-linux-kernel-dev/blob/ti-linux-5.4.y/system.sh.sample

```
###OPTIONAL: LINUX_GIT: specify location of locally cloned git tree.
#
#LINUX_GIT=/home/user/linux-stable/
```

Anywhere in your root file system, clone Torvald's tree:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/

and set LINUX_GIT variable to it's location:

For example in home:

cd /home//repos/
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

Then set in system.sh
LINUX_GIT=/home//repos/linux/

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/CAOCHtYjWo%3DTrXqp04tkMA31O_fQ%2BJr_SFRz7hDZ_jGw49OS1qA%40mail.gmail.com.