[ PMP-100 SOFT(ware) DEV(loppment) ]-[arm toolchain, bsp, µClinux, C code, archi...]

[pmp.breaker]

here start a new thread about the software devloppment for the PMP-100.

I wanted to create this thread in order to begin to exchange about the knowledges of people who work around the PMP-100.

As told in the firmware thread of shamrockman, we have all we need to start developping new stuff for the PMP. The work that will be presented here will be technical only. No ask about the features that volunteers will add or date of firmware releasing SHOULD be posted here.

For people who would like to start working/developping around the PMP, please start by reading FULLY and CAREFULLY the firmware thread of shamrockman.

Thank you,
pmp.breaker.

[pmp.breaker]

In the source tarball from Iriver, we have the code of the Cadenux framebuffer driver. I am wondering if it is possible to display a console (login, shell...) on the PMP screen. As we can compile the kernel, it may be possible to add this functionnality as well as USB keyboard drivers...

Any advices, ideas ?

[pmp.breaker]

Have somebody successfully build a PMP-100 firmware understood by the update firmware function in the PMP-100 menu ?
Anybody has info about the structure of the firmware ?
Could somebody write a script to build the firmware ?


Thank you,
pmp.breaker

[pmp.breaker]

I have found on the net these two sites about PMP-100 dev. But their authors have not begin to really work around the PMP-100. I warned them about our progression and invited them to join us on this forum.

http://rain.prohosting.com/slimscsi/
http://unfix.org/projects/pimp/

pmp.breaker

[ShamrockMan]

I've been documenting everything about the firmware update and the iriversys file formats here:

http://wiki.shamrockman.net/index.ph...=Firmware_data

Hacks that do not involve firmware update can be found here:

http://wiki.shamrockman.net/index.php?title=PMP_Hacks

[UaDogga]

so now all new software for the pmp will be released in this thread?

[Z80]

Originally Posted by pmp.breaker

Have somebody successfully build a PMP-100 firmware understood by the update firmware function in the PMP-100 menu ?
Anybody has info about the structure of the firmware ?
Could somebody write a script to build the firmware ?

i think is possible build firmware:> in rrload load your *.rr file, boot pmp and dump firmware to file with programs in /fs/examples/fwupgrade ... you could also look at linux/drivers/dm270pmp/fwupgrade/fwupgrade.c
sorry iam not good programmer but only rewerse engineer ;o)

[pmp.breaker]

Originally Posted by UaDogga

so now all new software for the pmp will be released in this thread?

We can not speak about programs/softwares releasing here, because for the moment, we do not have the choice, we must provite a complete firmware for the lambda user (until sby write a "browser and launcher" which adds to the iriver firmware). So, the only public releases will be home brew firmwares which will be discussed on the shamrockman's thread (it seems logic form me and that's what I propose).


pmp.breaker

[pmp.breaker]

Originally Posted by Z80

i think is possible build firmware:> in rrload load your *.rr file, boot pmp and dump firmware to file with programs in /fs/examples/fwupgrade ... you could also look at linux/drivers/dm270pmp/fwupgrade/fwupgrade.c
sorry iam not good programmer but only rewerse engineer ;o)

For me, the firmware is the update data for the PMP-100 which will be run by the PMP update function. The shamrockman's wiki seems to provide all we need to build one. Who want's to script ?

pmp.breaker

[Z80]

Originally Posted by pmp.breaker

For me, the firmware is the update data for the PMP-100 which will be run by the PMP update function. The shamrockman's wiki seems to provide all we need to build one. Who want's to script ?

pmp.breaker

by this you could get allimage.hex without script i think

[ShamrockMan]

I dont have the update fully reverse engineered yet, as it still fails. I need a working PMP or emulator so I can figure out what is wrong. If the directory bug, or the invaild image bugs can be exploited, that would be better since people will not need to risk flashing the pmp.

[pmp.breaker]

Originally Posted by ShamrockMan

I dont have the update fully reverse engineered yet, as it still fails. I need a working PMP or emulator so I can figure out what is wrong. If the directory bug, or the invaild image bugs can be exploited, that would be better since people will not need to risk flashing the pmp.

Ok. You have not yet get a working PMP on ebay ?

I have worked a bit on the firmware. I don't understand what is sys.img ! Can sby light me about this file ?

Apparently, there are redondancies between the firmware file allimg.hex and the sys.img (which may be included in it and filled with data found in PmpVersion.defs). And there are big similarity between... I don't understand.

My tonight work gave me that :
[code]
0x00000000-0x0000000F : firmware header
->0x00000000-0x00000001 : major firmware version = PmpVersion.defS->USER_MAJOR
->0x00000002-0x00000003 : minor firmware version = PmpVersion.defS->USER_MINOR
->0x00000004-0x00000005 : major rrload version ? = PmpVersion.defS->PMP_RRLOAD_VER
->0x00000006-0x00000007 : minor rrload version ? = PmpVersion.defS->PMP_CODEC_VER
->0x00000008-0x00000009 : firmware checksum = PmpVersion.defS->PMP_KERNEL_VER
->0x0000000A-0x0000000B : region code = PmpVersion.defS->BMPVERSION
->0x0000000C-0x0000000D : region code
[code]

CRC computation :
memory data area from firmware : 0x00000010-00400000
C code found in ./fs/inputserv/checksysimg/crc.c

[szevvy]

What I'll do is (hopefully today) post up some code for someone who's rooted in to run - it'll be something along the lines of

#include <iostream>

int main(){
void * address1 = (void*)(0x4052345);
void * address2 = (void*)(0x4356363);
std::cout << *((unsigned int*)address1) << ", " << *((unsigned int*)address2);
}

or similar (with proper values, not ones I made up just then ), which'll mean I'll be able to start tracking down the problem with the emulator. Is that in the scope of what you guys are able to run? There might be a few of these over the course of some time until I figure out what the hell's going on. In the meantime - I've knocked up an old Linux box to try and compile and so forth. Should I use Fedora or Redhat?

[ShamrockMan]

I won one on the 7th, but they are quite slow in shipping it to me. I sent them a email about it.

Sys.img is the filesystem romfs image with a little bit of extra data. It has not been completly reverse engineered yet. It may need to be in .rr format, I'll take a look more closely at it tonight.

szevvy, either one should work.

[szevvy]

Where are you people getting this sys.img file from? I've looked in the 2.04 firmware zip and for the life of me can't find it.

[pmp.breaker]

Originally Posted by szevvy

What I'll do is (hopefully today) post up some code for someone who's rooted in to run - it'll be something along the lines of

or similar (with proper values, not ones I made up just then ), which'll mean I'll be able to start tracking down the problem with the emulator. Is that in the scope of what you guys are able to run? There might be a few of these over the course of some time until I figure out what the hell's going on. In the meantime - I've knocked up an old Linux box to try and compile and so forth. Should I use Fedora or Redhat?

1) personnaly I love Debian, but any distro should work.
2) i think it will be more simple for us to compile C code, as our makefile is done for C, not C++... If you have probems with it, I will try to translate it (cout << to printf).



pmp.breaker

[pmp.breaker]

Finally, I think that for our work, we need a special area for creating threads about our work. Beacause it will be more and more difficult to work on only 1 thread about plenty of subject.... I will ask to misticriver if they can open a new area for our work. If any body has an other idea ?

pmp.breaker.

[Astec]

PMP breaker feel free to start a thread and link to the various areas of the development via a main link thread. Then that thread can also be used for discussion. Alternatively you can keep people updated here and post to your own site for the topic. It may be worth PMing SRM to see if he would be interested in starting up a forum on his site regarding this.

A

[ShamrockMan]

It might bee better if we used my forum for the tech talk, as not to frighten the locals here. (you can also have 1mb zip attachments on my forum)

[pmp.breaker]

Shamrockman, if you would lilke to host our work I would be pleased !
But let me do a mirroring