- 精华
- 0
- 帖子
- 666
- 威望
- 0 点
- 积分
- 720 点
- 种子
- 0 点
- 注册时间
- 2005-2-21
- 最后登录
- 2016-3-20
|
发表于 2010-10-20 10:13 · 四川
|
显示全部楼层
================================================================================
AsbestOS README
================================================================================
== Introduction ==
AsbestOS is a Linux bootloader that runs off of the PS3 Lv-2 USB exploit. It is
designed to boot on PS3 systems running System Software version 3.41, though it
could be adapted to earlier versions. Linux runs on the GameOS partition, thus
having the same access to hardware that GameOS has.
== Building ==
The PS3DEV environment variable needs to point to a usable PowerPC64 toolchain
(e.g. $PS3DEV/bin/powerpc64-linux-gcc). If you don't have one, point it at an
empty dir and run
$ cd toolchain && ./buildit.sh ppu
To compile stage1 or stage2, just type 'make' in the respective directories.
You can also compile the UDP debug message client by doing the same in the tools
directory. 'make' in the root of the source tree will do all three (but not
ps3pwn).
To compile ps3pwn, you need to be on the target platform (ARM-Linux OMAP3) with
a native compiler (or hack the Makefile to use some cross compiler). Just type
'make' in that directory. ps3pwn is just the reference implementation of the
exploit and is not required as there are alternatives (see below).
== Usage ==
First compile AsbestOS and get a compatible USB exploit delivery mechanism. You
should also connect your PS3 and PC to a network (they need to be in the same
broadcast domain) and make sure your PC allows broadcast packets to UDP port
18194. The IP source and destination are both 255.255.255.255 for these packets.
Run tools/dbgcli to get AsbestOS debug output. Fire off the exploit device, turn
on your PS3 using power followed by eject within 0.2 seconds (if required by
your exploit implementation), and cross your fingers. If you get anything at
all, congratulations, stage2 is running. At this point, if you have any issues,
the problem should be fairly apparent from the messages.
If you get nothing, either the packets aren't making it to your PC or stage2 is
failing to start up properly. If your exploit device can show the debug "print"
USB messages, that might help you find out whether stage2 is at least being
loaded properly.
If your PS3 panics (blinking red light) or spontaneously reboots, then something
somewhere probably hit an error condition. The first thing that stage2 does is
inititalize Ethernet debugging, so chances are either that failed, or stage1
failed.
Basically, if stuff doesn't work, poke me on IRC ('marcan' on either EFNet or
freenode) and we'll see what we can do.
To get a kernel to load (see below for instructions to build one), you need to
have a DHCP server on your network. It needs to be configured to feed a boot
server and filename to the PS3. The boot server should point to a machine
running a TFTP server that can serve the specified file, which should be the
kernel image. For example, on an OpenWRT Kamikaze router, put something like
this on your /etc/config/dhcp:
config host
option name ps3
option mac 00:1f:a7:aa:bb:cc
option ip 192.168.3.60
option networkid ps3
config boot
option networkid ps3
option filename dtbImage.ps3.bin
option servername foobar
option serveraddress 192.168.3.171
Where 192.168.3.60 is the IP that you want your PS3 to get and 192.168.3.171 is
the IP of the TFTP server. The server name doesn't really matter, but it's a
good idea to set it to the hostname of the TFTP server. Don't forget to specify
the MAC address of your PS3 correctly.
== Compatible devices ==
AsbestOS can potentially run on any device capable of implementing the exploit
and which has access to at least 40kB or so (currently) of free internal or
external memory. The following ports are known to exist so far:
- TI OMAP3 devices running Linux (ps3pwn reference implementation)
IGEPv2 board, BeagleBoard, Nokia n900, Palm Pre, Motorola Droid, Pandora...
Included in this distribution.
Implements the MUSB device driver in userspace. You need to disable all USB
services (if any) and either unload the kernel musb driver or unbind it via
sysfs. Do not remove the driver for your OTG PHY, though (varies).
- AVR Software USB (for AVRs without hardware USB)
Arduinos, etc...
http://github.com/rvalles/asbestos-avr8susb
Supports both >=64k AVRs and |
|