OSDev.org

I'm starting in os dev and I have in my kernel, functions to print to the terminal, cursor update and serial communication. I'm searching for a long time and nothing :/

I want to know how can I print the address of a pointer to screen and get this address and convert it to a string and send it to my serial port. Plz help me dudes, I'm dumb

Well, first you need to cast the pointer to an appropriately-sized unsigned integer. (uint32_t, or uint64_t on a 64bit cpu in long mode.) Now, every 4 bits of that integer is one hex digit. So to convert it to a string, you can just shift and mask to get just the 4 bits you want, and map that into a static global array of characters ("0123456789abcdef"). To get the number in the right readable direction, make sure you're converting the most significant bits first.

Here's an very simple example from my bootloader.

Ok, I'll try to adapt it to my needs. When casting a common pointer to a uint32_t pointer for example, I can get the common pointer memory address?

I'm searchin ways to debug my kernel, I'm using serial ports bcs I don't know how to make my own printf function.

So I really get strange things, first when trying to convert a pointer to uint32_t pointer not seems to work.

Second thing, what this means: 0000694f00000000

Putting it into an Hex to ASCII I get crazy symbols and iO (yes inverted).

My code:

Ow there's one more thing, this function convert a string to hex. I want to get the memory location of a pointer and prints it as hex example:



and the out something like: 0xA9924354

You probably don't want uint16_t for your implementation. In this case I was working with UEFI, which uses wide characters. Unless you're also in UEFI-land, you most likely want just char. (Which also means you don't need the u prefix on your character literals.



Take a step back and think about what you're asking the compiler for with the data types here. Remember than in C, a pointer and an array are not very different. So you're telling the compiler to allocate two bytes on the stack for 'Oi', and c points to those two bytes. You then make p point to the same address, and then ask it to read 4 bytes starting at p as a uint32_t, and then the next 4 bytes after that as a uint32_t, when you only allocated 2 bytes.

What you probably want here is the address of each uint8_t in array c. And you want to convert the address (not the value) to a uint32_t. So instead of casting it as pointer (uint32_t*) you just want to treat it as a value (uint32_t).

You might want to refresh yourself on pointers and datatypes (here's a short tutorial). As for why you see "iO" in the output, it's because you're treating that memory as a 32-bit number on a little-endian computer - what used to be known as the "NUXI" problem on old UNIX machines.