Is this normal for a bricked modem, or do I have a bad connection?

[theman01]

I am doing a little bit of spring cleaning and decided I would fix a couple bricked modems now that I got my NT. Both of them became bricked the same way, by upgrading firmware via haxrware GUI and then having the connection cut out due to an issue with my former ethernet adapter.

My issue is that I can't detect both modems:

The first modem I was actually able to detect after a few tries and then I tried the poke method of debricking. I installed a 2mb sb5101 flash dump on it and unplugged power/plugged it back in and the lights came on for a little longer before going out. Now I can't detect it at all. Here is a log from that one:

Code:

Copyright (C) 2010-2015
USB JTAG NT    0.68
Target: SB5101Mod
-detect
IDCODE FFFFFFFF
-poke fffe230c 3
-poke fffe2304 0
-poke fffe2300 a
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 1c
-detect
-poke fffe230c 3
-poke fffe2304 0
-poke fffe2300 a
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 1c
-detect
-poke fffe230c 3
-poke fffe2304 0
-poke fffe2300 a
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 1c
-detect

Now my second modem was completely untouched since I bricked it, the same way as the first. The issue with this one is that it won't detecta aswell. I try the poke method on this one and it just says manufacturer not found, which is different from the first. Here is a log of that:

Code:

Copyright (C) 2010-2015
USB JTAG NT    0.68
Target: SB5101Mod
-detect
IDCODE FFFFFFFF
-poke fffe230c 3
-poke fffe2304 0
-poke fffe2300 a
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 9
-poke fffe2300 1c
-detect
IDCODE 8000007F
Manufacturer not found 03F

The thing is that I am using a brand new solderless header pin, and I am wondering if it is not connecting to the board properly. When I stick it in the holes it barely goes in, and one little touch will knock it out of place.

Does it look like a bad connection or a standard bricked modem? How can I proceed from here? Since I cant detect I am limited to the poke method to debrick it and that isn't working, can anyone shed some light? Huge PITA.

[KnoxK]

if your flasher isn't reading you device when you have it hook up to it then you pin config is probably incorrect make sure you pins are in the right order. soderless is the way to go so that shouldn't be a problem. I use sder pins and just hold in place when im flashing. check and make sure your pins are lined crrectly

[sixteen]

Since am not their to see your connection can you take a full pic of the JTAG software out put and upload it here. Its a connection problem tho.

[southernyankey1970]

NT is finicky for debricking but there are options...

1 the easy way is the hotswap. Get the NT to detect a good cm then swap the cable to your BrickO' Matic and set the speed to low or I highly suggest themanual ldram 9fc00000,then sprogram 9fc00000 200000 as sprogram will not hang up on the erase part...

2. go to SBH and follow Daks's excellent 5101 hard reset tutorial to get it to detect.

[sixteen]

Again the modem is not brick there is no connection.....IDCODE FFFFFFFF means the connection is bad.

[theman01]

No the modem was definitely bricked, but it also had a bad connection. The issue was the crappy solder less header(which I already knew) once that was taken care of by soldering a header in, I was able to take care of it with no problems using the same method SY just posted.

[theman01]

I am doing a little bit of spring cleaning and decided I would fix a couple bricked modems now that I got my NT. Both of them became bricked the same way, by upgrading firmware via haxrware GUI and then having the connection cut out due to an issue with my former ethernet adapter.

Again the modem is not brick there is no connection.....IDCODE FFFFFFFF means the connection is bad.

What about my post makes you feel this strongly that the modem is not bricked? It was never a question whether it was bricked or not, it was a question about if I am having a connection problem, or since my modems are infact bricked, if this is normal behavour.

Over at the modem site he post the same thing and we told him its a connection problem, but you know these guys always think there way is the right way.

[southernyankey1970]

No the modem was definitely bricked, but it also had a bad connection. The issue was the crappy solder less header(which I already knew) once that was taken care of by soldering a header in, I was able to take care of it with no problems using the same method SY just posted.

Hehe,

Things like this actually keep me interested these days. Congrats for figuring it out.

[sixteen]

Wow, one more banana brain added to the table........

[southernyankey1970]

why are you trolling? 4his is not KideeHackk....lol.