devkitPro

I think the first issue is just a symptom of using nitrofs which appends the data to the rom. The second issue is more likely the problem. That it is complaining about the second texture slot which is not displaying correctly sounds like it is the issue. This can also be a false positive if you use...

Sounds like a palette issue. The original images load fine for me. Try a different image with more colors and details and see if you get something recognizable. Also try it out in desmume use the VRAM tools to see if the images are loaded correctly. The palette loads fine, I can see it in the palet...

I am not saying that there is anything wrong with nflib. I am only pointing out that the assets you are trying to use are not particularly suited to the ds. keep in mind the ds screen resolution is 256x192 so you do not really need huge images. also you should probably look at 8bit or even 4bit tex...

Meh... Then, any idea/suggestion how I should do the graphics? I dont know how to directly work with the DS hardware, I've always used a lib for that (like NFlib, PAlib or NitroEngine). I've though about create a somewhat optimized tileset of the background and do like PoKéMoN for GBA did (have a ba...

I resized nitrofiles\stages\yoshi\yoshi from 512x512 to 128x128 and everything loads fine. But it doesn't make sense. I only have those 3 graphics on VRAM. Before adding this to my engine I tested it first on a separate project and it worked without any problem (see attachment). The only difference...

Did you verify the amount you are trying to allocate when it fails? Do you have any code that I could look at? Yep, I added some debug and NitroEngine tries to allocate 524288 bytes to load a texture. The image is a BMP of 24 bits, 512x512. I can send you all the code (Makefile, source, include, ni...

I cannot edit last post so I'll make a new one: I've run the example on different DS to see if the data changes, these are the results: 3DS and DSi (DSMode) Before trying to allocate space for texture data Memory: 1432324 1420460 11864 After trying (failed) to allocate texture data Memory: 1432324 1...

take a step back. how much memory are you trying to allocate? the ds only has 4MB of ram that is shared with both code and data. use the arm-none-eabi-size.exe program to see how much code and static data you have. that will let you know how much main ram will be available for use with malloc. is i...

Sorry, for double-posting but the forum doesnt let me edit my last message... I've added some debug to show the info from mallinfo and this is the output: Before trying to allocate space for texture data Memory: 1370044 1354084 15960 After trying (failed) to allocate texture data Memory: 1370044 135...

try searching for mallinfo. keep in mind that on a system with limited resources like the ds you can run into issue where you have enough free memory but it is fragmented - so you do not have a free chunk that is big enough to satisfy a malloc request. it can even come down to the order that object...