Thank You for your continued support and contributions!
fuzpa.bin - bootloader + original firmware, you should update it only if you need changes in bootloader or need new original firmware. Don't update it without good reasons - you can brick player if something going wrong.For regular update to new rockbox revision - just replace .rockbox/* .For small internal changes (like you doing with this patch) just replace one file - .rockbox/rockbox.sansa
First, try find lower value for first delay. Then try same for second delay.
$ ./configure --no-ccache --target=63 --type=b [...]$ make [...] CC firmware/target/arm/as3525/sansa-fuzev2/button-fuzev2.c [...]
The bootloader is a few kilobytes, the rest is the OF.
Quote from: Mihail Zenkov on January 04, 2016, 04:50:31 AMFirst, try find lower value for first delay. Then try same for second delay.So, I narrowed the things down to get to know the shortest possible delays where the hold-switch still works on my Sansa fuzev2.[...]So, shortest possible delays which still work for my device:1. udelay(): 19, 2. udelay(): 5. (19, 4 still needs to be tested!)Corresponding patch attached.
I did notice that during frequent boosting some button inputs are skipped, although maybe that is unrelated.
So, I narrowed the things down to get to know the shortest possible delays where the hold-switch still works on my Sansa fuzev2.Here are the results:
@ Mihail Zenkov: Can you include that one in your patchset?
And: Is there a way to make this patches upstream?
If not, it would be nice to host it somewhere (that people do not have to dig through all the forum posts to find the correct versions), if hosting is not possible and we have to resort to the forum, then putting everything into one file (.tar-archive, or a single patch file) makes things still more easy.
Edit: Both delays set to 10 works pretty well, will try other values:
Well, but I observe that also when compiling the bootloader, the file 'button-fuzev2.c' get's compiled:So, what's the reason that the bootloader takes into account that file?
Why is it not sufficient to just have a small bootloader ("fuzpa.bin") without the original firmware?
Does it fallback to the original firmware automagically if we don't have the .rockbox-tree on the device?
A user asked me if I can provide a working build. The forum does not allow to upload archive files. Is there a way I can upload it somewhere to a subpage of rockbox.org? I feel uncomfortable with hosting it by myself ... I did not dig into the legal issues yet (impressum of the website would be needed, warranty-disclaimer maybe, maybe some attribition to property rights I need to make).Otherwise, I would email the .tar.xz-archive if people ask me directly (private message, and include your email address).
Page created in 0.07 seconds with 21 queries.