Hacking PXA270 internal USB HOST

[kickme]

Bigbop,

Just trying to help here...

Image @ http://www.toradex.com/colibri_downl.../Image_1.7.zip

can be viewed with viewbin.exe (inside evcsp4 - http://www.microsoft.com/downloads/d...displaylang=en)

I see the usb dlls not sure how to extract yet... If I get them out I will post them.

We are all counting on you!!!!

[bigbop]

Bigbop,

Just trying to help here...

Image @ http://www.toradex.com/colibri_downl.../Image_1.7.zip

can be viewed with viewbin.exe (inside evcsp4 - http://www.microsoft.com/downloads/d...displaylang=en)

I see the usb dlls not sure how to extract yet... If I get them out I will post them.

We are all counting on you!!!!

Thanks - I grabbed the NK.bin from the Colabri site but have been unable to pull it apart using the tools from the XDA forums.
I have to modify a cheap USB hub so I can connect it to my X50v. For this to work, I have to supply the +5v to the hub from an external source. I've already done this with my Nokia N770.

[kickme]

I got it to open !!! ;)

extracted to "dump" dir

>cvrtbin.exe -r -a 80100000 -l FA3914 -w 32 nk.bin
>dumprom.exe nk.nb0 -d dump

Let me know if you need anything else.

Good luck!

[kickme]

In case you do not have the correct version (took me a few itterations to find the correct ones) here they are attached

tools.zip has cvrtbin.exe and dumprom.exe
viewbin.zip is viewbin.exe (could not put it in the same zip due to the 100k attachement limitation)

Cheers!

[bigbop]

In case you do not have the correct version (took me a few itterations to find the correct ones) here they are attached

tools.zip has cvrtbin.exe and dumprom.exe
viewbin.zip is viewbin.exe (could not put it in the same zip due to the 100k attachement limitation)

Cheers!

Damn! - I think I just wet my pants
Good work - Thanks, I'll have a look at this.:approve:

OK, I had a look at the dlls and there are a few missing.
I'll try playing with the utils you posted to pull them out. What you missed were the actual low level interface drivers (host port/client port). What you posted are the device drivers (printer,disk,etc). Great start though!!

Also, how did you get the starting offset?

[kickme]

Hi,

The viewbin.exe is the key to finding the offsets, hence I provided it :)

If you have any problems extracting (you should not) let me know what we are missing and I will upload them as well. I uploaded a few DLLs which look interesting - not sure which ones we need.

good luck!

p.s. found a link where someone does similar things for an ETEN M500 Could be this may help as well - Translated version of http://www.etenclub.ru/board/lofiversion/index.php/t73.html

[bigbop]

Hi,

The viewbin.exe is the key to finding the offsets, hence I provided it :)

If you have any problems extracting (you should not) let me know what we are missing and I will upload them as well. I uploaded a few DLLs which look interesting - not sure which ones we need.

good luck!

p.s. found a link where someone does similar things for an ETEN M500 Could be this may help as well - Translated version of http://www.etenclub.ru/board/lofiversion/index.php/t73.html

Thanks - actually, it's an M600 and I've had that info for a while now. The problem is that the M600 uses a Samsung uP which although has an Xscale core, the peripherals for the USB host is slightly different - but it DOES use the same shared pins for client and host. I've been trying to get more technical info on the internal registers of the Samsung uP but it's difficult without signing an NDA.

I was able to dump the ROM last night and I have all of the modules now. There is a trick to converting the XIP modules into standard EXEs but I don't know how to do it myself yet.

[kickme]

I noticed it was a Samsung, just thought the registry infor and the dlls they uesed would be similar.

I am not sure I understand what you mean by converting XIP modules to standard EXEs. Since this is all new to me I am just doing this with Trial and Error :) but if you explain a bit more I can try to do some more searching.

Cheers....

[bigbop]

I noticed it was a Samsung, just thought the registry infor and the dlls they uesed would be similar.

I am not sure I understand what you mean by converting XIP modules to standard EXEs. Since this is all new to me I am just doing this with Trial and Error :) but if you explain a bit more I can try to do some more searching.

Cheers....

XIP = eXecute In Place - The module is run directly from non-volatile memory (flash) so that it takes up less RAM. This was big for WM2003 which had the OS stick a big chunk of itself into RAM. As of WM5, everything is XIP as the technology has changed and just about everything in the OS runs out of flash.
The XIP modules are also not relocatable. That is what prevents them from running on their own if I just grab one and stick it into the \Window dir. That is why I can't just take the DLLs we grabbed from the Colibri OS and try to reuse them on the Axim as-is.

I hope that clears it up a bit.

[makuu]

Do you want the xip modules from the axim? If so I have them.

[Dogo]

Do you want the xip modules from the axim? If so I have them.

Mon Dieu !

Bigbop and Makuu working together ! :approve::approve::approve:

What else can we x51v owners ask for ???

The sky´s the limit for you two !!!

PD: je m´excuse Mr. Makuu for defeating France at the Rugby World Cup. But we well deserved that bronze medal.

[kickme]

Hi bigbop,

Yeah after you mentioned XIP I did some reading :) seems one can change where the code is run. Are you sure it can be "converted" to a regular dll/exe I could find no reference to this (Only found changing the addresses and re-signing).

[bigbop]

Do you want the xip modules from the axim? If so I have them.

Thanks, but I have the modules for the X50v already for release WM2003SE A02, which had the original OHCI.dll. After the WM2003SE A02 ROM, they replaced that dll with the peripheral.dll module that senses the state of pins 5 & 6 on the sync connector.

What I need to do now is to dissassemble the DLLs from the Colabri bin file and see how the client and host modules interact.

I seem to recall that an XIP module can be made into a relocatable module so that it can be installed manually. Do you know how to do that?

Thanks for any help.

By the way, I munged the GPIOConfig_v1.2B utility found on the Colabri website so that it would run on my X50v (has to run in VGA mode) but unfortunately, it needs a right mouse button function to enable some of its features - Is there a utility that can pretend to handle a right button on a mouse for WM2003SE/WM5?

I've attached the modified utility.

[kickme]

Bigbop,

Maybe remote control of the PDA from your PC would work? I know the mouse works, not sure about the buttons though...

Just an idea...

[bigbop]

Bigbop,

Maybe remote control of the PDA from your PC would work? I know the mouse works, not sure about the buttons though...

Just an idea...

Never thought about that - I'll give it a try.
Thanks