[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4326: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3501)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4328: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3501)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4329: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3501)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 4330: Cannot modify header information - headers already sent by (output started at /includes/functions.php:3501)
0.5.0.0 release date
Sign up here and you can log into the forum!

0.5.0.0 release date

General homebrew discussion area

0.5.0.0 release date   

Postby b-rad.cc » Thu Aug 18, 2011 10:12 am

Hey guys. 0.5.0.0 was due to be released 3 weeks ago, but hours before I was to flip the switch one of my online update guinea pigs ended up getting bricked. Seeing as how I hold stability in the highest regard, the release was immediately suspended until it could be figured out exactly what went wrong. The user was finally able to obtain a serial cable and I was able to guide them back to eventual safety...In the end it turned out that this bricking had zero to do with WDLXTV and instead was caused by the user themselves. Theres an important lesson to be learned here because of this:



The user wanted to comment out one value, and in doing that bricked themself by inserting an invalid character.

Since I saw the one weakness in my code, last weekend I decided I would put myself into the same bricked state to ensure I would prevent this in the future. Well something went miserably wrong in my unbricking and I irrecoverably bricked my own plus. I went out and bought a new one a couple days ago, but I've been absolutely sacked with other work, so haven't had a chance to finish my last bit of testing. That will get taken care off this weekend however, and 0.5.0.0 will be released!

I'm sorry about the delay, but I can assure you that I don't want to be the cause of (possible) thousands of devices brickings infinitely more than you don't want to brick your one single device by bad luck.

This project has so far not been the sole reason for bricking *anyone* over the last 2+ years and I intend to keep it that way. Even if that means delaying a release for time to ensure all of your safety.

:ugeek:

PM's are for private matters only, please post public matters on the forum to help others who might have the same issue.
:mrgreen:
User avatar
b-rad.cc
WDLXTV Team
 
Posts: 3003
Joined: Sat Apr 03, 2010 9:35 am
Location: New York

Re: 0.5.0.0 release date   

Postby blachanc » Thu Aug 18, 2011 10:56 am

B-Rad,
out of curiosity,
if you had the $1000.00 JTAG cable (& dev. kit),
do you believe you would be able to un-brick your box ?

-Ben

PS; thx for the work (this WDLXTV project is probably more demanding than a mistress or two :-) )
blachanc
Patron
 
Posts: 238
Joined: Tue Feb 22, 2011 7:10 am
Location: Montreal,QC, Canada (french)

Re: 0.5.0.0 release date   

Postby b-rad.cc » Thu Aug 18, 2011 11:27 am

Using a jtag with a commercial device would be very tricky. There isn't a jtag socket, so it would require me figuring out which spots on the pcb to connect probes to...then figuring out what to actually do, considering there is zero information on this out there really. I have some minimal documentation on sigma jtag, but it is so minimal as to be of little help in doing anything 'real'. In all if I had the jtag I could possibly spend months trying to figure out anything. It would be fun as all to actually have a sigma jtag, but I feel that it could take me an eternity to get anywhere without an additional $50k in sigma dox to help me.

What I need, and I've priced out, is a surface mount station. I found one that is very nice for ~$400. With that I could replace the surface mounted chips and fix any nand related issues, no matter what they are. I've whipped up a tool to hack nand live on the pcb, but its a bit dangerous as it leads to voltage leak on other components output pins--and that is a fairly big no no in the IC world when theres no Vin. So I just haven't gotten around to attempting an unbricking that way. I'm hesitant to spend $400 of my own cash on a SMS, because well...Its definitely not in my budget plus i don't really have need for one, except to unbrick wdtv's, irregardless of how much I like new toys :lol: I do have 3 bricked wdtv's though, from my adventures the last few months, that I could fix pdq if I did have one.
PM's are for private matters only, please post public matters on the forum to help others who might have the same issue.
:mrgreen:
User avatar
b-rad.cc
WDLXTV Team
 
Posts: 3003
Joined: Sat Apr 03, 2010 9:35 am
Location: New York

Re: 0.5.0.0 release date   

Postby PaulF » Fri Aug 19, 2011 5:22 pm

JTAG has a few mandatory instructions that mainly do boundary scan where you can read and write to chip pins. All other instructions are custom and mostly secret. I was the JTAG designer on a couple of Intel cpus and there were some things even I could never see(unlock codes for instance). I think maybe the cpu cores have public instructions, though. Is the /conf directory in an external flash? If so what is the flash chip part number?
User avatar
PaulF
Developer
 
Posts: 427
Joined: Sat May 08, 2010 8:34 pm
Location: Oregon

Re: 0.5.0.0 release date   

Postby b-rad.cc » Sun Aug 21, 2011 8:41 am

PM's are for private matters only, please post public matters on the forum to help others who might have the same issue.
:mrgreen:
User avatar
b-rad.cc
WDLXTV Team
 
Posts: 3003
Joined: Sat Apr 03, 2010 9:35 am
Location: New York

Re: 0.5.0.0 release date   

Postby Vipeout » Sun Aug 21, 2011 3:05 pm

Thank you man!
Vipeout
n00b
 
Posts: 1
Joined: Sun Aug 21, 2011 3:03 pm

Re: 0.5.0.0 release date   

Postby jizzajam » Sun Aug 21, 2011 3:14 pm

it appears to have bricked my live plus, it hung on the updating firmware screen at 0% for an hour, so i yanked the plug and now it hangs at the wdtv screen

i have a max232 dip sitting here, once i get some tty access i'll post some details
jizzajam
Donor
 
Posts: 6
Joined: Tue Jul 26, 2011 10:53 am

Re: 0.5.0.0 release date   

Postby onneeye » Sun Aug 21, 2011 4:16 pm

I think I found a bug in the USB power off. When I turn off the live+ and the hard drive finally powers off completely. Turn it back on the, the live will not recongise the hard drive. Plugged the hard drive in my pc, the computer states hard drive not properly eject, does auto fix. Plug it back into the live+, plays fine until I power off the live and wait for the hard to power off and power it back on. Does the same thing.
onneeye
n00b
 
Posts: 2
Joined: Tue Sep 14, 2010 1:27 pm

Re: 0.5.0.0 release date   

Postby RMerlin » Sun Aug 21, 2011 7:29 pm

WDLXTV Webend maintainer. Visit http://www.lostrealm.ca/wdlxtv to see my other WDLXTV projects.
If you like my work, please consider .
User avatar
RMerlin
WDLXTV Team
 
Posts: 3236
Joined: Sat Jun 26, 2010 9:25 am
Location: Montreal, Canada

Re: 0.5.0.0 release date   

Postby chrrh » Mon Aug 22, 2011 1:10 am

Everything is running fast and smooth here with 0.5.0.0 (WDLXTV-LIVE)

the 1.5.x.x Firmware runs fine all my DVD-Menus over SMB. (The regular VOBs played fine with every FW I tried)

Thank you very much. Best Release I tried so far.

Regards,
chrrh...

PS: No problems with the upgrade process on my side. Everything works like a charm.
chrrh
n00b
 
Posts: 1
Joined: Tue Aug 02, 2011 11:39 am

Next

Return to WDTV G2 & WDTV Live homebrew discussion

Who is online

Users browsing this forum: No registered users and 1 guest