PL3 Confusion

[tthousand]

When ever there is a new hermes, or other new hex file, it seems to be released where everyone can find a copy of it.

But with PL3, updating constanly, it is harder to find the hex I am looking for. They have DEV, DEF, NOAUTH, etc., and now others too.

Basically, I want to know where I can find the PL3 hexes that I am looking for, or a way to compile my own.

I allready have the 10.10 ubuntu virtual machine, and have been able to compile from github.com/psgroove, but I can not find out how to compile gitub.com/kakaroto, and that is the one I want.

Anyone know of a tutorial, or any leads?

[chocobo]

I have no idea what you have on that Ubuntu virtual box image, but this should/could work:

idiot@shelf:/var/tmp/psgroove$ git clone https://github.com/kakaroto/psgroove.git
idiot@shelf:/var/tmp/psgroove$ cd psgroove
idiot@shelf:/var/tmp/psgroove$ git submodule init
idiot@shelf:/var/tmp/psgroove$ git submodule update
./build_hex minimus1
idiot@shelf:/var/tmp/psgroove$ ls psgroove_hex/Minimus\ v1/
psgroove_minimus_at90usb162_16mhz_firmware_3_01.hex
psgroove_minimus_at90usb162_16mhz_firmware_3_10.hex
psgroove_minimus_at90usb162_16mhz_firmware_3_15.hex
psgroove_minimus_at90usb162_16mhz_firmware_3_41.hex
idiot@shelf:/var/tmp/psgroove$

This assumes that you have properly setup avr-gcc and ps3toolchain.

If you want to use the latest and greatest PL3 payloads (and this is required for NUS PL3 payload), you'll need to do something like this (I'm bad with git, so there is probably better/other way to do this - like, remove PL3 subdir and check it out from PL3 tree on kakaroto's github):

(obviously, these commands assume that commands above have been executed already - if you didn't to stuff from above, use common sense to figure out what you need to do with commands below)

idiot@shelf:/var/tmp/psgroove$ make clean
idiot@shelf:/var/tmp/psgroove$ cd PL3
idiot@shelf:/var/tmp/psgroove$ git pull origin master
idiot@shelf:/var/tmp/psgroove$ cd ..
idiot@shelf:/var/tmp/psgroove$ rm -rf psgroove_hex
idiot@shelf:/var/tmp/psgroove$ ./build_hex minimus1
Building for targets :  minimus1
Compiling psgroove_minimus_at90usb162_16mhz_firmware_3_01 for Minimus v1
dump_syscall.c: In function ‘main’:
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:588: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
dump_syscall.c:609: warning: '0' flag ignored with precision and ‘%X’ gnu_printf format
Compiling psgroove_minimus_at90usb162_16mhz_firmware_3_10 for Minimus v1
Compiling psgroove_minimus_at90usb162_16mhz_firmware_3_15 for Minimus v1
Compiling psgroove_minimus_at90usb162_16mhz_firmware_3_41 for Minimus v1
idiot@shelf:/var/tmp/psgroove$

You can choose the payload by editing descriptor.h and modifying PAYLOAD definition. It's payload_dev by default.

[tthousand]

Allright, on line 27 it states "#define PAYLOAD payload_dev". I try to switch it to say "#define PAYLOAD payload_default", but no hexes end up being built.

Originally, I ws trying to make something out of the kakaroto PL3, but after what you said, I moved that folder to replace the one inside the psgroove. It seems I was able to make the dev payloads, but nothing else as of yet.

[chocobo]

Allright, on line 27 it states "#define PAYLOAD payload_dev". I try to switch it to say "#define PAYLOAD payload_default", but no hexes end up being built.

Originally, I ws trying to make something out of the kakaroto PL3, but after what you said, I moved that folder to replace the one inside the psgroove. It seems I was able to make the dev payloads, but nothing else as of yet.

Use "default_payload" instead of "payload_default".

[tthousand]

Thank You @chocobo. I have been trying to figure this out for weeks now. Do you know the other payloads I can replace the "payload_dev" with?

[tthousand]

Thank You @JonahUK. It will be great always having the new PL3 hex!