Tsop/eeprom?

[OneHwyMan]

[QUOTE]Originally posted by vyralsurfer
[B]I'm just begining to study up on Dish/BEV and am still heavily in the Dave scene. Well, with that said, I have some questions for ya. Now technically, I COULD just go through the steps and flash the EEPROM and TSOP and program myself a Rom10, but I'm in it for the knowledge right now, so most of these questions arent need-to-know things, but things I like to know to better understand what I'm doing.

1. Why do we need to flash the EEPROM/TSOP? Why cant we just program the cards? (I know, sounds like I'm too used to Dave....)

2. Is the TSOP like the equivilant of a computer's BIOS? or would that be the EEPROM? (Also, whats the diff between the two?)

3. Is it true that I can just re-program the TSOP (Or EEPROM, not sure lol) on a Dish system and get BEV? It would make sense since they run off of the same hardware and the same satellite locations...

Ok let me try to help you as much as I can and try to answer you questions in order asked.
Typicaly you only flash your Tsop after an ECM.
Your Tsop has information (alot like the BIOS)that is specific to your hardware,this is what gets hit by the ECMs and depending on the ird you may have one or two.
Your eeprom is just that,a ROM
You could just program cards but you still need to get info from the ird because they marry(boxkeys)
when you flash your Tsop what you are doing is erasing parts of the Tsop that get upgraded,thus needing to be updated by the sat provider(BEV or DISH)so saying this by pointing this "virgin"TSop to a specific bird(BEV or Dish)it will update that firmware,converting BEV to Dish or vice versa.


This just a general description,there is alot more detail but it could get very lonnng with the explanation and varies from ird to ird and AVR,Atmega,Rom2,3,10,11.

Welcome to Echostar testing.........lol


OHM:D

[OneHwyMan]

Oh yah
Always back up your Tsop,and spend a few $ on a digilock.

Just in case.


OHM:D


p.s. BEV and Dish have there own birds..

[OneHwyMan]

Thats right BUT ,now charlie is using an ECM that seeks out the eeprom lock.So if you had a lock on,you get a nag screen.
Go figure....lol

OHM

[t160hq]

Originally posted by vyralsurfer
Hey thanks again. I still got 1 more question...

What really is the Digital Lock? is it like an all-in-one EEPROM and TSOP locker?

Nope. digital lock and eeprom lock are two different
locks. Digital Lock is for the TSOP only. It prevents
writes to the TSOP.

The quick and simple answer is a TSOP requires
a logic low be sent to a specific pin
(the WE pin = write/erase) to enable a write or
erase of a specific byte or section of the TSOP.

The orginal TSOP lock used to just keep the WE
at a logic high all the time. This worked well until
DN developed a check that sends two logic low
pluses to cause a special response from the TSOP.
If the proper response is not received a bit of
code is excuted causing a Serious Error Nag.

Then the digital lock came about. It allows the
double logic low to be excuted for the check but not
the constant logic low necessary for a write.

t160hq

Almost forgot the eeprom bit. It just keeps
the WP (Write protect pin) of the eeprom at
a constant logic high preventing a write. A
eeprom requires a logic low on the WP pin
to perform a write. DN has hits for both the
TSOP and eeprom. Both hits write to either the
TSOP or the EEPROM depending on which hit it
is. They cause the serious error nag message.
On unprotected TSOP or EEPROM, after a reset
(unpluging and pluging back in), You end up
with America's Top One. The only channel that
will tune in or show up in the guide is 101.

In that case you have to either reflash the TSOP
or EEPROM. Whichever one was hit.