Rockbox Development > New Ports
Meizu M6 "miniplayer"
gevaerts:
OK, there seems to be a lot of confusion about the meizu_dfu tool, so maybe I should mention some facts:
get_cpu() is executed twice to match the behaviour of the original windows dfu tool that's mentioned on the meizume forums.
meizu_dfu is designed to upload a firmware file, wait for it to start running and start its own dfu mode, and upload another file. This is because that's what you need to do to install the OF.
For running the rockbox test code, you only need one, and it doesn't speak dfu itself, so the second set of get_cpu() and upload fails.
Of course, some changes to the meizu_dfu code to have a mode where it only tries upload a single file (maybe by looking at how many files it's given on the command line) would be welcome
l4:
I am glad gevaerts pointed out these facts. I have debugged and resolved my get_cpu issue which opposed to yijie's was in failing to get_cpu even before the first image was sent. Now what is happening is after sending the first image, the USB connection is reset to be reestablished with the upload code that has been sent in the first image. I got 'No Device Found' on the atempt to reestablish the connection. This is due to the player not being rediscovered during the 'Wait a sec (literally)..." message. This can be avoided by changing the waiting interval to 2 seconds.
If you encounter this issue just go to the rockbox/utils/meizu_df/meizu_dfu.c and change the sleep(1) to sleep(2) (in the code that is used for your version of player!). Now recompile the dfu tool and try again.
My status is now hanging on sending the second image. I assume the update code is not accepting it (most likely my fault) but I know its running as it is returning the CPU model S5L8700 Rev.2-BE 070831
(If anyone has a feeling that random thoughts of two minds is better than just one, visit the IRC, you can catch me with /msg l403 on freenode)
yijie:
Thanks everyone! Finally I get response. :)
To wpyh: I tried to hold two buttons down all the time, but failed again. And if I press only M button, the command meizu_dfu updateNAND_BE_070831.dfu M6SL.ebn works.
Seems like after the first image updateNAND_BE_070831.dfu was uploaded, it begins to run. So, what is the address does it run from? Can we make rockboot.ebn run on this address and discard the second satge?
gevaerts:
--- Quote from: yijie on May 29, 2009, 11:45:15 PM ---Seems like after the first image updateNAND_BE_070831.dfu was uploaded, it begins to run. So, what is the address does it run from? Can we make rockboot.ebn run on this address and discard the second satge?
--- End quote ---
We can, and that's why we do that.
bertrik:
Hi all,
gevaerts lent me his Meizu M3 and I'm working on getting more stuff to work on it. So far we've been able to control the backlight brightness by doing interrupt-driven PWM, getting the i2c bus to work so we can talk to the codec and the real-time-clock chip. Hopefully we'll soon be able to communicate with the radio chip too.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version