DM365 remote control issues

c wragg

I am using the DM365 evaluation board but the remote control is intermittent.

The remote supplied with the kit is not the same as shown on the pictures so I presume it is a newer model.

I have printf'ed in the source code that reads from the remote controller ic and I get different button code when pressing the keys, sometimes correct and at other times incorrect and this is messing the demo application up.

What can I try to rectify this?

over 16 years ago

0 Juan Gonzales over 16 years ago

TI__Mastermind 37340 points

can you tell us which file you put the print statements in? I want to duplicate this in my setup so I can investigate further.

FYI, in my setup, it works most of the time, but misses the key every now and then. I assumed it was weak batteries...but since your brought this up, I am wondering if this may be something else. We did move from an older model philips RCU unit into a newer model for DM355. I just checked the codes and they are slightly different between the older RCU and newer RCU nits fom Philips; our software team may have accounted for this already, but it is worth investigating. I have both RCU units as well as multiple platforms (DM6446, DM355, DM365...) which I can compare against and maybe get to the bottom of this.

0 c wragg over 16 years ago in reply to Juan Gonzales

Prodigy 50 points

Hi Juan

In my case in the folder ~/dvsdk_2_10_01_18/dvsdk_demos_2_10_00_17/dm365/interface there are several c files. If you take say menu.c you will find a call to Ir_getKey which returns the IR key code. If you printf after this (in pressed section) you can see the code returned and thus determine that the codes are not the same even when the same key is pressed. Note that the other c files need this added to see in all cases as the main program offloads to routines in each .c file for each menu option.

The c file holding the routine is in ~/dvsdk_2_10_01_18/dmai_1_21_00_10/packages/ti/sdo/dmai/linux/dm365/Ir,c

0 c wragg over 16 years ago in reply to c wragg

Prodigy 50 points

Hi Juan

Have you had chance to try it out yet?

I could do with an answer so I can code up some demonstrations to use with end customers.

0 Juan Gonzales over 16 years ago in reply to c wragg

TI__Mastermind 37340 points

not yet, I was planning on making some time this afternoon.

0 Juan Gonzales over 16 years ago in reply to Juan Gonzales

TI__Mastermind 37340 points

ok, we find the RCU model did not make any difference. We also found that other EVMs (other than DM365) do receive the correct code when a key is pressed and de-pressed. The control code basically boils down to a couple of I2C reads; the code is being read in a polled fashion via DMAI library. I suspect we may be looking at either bad firmware on MSP430 or an issue with i2c read; our investigation has shown we get random codes even when we do not press any keys. I will submit a bug and have this investigated at a deeper level by our software teams.

0 Tatsuya Ohsawa over 16 years ago in reply to Juan Gonzales

Prodigy 100 points

Hi !

I am worried by a remote control key of DM365, too.

When "Improvement" is pushed by remote control, "0x301C" can usually be acquired in IrGetKey.

However, it comes to acquire "0x3039" and "0x2039".

What is the cause?

Please teach the method of measures.

BestRegards.

Ohsawa

0 Tatsuya Ohsawa over 16 years ago in reply to Tatsuya Ohsawa

Prodigy 100 points

Then, is investigation progressing?

Although I am demanding the reply, there is no reply.

I am waiting for a reply.

BestRegards.

Ohsawa

0 Juan Gonzales over 16 years ago in reply to Tatsuya Ohsawa

TI__Mastermind 37340 points

Ohsawa,

This bug has been filed; from other discussions in this matter, I believe the problem lies in the DMAI code

"there is an error/mismatch in the DMAI function that reads the IR value (getIrVal in dmai/linux/dm365/Ir.c). The LOW byte should be read before the HIGH byte. The MSP430 code advances it's internal buffer pointer after the high byte is read, so if you read this byte first you can sometimes get invalid codes returned (but sometimes it works). If you fix the function in Ir.c, you should see better performance from the remote."

You can try the above suggestion in the mean time which should improve your RCU experience.

0 Tatsuya Ohsawa over 16 years ago in reply to Juan Gonzales

Prodigy 100 points

Hi,Juan,

Thank you for explaining it.

I want to fix a function of Ir.c, but do not know the way of a build of DMAI.

Please teach how to build of DMAI in detail.

0 Furuse over 16 years ago in reply to Tatsuya Ohsawa

TI__Intellectual 2200 points

Hello. Ohsawa-san,

To rebuild DMAI, you just need to execute "make dm365_al" at the DMAI directory in the DVSDK.
And then "make install", if you want to reinstall the sample programs to your target directory.
I assume that you have already configured Rules.make in the DVSDK root directory when you installed the DVSDK release.

Best regards,
Furuse

0 Tatsuya Ohsawa over 16 years ago in reply to Furuse

Prodigy 100 points

Hi Furuse,

Thank you for the reply.

Although "make dm365_al" was performed, the following link errors have occurred.

What is a cause?

Is a setup of a file(Rules.make) wrong?

-------------------------------------------------------------------------------------------------

[user@localhost dmai_1_21_00_10]$ make BUILD_TYPE=release VERBOSE=true dm365_al
make[1]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai'
make[1]: Nothing to be done for `dm365_al'.
make[1]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai'
make[1]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps'

Executing make dm365_al in subdirectory audio_decode1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_decode1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_decode1'

Executing make dm365_al in subdirectory audio_decode_io/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_decode_io'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_decode_io'

Executing make dm365_al in subdirectory audio_decode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_decode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_decode_io1'

Executing make dm365_al in subdirectory audio_encode1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_encode1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_encode1'

Executing make dm365_al in subdirectory audio_encode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_encode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/audio_encode_io1'

Executing make dm365_al in subdirectory image_decode_io/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_decode_io'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_decode_io'

Executing make dm365_al in subdirectory image_decode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_decode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_decode_io1'

Executing make dm365_al in subdirectory image_encode_io/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_encode_io'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_encode_io'

Executing make dm365_al in subdirectory image_encode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_encode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/image_encode_io1'

Executing make dm365_al in subdirectory speech_decode1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_decode1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_decode1'

Executing make dm365_al in subdirectory speech_decode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_decode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_decode_io1'

Executing make dm365_al in subdirectory speech_encode1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_encode1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_encode1'

Executing make dm365_al in subdirectory speech_encode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_encode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/speech_encode_io1'

Executing make dm365_al in subdirectory video_decode_io/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_decode_io'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_decode_io'

Executing make dm365_al in subdirectory video_decode_io2/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_decode_io2'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_decode_io2'

Executing make dm365_al in subdirectory video_display/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_display'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_display'

Executing make dm365_al in subdirectory video_encode_io/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_encode_io'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_encode_io'

Executing make dm365_al in subdirectory video_encode_io1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_encode_io1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_encode_io1'

Executing make dm365_al in subdirectory video_encode_io_multich1/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_encode_io_multich1'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_encode_io_multich1'

Executing make dm365_al in subdirectory video_loopback/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback'

Executing make dm365_al in subdirectory video_loopback_blend/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_blend'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_blend'

Executing make dm365_al in subdirectory video_loopback_convert/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_convert'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_convert'

Executing make dm365_al in subdirectory video_loopback_copy/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_copy'

Linking linux/video_loopback_copy_dm365.x470MV from appMain.dm365.o470MV linux/main.dm365.o470MV linux/video_loopback_copy_dm365_config/linker.cmd /home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/lib/dmai_linux_dm365.a470MV..
/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc -lpthread -lm -L/lib -lasound -Wl,-Map,linux/video_loopback_copy_dm365.x470MV.map -o linux/video_loopback_copy_dm365.x470MV appMain.dm365.o470MV linux/main.dm365.o470MV linux/video_loopback_copy_dm365_config/linker.cmd /home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/lib/dmai_linux_dm365.a470MV
/opt/mv_pro_5.0/montavista/pro/devkit/arm/v5t_le/bin/../lib/gcc/armv5tl-montavista-linux-gnueabi/4.2.0/../../../../armv5tl-montavista-linux-gnueabi/bin/ld: cannot find /home/a0756824/davinci_multimedia_application_interface/dmai/packages/ti/sdo/dmai/apps/video_loopback_copy/linux/video_loopback_copy_dm365_config/package/cfg/video_loopback_copy_dm365_x470MV.o470MV
collect2: ld はステータス 1 で終了しました
make[2]: *** [linux/video_loopback_copy_dm365.x470MV] Error 1
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_copy'
make[1]: *** [video_loopback_copy/.dm365_al] Error 2
make[1]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps'
make: *** [dm365_al] Error 2
[user@localhost dmai_1_21_00_10]$

-------------------------------------------------------------------------------------------------

BestRegards,

Ohsawa

0 Juan Gonzales over 16 years ago in reply to Tatsuya Ohsawa

TI__Mastermind 37340 points

does the following directory suggested in your log exist?

/home/a0756824/davinci_multimedia_application_interface/dmai/packages/ti/sdo/dmai/apps/

If not, you may have to do a 'make clean' prior to 'make dm365_al'. Otherwise, we may need to dig where the build tree is getting this directory..

0 Tatsuya Ohsawa over 16 years ago in reply to Juan Gonzales

Prodigy 100 points

Hi,Juan

Thank you for the reply.

>does the following directory suggested in your log exist?

I was sure that the directory does not exist.

>If not, you may have to do a 'make clean' prior to 'make dm365_al'.

After having executed "make clean", I executed "make dm365_al". The log is the following.

------------------------------------------------------------------------------------------------------------------------------

[user@localhost dmai_1_21_00_10]$ make dm365_al
make[1]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai'
make[1]: Nothing to be done for `dm365_al'.
make[1]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai'
make[1]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps'

Executing make dm365_al in subdirectory video_loopback_copy/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_copy'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_copy'

Executing make dm365_al in subdirectory video_loopback_resize/...
make[2]: Entering directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_resize'
make[2]: Nothing to be done for `dm365_al'.
make[2]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps/video_loopback_resize'
make[1]: Leaving directory `/home/user/dvsdk_2_10_00_17/dmai_1_21_00_10/packages/ti/sdo/dmai/apps'
[user@localhost dmai_1_21_00_10]$

------------------------------------------------------------------------------------------------------------------------------

BestRegards,

Ohsawa

0 Juan Gonzales over 16 years ago in reply to Tatsuya Ohsawa

TI__Mastermind 37340 points

I do not see any errors in this latest log, but it does not appear to have built anything either...

I also just noticed from your log that you are using DVSDK_2_10_00_17 which was an early release beta candidate; I would recommend upgrading to the GA release ; I can confirm DMAID builds without any issues in the GA release.

0 Tatsuya Ohsawa over 16 years ago in reply to Tatsuya Ohsawa

Prodigy 100 points

Juan,

Does you say that it can not build with "DVSDK_2_10_00_17"?

BestRegards,

Ohsawa

0 Juan Gonzales over 16 years ago in reply to Tatsuya Ohsawa

TI__Mastermind 37340 points

I have never used this beta DVSDK and hence I cannot confirm if DMAI build works in this DVSDK or not; it was meant as a beta early adoptor release and I would not recommend it for development; we have the 2.10.00.18 GA (General Availability) release which I have been using for quite some time and this release seems pretty stable. I have can cofirm there are no issues building DMAI in this GA release.

0 Tatsuya Ohsawa over 16 years ago in reply to Juan Gonzales

Prodigy 100 points

Juan,

I understood it.I tried it.

I had downloaded dvsdk_2_10_01_18. So, build with this version.

・dvsdk_2_10_00_18 (you)
・dvsdk_2_10_01_18 (me)

The build was completed without the error going out.

The check of the key of remote control has not been carried out yet.
Because I seem to take time a little, I will do a reply later.

BestRegards,
Ohsawa

0 Juan Gonzales over 16 years ago in reply to Tatsuya Ohsawa

TI__Mastermind 37340 points

this is great news, by the way, I am using 2.10.01.18 as well. 2.10.00.18 was a typo on my part; thanks for catching this

0 Tatsuya Ohsawa over 16 years ago in reply to Juan Gonzales

Prodigy 100 points

Juan,

It checked that the key of remote control was also normally acquirable.

It solved.

I appreciate your kind behavior from the bottom of my heart.

Thank you.

BestRegars,

Ohsawa

Processors

Processors forum

DM365 remote control issues