TMDXEVM3358: Setup issue

Hello Jason,

They are probably skipped or miss-calibrated the touch screen calibration step. Can you tell them to delete the /etc/udev/rules.d/ws-calibrate.rules file, reboot the board and recalibrate the touch screen coordinates by taping on the tree red crosses.

root@am335x-evm:~# rm -rf /etc/udev/rules.d/ws-calibrate.rules

Best regards,
Kemal

Dear Kemal :

According your instruction ,our engineer do delete the /etc/udev/rules.d/ws-calibrate.rules file, reboot the board and recalibrate the touch screen coordinates, but the screen show three different status  one by one as attachment: not showing the tree red crosses .Please may you advise how to treat it on next step ?

Screen re-calibrate.docx

Dear Kemal:

My engineer told me that they are fault to do  reboot the board and recalibrate the touch screen coordinates.

Best Regards

Jason

Can you tell them to attach a USB mouse, run the Touch -> Interaction -> Multipoint Flames application and check if the touches are properly reflected on the screen?

Dear Kemal:

According to you suggestion to do re-calibration for screen,now our engineer feedback that the old problem are not resolved ,and has new problem .

He send the output information as following :

[  OK  ] Found device /dev/ttyS3.

[  OK  ] Listening on Load/Save RF Kill Switch Status /dev/rfkill Watch.

         Starting Update UTMP about System Boot/Shutdown...

         Starting Network Time Synchronization...

[  OK  ] Started Network Time Synchronization.

[  OK  ] Found device /dev/mmcblk0p1.

[  OK  ] Started Update UTMP about System Boot/Shutdown.

         Starting Synchronize System and HW clocks...

[  OK  ] Reached target System Time Synchronized.

[  OK  ] Started Synchronize System and HW clocks.

[   14.608322] usbcore: registered new interface driver usbfs

[   14.643001] usbcore: registered new interface driver hub

[   14.699150] usbcore: registered new device driver usb

[   14.819145] musb-hdrc musb-hdrc.0.auto: MUSB HDRC host driver

[   14.887141] musb-hdrc musb-hdrc.0.auto: new USB bus registered, assigned bus number 1

[   14.951658]  remoteproc0: powering up 4a334000.pru0

[   14.963567] hub 1-0:1.0: USB hub found

[   14.982097] hub 1-0:1.0: 1 port detected

[   14.990479]  remoteproc0: Booting fw image am335x-pru0-fw, size 75724

[   15.041836] ti-pruss 4a300000.pruss: configured system_events = 0x0000000000030000 intr_channels = 0x00000005 host_intr = 0x00000005

[   15.060544] musb-hdrc musb-hdrc.1.auto: MUSB HDRC host driver

[   15.101454] musb-hdrc musb-hdrc.1.auto: new USB bus registered, assigned bus number 2

[   15.117528]  remoteproc0: remote processor 4a334000.pru0 is now up

[   15.144842] hub 2-0:1.0: USB hub found

[   15.155719] virtio_rpmsg_bus virtio0: creating channel rpmsg-pru addr 0x1e

[   15.163473] virtio_rpmsg_bus virtio0: rpmsg host is online

[   15.171232] hub 2-0:1.0: 1 port detected

[   15.184859]  remoteproc1: powering up 4a338000.pru1

[   15.200515]  remoteproc1: Booting fw image am335x-pru1-fw, size 75724

[   15.244205] ▒CCCCCCCC         //(at this step ,it can't go next step and request to re-start ,again and again)

U-Boot SPL 2016.05-g4db46a6bbd (Mar 29 2017 - 17:44:45)

Trying to boot from MMC1

reading args

spl_load_image_fat_os: error reading image args, err - -1

reading u-boot.img

reading u-boot.img

reading u-boot.img

reading u-boot.img

U-Boot 2016.05-g4db46a6bbd (Mar 29 2017 - 17:44:45 -0400)

CPU  : AM335X-GP rev 2.1

Model: TI AM335x EVM

       Watchdog enabled

DRAM:  1 GiB

NAND:  256 MiB

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

reading uboot.env

<ethaddr> not set. Validating first E-fuse MAC

Net:   eth0: ethernet@4a100000

Warning: usb_ether MAC addresses don't match:

Address in SROM is         de:ad:be:ef:00:01

Address in environment is  98:5d:ad:34:37:e3

, eth1: usb_ether

Press SPACE to abort autoboot in 2 seconds

switch to partitions #0, OK

mmc0 is current device

SD/MMC found on device 0

reading boot.scr

** Unable to read file boot.scr **

reading uEnv.txt

** Unable to read file uEnv.txt **

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1...

switch to partitions #0, OK

mmc0 is current device

SD/MMC found on device 0

3477576 bytes read in 253 ms (13.1 MiB/s)

42154 bytes read in 39 ms (1 MiB/s)

Kernel image @ 0x82000000 [ 0x000000 - 0x351048 ]

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Device Tree to 8fff2000, end 8ffff4a9 ... OK

Starting kernel ...

Dear Kemal:
Our customer complains that it lasted two weeks ,but haven't any progress on the result .

Please may you approve us to return it to US and checked by your experts ? It's better that you send a new replacement to us and we return the old one to you.

Thank you for your support .

Best Regards

Jason