Hello, dont know if it is right to put this -> i have a problem, yesterda just arrived my wonderfull Pokitto with 2GB SD card. Now when i´m addigng games/programms/demos-*.bins to on the SD card existing ones and there are over 100 -*.bins and i start the loader, i cant scroll down to select the bins to start, it stuck at the first *bin.. :( is there a limit of ~100*.bins on sd-card, and than the filesystem is overloadet?
1 Like
Have you tried removing some of the .bins?
If it still doesn’t work after than then it’s probably not the number of bins.
(Unfortunately I can’t play the video.)
yes, when i remove a few added .bins (from the ones a added to the existing ones from gamedisc) it works.
But there is still 1,3 GB free Rom on SD Card. ~80 .bins working fine, over 80, its impossible to scroll down when loader is started… How much .bins do you have on sd Card??
1 Like
Hi. Sorry but this is a bug. We need a new release of loader
1 Like
Ok thank you <3 so atm the loader can handle only ~80 .bins?
Correct. Sorry about that, I think fixing it is easy but at the moment I have no opportunity to check it out. I am in the middle of changing jobs and its a challenging situation. I’ll try to get to it as soon as possible
2 Likes
ok, I wish you success 
should i add it to bugrep or is it already known?
3 Likes
I’ve migrated this to the bug reports section of the forum.
I’ll also add an issue to the GitHub.
I’d look into it myself but I don’t know where the loader is kept.
I’ll have a dig later if I get time, but I’m currently busy working on something else Pokitto related.
If neither me or @jonne get time to have a look, maybe @FManga or @Hanski will have a free moment.
1 Like
The loader isn’t on github yet.
1 Like
Thanks to take care of it 
1 Like
True. Coming soon
EDIT : the reason is I need to update the code to work with the latest codebase
2 Likes
Oh right, I forgot it’s stored in the LOA.DER file.
I’ve already made the issue so we can close it or leave it as it is.
If @jonne’s going to be adding the loader then it’s probably best to leave it until we know which is going to happen first - the bug getting fixed or the loader being added to the repo.
And a delayed grab of Jonne’s post.
Please add it to our fancy-pants open for everyone todo list
I’ve added it on behalf of @Haunebu123.
I also added a note about uploading the loader to GitHub,
and I’ve also forked the list into a ‘completed’ list so the todo list can actually shrink as stuff gets done.
2 Likes
I’ve started work on this. I have brought the loader to the new codebase but it is too big to fit in the memory area allocated. I’m trying to figure out what has increased the binary size
2 Likes
Got it to compile.
Phew.
Went from overflow (too big) of .text section (=program code) by 4092 bytes to 1300 bytes to spare 
Link-Time Optimization for the win!
1 Like
An interesting information in that link. Do you remember if we have dead code & data removal in use in PokittoLib?
LTO, link time optimization, is something I have never used before. This time I was desperate.
What it does is that it re-analyzes unused code and data sections again when the compilation is finished and the linking is ongoing.
So no, we have not used this option before.
EDIT: in this case, LTO helped clear out float math operations that were actually not used. Compiler optimization -Os only looks at individual compilation units. LTO looks across all compilation units. The difference in this case was a whopping 1320 bytes.
1 Like
To enable dead code removal, all the C/C++ source code files must be compiled using the command line option -ffunction-sections. Furthermore, the linker must be launched with the linker command line option --gc-sections.
To enable dead data removal, all the C/C++ source code files must be compiled using the command line option -fdata-sections. Furthermore, the linker must be launched with the linker command line option --gc-sections.
These could be very useful also in PokittoLib.
1 Like
Unfortunately, this option (LTO) is experimental, and i am beginning to see why.
Won’t run.
EDIT: confirmed. It messes up the binary
EDIT: and here’s the bug
1 Like