Meizu M6 "miniplayer"

[vcf]

fine. does it work only on sl?
do you know if someone tried on sp?
and nothing is writed on the player, yes? so no info will be lost? i saw that only on first version of code where it worked only with pluged in usb

[gevaerts]

fine. does it work only on sl?
do you know if someone tried on sp?

This works on sl, yes.
It won't work as such on the SP. The GPIO pins for LCD communication are different. I don't know about M3.

and nothing is writed on the player, yes? so no info will be lost? i saw that only on first version of code where it worked only with pluged in usb

This is still RAM only, yes, although it is possible to flash it if you really want.

[denes]

I don't know about M3.

It won't work on the M3. The M3 has the LCD connected to the LCD interface in the SoC, and the picture is sent out with dma from memory to the LCD IF. Actually I was able to draw something on the M3's lcd with programmed io, but the code in question is not bulletproof yet.

btw awesome work with the meizu_dfu tool - I am using linux too, so it's a great help - thanks wpyh and gevaerts.

[markun]

Yesterday I added separate ports for the M6SP Aand M3, I hope that will make it easier to work on those targets.

Actually I was able to draw something on the M3's lcd with programmed io, but the code in question is not bulletproof yet.

That's great! Do you want to come on IRC from time to time to talk about the progress and things you've figured out?

[gevaerts]

A bit more progress on the m3, nearly fully thanks to denes:



Edit: Now the colours are correct!

[vcf]

cool! why where the colours not correct on the first picture? i've heard you've got SP and M3 too.so what about SP's lcd? we have full sp schematics http://www.meizume.com/attachments/rockbox/2005d1206010842-schematic-m6sp-m-p-v7.rar (by kgb2008)

[ii]

Hi.

I'm a new user of meizu m3 and I'm very interested in porting rockbox to this device.
I have some experience in coding, reverse engineering and electronics.
If anyone detalized me current status of the port and problems to be solved I would join the project for sure.

[ii]

Okay, I've found the port status page 
So how can I help?

[RichterSkala]

So. Today instead of doing some work for university I decided to mess with my M6SP and you're progress so far (see if my little skills in coding could contribute a thing). But I wasn't able to get the DFU mode to work.
So first of all there seems to be two different methods: Press Power and M or press M and Play.

If I press Power and M, plug in the usb connection and run meizu_dfu M6 M6.ebn M6.ebn it stops at USB initialization, takes some time to state later, that it couldn't find a device. During that time lsusb will give no output either.
Same procedure with Play and M: meizu_dfu takes no time on USB initalization and skips immediately to "No device found".

What am I doing wrong? My host system is a plain Ubuntu 8.06 - any reasons there maybe?

[zorgblaubaer]

i can't figure out how to compile the testcode for the m6... can anyone help me out?

this is what i tried:

Code: [Select]

lucas@lucas-desktop:~/meizu_dfu/rockbox/build$ ../tools/configure
Enter target platform:
 ==Archos==               ==iriver==             ==Apple iPod==
  0) Player/Studio        10) H120/H140          20) Color/Photo
  1) Recorder             11) H320/H340          21) Nano
  2) FM Recorder          12) iHP-100/110/115    22) Video
  3) Recorder v2          13) iFP-790            23) 3G
  4) Ondio SP             14) H10 20Gb           24) 4G Grayscale
  5) Ondio FM             15) H10 5/6Gb          25) Mini 1G
  6) AV300                                       26) Mini 2G
                          ==Toshiba==            27) 1G, 2G
                          40) Gigabeat F
 ==iAudio==               41) Gigabeat S         ==SanDisk==
 30) X5/X5V/X5L                                  50) Sansa e200
 31) M5/M5L               ==Tatung==             51) Sansa e200R
 32) 7                    60) Elio TPJ-1022      52) Sansa c200
 33) Cowon D2                                    53) Sansa m200
 34) M3/M3L               ==Olympus==            54) Sansa c100
                          70) M:Robe 500         55) Sansa Clip
 ==Creative==             71) M:Robe 100         56) Sansa e200v2
 90) Zen Vision:M 30GB                           57) Sansa m200v4
 91) Zen Vision:M 60GB    ==Philips==            58) Sansa Fuze
 92) Zen Vision           100) GoGear SA9200
                          101) GoGear HDD1630    ==Logik==
 ==Onda==                                        80) DAX 1GB MP3/DAB
 120) VX747               ==Meizu==
 121) VX767               110) M6SL
                          111) M6SP
                          112) M3

110
Platform set to meizum6sl
Build (N)ormal, (A)dvanced, (S)imulator, (B)ootloader, (M)anual: (Defaults to N)
B
Bootloader build selected
Using source code root directory: /home/lucas/meizu_dfu/rockbox
Using arm-elf-gcc 4.0.3 (400)
Using arm-elf-ld 2.16.1
Created Makefile
lucas@lucas-desktop:~/meizu_dfu/rockbox/build$ make clean
Cleaning build directory
lucas@lucas-desktop:~/meizu_dfu/rockbox/build$ make
make[1]: `rdf2binary' is up to date.
make[1]: `convbdf' is up to date.
make[1]: `codepages' is up to date.
make[1]: `bmp2rb' is up to date.
Create sysfont.h
CC ata_idle_notify.c
CC events.c
CC backlight.c
CC buffer.c
CC powermgmt.c
CC system.c
CC usb.c
CC kernel.c
CC rolo.c
rolo.c: In function ‘rolo_load’:
rolo.c:202: warning: unused variable ‘i’
CC thread.c
thread.c:795:6: warning: #warning core_sleep not implemented, battery life will be decreased
CC timer.c
timer.c: In function ‘timer_set’:
timer.c:253: warning: implicit declaration of function ‘__TIMER_SET’
timer.c: In function ‘timer_register’:
timer.c:326: warning: implicit declaration of function ‘__TIMER_REGISTER’
CC panic.c
CC debug.c
CC common/atoi.c
CC common/crc32.c
CC common/ctype.c
CC common/dir_uncached.c
CC common/file.c
CC common/disk.c
CC common/errno.c
CC common/memcmp.c
CC common/memchr.c
CC common/qsort.c
CC common/random.c
CC common/sprintf.c
CC common/strcasecmp.c
CC common/strcasestr.c
CC common/strcat.c
CC common/strchr.c
CC common/strcmp.c
CC common/strcpy.c
CC common/strncmp.c
CC common/strncpy.c
CC common/strrchr.c
CC common/strtok.c
CC common/strstr.c
CC common/structec.c
CC common/timefuncs.c
CC common/unicode.c
CC scroll_engine.c
CC arabjoin.c
CC bidi.c
CC font_cache.c
CC font.c
CC hangul.c
CC lru.c
CC drivers/lcd-16bit.c
CC drivers/led.c
CC drivers/button.c
CC drivers/serial.c
CC drivers/ata_flash.c
drivers/ata_flash.c:47:5: warning: "CONFIG_FLASH" is not defined
drivers/ata_flash.c:47:21: warning: "FLASH_IFP7XX" is not defined
drivers/ata_flash.c:78:5: warning: "CONFIG_FLASH" is not defined
drivers/ata_flash.c:78:21: warning: "FLASH_IFP7XX" is not defined
drivers/ata_flash.c: In function ‘flash_select_chip’:
drivers/ata_flash.c:80: error: ‘GPIO5_CLR’ undeclared (first use in this function)
drivers/ata_flash.c:80: error: (Each undeclared identifier is reported only once
drivers/ata_flash.c:80: error: for each function it appears in.)
drivers/ata_flash.c:82: error: ‘GPIO5_SET’ undeclared (first use in this function)
drivers/ata_flash.c: In function ‘flash_wait_ready’:
drivers/ata_flash.c:113: error: ‘GPIO6_READ’ undeclared (first use in this function)
drivers/ata_flash.c: In function ‘nand_get_info’:
drivers/ata_flash.c:471: error: ‘struct storage_info’ has no member named ‘serial’
drivers/ata_flash.c:457: warning: unused variable ‘i’
drivers/ata_flash.c:456: warning: unused variable ‘blocks’
make[1]: *** [/home/lucas/meizu_dfu/rockbox/build/firmware/drivers/ata_flash.o] Error 1
make: *** [build] Error 2


[gevaerts]

I still haven't updated the meizu code to the new storage layer, sorry about that.

Frank

Edit: fixed now

[jensu]

i've a question regarding the spi connection to the driver ic of the m6sl lcd.
does anyone know how this is connected to the samsung arm chip?
is there another layout instead of this file M-P-V7.pdf (i guess this is not the m6 layout)? i was just wondering, because i had a look at the init_lcd_spi function and there are ports used (e.g. PCON4 bit2,3) which are not connected to anything.
where can i get this informations (nothing found on the wiki page of the meizu port)?

cheers
jens

[gevaerts]

As far as I know M-P-V7.pdf is the layout of the m6sp. I'm not aware of any information that isn't on the wiki

[jensu]

sorry, i overlooked the link to the reverse engineering page.

[jensu]

does anyone currently working on the lcd driver for the m6sl?
i tried to get the id of the driver ic yesterday, but instead of 0x0154 i always got 0xffff.
did someone succeed in getting this id? can we be sure that all the port addresses regarding the m6sl model are correct?

best
jens