psplink patch + another psplink bug / interesting find

[danzel]

Firstly, hexdump has a bug, the mask param is read from the wrong place, heres the patch:

Code: Select all

Index: psplink/shell.c
Index: psplink/shell.c
===================================================================
--- psplink/shell.c     (revision 2211)
+++ psplink/shell.c     (working copy)
@@ -2994,7 +2994,7 @@

                if(argc > 3)
                {
-                       masksize = decode_hexstr(argv[4], mask_d, sizeof(mask_d));
+                       masksize = decode_hexstr(argv[3], mask_d, sizeof(mask_d));
                        if(masksize == 0)
                        {
                                SHELL_PRINT("Error in mask string\n");

And now the bug which I can't solve :) [Pre posting edit: nevermind, solved it lol]
It looks like 'reset vsh' doesn't work correctly under OE 3.10' firmware (I haven't tryed under non-OE)

Instructions to reproduce:
start up psplink, usbhostfs, pspsh.
in pspsh:
> reset vsh
> flash0:/vsh/module/vshmain.prx
Now on your psp the vsh will load up: navigate to settings, network settings.
The psp now loads the net modules.
Back in pspsh:
modlist (to verify they are loaded)
modinfo @sceNet_Library

Code: Select all

host0:/> modinfo @sceNet_Library
UID: 0x052B8705 Attr: 0006 - Name: sceNet_Library
Entry: 0xFFFFFFFF - GP: 0x08412920 - TextAddr: 0x08400000
TextSize: 0x0000A85C - DataSize: 0x000000B4 BssSize: 0x00001570
Segment 0: Addr 0x08400000 - Size 0x0000A868
Segment 1: Addr 0x0840A870 - Size 0x00001630

These memory addresses are strange as they aren't mapped addresses.
Some other modules show this as well, while some are fine.
modfindx also produces strange results ( modfindx @sceNet_Library sceNet_lib 7BA3ED91 )
The net library seems to be loaded correctly as you can go into infrastructure and scan for wifi points.
Any idea where these strange memory addresses are coming from?
[Note: If you try reset your psp with psplink while in 'network settings' it will lock up, close network settings and open the 'game', 'memory stick' menu to unload the network modules, you can then restart safely]

BAH!!! After writing all this I searched the memory address on the forums, leading of course to this thread:
http://forums.ps2dev.org/viewtopic.php?t=6800
running 'memprot off' allows me to poke around this area of ram and it seems all is fine.
Interesting to note that this section of memory is used during vsh however :)