Cemu101.5 "Not currently have authorizatoin.. " HELP

[robx]

I have just completed doing a one-chip 2313 in my 3900 reciever...

Seems everything is good, i get the guide and the preview channels fine. But if try to go to any channel it says "Your smart card does not currently have authorization to view or purchase this program."

It use to do this on my rom2's back in N1 and after a few minutes it would come in but right now it never does...

Do you have to apply some type of tiers to the image on the bootdisk?

I used the cemu101.5 bootdisk creator.

Jtaged to a proper tsop for my 3900.

[chumlee]

I am getting the same message as you a 005, I get the freeview channles and that is all. Running the same ird as you a 3900 w/101.5 boot disk creator

I am getting the 005, I will try a few things tonight, and see what happens.

[rubberman]

getting the same error 05. any solutions?

[rubberman]

i found that using the updated CEMU101.5 boot disk creator helped fix my problem.

[ruciz]

005 is to do with your eeprom.bin file, you simply don't have keys. Remember the old N1 days when you would get the same error on power up, 20 min later it would be gone?

Put it on a low channel, in the 100-200 range for 5-10 min to see if it will roll the keys. If its still 005'ing you can try another channel but its likly that your EMM-G key is wrong and isn't grabbing/decrypting the new keys from the stream. Use a new version of the CEMU, patch the eeprom file to be able to handle the new EMM-G packet, or remove your blocker from your eeprom.bin and put static keys in there - you can't loop a floppy :)

[ruciz]

btw robx, I would suggest ordering in some samples from maxim-ic.com of the MAX232A chip and turning your 1-chip into a 2-chip for the cost of some solder and a few wires.. 12V going to a chip made to handle at max 7.5V isn't a good thing, then you can run your computer 100 feet away from your IRD and still be good :D

[blusky]

I had the same problem with the error 005 using a 3900 Ird. I let it sit for 4 hours still had 005 error. I finally checked my bin file to see if DT08V23 was writing the sk keys and it was not. I downloaded another DT08V23 file and it worked.

I still get the eror 005 for about to minutes while the keys roll. But it works fine. very stable. Some people do not get the error 005 at all. I am using the Updated 101.5 disk. Hope this helps.

On another note I have bben having some problems using computers that have around 32 Megs of ram. I am using a tiers.txt file. When I start cemu it goes just past tiers.txt on the screen then I get an memory error message. It somehow corrupts the disk. I have tried it twice with a P133 32megs ram and a Laptop P200 32 megs of ram. Presently using aP450 386 megs ram , no problem. Has anyone else had this experience?

[franko325]

Information (Jan30, 2006);
Dish Network testing with CEMU (WinXP/2000 and/or DOS boot) with AUTOROLL-KEYS function.
************************************************** **************
NOTE(FEB20, 2006); On Feb14/06, DishNetwork changed there key delivery method to include a false key pair as a method of disabling ‘auto-roll’ testing devices. (Happy Valentines from Dish :) For the interim, it will be necessary to obtain an older CEMU and bin that doesn't have auto-roll function in it.
Details of what happened on Feb14th/06:
DishNetwork inserted a $00 into their key-change packets to combat/circumvent auto-roll devises. When a legitimate system encounters a 00, it stops EMM processing; however, ‘auto-roll’ testing units do not. They pick up the EMM$42 (key-change) packet arriving after the $00 in the stream and use those keys, which are invalid. All auto-roll testing methods need coding to acknowledge these packets as being false. Until auto-roll bins are active again, non-auto-roll cemun2dos.zip will be used as the testing files in place of CEMU95A_Dish.zip in this document (please reflect accordingly). Also, obtain a copy of “Emulation Key Changer batch file.rar”, complements of TIDA, to assist in changing the keys as required (how-to is included in the rar-package). This is a handy little tool for quickly changing the keys in any non-auto-roll N2 bin image.
************************************************** **************
In my tests I use a jumper less-AVR interface (with 8515 chip), 2700IRD (CANJ-Build), and p853TSOP (the latest Dish Network release firmware).
(I have not tested this with p851(2700IRD) as the P853 is better code, and I haven't tested this method with 2313 flash and Max/Mel board.)
History/background;
The problems so many people have encountered when testing CEMU is due to the lack of error-free communications between the PC and the IRD. You need to understand that the CEMU method of communication is prone to initial failures, given all the variables (identified in this document) when attempting to obtain error-free communication between asynchronous devices (PC-COM ports) and synchronous devices (IRD).
Your PCs COM port communicates via RS232 asynchronous protocol, which uses 12volt logic (11volts in practice). However, your AVR/Atmel uses 5Volt TTL-logic to communicate synchronously, via a clocking signal, to your IRD (i.e. Your IRD communicates to the CAM slot/card via synchronous serial data transfer). The data transfer rate (baud) of the COM port is set to 115200 by the CEMU application, which closely (enough) matches the clocking signal of the IRD CAM slot to accomplish compatible communication between these dissimilar protocols.
In testing, if we limit the potentially damaging 12volt logic from our PC to match the 5volt logic of the AVR board with a ‘buffered’ cable, we will eliminate the possibility of harming our AVR or Atmel board, acquiring a stable CEMU testing platform.
Do NOT attempt to use an un-buffered cable, despite what you may have read elsewhere. It is necessary to build a "buffered" PCtoIRD cable for proper CEMU testing. If you have already used an un-buffered cable with no success, it will be difficult to rely on your AVR as being undamaged past this point. I.e. you may still be able to read and write to the AVR-Flash, however, the board may still not communicate to your CEMU application. (You can test this as we go.)
I believe the Max232/Atmel is a better match for this testing method, as it matches communication protocols between the COM port and the Max232 chip. Be aware, however, that the Max/Mel uses 5volt signaling when powered from the IRD, so a buffered cable is still the best-choice when testing with this configuration.
Given the above mentioned inconsistencies, the CEMU testing is prone to communication issues... but it will work effectively if you take certain precautions, which I'll attempt to relay in this document.
Another component that seems to be questioned/blamed often for failure to successfully test with CEMU is the type of PC or U(S)ART chip used.
All 32-bit PCs that have a RS232 COM port (9 pin DB male connector) will conform to the RS232 standard, and should be able to run the CEMU executable found in the cemu95a_dish.zip, which calls the "COM1 port” properly on any 32-bit PC. The CEMU application also requires 8Meg of RAM. I have tested the CEMU app on an IBM ValuePoint/486DX2, Dell GX100/500PII, and a Dell Latitude Laptop. All of these worked well after following these instructions.
Let’s start testing!
Tools needed;
- Any Dish/Bell IRD except 1000IRD (firmware no longer supported)
- FlashEdit-2[1][1].1beta9 (found in the file section)
- Jkeys29.xx
- jEEPersDX
- Cemu95a_dish.zip (Cemu95a_Auto.zip for B3V testing)
- Cemu101[1][1].5_DOS_DN_BootDisk_Creator.zip
- AVR board (no CAM required in slot)
- Buffered cable to communicate between PC COM port to AVR parallel interface.
- Obtain an un-modified TSOP or use a TSOP pre-edited with the IRD and BoxKey numbers described later in this document. DO NOT use ATMEGA-N2 modded TSOPs! (These will have IRD#R 00 4477 9361-67 when viewed using FlashEdit.)
Note: You should have a basic understanding of computers (how to copy Files, etc.).
First;
Flash your AVR with N201Ird2pcV2.pfg (found at end of this document) using jEEPers. (Note; You can clip and paste text to notepad and save as N201Ird2pcV2.pfg) Don’t forget to erase the AVR/Atmel flash first. This AVR image will work with B3V also as it does not set any particulars, (CEMU and the appropriate CAM image/bin file supplies the pertinent CAM info to IRD). Note; The time to write the flash takes about 10 seconds, as there is not much code/parameters here as the AVR/Atmel card only serves as a communication interface to the IRD. The CEMU application performs all of the CAM operations and auto-rolling functions.

Next;
Make your Buffered cable using Cat-5e cable. This will ensure low noise or EMI/EMF interference which could induce bit-errors into the PCtoIRD data streams. I have also used 3-conductor shielded audio cable with good results. I will not recommend flat telco cable, as some documents suggest. Keep the length less than 6 feet until success in testing is reached, (then make another cable if your requirements call for a greater distance between the PC and IRD).
You will need a DB9 female connector and a DB25 male connector, a zenier diode around 4.8-5.6 volt, and a 1k resistor (these components can be small wattage, not alot of current here :).
You may also substitute the zanier diode with another 1K resistor, effectively creating a voltage divider circuit. (i.e. 11volts / 2 = 5.5volts~TTL logic level… perfect!)
Connections; pin#5 on DB9 straight to pin#25 on DB25, Pin#2 on DB9 straight to pin#8 on DB25.
Connect the third (last) wire from pin#3 on DB9, and then on the DB25 end solder the 1K resistor between Pin#7 and this wire. Next, to limit the signal voltage at the AVR/IRD "receive" port to ~5volts, solder the band end of the zenier diode to the DB25 side of the 1k resistor. The other end of the zenier goes to pin#25 of the DB25 (ground). I have seen documents with the zenier installed backwards… beware of this mistake as a zenier with the band to ground is just a diode (0.7volts drop).
Note that I have not included a buffer for pin#8 of the DB25 as you may have read in other "How-To's". This is deliberate, as pin#8 is the transmitting line from the AVR/IRD which is 5volt logic, and therefore will work fine for RS232 receive line (pin#2 on COM1). The HI-level logic threshold of COM ports will trigger on any voltage above ~4 volts so there is no need to risk consumption of this TTL-voltage crossed a 1k resister resulting in too low a voltage.
Testing;
The first thing to test is communication of CEMU_95A_Dish from WinXP/2000 environment to insure your cable and AVR works/communicates properly. (Unzip this application into the default folder.)

To insure COM1 port resources are proper; under Windows device manager (right click on My Computer/Properties/Device Manager/Hardware), go to ports, set com1=Int4, port=03f8-03ff, 115200 baud, 8 data bits, no party, 1 stop bit, and no flow control (‘no flow control’ is another reason this testing method is tedious). Disable “use automatic setting” under resources page/tab.
CEMU_95A_Dish.exe will use CAM ID=S0439731349-61 and
Your TSOP needs to reflect the following, Dish.bin info (included in zip);
IRD#R 00 2324 5698-16 (0162B382)
BoxKey#87 38 2E C5 AC C1 04 7E
Obtain a TSOP, if you have not already done so, that matches at least the first two characters of your IRD Build Config sticker on the IRD main board. The more characters that match your IRD the better, (match left to right sequentially).
Use FlashEdit to change the above values (if required), along with the Build Config to match your IRD then save to a bin file. Then, before closing FlashEdit, save a virgin eeprom using the script under the pull-down in FlashEdit and hit ‘apply’. (If you do not see the “virgin-script”, copy it from FlashEdit Beta4 zip install).
Using your Jtag, update your IRDs flash and eeprom with these files. There are plenty of excellent “how-to’s” on Jtagging, FlashEdit and jEEpers, so I will not get into there respective details in this document, (is it getting too long already?).
In the installed CEMU folder, open the CEMU.ini file and change the following lines (Note, a # in front of a line effectively causes CEMU.exe to skip its contents);
- Remove the # from ‘Int 4’ (change if necessary to match your port settings)
- Remove the # from ‘Base address 038f-03ff’
Save the edited file as CEMU.ini.
With your dish pointed at the appropriate bird (DN=61.5, 110, 119 etc. or the B3V bird), and your IRDtoPC cable installed with AVR in the CAM slot/IRD, click on the CEMU_95A_Dish.exe in the installed folder, and then click on the upper-most left point on the DOS window header that appears. You will have a pull-down menu. Click on ‘Properties’ and select ‘Full Screen Mode’ and apply. This will insure the DOS application (CEMU) has CPU priority in the Windows environment. (This is just a precaution as the CEMU application is not CPU intensive.) You may also want to change ‘buffer size’ to 100 and ‘number of buffers’ to 40 under the properties page, just to be sure…
Plug-in your IRD and, after a short wait, you will see the following on your TV;
Acquiring satellite signal, wait, then acquiring satellite signal again...
While waiting, go through your IRD menu and set ‘Ask before download’ of new software, and disable locks (press OK at password) as this is a virgin eeprom.
Watching the PC DOS screen you will see (among a lot of bi-directional commands/data) the following scroll-by;
>>Set keys, provider: 101
[RX] - $CMD 07 - Entitlement Management Message (EMM)
Dish EMM 0101 ,etc… This is good for the auto-roll funtion!
If you see data flow on the DOS screen, your cable and COM communication works!
In less than five minutes the picture should come in.
Change channel, and watch TV! You can activate your DigiLock now, if installed.
If you do not see data flow after powering the IRD up, your communication is not getting through. You will also get “your smart card is not inserted correctly”. Re-check all your work, so far.
If you see plenty of data flow, and yet still “acquiring satellite signal”, after this five minute time frame, check your dish signal for the proper bird, and then ‘check switch’ under the IRD menu/Dish pointing page, (necessary step for some receivers).
If you get the “you are not authorized to view or purchase” nag, then it is most likely a bad TSOP… try again.
If you get “invalid smart card”, check that the info you inserted with FlashEdit is correct. If it is correct, then you used a modded TSOP… try again with a un-modded N2 TSOP. You should also be able to reflect the same IRD info in a TSOP that has already been successfully used for the DOS-101 CEMU, (which would have IRD#R 00 1864 2028 (hex 011c746c) in FlashEdit).
(Finding a TSOP that will work for you can be frustrating… hang in there, you’ll get it right.)
If you are satisfied at this point… watch TV! Otherwise, you may wish to dedicate an old, bare-bones PC to this task. Most 486 and above CPUs with 8Megs of RAM can be setup to run CEMU without keyboard, monitor, hard disk, etc. and boot from floppy. If you wish to do this stile of CEMU testing, this is how you should proceed.
Dedicated Floppy CEMU PC testing;
Create a 1.44Meg floppy boot disk following the instructions that come with Cemu101[1][1].5_DOS_DN_BootDisk_Creator.zip . Then, in the Cemu95a_dish directory that you created for the above test, rename the CEMU_95A_Dish.exe to CEMU.exe and copy the entire contents of this Cemu95a_dish directory into the root of the boot disk you just created, overwriting any files that exist with the same names.
On the floppy disk, leave the CEMU.ini from your Cemu95a_dish configuration, as you have already edited it to your needs, unless the COM port parameters are different on your dedicated PC than on the WinXP/2000 PC used for the above tests. However, these are standard parameters for all of the PCs I have worked with and, as long as the COM port number is the same, they will work.
Next, insert the floppy into the PC you intend to use and follow the same startup instructions as above. You can expect the same start-up results, time, and sequence. If you wish, you can turn off ‘reporting of keyboard errors’ in the system bios. This should allow you to run to dedicated PC without a keyboard and other input/output peripherals.
Don’t get stressed out, and have fun… we’re only testing!
Cheers!
Complements of the CompDoc.
********clip everything from [Info] and below, save as N201Ird2pcV2.pfg********
[Info]
Name = N201Ird2pcV2
Description = IRD2PCv2 Used for flashing the 8515 to communicate to PC. Ignores 10/12 jumper. provider 0001 Rom 102 rev 103.
Kudos = THANKS TO EVERYONE WHO HELPS FREEWARE BE WHERE IT IS!
Flash Signature = 0120, 8, 909A00C096E068D0
I2C EEPROM = none, none // 24LC64,128,256,515
[Fields]
Network, Disabled, EMU, {EMU}
Enabler, Disabled, No CAM, {No CAM}
Board, Disabled, AVR, {AVR}
MinTier, Disabled, 0000
MaxTier, Disabled, 0000
MinTier2, Disabled, 0000
MaxTier2, Disabled, 0000
MinTier3, Disabled, 0000
MaxTier3, Disabled, 0000
MinTier4, Disabled, 0000
MaxTier4, Disabled, 0000
MinTier5, Disabled, 0000
MaxTier5, Disabled, 0000
BlackOut, Disabled, 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00, {00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
CAM Type, Disabled, None, {None}
CAM Key, Disabled, 00 00 00 00 00 00 00 00
CAM Key Used, Disabled, 0
CAM Box Key, Disabled, 00 00 00 00 00 00 00 00
CAM ID, Disabled, S 00 0000 0000
IRD Number, Disabled, R 00 0000 0000
IRD Box Key, Disabled, 00 00 00 00 00 00 00 00
Key0, Disabled, 00 00 00 00 00 00 00 00
Key1, Disabled, 00 00 00 00 00 00 00 00
Aux0, Disabled, 00 00 00 00 00 00 00 00
Aux1, Disabled, 00 00 00 00 00 00 00 00
Time Zone, Disabled, None, {None}
Zip Code, Disabled, 00000
Password, Disabled, 00 00 00 00 00 00 00 00
[Field Conditional Enables]
[Configure]

[Read]
Network = EMU
Board = AVR
Enabler = No CAM
CAM Type = None
CAM Key = 0000000000000000
CAM Key Used = 0
CAM Box Key = 0000000000000000
Password = 0000000000000000
Key0 = 0000000000000000
Key1 = 0000000000000000
Aux0 = 0000000000000000
Aux1 = 0000000000000000
MinTier = 0000
MaxTier = 0000
MinTier2 = 0000
MaxTier2 = 0000
MinTier3 = 0000
MaxTier3 = 0000
MinTier4 = 0000
MaxTier4 = 0000
MinTier5 = 0000
MaxTier5 = 0000
BlackOut = 000000000000000000000000000000
CAM ID = 0
IRD Number = 0
IRD Box Key = 0000000000000000
Time Zone = None
Zip Code = 00000


[Flash]
:100000000CC0189521C01895189518951895189535
:1000100018951895189518951895479AF8940027EB
:100020000BBF05BFD0E0C0E60993C036E8F3D2307D
:10003000D8F30DED02BB00E201BB00EC07BB00E70B
:100040000DBF00E00EBFC79800E70DBF00E00EBF78
:10005000839BFECFF89400E80BBF789490E2CCD05D
:10006000EAE6F2E02BE1C8953196002D99D0D9F758
:1000700000E70DBF00E00EBFBCD060D009935ED09A
:1000800009935CD00993402E442029F0242D56D0AA
:1000900009932A95E1F752D00993242D04E0200F0B
:1000A000422EA7D00991ABD02A95E1F7A2D05ED01D
:1000B00009935CD009935AD00993402E442029F02B
:1000C000242D54D009932A95E1F750D00993242D7B
:1000D00004E0200F422E8DD0099103D02A95E1F73C
:1000E000C7CF2F93809BFECF889A98E085D000C021
:1000F000909800C000C0000028E0882794E07CD0E1
:100100000000001FC8F00000909A00C0891F817095
:100110002A95A1F794E070D000C0879558F00000B0
:10012000909A00C096E068D0000000C0909A88982D
:100130002F9108959098F6CF9098E8CF2F93809BB9
:10014000FECF8099FECF96E09A95F1F701E099E015
:100150009A95F1F780B38695001FC8F7009599E04E
:100160009A95F1F7809BFECF2F910895B59901C024
:10017000FDCF97E09A95F1F7000000E89AE09A9594
:10018000F1F70000000096B3990F990F990F0795AA
:10019000A8F700959AE09A95F1F7B599FECF0895E2
:1001A0002F93889A90EF28D0909800C000C0F02E2E
:1001B00028E0882795E720D000C0001FC0F000008D
:1001C000909A00C0891F81702A95A1F796E714D0F4
:1001D000879558F00000909A00C098E70DD0000075
:1001E000909A88982F912A9508959098F6CF909894
:1001F000E9CFC0E8D0E008959A95F1F708952F93DC
:10020000C79A9AE09A95F1F788E0079558F00000B0
:10021000C79A0000000099E000009A95F1F78A95CE
:10022000A1F70AC0C7980000000099E000009A9565
:10023000F1F78A9551F700C0C79899E0DDDF2F915B
:100240000895FF920795FF1C0795FF1C0795FF1C5B
:100250000795FF1C0795FF1C0795FF1C0795FF1CC2
:100260000795FF1C0F2DFF9008953FFF9500FF910C
:100270008171FF4700444E41535031303220526566
:10028000763130336400FFFFFFFFFFFFFFFFFFFF0A
:00000001FF
[EEP]
:10000000ffffffffffffffffffffffffffffffff00
:10001000fffffffffffffffffffffffffffffffff0
:10002000ffffffffffffffffffffffffffffffffe0
:10003000ffffffffffffffffffffffffffffffffd0
:10004000ffffffffffffffffffffffffffffffffc0
:10005000ffffffffffffffffffffffffffffffffb0
:10006000ffffffffffffffffffffffffffffffffa0
:10007000ffffffffffffffffffffffffffffffff90
:10008000ffffffffffffffffffffffffffffffff80
:10009000ffffffffffffffffffffffffffffffff70
:1000a000ffffffffffffffffffffffffffffffff60
:1000b000ffffffffffffffffffffffffffffffff50
:1000c000ffffffffffffffffffffffffffffffff40
:1000d000ffffffffffffffffffffffffffffffff30
:1000e000ffffffffffffffffffffffffffffffff20
:1000f000ffffffffffffffffffffffffffffffff10
:10010000ffffffffffffffffffffffffffffffffff
:10011000ffffffffffffffffffffffffffffffffef
:10012000ffffffffffffffffffffffffffffffffdf
:10013000ffffffffffffffffffffffffffffffffcf
:10014000ffffffffffffffffffffffffffffffffbf
:10015000ffffffffffffffffffffffffffffffffaf
:10016000ffffffffffffffffffffffffffffffff9f
:10017000ffffffffffffffffffffffffffffffff8f
:10018000ffffffffffffffffffffffffffffffff7f
:10019000ffffffffffffffffffffffffffffffff6f
:1001a000ffffffffffffffffffffffffffffffff5f
:1001b000ffffffffffffffffffffffffffffffff4f
:1001c000ffffffffffffffffffffffffffffffff3f
:1001d000ffffffffffffffffffffffffffffffff2f
:1001e000ffffffffffffffffffffffffffffffff1f
:1001f000ffffffffffffffffffffffffffffffff0f
:00000001FF