no guide listings for live tv or guide listings

[lollercoaster]

Thanks for your help guys at least we're getting somewhere!
If it is the crypto chip does that mean a complete motherboard replacement or could the chip just be replaced?

[Darren King]

Chip can be replaced but it is not something you can do, nor can be done in the space of five minutes. My approach (given as it is now my responsibility) will be to do an on the spot board change and I'll have to investigate your board at a later date.

Of course there is no cost for this I'll have to cop it sweet as being something I missed or has gone belly up inside the warranty period.

I'll be in touch via email to square up a suitable time for all this to happen.

[petestrash]

Darren,

When you get around to fault finding, I would still be interested to know if that board does pull slices using an already imaged drive. Given that it's not sending a TCDID to the emulator. Or if was just bad luck having the crypto die since you tested it.

Peter.

PS my package arrived from you today, after delay by the courier. I haven't opened it yet, but I understand the contents are under an embargo till Monday

[Darren King]

Hi Peter

Will do. I'm just organising taking delivery of the TiVo and will investigate further when I get it. Ultimately lollercoaster will end up with a working TiVo but I am just as eager to interrogate the board as he is for a 100% working TiVo

Glad to hear the package arrived. Public announcement on what I have up my sleeve is due for release Monday but I welcome any comments you have (or any of the other half a dozen lucku people with the modification) to comment off list with me.

[Darren King]

This looks better:

Aug 5 22:27:59 (none) comm[168]: About to execute: /tvbin/genkey 128 1 2>&1
Aug 5 22:28:00 (none) comm[168]: Command succeeded
Aug 5 22:28:00 (none) comm[168]: EncryptLog: key was empty for BACKHAUL_PRIVATE
Aug 5 22:28:00 (none) comm[168]: Done with actual private logs processing
Aug 5 22:28:00 (none) comm[168]: About to execute: /tvbin/crypto -gsn 2>&1
Aug 5 22:28:01 (none) comm[168]: Command succeeded
Aug 5 22:28:01 (none) comm[168]: About to execute: /tvbin/crypto -gsv 2>&1
Aug 5 22:28:02 (none) comm[168]: Command succeeded
Aug 5 22:28:03 (none) comm[168]: About to execute: /tvbin/crypto -x -gek 2>&1
Aug 5 22:28:10 (none) comm[168]: Command succeeded
Aug 5 22:28:11 (none) comm[168]: SvcLogRqst: rename failed (/var/log/svclog probably doesn't exist) skipping
Aug 5 22:28:11 (none) comm[168]: SvcLogRqst: rename failed (/var/log/commlog probably doesn't exist) skipping
Aug 5 22:28:11 (none) comm[168]: Start TCD411 Request ==================
Aug 5 22:28:11 (none) comm[168]: areaCode: 003
Aug 5 22:28:11 (none) comm[168]: prefix: %2C%23401
Aug 5 22:28:11 (none) comm[168]: dialInAreaCode:
Aug 5 22:28:11 (none) comm[168]: curPhNum:
Aug 5 22:28:11 (none) comm[168]: objVer:
Aug 5 22:28:11 (none) comm[168]: tcdId: 002XXXXXXXXD9
Aug 5 22:28:11 (none) comm[168]: callId: <removed>
Aug 5 22:28:11 (none) comm[168]: dialPrefix: %2C%23401
Aug 5 22:28:11 (none) comm[168]: dialToneCheck: 1
Aug 5 22:28:11 (none) comm[168]: offHookDetect: 0
Aug 5 22:28:11 (none) comm[168]: tonePulseDial: T
Aug 5 22:28:11 (none) comm[168]: callWaitPrefix:
Aug 5 22:28:11 (none) comm[168]: tollFreeAuth: 1
Aug 5 22:28:11 (none) comm[168]: callType: TS_SR_ACCEPTED
Aug 5 22:28:11 (none) comm[168]: swVerName: 3.0-01-1-000
Aug 5 22:28:11 (none) comm[168]: End TCD411 Request ==================
Aug 5 22:28:11 (none) comm[168]: sigType=st=2 connector=con=1...
Aug 5 22:28:11 (none) comm[168]: Error getting the Avalanche Disk Directories: errNmNameNotFound
Aug 5 22:28:11 (none) comm[168]: Start Ident ==================
Aug 5 22:28:11 (none) comm[168]: version: 3
Aug 5 22:28:11 (none) comm[168]: centerID: 002XXXXXXXXD9
Aug 5 22:28:11 (none) comm[168]: reasonCode: 6
Aug 5 22:28:11 (none) comm[168]: softwareDesc:

Needless to say it is now working and has a valid ID number (which I have partially removed from this post). A couple of entries might look odd for "normal" operation as this was lifted from the setup call, but the end result is that it has finished loading and indexing valid guide data and is happily running like it should.

The problem? Yes it was hardware and did not take long to find. It turned out to be transistor Q16. For those playing at home, the crypto chip is the "Atmel" branded chip right next door to the IDE hard disk connector and the front panel connector and Q16 is in the group of parts in the near vicinity. It's involvement is to buffer the data exchange between the crypto chip and the processor and I it had simply gone belly-up for an unknown reason.

A little signal tracing of the data requests to and from the crypto chip showed where they were stopping and another replacement transistor and everything is up and running.... and I didn't even have to remove the board from the case

[petestrash]

Good catch Darren!

Peter.

[zollymonsta]

Probably a silly question.. but you've mentioned 'Crypto'... This is a chip on the MB I take it? What does it do? (Cryptology or something?)

[Darren King]

Yep.

The part is an Atmel AT90SC3232 secure microcontroller which can do some really cool stuff and very under utilised on the TiVo. Datasheets can be found here: http://soviva.com/pdf/at90sc3232.pdf

For use in the TiVo it contains in it (among other things) the service ID number of your TiVo which are supposed to be unique but not always the case as was recently highlighted on the OzTiVo email list of two people having the same ID number. This is because it can be changed with the right tools of the trade.

In a TiVo the "crypto chip" as it is called here sends and receives serial data instructions from the main processor to validate the TiVo and as highlighted in this thread the ability to download valid guide data.

[lollercoaster]

hey guys

Funny how such a small thing can cause so much trouble. Want to thankDarren once again for being an absolute legend and making the trip to fully functional tivo a helleva lot easier.

[petestrash]

Probably a silly question.. but you've mentioned 'Crypto'... This is a chip on the MB I take it?

It's the chip numbered '34' (U17) on the front of the mainboard between the front panel and IDE connectors.


Peter.