RaspberryPi Osdev - Revision history

Ghans at 18:41, 18 June 2012

2012-06-18T18:41:37Z

Cheery: Linked to some really good reading by David Welch

2012-06-16T11:42:44Z

Linked to some really good reading by David Welch

Cheery: /* Existing Forums Posts On Assembly Code */ added a link that's related

2012-06-14T12:26:16Z

‎Existing Forums Posts On Assembly Code: added a link that's related

Cheery: Links to forum posts that tell about assembly.

2012-06-08T14:30:52Z

Links to forum posts that tell about assembly.

Cheery: /* Hardware Specific Documentation */

2012-06-07T23:22:40Z

‎Hardware Specific Documentation

Cheery: Bit of instructions

2012-06-07T23:22:10Z

Bit of instructions

Cheery: Raspberry pi osdev community bootup

2012-06-07T21:18:19Z

Raspberry pi osdev community bootup

New page

Raspberry Pi is an opportunity for people to learn OS development on fixed hardware. This makes it easier to make designs that you can share with others. Thereby we have started a community, which communicates through IRC.

== IRC Channel ==

irc.freenode.net#raspberrypi-osdev

=== How to connect ===

* install irssi
* start irssi and type in: /connect irc.freenode.net
* then type: /join #raspberrypi-osdev

← Older revision		Revision as of 18:41, 18 June 2012
Line 40:		Line 40:
	* start irssi and type in: /connect irc.freenode.net		* start irssi and type in: /connect irc.freenode.net
	* then type: /join #raspberrypi-osdev		* then type: /join #raspberrypi-osdev
		+
		+	[[Category:RaspberryPi]]

@@ Line 15: / Line 15: @@
 Once you've gotten the Raspberry Pi to blink a led there's an one very logical next step. First
 thing any kernel should be able to do is to load some programs from the development computer. A working environment will resemble a live coding system, bit similar to SuperCollider. The motivation is that you should be able to have fast compile-test -cycles and removing-reformatting-inserting the SD card all the time causes external and internal wearing on the card.
 == Existing Forums Posts On Assembly Code ==

@@ Line 25: / Line 25: @@
 * http://www.raspberrypi.org/phpBB3/viewtopic.php?f=47&t=3675&p=88593&hilit=assembly
 * http://www.raspberrypi.org/phpBB3/viewtopic.php?f=34&t=5646&p=82415&hilit=assembly
 == IRC Channel ==

@@ Line 15: / Line 15: @@
 Once you've gotten the Raspberry Pi to blink a led there's an one very logical next step. First
 thing any kernel should be able to do is to load some programs from the development computer. A working environment will resemble a live coding system, bit similar to SuperCollider. The motivation is that you should be able to have fast compile-test -cycles and removing-reformatting-inserting the SD card all the time causes external and internal wearing on the card.
 == IRC Channel ==

@@ Line 7: / Line 7: @@
 There's other documentation there all splattered around. Especially the forums seem to have gathered some posts that are worth referencing in the wiki once they're refound.
-The basics for programming a kernel for raspberry pi seem straightforward. You'll fill a fat32 -partition to a memory card. It contains some specific files you can retrieve from /boot -directory in [https://github.com/raspberrypi/firmware].
+The basics for programming a kernel for raspberry pi seem straightforward. You'll fill a fat32 -partition to a memory card. It contains some specific files you can retrieve from /boot -directory in raspberry firmware github repository[https://github.com/raspberrypi/firmware].
 Your kernel goes into kernel.img. The first 16 bytes contain an interrupt vector table and the very first vector is a RESET interrupt, which will boot up the computer. Bootloader might corrupt the first 0x8000 bytes with linux-related attributes if misconfigured. Because of that you might want to add such padding to your kernel as well.

← Older revision		Revision as of 23:22, 7 June 2012
Line 1:		Line 1:
	Raspberry Pi is an opportunity for people to learn OS development on fixed hardware. This makes it easier to make designs that you can share with others. Thereby we have started a community, which communicates through IRC.		Raspberry Pi is an opportunity for people to learn OS development on fixed hardware. This makes it easier to make designs that you can share with others. Thereby we have started a community, which communicates through IRC.
		+
		+	== Hardware Specific Documentation ==
		+
		+	It is bit of essential to know the hardware you're programming. I propose looting the [[RPi Hardware]] -page. From the Components -section you should pick yourself the datasheets of the SoC and CPU Core. Also you might like to look up the quick reference card for ARM instruction set by searching in the internet a bit.
		+
		+	There's other documentation there all splattered around. Especially the forums seem to have gathered some posts that are worth referencing in the wiki once they're refound.
		+
		+	The basics for programming a kernel for raspberry pi seem straightforward. You'll fill a fat32 -partition to a memory card. It contains some specific files you can retrieve from /boot -directory in [https://github.com/raspberrypi/firmware].
		+
		+	Your kernel goes into kernel.img. The first 16 bytes contain an interrupt vector table and the very first vector is a RESET interrupt, which will boot up the computer. Bootloader might corrupt the first 0x8000 bytes with linux-related attributes if misconfigured. Because of that you might want to add such padding to your kernel as well.
		+
		+	== First Steps ==
		+
		+	Once you've gotten the Raspberry Pi to blink a led there's an one very logical next step. First
		+	thing any kernel should be able to do is to load some programs from the development computer. A working environment will resemble a live coding system, bit similar to SuperCollider. The motivation is that you should be able to have fast compile-test -cycles and removing-reformatting-inserting the SD card all the time causes external and internal wearing on the card.

	== IRC Channel ==		== IRC Channel ==