M3 Firmware (might be relevant for M6 too)

Well, I said a few days ago that I would post some of my adventures with M3 firmware. I haven't cleaned it up, so this is all I can post right now (see attachment).

Now I've got some help from Rupan, and the M6SL image format is now supported.

The first attachment is Rar.exe that we need to compress the firmware image.

The second attachment is the utilities. It contains:

meizu-firmware : Utility for joining or splitting a firmware image.

meizu-resource : Utility for joining or splitting a resource file.

meizu-convert: Utility for converting between resource types.

m3_settings_show : Utility for examining the settings file from an M3.

other c files: common functions.

Please note that Windows users won't need the resource converters since they have Resource Editor.

Hope this helps.

I edited 2.004.5 firmware so that it uses SYSTEM\SETTINGS.DAT instead of SYSTEM\SETTIGS.DAT (sic)

I did not modify the resource file, so I'm not attaching it here

What is this?, anymore information?

Uh, sorry. The file meizu-firmware-utils.zip is just some utilities to manipulate the firmware. Currently I only have something to create a .ebn firmware from its components (firmware_combine.c) and something to show M3's settings (m3_show_settings.c).

The file new5.zip contains a proof-of-concept edited firmware. I edited the firmware so that it saves and loads its settings from SYSTEM\SETTINGS.DAT, instead of SYSTEM\SETTIGS.DAT.

Originally Posted by wpyh

Uh, sorry. The file meizu-firmware-utils.zip is just some utilities to manipulate the firmware. Currently I only have something to create a .ebn firmware from its components (firmware_combine.c) and something to show M3's settings (m3_show_settings.c).

The file new5.zip contains a proof-of-concept edited firmware. I edited the firmware so that it saves and loads its settings from SYSTEM\SETTINGS.DAT, instead of SYSTEM\SETTIGS.DAT.

Ok thanks for youre reply!, I don't want to risk my M6 so I'm not gonna try it out:P

Originally Posted by wpyh

I edited 2.004.5_beta firmware so that it uses SYSTEM\SETTINGS.DAT instead of SYSTEM\SETTIGS.DAT (sic)

im testing. confirm - your firmare working on my M3.
May be you activate all language, calc and games?

Originally Posted by wpyh

Well, I said a few days ago that I would post some of my adventures with M3 firmware. I haven't cleaned it up, so this is all I can post right now (see attachment).

Some...
Whether there is a ready this utilites?

There are some mistakes in font format description in meizu-firmware-utils/formats/font.

=============
CODES SECTION
=============
...Entries with a value other than 0xffff have a glyph associated with it. The
meaning of the value contained in the entry itself is unknown...

It's the index of the glyph in the glyph section. For example if you want a glyph for codepoint 0x0020, index of the glyph will be the word at offset_of_codes + 2 * 0x0020.

==============
GLYPHS SECTION
==============
...This section is an array of 32-byte glyphs... Every glyph is coded in one of two different modes: 8-pixels-wide or 16-pixels-wide...

Not exactly right. Width of a glyph in bytes may be 1, 2 or 3 i.e. 8, 16, or 24 pixels. For 16 wide font each glyph is 16 * 2 = 32 bytes, for 20 wide - 20 * 3 + 4 = 64 bytes (4 bytes for alignment), for 24 wide - 24 * 3 = 72 bytes.

=============
CHARACTER SET
=============
The character set of the fonts are not known. For some glyphs they match the
UTF-16BE encoding, but for some glyphs they have an offset against UTF16-BE.

There are NO characters sets. They are unnecessary for BMP (basic multilingual plane).

@dravik: This is for the M3

@strangers: The utilities are in the attachment, in source form.

@Asmo: I've been looking at your thread for 15 minutes and still pondering... Will report back. Thanks a lot!

Originally Posted by wpyh

@dravik: This is for the M3
@strangers: The utilities are in the attachment, in source form.

May be this is not complete source?
Im try compile and what say editor:
Info :Compiling C:\BC5\m3_settings_show.c
Error:m3_settings_show.c(7,2):Unable to open include file 'STDINT.H'
Error:m3_settings_show.c(11,2):Unable to open include file 'SYS\MMAN.H'

Error:m3_settings_show.c(16,16):Declaration missing ;
Error:m3_settings_show.c(19,17):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,17):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(19,17):Declaration missing ;
Error:m3_settings_show.c(21,16):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,16):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(21,16):Declaration missing ;
Error:m3_settings_show.c(24,26):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,26):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(24,26):Declaration missing ;
Error:m3_settings_show.c(25,19):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,19):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(25,19):Declaration missing ;
Error:m3_settings_show.c(27,16):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,16):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(27,16):Declaration missing ;
Error:m3_settings_show.c(30,20):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,20):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(30,20):Declaration missing ;
Error:m3_settings_show.c(31,26):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,26):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(31,26):Declaration missing ;
Error:m3_settings_show.c(32,21):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(32,21):Too many error or warning messages
----------------------------------------------------------------------
May be you try attach complete project, ok? Thanks.

does this mean you are working on a custom firmware for the meizu player, i am very interested to see the progres of the meizu and custom firmware,
have you heard of the project "rockbox", maybe someone could try to make it work on the meizu players?
I really hope this will be possible in the future.

Originally Posted by strangers

im testing. confirm - your firmare working on my M3.
May be you activate all language, calc and games?

I don't think that's too easy...

Originally Posted by strangers

May be this is not complete source?
Im try compile and what say editor:
Info :Compiling C:\BC5\m3_settings_show.c
Error:m3_settings_show.c(7,2):Unable to open include file 'STDINT.H'
Error:m3_settings_show.c(11,2):Unable to open include file 'SYS\MMAN.H'

Error:m3_settings_show.c(16,16):Declaration missing ;
Error:m3_settings_show.c(19,17):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,17):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(19,17):Declaration missing ;
Error:m3_settings_show.c(21,16):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,16):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(21,16):Declaration missing ;
Error:m3_settings_show.c(24,26):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,26):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(24,26):Declaration missing ;
Error:m3_settings_show.c(25,19):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,19):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(25,19):Declaration missing ;
Error:m3_settings_show.c(27,16):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,16):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(27,16):Declaration missing ;
Error:m3_settings_show.c(30,20):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,20):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(30,20):Declaration missing ;
Error:m3_settings_show.c(31,26):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(16,26):Earlier declaration of 'uint8_t'
Error:m3_settings_show.c(31,26):Declaration missing ;
Error:m3_settings_show.c(32,21):Multiple declaration for 'uint8_t'
Error:m3_settings_show.c(32,21):Too many error or warning messages
----------------------------------------------------------------------
May be you try attach complete project, ok? Thanks.

Uh, I think <sys/mman.h> is a POSIX header. I don't think BC5 is POSIX-compliant...

Maybe you should try another compiler. I'm not familiar with Windows, but I've heard of OpenWatcom before. Or try Visual C++.

@Asmo: Thanks for the information on the font file format, I got it (mostly) figured out now.

About the number bytes in a font glyph, I'm not sure I understand you correctly. Are you saying that the glyph may consist of a different number of bytes, depending on its width? I've not observed this on the font files that I have looked at, namely resource 16, 18 and 19. Would you please explain on this one?

Originally Posted by roelandb

does this mean you are working on a custom firmware for the meizu player, i am very interested to see the progres of the meizu and custom firmware,
have you heard of the project "rockbox", maybe someone could try to make it work on the meizu players?
I really hope this will be possible in the future.

I thought the rockbox port was discontinued?

I'm not making a custom firmware right now (as in a new compiled firmware), I'm just altering the bytes to modify / unlock functionalities.

Originally Posted by wpyh

Uh, I think <sys/mman.h> is a POSIX header. I don't think BC5 is POSIX-compliant...
Maybe you should try another compiler. I'm not familiar with Windows, but I've heard of OpenWatcom before. Or try Visual C++.

Hello.Thanks for the reply. Im tryning compiler through VC++ 6.0 Standart Edition ( see logs: )
Compiling...
m3_settings_show.c
c:\meizu-firmware-utils\m3_settings_show.c(7) : fatal error C1083: Cannot open include file: 'stdint.h': No such file or directory
Error executing cl.exe.
m3_settings_show.exe - 1 error(s), 0 warning(s)
-----------------------------------------------------------------------
I think still need 'stdint.h' and others (.h-files).

Originally Posted by wpyh

@Asmo: Thanks for the information on the font file format, I got it (mostly) figured out now.

About the number bytes in a font glyph, I'm not sure I understand you correctly. Are you saying that the glyph may consist of a different number of bytes, depending on its width? I've not observed this on the font files that I have looked at, namely resource 16, 18 and 19. Would you please explain on this one?

For M3 every glyph consists of 32 bytes (16 * 2). For M6 there are 20x20 and 24x24 fonts besides 16x16. So 20x20 glyph is 64 bytes, 24x24 glyph is 72 bytes.

Originally Posted by Asmo

For M3 every glyph consists of 32 bytes (16 * 2). For M6 there are 20x20 and 24x24 fonts besides 16x16. So 20x20 glyph is 64 bytes, 24x24 glyph is 72 bytes.

I see. I haven't looked into M6 resource files yet

@strangers: I think I will just declare the integer definitions inside the source files...

Bump. I think it would be useful if we can make it sticky and available from both the M6 firmware board and this (M3 firmware) board. Admin?