Postei um tutorial do desbloqueio do zeebo e cópia de jogos comerciais num forum americano!

[Zeebo]

Por favor, vocês que têm mais experiência nisso, vejam se está correto (o meu zeebo está para chegar ainda haha).

assemblergames.com/forums/showthread.php?42614-Zeebo-s-Application-Pack-All-Brazilian-Releases-Why-no-Zeebo-icon-%28

ow-to-use:

You'll need a JTAG dongle which operates at 2.6 V, that's very important. Or you can try and build a low-voltage "wiggler" with these schematics here. Once you get ahold of one, connect it on the Zeebo JTAG interface as follows:



On a default 20-Pin ARM interface dongle, connect it as follows:



Pin 1 (VCC) goes onto VREG_MSMP
Pin 5 (TDI) goes on JTAG_TDI
Pin 7 (TMS) goes onto JTAG_TMS
Pin 9 (TCLK) goes onto JTAG_TCK
Pin 11 (RTCK) goes onto JTAG_RTCK (unless the dongle doesn't have Pin 11/RTCK, if that's the case connect the Zeebo's JTAG_RTCK onto GND)
Pin 13 (TDO) goes onto JTAG(TDO)
One of the GND Pins (20 for example) goes onto Zeebo's GND pin.

Then connect the dongle on your PC and install Open OCD 0.4.0! You'll need config files so that the software communicates both with the ARM 9 and ARM 11 chips, so copy this and save it for the ARM9 (remember to change some stuff according to your dongle type, this is setup to work with the Signalyzer H2 dongle!):

# Zeebo ARM9 OpenOCD script

## Change it according to your cable/dongle type!
interface ft2232
ft2232_device_desc "Signalyzer H2"
ft2232_layout signalyzer-h
ft2232_vid_pid 0x0403 0xbca2

## Change it according to your cable/dongle type!
## If wiggler, set to a lower speed. e.g. 100
## 0 means Adaptive Clock.
jtag_khz 0
reset_config none

set _CHIPNAME arm926ejs
set _ENDIAN little
set _CPUTAPID 0xa01700e1

jtag newtap arm9 cpu -irlen 4 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID

set _TARGETNAME arm9.cpu
target create arm9 arm926ejs -endian $_ENDIAN -chain-position $_TARGETNAME

arm7_9 dcc_downloads enable
arm7_9 fast_memory_access enable

proc mf { } {
halt
arm mcr 15 0 1 0 0 340348
}

proc mo { } {
arm mcr 15 0 1 0 0 340349
resume
}

proc rst { } {
mf
reg pc 0xFFFF0000
mo
}

proc brew { } {
mf
mww phys 0x11428800 0x1008000
mo
}

proc em { } {
mf
mww phys 0x11428800 0x1007001
mo
}
Save this file as "msm7201a_arm9.cfg" (plain text, of course!) and move it to the "scripts/target" folder which is on the OpenOCD installation folder.

Next, copy this on a plaintext editor:

# Zeebo ARM11 OpenOCD script

interface ft2232
ft2232_device_desc "Signalyzer H2"
ft2232_layout signalyzer-h
ft2232_vid_pid 0x0403 0xbca2

jtag_khz 0
reset_config none

set _CHIPNAME arm11
set _ENDIAN little
set _CPUTAPID 0xa7b360e1

jtag newtap arm11 cpu -irlen 5 -ircapture 0x1 -irmask 0xf -expected-id $_CPUTAPID

set _TARGETNAME arm11.cpu
target create arm11 arm11 -endian $_ENDIAN -chain-position $_TARGETNAME
Again, save on the same folder with the filename "msm7201a_arm11.cfg".

Note: if you have built the wiggler, delete the part which reads

interface ft2232
ft2232_device_desc "Signalyzer H2"
ft2232_layout signalyzer-h
ft2232_vid_pid 0x0403 0xbca2
and replace it with

interface parport
parport_port 0x378
# On Linux, use "parport_port 0" instead
parport_cable wiggler
and also change the clock to a low speed like "jtag_khz 100".

Ok, turn your zeebo on now run OpenOCD in a DOS window with the parameters -f target/msm7201a_arm11.cfg, you should get this:

Open On-Chip Debugger 0.4.0 (2011-04-17-13:28)
Licensed under GNU GPL v2
For bug reports, read
RCLK - adaptive
none separate
Info : Signalyzer: EM-ARM-JTAG (ARM JTAG) detected. (HW: 0).
Info : max TCK change to: 30000 kHz
Info : RCLK (adaptive clock speed)
Info : trst: 0, srst: 0, high_output: 0x12, high_direction: 0x1f
Info : JTAG tap: arm11.cpu tap/device found: 0xa7b360e1 (mfg: 0x070, part: 0x7b36, ver: 0xa)
Info : found ARM1136
Info : arm11: hardware has 6 breakpoints, 2 watchpoints
Ta-da! We have access to the ARM. Now open another terminal and type: telnet localhost 4444. If everything went fine, you'll see this:

Escape character is '^]'.
Open On-Chip Debugger
>
Type 'brew' to force Brew execution, then 'rst' to reset the console. Then type 'field' to gain access to the Field Test, and execute EMAPPLET from the BREW Appmgr menu.

Extract one of the game folders (the ones with numbers on them, of course) on the root of a SD Card (which should now have two folders: "mif and mod " on the root of the SD Card). Insert the SD Card on the zeebo, then go to Field Test > Memory Copy. Wait until the copy finishes then reset. Done!

If you have any questions, contact TripleOxygen on the openzeebo forum. Don't worry about language issues, ask in english! Also check out the Wiki link at the page header. There's a lot of info on the zeebo dev/homebrew, including upcoming Linux/Android ports (wiki in portuguese).

[Zeebo]

Ah, e fiz upload dos jogos do zeebo no 4shared. Passa no tópico "Coletânea de todos os jogos e apps do Zeebo!"