USB Atmega up?

[PRCHOICE]

I am still fighting with my usb atmega 256 and not winning. I had it going with 1.03 but never with any of the newer versions including 2.04. I dont know if it is a symptom of my problem but I cannot read back the eeprom after writing. I have tried programming onto an older p4 machine but no difference. I have been using public bins from ee and running different tier scenarios. I still get scnic.
I am working with dish irds 2700, 3700, 3100 that are all good with public atmega 128 and rom102. I have reloaded the windows drivers, rebooted pc you name it, I have been reading at card-coders daily for help but no luck. I have been using keyupdate (8.5) to add keys to bin but It says it cannot add 0106 keys only change - is this my problem?

[mili]

You don't need a 10C BIN man. Use a rev103 BIN and all you got to do is patch tiers to it in MrTierworks 3.1.

mili

[PRCHOICE]

youve got to be kidding. I have been reading at cardcoders for weeks ever since 1.03 died. Absolutely nothing since. The supposed experts at CC spend too much time fighting and there has never been a clear how to on this pita.
I am rewriting as we speak.
This is just another example of why you are THE GREATEST

[PRCHOICE]

Sounded too easy - If it makes any difference, I am not using a jtag adapter.
Guide looks fine but black screen. No error messages. I used dish 0106 keychanger. Should the keys be put in the bin or through the GUI.
Of note, I have never been able to read back the ird info and have tried redoing drivers and using an older pc

[jocko50]

Usb working here on 301-10 E542. This latest update fixed some problems such as black scream etc. Struggled for weeks to get this working and it still a little buggy but its rolling. U need to be able to read the MECM after putting card in reciever(just to make sure it wrote it to the card)

[PRCHOICE]

Since the software 2.0 and up, I have never been able to read back the cam and ird properly from the card.

Tjis is the mecm40
ff ff ff ff ff ff ff fc
d9 c9 41 a7 67 70 1e d7
7f 0c 68 f8 28 f8 b2 13
16 0d 74 ec 14 0f 4f 16
ae cf f8 13 cc 08 9f 3a
4f 55 ff d5 cc b0 ac cd
d7 29 46 17 cf c6 71 0c
37 bb 8e e4 f1 a7 40 ff
ff ff ff ff ff ff fe 3f
cd 1b 1b 2f 8d e6 07 51
22 2b 90 18 04 ff 2a be
b9 20 6b a9 2d 11 31 0e
6e 4b 10 99 ff 1b 0e 75
84 86 f1 47 88 63 20 71
14 7d f6 00 44 df 5e e4
8d ff 93 10 43 f8 ff ff
ff ff ff ff ff fc 23 2b
a2 bc 58 47 ff dd 98 ef
44 f3 37 da 8d 23 7e 5e
3c 0e 69 eb 50 fb 42 9f
61 d5 84 94 ca 2c e1 48
3b 12 6b e3 9d 5c e0 3c
1b 8d 15 30 7c c7 bf 12
b8 d8 71 56 8b ff ff ff
ff ff ff ff fe 57 12 c8
83 3c 3a 9d 3b 37 9c d0
66 65 d1 28 fd 7e fe ea
e9 54 b2 f5 85 81 da 8f
b0 ed 77 ae 6b d2 09 5e
56 0e 15 25 19 6c f9 05
b2 75 cb 47 67 4c 15 12
95 9c 66 d7 ff ff ff ff

I have been using two different pcs and drivers with clean boots but no luck
At this stage, I dont know if it is a problem with the bins I have been using but I'm pretty sure that I've tried all suggestions. I have tried virtually all tier writing suggestions and was hoping that Mili's simple cure would do the trick but same header only screen.

I prefer to figure things out with reading but this card is a pain

[jocko50]

The problem it seems is the Mecm u posted has FFFF FFFF to start with. Its almost all there but this won't work. Try leaving the card in the reciever and then every once in a while try reading your card and see if you get a good read (mecm) The moment you get no ff ff ff anywhere on the mecem read you are good to go. Try unplugging USB cable a couple of times then read.

[PRCHOICE]

I am currently writing 2.05 with the stock bin to see if it will read back the cam and ird which I have never been able to do. I am wondering if I should buy a new usb cable. I notice that when I detect, it will fail sometimes. It is a 5 wire but stock camera cable.

Are there supposed to be 5 contacts on the card or only 4 wires in the 5 slots. My card only has two wire contacts on each side and the middle contact slot does not have a wire sticking up.

[fubr]

There is a few times I had problems with my card, I got through it each time but was starting to wonder.
The few hours I spend messing with it I get a bit angry and cuss a little bit but the weeks it is running with no problems I am not so mad at it :)

Not making light of your situation, I do under stand what you mean, there has been a few times I have had to read a working eprom off of a enigma and write it to the card to get it to work. Once I did this with plastic.

I am going to bet you got some kind of usb issue, try to re-install drivers just before use and unplug the card and replug it before programing.
I got a older cable that works but it gives one hell on a bad response and is very slow. It will detect most of the time. I dont use it anymore I use the cable from my camerae now

[JT]

I think maybe someone should make a sticky post about the differences in USB cables. (I don't know, so I can't really do it) When I went to buy one yesterday I was suprised to see I had five different options that had mini USB on one end and normal USB on the other. I got a "Type A-5 pin (mini-B) cable and it works fine. It says right on the bag the cable came in "...for digital camera, MP3 player, PDA and other portable device". I wouldn't be suprised if a lot of these issues aren't due to the wrong kind of USB cable. It MUST be a 5 pin cable I think.

[PRCHOICE]

Mine is/was a five pin camera cable - i read that requirement and checked. In order to try to eliminate potential sources of my problem, I went to future shop and bought a new 5 pin usb cable and simply wrote the dish bin from 2.05 with absolutely no changes and it is up and wide open with 58 tiers.
Thanks to everyone who has helped and to others with black screen/scnic problems go buy a new 5 pin cable

[fubr]

there used to be a thread mili made about cables.