Olympus m:robe MR-100

[Kezza]

There are 2 types MR-100 and MR-500i can rockbox be ported to these if a compiler was purchased and given to the project?

Kezza

Sorry just saw another post about the mr-500i but the question still stands for the mr-100 as it has a different chip

[scaramanga_goldengun]

Yes, I'd would also like it if this program were ported to the MR-100. The defualt firmware pretty much sucks, and not much development is possible on it, so anybody? The MR-100 is at least a year old too, and you could probably get one (working, w/ all accessories) between $75-$100.

The only problem I could see is the controls.

[lowlight]

I have one and I'm experimenting   (but my battery died  ). I need to find a cheap one to disassemble since there's a metal frame soldered onto the board that obscures some of the chips. The controls should be ok, I'm worried about th lcd and controller.

[Bagder]

The mr-100 has a PortalPlayer chip while the mr-500 is TMS320-based

For both an ARM gcc is good enough, with an additional DSP assembler for the mr-500. So no need to buy any compilers or tools at all.

Both architectures are plagued by the fact that there are no public docs for them.

What we need is simply brave and eager souls that step forward and start working on these toys.

[lowlight]

I've put some board & chip scans for the MR-100 on the wiki:
http://www.rockbox.org/twiki/bin/view/Main/OlympusMR100Info
http://www.rockbox.org/twiki/bin/view/Main/OlympusMR100HardwareComponents

Please help id the unknown chips, especially the LCD.

[barrywardell]

According to the public docs for PP5020 (the brief spec sheet) there are two interfaces for the LCD built in, a direct interface and a bridge interface:

• The direct interface "drives single-scan 1-, 2-, or 4-bit monochrome STN panels".
• The bridge interface "drives 1-bit, 4-bit or 8-bit interfaces".

I believe the H10 and the colour iPods use the 8-bit bridge interface which is at address 0x70008a0c, while the monochrome iPods use the direct interface which is at address 0x70003000. With that in mind and the fact that the mr-100 is monochrome, I suspect that it would use the direct interface. Looking at the BL file, the address 0x70003000 appears a couple of times which makes it even more likely that this interface is used.

So, how about running a test using the monochrome ipod lcd driver and see if you get anything on the LCD?

[lowlight]

I'm not sure if the display is 1bpp or 2bpp. The ipods are greyscale: 2bpp with horiz packing. I tried the LCD_IPOD2BPP driver and it displayed a few pixels of garbage in the lower right corner.

Barry, I'd be interested to get your views on enabling the touchpad. I was hoping it would be read through the ADC like the H10 scrollpad, but I don't see a similar initialization in the BL file.

[barrywardell]

Sounds like you're at least on the right track with the LCD. As a guess, I would say the line

Code: [Select]

lcd_cmd_and_data(R_RAM_ADDR_SET, (y << 5) + addr_offset - x);could be the problem.

I still don't fully understand the ADC on the H10. I think it is the built in one mentioned in the PP brief public specsheet. On that sheet, it's mentioned that the ADC is used for battery, thermal and touchscreen functions, which makes sense in the case of the H10.

It's 4-channel and 10-bit per channel, channel 0 is for the battery level, channel1 is unknown (possibly temperature), channel2 is unknown (possibly disabled on the H10) and channel4 is the touchpad. If it really is the PP5020's built in ADC, and the mr-100 uses it too, it should be possible to read the ADC values using the H10's driver and the adc_scan(channelnum) function. You should get a value between 0 and 0x3ff.

In the case of the H10 touchpad, things are a bit more complicated. It seems that there are a few gpio ports which affect how the value is read by the ADC. By default, it reads either 0 or 0x3ff depending on whether it is touched. Writing to GPIOD pins 1 and 6 change how it is read.

[lowlight]

No real progress lately.

Regarding the lcd...when using the IPOD_MINI or IPOD_4G lcd driver a few pixels are turned on in the lower right corner. I tried writing several lines of "Hello World!", but the display did not change. When using the IPOD_MINI2G lcd driver, the screen is m:robe boot graphic is flipped.   The graphics in the bootloader are 1bpp, so I assume the display is 1 bpp as well.  However, since the ipod lcd driver is 2 bpp I tried halving the lcd dimensions. However, this did not change anything.  

Regarding the touch pad...in comparing the H10 bootloader to the MR100, I don't see similar code enable the scrollpad/touchpad. It doesn't appear tht the touchpad is used in the bootloader, so maybe it's not initialized?  But the touchpad lights are used, so there must be some way to turn them on/off.

[scaramanga_goldengun]

So is making rockbox for this plausible? Meaning that it will be done sometime in the future?

[Bagder]

So is making rockbox for this plausible?

Yes

Meaning that it will be done sometime in the future?

No, meaning it might be done sometime in the future given enough interest and effort spent by volunteers!

[lowlight]

This port is definately doable given the similarities to the H10 and some ipods. The current stumbling blocks are figuring out the touchpad and the lcd...I've tried most of the easy/obvious stuff, now it looks like I need to look more in depth at the bootloader asm...any volunteers?.

[Kezza]

This port is definately doable given the similarities to the H10 and some ipods. The current stumbling blocks are figuring out the touchpad and the lcd...I've tried most of the easy/obvious stuff, now it looks like I need to look more in depth at the bootloader asm...any volunteers?.

What do you need?
I will help if I can, point me in the right direction and we will see where I end up.

Kezza

[qc_metal]

I would be interested in a Rockbox version for the M:Robe 100 as well - - seems like nice hardware, its just that the way the M:Trip software works by creating proprietary play lists, etc.

[scaramanga_goldengun]

So has there been any progress yet?