C/C++ Programming Help Thread

i am new to developing for the psp and want this code to work. i want display the current firmware version onscreen when the eboot has been run

Code:

---

#include <pspkernel.h>
#include <pspdebug.h>
#include <string.h>
#include <stdio.h>
#include <stdlib.h>
#include <pspsdk.h>
#include <pspctrl.h>
#include "systemctrl_se.h"
#include "pspvshbridge.h"
#include "systemctrl.h"

MODULE_INFO ....
DEFINE....

int main (int argc, char **argv)
{
              pspDebugScreenInit();
        getFirmwareVersion(void)
        {
        u32 firmware=(u32) sceKernelDevkitVersion();

        printf("%i" , (((firmware&0x0f000000)>>24)*100)+(((firmware&0x000f0000)>>16)*10)+((firmware&0x00000f00)>>8)));
      }

---

I believe you ain't gonna need this

Code:

---

#include <pspctrl.h>
#include "systemctrl_se.h"
#include "pspvshbridge.h"
#include "systemctrl.h"

MODULE_INFO ....
DEFINE....

---

And also, how's your makefile?

Cheers

Zitat:

---

Zitat von placo23

I believe you ain't gonna need this

Code:

---

#include <pspctrl.h>
#include "systemctrl_se.h"
#include "pspvshbridge.h"
#include "systemctrl.h"

MODULE_INFO ....
DEFINE....

---

And also, how's your makefile?

Cheers

---

here is my makefile

Code:

---

TARGET = get_version
OBJS = main.o

CFLAGS = -O2 -G0 -Wall
CXXFLAGS = $(CFLAGS) -fno-exceptions -fno-rtti
ASFLAGS = $(CFLAGS)

LIBDIR =
LIBS =
LDFLAGS =

EXTRA_TARGETS = EBOOT.PBP
PSP_EBOOT_TITLE = PSP Get_Version

PSPSDK=$(shell psp-config --pspsdk-path)
include $(PSPSDK)/lib/build.mak

---

Tell me what's the error you get mate.

It'll be difficult to know what's wrong without having an error message.

Also, why don't uyou start by the basic hello world?

Cheers

i think my problem is i do not know where to find sceKernelDevkitVersion(); or getFirmwareVersion finctions. i need to include the header file but do not know which one it is.

He's probably already done Hello World.
-= Double Post =-
sceKernelDevkitVersion() : pspsysmem.h

Zitat:

---

Zitat von JaSo PsP

He's probably already done Hello World.

---

yes hello world is too easy:tup:

Code:

---

#include "callbacks.h"
.....

MODULE_INFO
#define printf ....

int main{
pspdebugscreen;
printf("Hello Scene/n/n/n/n
        -pspN00bdev ;)/n/n")
return 0

---

lol very quick code

-=edit=-
i added pspsymem.h to main.c but exact same error occur.

Zitat:

---

implicit declaration of function getFirmwareVersion

---

:Cry:

Zitat:

---

Zitat von pspN00bDevoloper

yes hello world is too easy:tup:

Code:

---

#include "callbacks.h"
.....

MODULE_INFO
#define printf ....

int main{
pspdebugscreen;
printf("Hello Scene/n/n/n/n
        -pspN00bdev ;)/n/n")
return 0

---

lol very quick code

-=edit=-
i added pspsymem.h to main.c but exact same error occur.

:Cry:

---

Very quick and very wrong too XD

Zitat:

---

Zitat von Coolj

Very quick and very wrong too XD

---

That's why I'm saying.

Start with Hello World

sheesh, here is correct code. now back to my other problem

Code:

---

#include <pspkernel.h>
#include <pspcallbacks.h>
#include <pspdebug.h>


PSP_MODULE_INFO("Hello World",0,1,1);

#define printf pspDebugScreenPrintf

int main()
{
        SetupCallbacks();
            pspDebugScreenInit();
        printf("Hello World/n/n/n/n/n/n/n/n/n/n/n/n");
        sceKernelSleepThread();
        return 0;
}

---

Zitat:

---

Zitat von pspN00bDevoloper

sheesh, here is correct code. now back to my other problem

Code:

---

#include <pspkernel.h>
#include <pspcallbacks.h>
#include <pspdebug.h>


PSP_MODULE_INFO("Hello World",0,1,1);

#define printf pspDebugScreenPrintf

int main()
{
        SetupCallbacks();
            pspDebugScreenInit();
        printf("Hello World/n/n/n/n/n/n/n/n/n/n/n/n");
        sceKernelSleepThread();
        return 0;
}

---

---

That's still wrong, escape sequences need a forward slash, not a backslash.

And check here for SDK documentation. Search for the function you need.

http://psp.jim.sh/pspsdk-doc/

The problem here is that you have declared the getFirmwareVersion function the first time you use it... Plus it has no return type at the start. Heres how it should look:

Code:

---

#include <pspkernel.h>
#include <pspdebug.h>
#include <pspsysmem.h>
#include "callbacks.h"

#define printf pspDebugScreenPrintf

PSP_MODULE_INFO("Firmware Version", 0, 1, 1);

void displayFirmwareVersion();

int main()
{
        SetupCallbacks();
        pspDebugScreenInit();
       
        displayFirmwareVersion();
       
        sceKernelSleepThread();
        return 0;
}

void displayFirmwareVersion()
{
    u32 firmware = (u32)sceKernelDevkitVersion();
   
    printf("%i" , (((firmware&0x0f000000)>>24)*100)+(((firmware&0x000f0000)>>16)*10)+((firmware&0x00000f00)>>8)));
}

---

Assuming you have a callbacks.h accompanying main.c

Zitat:

---

Zitat von Judas

That's still wrong, escape sequences need a forward slash, not a backslash.

And check here for SDK documentation. Search for the function you need.

http://psp.jim.sh/pspsdk-doc/

---

I believe you wanted to say it the other way round.

The correct is to use Backslashes and not forward slashes.

ex:

Code:

---

printf("Hello World \n\n\n\n");

---

Cheers

Zitat:

---

Zitat von placo23

I believe you wanted to say it the other way round.

The correct is to use Backslashes and not forward slashes.

ex:

Code:

---

printf("Hello World \n\n\n\n");

---

Cheers

---

Oops, you're right. I always get the two confused.

Zitat:

---

Zitat von Judas

Oops, you're right. I always get the two confused.

---

Same lol, because they can both go forwards and backwards depending on which way you draw them.

Zitat:

---

Zitat von JaSo PsP

Same lol, because they can both go forwards and backwards depending on which way you draw them.

---

What do you mean with "which way you draw them"

Zitat:

---

Zitat von JaSo PsP

Code:

---


void displayFirmwareVersion()
{
    u32 firmware = (u32)sceKernelDevkitVersion();
   
    printf("%i" , (((firmware&0x0f000000)>>24)*100)+(((firmware&0x000f0000)>>16)*10)+((firmware&0x00000f00)>>8)));
}

---

---

HI

On custom firmware it will return 1.50 , because of the 1.50 kernel

Zitat:

---

Zitat von placo23

What do you mean with "which way you draw them"

---

If you were to draw a back slash or a forward slash on a piece of paper you could start from the top of the symbol or at the bottom, thus determining weather you will 'slash' backwards or forwards.

Zitat:

---

Zitat von ropost

HI

On custom firmware it will return 1.50 , because of the 1.50 kernel

---

I didnt write that function, I was just showing the guy how to make the function work.

Hi

just a notice :) , But you can check it by checking the recovery or vshmain md5sum

How would I go about writing a single bit to a file?

-Aura

you mean BIT or BYTE? lol

Zitat:

---

Zitat von myschoo

you mean BIT or BYTE? lol

---

He write BIT didn't he? A bit is a single numeric value, either 0 or 1. I spose you could write an integer to a file.

Zitat:

---

Zitat von JaSo PsP

He write BIT didn't he? A bit is a single numeric value, either 0 or 1. I spose you could write an integer to a file.

---

Yeah, I did mean a bit, as in 0/1, I tired used u2, but it didn't work (no supprise there really), if I write an integer, it will write a byte for each digit, as it would appear to be ascii, I'm looking to do something like Dark_AleX's plugin config, where it is either on or off, he makes the file in actual binary.

-Aura

Write in binary mode. Although to be honest it doesn't matter that you waste a few bytes to maintain easy readability of files.

u2 doesn't work because it isn't a base type. Neither are u32, s32, u8, etc. If you look in the headers that you include, you find that they are typedefs.

Zitat:

---

Zitat von yaustar

Write in binary mode. Although to be honest it doesn't matter that you waste a few bytes to maintain easy readability of files.

u2 doesn't work because it isn't a base type. Neither are u32, s32, u8, etc. If you look in the headers that you include, you find that they are typedefs.

---

The only thing that is going to read the file is the program...

And I didn't know about the u32 etc, I knew u2 didn't work at all, but I always assumed they were the same as int.

Anyway, I'm set up in binary mode, but... well I havn't got a clue how I'm actually meant to write in binary though?

-Aura

Data is stored in groups of 8 bits ( 1 byte ). You can't write 1 bit of data. You can use bitwise operators to operate on the bits in a byte, but you won't find just 1 bit of data without 7 other bits to accompany it. You can use bitshifting, bitfields, and other methods to store much data in a single byte, versus using many bytes.

But anyways... I still can't understand the point in writing one single bit into a file.

Cheers

Zitat:

---

Zitat von Moca

Data is stored in groups of 8 bits ( 1 byte ). You can't write 1 bit of data. You can use bitwise operators to operate on the bits in a byte, but you won't find just 1 bit of data without 7 other bits to accompany it. You can use bitshifting, bitfields, and other methods to store much data in a single byte, versus using many bytes.

---

I have to disagree, there is a way of doing it, take a look at the OE firmwares, the plugin save file thing is in bits...

Zitat:

---

Zitat von placo23

But anyways... I still can't understand the point in writing one single bit into a file.

Cheers

---

I guess there isn't much reason to do it, but it would be helpful for apps using a very small amount of space, and also just for reference (which is mainly why I want to do it).

-Aura

Why bother trying hard to find out how to write a bit to a file when you can just write an integer, with the same results.

Zitat:

---

Zitat von JaSo PsP

Why bother trying hard to find out how to write a bit to a file when you can just write an integer, with the same results.

---

You can't write ONLY 1 bit to a file.

Zitat:

---

Zitat von Auraomega

I have to disagree, there is a way of doing it, take a look at the OE firmwares, the plugin save file thing is in bits...



I guess there isn't much reason to do it, but it would be helpful for apps using a very small amount of space, and also just for reference (which is mainly why I want to do it).

-Aura

---

It writes things in groups of 8 bits :|

Note how I said you can store quite a bit of data in a byte by using bitfields and bitwise operators, however it will take more machine instructions to shift access the data.

If you really must then yes you can use bitfields in your struct, eg:

Code:

---

struct config
{
    int optionA : 1;
    int optionB : 1;
    int optionC : 1;
    ...
    etc.
};

---

Each of which take up 1 bit. Its best to make sure the size adds up to multiples of ints, since you never know how the padding & alignment will turn out. Go lookup unions & bitfields for more info.

But anyway, since you're trying for a config like OE, you should know that OE uses ints for its config struct.

Moca you're right, I feel like such an idoit... just dragged it into a hex editor and it is in bytes, and not bits, sorry about that.

While I'm here...

Code:

---

width  = im->imageWidth;
height = im->imageHeight;

---

I've taken this from my code, it works, I just don't understand what its actually meant to do normally, so could someone explain?

-Aura

It just gets the width and height from the image pointed to by im and stores them in two different variables. Nothing special.

Zitat:

---

Zitat von coolguy5678

It just gets the width and height from the image pointed to by im and stores them in two different variables. Nothing special.

---

I know that, I was messing around when I found that code, and I know what it does seeing as its actually in my code, what I mean is how does the -> normally work, not what does it do in this case...

-Aura

http://www.cprogramming.com/reference/struct/

OK. -> accesses a struct member through a pointer. example:

Code:

---

typedef struct {
  int hello ;
  int goodbye ;
} Blah ;
// ...
Blah* qwert = /* something */ ;
// qwert->hello is equivalent to (*qwert).hello

---

It's really just a shorthand.

Alright, I wan't to make an image i load external, so other .c files can use it,
so far i've tried loading it like this,

Code:

---

Image * back1;
Image * background1;
Image * hud;

---

that is above the function, then i declare what they are in the image loading function like,

Code:

---

back1 = loadImage("./sprites/namer1.png");
background1 = loadImage("./backgrounds/background1.png");
hud = loadImage("./sprites/hud.png");

---

and in the imageLoading.h, i have

Code:

---

extern Image *back1;
extern Image *background1;
extern Image *hud;

---

this gives me there errors,

Code:

---

space_images.h(6)  C:\Documents and Settings\Owner.JAWS\Desktop\AceOfSpace\space_images.h(6) syntax error before '*' token
space_images.h(6)  C:\Documents and Settings\Owner.JAWS\Desktop\AceOfSpace\space_images.h(6) [Warning] type defaults to 'int' in declaration of 'back1'
space_images.h(6)  C:\Documents and Settings\Owner.JAWS\Desktop\AceOfSpace\space_images.h(6) [Warning] data definition has no type or storage class
space_images.h(7)  C:\Documents and Settings\Owner.JAWS\Desktop\AceOfSpace\space_images.h(7) syntax error before '*' token

---

space_images.h(7) C:\Documents and Settings\Owner.JAWS\Deskt op\AceOfSpace\space_image s.h(7) [Warning] type defaults to 'int' in declaration of 'background1' [/CODE]

include the header in the headers where "Image" get declared

image.h

Code:

---

blah
blah
load images
blah

---

main.c

Code:

---

#include "image.h"
blah
blah
use image
blah

---

im sorry, i was a little rushed in my post, had to get off computer, but i forgot to mention i already had image.h included in all the .c files that use the images. The compiler gives me errors about space_images.h (the header file of the C file i load the images to the program from), the errors i get say,

Code:

---

  syntax error before '*' token

---

ill post the whole space_images.h

Code:

---

Spoiler for code of space_images.h:

#ifndef __SPIMG__
#define __SPIMG__

extern void space_images();

extern Image *back1;
extern Image *background1;
extern Image *hud;
extern Image *playerimg;
extern Image *pBulletpic;
extern Image *eBulletpic;
extern Image *exp1;
extern Image *enemy1img;
extern Image *enemy2img;

extern Image *great;
extern Image *ok;
extern Image *bad;
extern Image *dead;

extern Image *pauseBack;
extern Image *pauseCursor;

extern Image *namer1;
extern Image *namer2;
#endif

---

does this help explain? Would you also like me to post space_images.c?