I have used the "free" command to get amount of memory available and it sais I have 30884 total memory, of which 15468 is used and 15416 is free.
Am I using a wrong command, mis-reading, or does it look like I only have 15MB of free memory to work with?
What happened to 64MB RAM?
Dude... DUDE!!!
Ok, so that pretty much sucks for development. I have downgraded my F100 to version 3.0 that appears to have telnet and samba still.
Are F100 and F200 pretty much identical except for the Dpad and Touchscreen (and the lack of netchip in F200)? CPU is the same, RAM is the same...
I'm also getting the F200 model. Does this mean F200 development will be sans-samba too? :(
Anyone know of a reason net stuff are gone? Security? Licensing? DRM?
What would the most efficient way be for developing for F200 now assuming I'm using Visual Studio and SDL?
I'm sorry for resurrecting such an old topic, but it seems this is a problem again.
I have been away from GP2X dev for few years now, and updated to firmware 4.0. Eh, what happened to Samba?
Are we back to PC -> Compile -> SD card -> GP2X -> Run -> Crash -> PC -> etc...?
Man, after all the help on this thread, I have been able to set it up where I have about 5 seconds between build and launch. Oh, and not to mention the saving of my SD card's use by not erasing every build. This should definately go into the Wiki page right after Visual C++ setup. I tried...
It appears that if SDL is not launched, then printf() works great. But, as soon as I launch SDL, it does not display printf() statements.
[EDIT / UPDATE]
OK, problem found. It was my code. I did not put \n at the end of the lines so I guess the buffer never cleared and printed. After I put in...
Squidge, thank you. And thank you Parkydr. It is working beautifully.
Yes, I wanted to avoid the SD/NAND memory copy and also speed up the process. Seems to work. I'll test it out. This is something that should be put on Wiki right after the Visual Studio 2005 setup docs.
P.S. I still do...
Parkydr, no go on both accounts.
Oh, I can see the printf statements if the program fails to launch and the "SDL Parachute" deploys ( :) ). But, if SDL successfully sets the video and launches the app, then I am out of luck, no printf statements. I have put them everywhere in the code and...
I created a share under windows called gp2xdev, I try to mount it and it sais "No such device.
I am using this:
mount -t smbfs //10.30.78.105/gp2xdev /mnt/dev -o username=gp2xdev password=gp2xdev
And nothing... I get "No such device". Any ideas?
Also, I do not see the printf statements. I...
Excellent, but how, in Windows, do I get to see the output of printf() statements for debugging? Say I have the gpe on my sd card and now i picked up my gp2x and launched the program, what do i do on windows/gp2x to see those printf() statements?
thanks guys.
Ok, I got the samba server and networking bridged with my WinXP system. I can browse the gp2x filesystem. So how do I setup my development where I mount the PC folder/hd and able to see printf output for debugging? <_<
Thank you guys.
Hmmm, this is true even if I use the HW Accelerated SDL from Paeryn? I also am going to experiment talking directly to hardware, so I doubt the Windows compile will work well for me there.
BUT, I liket he samba idea better but I have never used linux before. I understand some portions of it but...
What is the fastest process? Currently here is my way:
- Compile the program in VC++ 2005
- On GP2x, Settings -> USB -> SD
- Copy the GPE from my PC to the SD card
- On GP2x, exit USB (sometimes crashes, need reboot)
- On GP2x launch the program
Is there a faster way? I do not have the serial...
Ok, hello folks. I'm pretty new to GP2x. I have setup my Visual Studio 2005 to compile the GPE files. Now, I have made a nice small demo using SDL (the paeryn hw library, THANKS!).
Now, I am wondering how I can develop without the SDL library. I read about the minimal library but the license is...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.