This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Messages - BrandonW
Pages: 1 2 3 [4] 5 6 ... 8
46
« on: November 18, 2010, 11:42:07 pm »
Nice. I am not sure if I saw those over here either. It looks familiar but I might just have seen them online and confused them with another kind. I wonder what other devices can jailbreak a PS3 besides the 84+/89T, that MP3 player? I haven't followed the scene much since I do not own a PS3. I wonder if the Prizm will do it...
A lot of cell phones will do it as well. The S1MP3 MP3 players are a cheap off-brand type made in China, disguised as iPod clones and other devices. It's hard to tell whether a particular device is S1MP3 just by looking at it, which is part of the problem. Wait, can said MP3 player be programmed, too? That would be pretty cool... I love the z80 processor now that I can program it...
Yes, it's programmable, and there is an open source firmware replacement project for it.
47
« on: November 18, 2010, 07:46:05 pm »
There was talk of jailbreaking a PS3 from those cheap S1MP3 MP3 players, because they also have a Zilog Z80 processor. I would get on it, but I can't find one locally and it would take weeks (months?) to get it here, with no guarantee that I got the right one.
48
« on: November 15, 2010, 10:58:42 pm »
The USB activity hook persists as well. They're very clumsy and just wipe out iy+34h/35h/36h (or whichever the 3 hook flags are, I forget), but not iy+3Ah which is where the USB activity hook's active flag is.
So you could carry around a USB adapter and jam it into the port whenever you want to re-enable it (after installing a USB activity hook that calls _RemoveAppRestrictions and uninstalls itself).
49
« on: November 15, 2010, 09:55:02 pm »
_SetAppRestrictions modifies the certificate to enable Press-to-Test, which is why RAM clears (or OS re-sends) have no effect.
50
« on: November 15, 2010, 09:48:22 pm »
This can't work. The ASIC is the CPU's interface to the rest of the hardware, and that one is distinctly 83-ish. There is no way for you to unlock the Flash chip (although I suppose the WE# pin lets you get around that) because there is no port 14h.
Because communication with the Flash chip is done through memory-mapped I/O commands, you MIGHT (and I stress MIGHT) get away with modifying the data in the Flash chip, which means you could modify the 83-ish OS.
But you can never run the 83+ OS, because it relies on an 83+ ASIC and port hardware. With some EXTREME patching to the OS, such a thing might be possible, but it would NEVER run 83+ programs.
Non-Flash calculators don't contain any sort of boot code, they never have to worry about the state of the Flash chip so they simply boot from 0000h.
It's *possible* TI left in some way for you to modify the data in the Flash chip, but there would be no way at all for you to recover from a bad write/erase because there is no boot code to fall back to.
I have both a TI-76.fr and TI-82 Stats.fr, but I'm not sure I want to risk soldering to that pin or erasing sectors of that Flash chip.
If you want to try this, you might want to disassemble the 83+ boot code BCALL _WriteAByte and see how it sends commands to the Flash chip to program a byte, and write an 83 program that does the same and see if it works.
51
« on: November 15, 2010, 09:41:22 pm »
You can't. Your only option is to prevent being put in that mode in the first place, of which there are several solutions, one of which is patching the OS.
Technically speaking, what does it is the OS calling _SetAppRestrictions. If you are able to call _RemoveAppRestrictions, you can disable it.
52
« on: October 21, 2010, 11:41:47 pm »
Low batteries can cause that behavior as well.
53
« on: September 11, 2010, 06:30:43 pm »
Wikipedia explains the purpose of the fifth pin.
If memory serves, whether it's grounded or not implies A-device or B-device.
54
« on: September 11, 2010, 04:47:02 pm »
Sending REAL variables is a lot more complicated, I don't have time to type up such an example. remote8x shows the direct USB link protocol that the OS uses to send and receive OS variables, and there's a text document out there ("DirectUSB.txt") somewhere that documents the entire thing fully.
"Zone 1" is just a convention I use to talk about the extra RAM pages. In the last two banks are usually RAM pages 1 and 0 (or "1\0"), which I consider zone 0.
Zone 1 is RAM pages 3 and 2.
Zone 2 is RAM pages 5 and 4.
Zone 3 is RAM pages 7 and 6.
55
« on: September 11, 2010, 04:10:14 pm »
Do you have any example code (or does anyone) of how to act as a peripheral, since one device would be host and the other would have to be control?
Good idea to link to Remote8x, though. 
Yeah, I just did link to the example code. The TI-OS will deal with who is host and who is peripheral through HNP (Host Negotiation Protocol) and make sure power is supplied to the port. You don't need to concern yourself with it. If you mean truly act as an independent USB peripheral (like a USB keyboard, mouse, PS3 jailbreak stick, etc.), then look at periph8x at http://brandonw.net/svn/calcstuff/periph8x/trunk/ or http://brandonw.net/svn/calcstuff/PS3JB/trunk/
56
« on: September 11, 2010, 03:51:43 pm »
There's some (admittedly old) code at http://brandonw.net/calcstuff/remote8x.zip that shows how to quickly talk back and forth between two calculators connected via direct USB. It does too much stuff between transfers so it's dog slow, but you get the idea.
57
« on: September 11, 2010, 04:39:44 am »
2.21 and 2.22 are far from stable. You shouldn't use them, ever. They have sequence graphing bugs (patched with http://brandonw.net/calcstuff/seqfix.zip if memory serves).
58
« on: September 10, 2010, 09:24:50 pm »
If we're being picky...corporations*
59
« on: September 09, 2010, 05:02:31 am »
Thanks for the kind words, everybody.
Crossing communities for a little bit was an amazing experience. Over the course of this thing, I gained 2,000 Twitter followers, 130,000 views on the YouTube video (and still climbing), and a lot of support from a lot of people. There's always the few haters that don't really understand what's going on, but that's to be expected with anything I suppose. I definitely have a lot of respect for the people who have to deal with these huge and impatient communities on a daily basis. Putting up with it for a week was a challenge to say the least.
The port itself was pretty crazy, too. It took a week non-stop (ever since the open source implementation of the exploit was released) of very little sleep and an expensive USB hardware analyzer I had FedEx overnighted here (by the way, that analyzer's going to help out with usb8x updates and more and more USB drivers -- we're talking wifi, webcams, you name it -- stuff I could never figure out before and simply had to give up on can now be resurrected).
Anyway, just wanted to congratulate you on being the first calculator site to pick this up (I think...at least ticalc.org wasn't first) and for the kind words.
And Netham45 for giving me the idea.
60
« on: August 02, 2010, 09:56:54 pm »
Hardware-wise it's an 83. That's why they were able to easily take the 83 OS, screw around with it, and slap it on there.
If it contained FLASH, I'd have already put the 83+ OS on mine.
Pages: 1 2 3 [4] 5 6 ... 8
|
Show Posts