After just a month of crashing the box I finally managed to create a working wrapper dll for the tv2engine.dll, that's what gets returned to the tv2clientce.exe in the diagbuffer:
TV2SecureCore Initialization Diagnostics (0x00000000, Success)
Successful initialization.
Server Authentication is enabled
Low level initialization diagnostics
Sigma XPU Security Core initialized and ready.
Session Key Registers : 8
Boundary Key Registers : 16
Public Key Registers : 6
XtaskLoadImage : \Hard Disk\XTLApp_1.2_XosE0.bin
XtaskUnloadImage : \Hard Disk\XTUApp_1.2_XosE0.bin
I guess this explains what those two files are for ;)
Cool,
I was also wondering what those files were for...
Mick
hmm so app ucode is loaded via tv2engine then. wonder what th boot ucode is for and where it used.
had wondered if the bootloader initialised these.
yes they are used by the bootloader... but if they do not exist it loads uCodes that are stored in flash
the file:
XTLApp_1.2_XosE0.bin and the other file XTUApp_1.2_XosE0.bin is also in the nk.bin.
But they are not equal.
Inside nk.bin the file XTUApp_1.2_XosE0.bin has the following header:
14 00 02 07
at the top Filesystem it is:
16 00 02 07
the rest of the file is obviously not equal :-)
The file XTLApp_1.2_XosE0.bin behaves the same as described before.
The uCodes on NMT Firmware have also such a header.
I described it in another post, but just in german.
Short version:
video_ucode - 3a 00 03 07
audio_ucode - 3b 00 04 07
demux_ucode - 3c 00 05 07
irq_handler - 3d 00 06 07
so does anyone know, why these files have the same filename, but are different?
Or what these 8 bytes means?