OSDev.org

First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

osdeverr wrote:First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

I've had this question for quite a long time:

Why is your OS called U365? Is it based off a movie? A video game? Your favorite book? Or does it have some other special meaning? Maybe you just made it up?

MajickTek wrote:

osdeverr wrote:First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

I've had this question for quite a long time:

Why is your OS called U365? Is it based off a movie? A video game? Your favorite book? Or does it have some other special meaning? Maybe you just made it up?

Unix 365.

osdeverr wrote:First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

That is expected. Your memory management code is very bad.
I don't think it is a good idea to keep working on other stuff until your fix it. Don't be another me. That is the exact reason why 3 of my revisions failed. I am not making that mistake again. So I decided to stop working on my project until I fully understand how memory works and how to manage it. Not having a proper memory management can be lethal to your project. Other than that I am quite amazed by your ELF loader. Imaging loading programs that have been made using your own OS. Self hosting. Just port GCC. I think your should work on your EXT2 file system a bit. It would open thousands of possibilities. Also I don't like gray that much, so maybe make your shell white. Just a suggestion, or do something like personal settings (assuming you have a working file system implementation).

octacone wrote:

osdeverr wrote:First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

That is expected. Your memory management code is very bad.
I don't think it is a good idea to keep working on other stuff until your fix it. Don't be another me. That is the exact reason why 3 of my revisions failed. I am not making that mistake again. So I decided to stop working on my project until I fully understand how memory works and how to manage it. Not having a proper memory management can be lethal to your project. Other than that I am quite amazed by your ELF loader. Imaging loading programs that have been made using your own OS. Self hosting. Just port GCC. I think your should work on your EXT2 file system a bit. It would open thousands of possibilities. Also I don't like gray that much, so maybe make your shell white. Just a suggestion, or do something like personal settings (assuming you have a working file system implementation).

My memory management is fully fixed, thanks to my teammate. He worked a lot in this project, guess who fixed all these bugs from 0.x era? Bingo. It was him.
I'm gonna check out my EXT2 code right now, won't promise that I'll work on it though. About the shell: I think that it'll be too bright.

octacone wrote:

osdeverr wrote:First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

That is expected. Your memory management code is very bad.
I don't think it is a good idea to keep working on other stuff until your fix it. Don't be another me. That is the exact reason why 3 of my revisions failed. I am not making that mistake again. So I decided to stop working on my project until I fully understand how memory works and how to manage it. Not having a proper memory management can be lethal to your project. Other than that I am quite amazed by your ELF loader. Imaging loading programs that have been made using your own OS. Self hosting. Just port GCC. I think your should work on your EXT2 file system a bit. It would open thousands of possibilities. Also I don't like gray that much, so maybe make your shell white. Just a suggestion, or do something like personal settings (assuming you have a working file system implementation).

Wait... what about joining our team? Your OS has some problems, what do you think about helping another project instead?

osdeverr wrote:

MajickTek wrote:

osdeverr wrote:First troubles :C
calloc crashes the entire system with Invalid Opcode exception.

I've had this question for quite a long time:

Why is your OS called U365? Is it based off a movie? A video game? Your favorite book? Or does it have some other special meaning? Maybe you just made it up?

Unix 365.

Why 365 though?

MajickTek wrote: Why 365 though?

idk

Some random number.

AFAIR, you said that it's the way it is because there are 365 days in a (non-leap) year.

Roman wrote:AFAIR, you said that it's the way it is because there are 365 days in a (non-leap) year.

Still thinking of using Nim for your OS? We were talking about this in #osdev on Freenode.

Dawn


http://DawnOS.tk

http://forum.osdev.org/viewtopic.php?f=2&t=31420

Dawn operating system is made for the SUBLEQ architecture. if somebody is not want to write a gui, he can use Dawn as gui by emulating it. emulating it is very simple. if somebody decides to use dawn as a payload, just throw a message, and i will guide it trough

Geri wrote:Dawn


http://DawnOS.tk

http://forum.osdev.org/viewtopic.php?f=2&t=31420

Dawn operating system is made for the SUBLEQ architecture. if somebody is not want to write a gui, he can use Dawn as gui by emulating it. emulating it is very simple. if somebody decides to use dawn as a payload, just throw a message, and i will guide it trough

I absolutely love the idea and look of it all! Amazing work! The emulation thing sounds very interesting. I'm totally gonna check this out more thoroughly!

zaval wrote:Impressive and really inspiring, guys! I was staring at the thread several days. xD
I wish I could post here something similar, but my project can't even write into the serial port yet.
I am trying to create NT-like OS but as a first subproject of it, I'm working on a UEFI implementation for a couple of machines of two architectures, namely - MIPS and ARM. The OS itself is planned for x86 as well apart from those two. But now I'm messing around with the Beagle Bone Black armv7 SBC writing the first stages of UEFI PI spec (SEC, PEI). And once it is able to talk to the world I'll let you know.)

As I've promised, I post first screenshot where we finally have some pretty and meaningful output. After figuring out the problem with the address where we have been loaded to, thanks to amazing Ingenic PM for making such a challenge, we finally can print into the serial port. So we print "hello", $ra register and some CPM PLL related registers.
The machine is Imagination Mips Creator CI20 SBC with dual-core mips32r2 XBurst CPU @1.2 Ghz, from Ingenic (the SoC is jz4780).
As the print suggests, this is a beginning (SEC phase) of the Uefi implementation. Next step is configure PLLs and initialize SDRAM! It's 1GB DDR3. Then load from an SD card the next module - Dxe.exe, Dxe phase, where all the work will happen. We plan use it not only as a FW core, but also as an OS kernel prototype, so we are going to implement more than UEFI requires there. Interrupts (with IRQL/IPL), SMP. Then it will be branched into the kernel module and Hal.dll. But those are plans, so far we have this tiny output.

Geri wrote:Dawn
http://DawnOS.tk

http://forum.osdev.org/viewtopic.php?f=2&t=31420

Dawn operating system is made for the SUBLEQ architecture. if somebody is not want to write a gui, he can use Dawn as gui by emulating it. emulating it is very simple. if somebody decides to use dawn as a payload, just throw a message, and i will guide it trough

Looks awesome! Kitűnő munka!

bzt wrote:Kitűnő munka!

köszönöm szépen (javaslom, az osedből vedd ki az avx-et, mint dependenciát, mert így csak a legújabb procikon fog futni)