sceGeEdramSetSize not working properly
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp
- Domain
- embedded-iot
Research direction
Start by reproducing the shown C++ program on a PSP Street and inspect the return values from sceGeEdramSetSize and sceGeEdramGetSize. Check the PSP SDK declarations and documentation for these entry points and compare the requested size with the device's reported behavior. Done means the platform-specific behavior and any required conditions are established and documented.
Written by the indexing model from the issue text.
Description
Hello, I'm trying to use sceGeEdramSetSize(0x400000) to increase the vram but it's not working on my PSP Street.
Any idea why this code doesn't work?
Thanks!
#include <string>
#include <pspkernel.h>
#include <pspdisplay.h>
#include <pspge.h>
PSP_MODULE_INFO("PSP VRAM ISSUE", 0, 1, 0);
PSP_MAIN_THREAD_ATTR(THREAD_ATTR_USER);
int main(int argc, char *argv[])
{
pspDebugScreenInit(); // Initialize the debug screen
if (sceGeEdramSetSize(0x400000) == 0)
{
pspDebugScreenPrintf("sceGeEdramSetSize 4MB ok\n"); // Never called
}
else
{
pspDebugScreenPrintf("sceGeEdramSetSize 4MB ERROR\n"); // Called
}
pspDebugScreenPrintf(std::to_string(sceGeEdramGetSize()).c_str()); // Prints "2097152" instead of the double
while (true)
{
sceDisplayWaitVblankStart();
}
}
- Dominant language
- C
- Stars
- 1.2k
- Forks
- 190
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 12
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pspdev/pspsdk
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pspdev/pspsdk#388 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pspdev/pspsdk#412 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
SPIDevice selects an active-high device as soon as it is createdPossibly taken @mikeysklar claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
adafruit/circuitpython#11869 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
gnif/LookingGlass#1352 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100