H3 hardware progress - Not working yet but a step closer...

[sirwio]

Hi All,

Thought it was time to brief the list of some progress that I have had in my attempt to port the H3 hardware to run VOMP.

At first I had a shot at setting up the develpment environment on an x86_64 machine but that did not work for me so I took one of my retired x86 machines and turned it into a VOMP development machine.

Since the vomp project build didn't succeed due to problems with the split_dongle script I decided to use the mvpmc project as base since it actually produced a dongle that worked for me on my H3 hardware. In order to get a vompclient I followed the following steps.

1. Fetched the latest mvpmc sources from the git repository.
2. Moved the original mvpmc/src folder to src.org.
3. Creeate a soft link to the /vomp/vompclient directory named src
4. Copied the SConstrict file from src.org to the src directory
5. Modified the Program section in the SConscript file to include the vompclient source files.
6. Modified the LIBS to use only pthreads, jpeg, rt and stdc++
7. Modified mvpmc/src/main.cc to not init and shutdown the MtdMVP class instance. Defaulted the videoFormat to Video::PAL
7. Added a env.Replace(CXX = cross + 'gcc') to the mvpmc/SConstruct file in the section where the compiler is setup for the mvp build.
8. Build the dongle with make mvp

Putting the dongle files on the tftp server with dhcp, tftd and mvprelay configured correctly make the H3 boot up (Guides for setting up mvprelay etc for H3 hw can be found on mvpmc wiki)

Telnet'ing to the mediamvp and executing the vompclient binary then gives:

# vompclient -d
18:06:34.681507 [info]   Core - Starting up...
18:06:34.682245 [info]   Core - Signal handlers set up successfully
18:06:34.682865 [info]   Core - Remote module initialised
18:06:34.683366 [info]   Core - LED module initialised
18:06:34.683836 [info]   Core - Mtd module initialised
18:06:34.685376 [info]   Core - Timers module initialised
18:06:34.685888 [info]   Core - Read from MTD: PAL 720x576
18:06:35.120155 [debug]  Video - Setting aspect to 0
18:06:35.130090 [debug]  Video - Setting aspect to 0
18:06:35.610085 [debug]  Video - Setting aspect to 0
18:06:35.611040 [info]   Core - Video module initialised
18:06:35.695059 [info]   Core - OSD module initialised
18:06:35.704087 [debug]  Audio - MUTE OFF OFF OFF
18:06:35.704625 [info]   Core - Audio module initialised
18:06:35.705100 [info]   Core - VDR module initialised
18:06:35.705560 [info]   Core - ViewMan module initialised
18:06:35.706023 [info]   Core - Command module initialised
18:06:35.706485 [notice] Core - Startup successful
18:06:35.707079 [debug]  Box - Construct, now 1
18:06:35.707605 [debug]  View - Construct 0x100c2568, now 1
18:06:35.943547 [debug]  View - Destruct, now 0
18:06:35.944091 [debug]  Box - Destruct, now 0
18:06:35.944627 [debug]  Box - Construct, now 1
18:06:35.945116 [debug]  View - Construct 0x100c26c8, now 1
18:06:35.945639 [debug]  Box - Construct, now 2
18:06:35.946124 [debug]  Command - PAL wallpaper selected
18:06:36.075583 [ERR]    BJpeg - Can't open JPEG
18:06:36.181650 [debug]  Box - Construct, now 3
18:06:36.182165 [debug]  View - Construct 0x100c4960, now 2
18:06:36.212116 [debug]  VConnect - Draw done
18:06:36.212769 [debug]  UDP - Starting UDP command server
18:06:36.251722 [debug]  UDP - Starting wait
18:06:36.252400 [debug]  UDP - UDP command server started
18:06:36.253235 [notice] VDR - Broadcasting for server
18:06:37.750262 [notice] VDR - Broadcasting for server

From the log it actually seems as if the vompclient is up and running. Before I evolve any further e.g. adds the missing jpeg files to to filesystem and fixes that the client finds my VDR machine I would like some feedback from you guys reading this list.

1. Will the approach taken above work or are there some missing propritary binaries that must be used from the hauppauge dongle.
2. Are there any drawbacks compiling with the gcc-3.4.5-uClib-0.9.28 croostool instead of the one used by the vomp. (The gcc-3.4.5-uClib-0.9.28 is used by default by mvpmc builds)
3. What file should one modify to change the application launched when the dongle is booted and the kernel is started.


- Magnus