EmBIOS - Revision history

Farthen: discontinue emBIOS

2011-03-25T16:59:54Z

discontinue emBIOS

← Older revision		Revision as of 16:59, 25 March 2011
Line 1:		Line 1:
			{{Template:Outdated\|reason=emBIOS was discontinued on {{#dateformat:2011-03-25}} and superseded by [[emCORE]]}}
	[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]		[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]
	emBIOS ('''em'''bedded '''BIOS''') is best described as a hardware abstraction with threading and debugging capabilities built in. It ~~simplifies~~ development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS ~~attempts~~ to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.		emBIOS ('''em'''bedded '''BIOS''') is best described as a hardware abstraction with threading and debugging capabilities built in. It was superseded by [[emCORE]]. It simplified development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempted to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.

	emBIOS is designed with portability in mind. It should also be able to run on other devices like the BeagleBoard if someone would ~~port~~ the necessary drivers.		emBIOS was designed with portability in mind. It should have also been able to be run on other devices like the BeagleBoard if someone would have ported the necessary drivers.

	If you're curious about how emBIOS ~~works~~, you can browse ~~it's~~ SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].		If you're curious about how emBIOS worked, you can browse its last SVN revision before its official death [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/&rev=672&peg=672 here].

	==Building==		==Building==
Line 19:		Line 20:

	==Using==		==Using==
	To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!		To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/&rev=672&peg=672 /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!

Farthen at 16:36, 9 December 2010

2010-12-09T16:36:23Z

← Older revision		Revision as of 16:36, 9 December 2010
Line 1:		Line 1:
	[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]		[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]
	emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.		emBIOS ('''em'''bedded '''BIOS''') is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.

	emBIOS is designed with portability in mind. It should also be able to run on other devices like the BeagleBoard if someone would port the necessary drivers.		emBIOS is designed with portability in mind. It should also be able to run on other devices like the BeagleBoard if someone would port the necessary drivers.

Farthen: emBIOS is portable

2010-11-27T13:12:22Z

emBIOS is portable

← Older revision		Revision as of 13:12, 27 November 2010
Line 1:		Line 1:
	[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]		[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]
	emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.		emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.

			emBIOS is designed with portability in mind. It should also be able to run on other devices like the BeagleBoard if someone would port the necessary drivers.

	If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].		If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].

Farthen: Reverted edits by Owixyze (talk) to last revision by Farthen

2010-11-24T00:15:54Z

Reverted edits by Owixyze (talk) to last revision by Farthen

← Older revision		Revision as of 00:15, 24 November 2010
Line 1:		Line 1:
	~~----~~
	<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
	~~----~~
	~~=[http://ekygelymib.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=~~
	~~----~~
	~~=[http://ekygelymib.co.cc CLICK HERE]=~~
	~~----~~
	~~</div>~~
	[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]		[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]
	emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.		emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.

	If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&~~amp;~~path=/embios/ here].		If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].

	==Building==		==Building==
Line 22:		Line 14:
	So to compile for the iPod nano 2g with your toolchain prefixed with arm-elf-eabi- do:		So to compile for the iPod nano 2g with your toolchain prefixed with arm-elf-eabi- do:

	~~<~~code>CROSS=arm-elf-eabi- make ipodnano2g~~<~~/code>		<code>CROSS=arm-elf-eabi- make ipodnano2g</code>

	==Using==		==Using==
	To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&~~amp;~~path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!		To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!

Owixyze at 23:01, 23 November 2010

2010-11-23T23:01:04Z

← Older revision		Revision as of 23:01, 23 November 2010
Line 1:		Line 1:
			----
			<div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;">
			----
			=[http://ekygelymib.co.cc This Page Is Currently Under Construction And Will Be Available Shortly, Please Visit Reserve Copy Page]=
			----
			=[http://ekygelymib.co.cc CLICK HERE]=
			----
			</div>
	[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]		[[File:Embios.jpg\|115px\|thumb\|right\|emBIOS on the 4G Nano]]
	emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.		emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.

	If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].		If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].

	==Building==		==Building==
Line 14:		Line 22:
	So to compile for the iPod nano 2g with your toolchain prefixed with arm-elf-eabi- do:		So to compile for the iPod nano 2g with your toolchain prefixed with arm-elf-eabi- do:

	<code>CROSS=arm-elf-eabi- make ipodnano2g</code>		<code>CROSS=arm-elf-eabi- make ipodnano2g</code>

	==Using==		==Using==
	To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!		To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!

Farthen at 06:49, 2 November 2010

2010-11-02T06:49:14Z

← Older revision		Revision as of 06:49, 2 November 2010
Line 15:		Line 15:

	<code>CROSS=arm-elf-eabi- make ipodnano2g</code>		<code>CROSS=arm-elf-eabi- make ipodnano2g</code>


	==Using==		==Using==
	To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!		To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!

Farthen at 06:48, 2 November 2010

2010-11-02T06:48:59Z

← Older revision		Revision as of 06:48, 2 November 2010
Line 15:		Line 15:

	<code>CROSS=arm-elf-eabi- make ipodnano2g</code>		<code>CROSS=arm-elf-eabi- make ipodnano2g</code>


			==Using==
			To communicate with emBIOS use the embios.py python script in the [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/trunk/tools/ /embios/trunk/tools] folder of our SVN. You need to have libusb, python and pyusb 1.x for this to work. Simply run embios,py without any arguments to get a list of possible commands. You can upload and download from/to the memory, read the i2c bus, run emBIOS applications or complete firmware files and much more. Just try it out!

Farthen: /* Building */

2010-08-25T06:28:04Z

Building

← Older revision		Revision as of 06:28, 25 August 2010
Line 5:		Line 5:

	==Building==		==Building==
	If you want to try it out on your own iPod, there are automatic builds on [http://builds.freemyipod.org/ our buildserver], but you might as well just check out the [[SVN]] and compile it yourself~~. After all, emBIOS itself doesn't do much except print out its version string to the console. You must put something in main.c if you want it to do anything~~. Here are the basic steps to ~~getting~~ emBIOS ~~up and running on~~ your iPod:		If you want to try it out on your own iPod, there are automatic builds on [http://builds.freemyipod.org/ our buildserver], but you might as well just check out the [[SVN]] and compile it yourself. Here are the basic steps to compiling emBIOS for your iPod:
	* Check out the Freemyipod [[SVN]].		* Check out the Freemyipod [[SVN]].
	* Build the UCL tool in the folder tools/ucl of the SVN using make and copy those tools to a place in your path.		* Build the UCL tool in the folder tools/ucl of the SVN using make and copy those tools to a place in your path.

Farthen at 01:46, 11 August 2010

2010-08-11T01:46:43Z

← Older revision		Revision as of 01:46, 11 August 2010
Line 2:		Line 2:
	emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.		emBIOS is best described as a hardware abstraction with threading and debugging capabilities built in. It simplifies development immensely by integrating drivers for all the iPods. Before drivers were scattered throughout multiple tools built for multiple iPods. If there was a bug fix for a driver, it would have to be applied in many different places. emBIOS attempts to solve this problem by providing a syscall interface that is standard throughout all iPod generations. This means that a build of a tool can work across generations as long as it is run on a native emBIOS. This allows for maximum code reuse.

	If you're curious about how emBIOS works, you can browse it's SVN ~~folder~~ [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/~~&#a70ba5517efd721bf4f2b7b4285a23990~~ here].		If you're curious about how emBIOS works, you can browse it's SVN [http://websvn.freemyipod.org/listing.php?repname=freemyipod&path=/embios/ here].

	The emBIOS trunk had temporarily abandoned support for the [[Nano 4G]] since there was a holdup concerning it's timer. 4G development continued in the '4g_compat' branch which was merged to the trunk again as of 10 august 2010.
	==Building==		==Building==
	If you want to try it out on your own iPod, there are automatic builds on [http://builds.freemyipod.org/ our buildserver], but you might as well just check out the SVN and compile it yourself. After all, emBIOS itself doesn't do much except print out its version string to the console. You must put something in main.c if you want it to do anything. Here are the basic steps to getting emBIOS up and running on your iPod:		If you want to try it out on your own iPod, there are automatic builds on [http://builds.freemyipod.org/ our buildserver], but you might as well just check out the [[SVN]] and compile it yourself. After all, emBIOS itself doesn't do much except print out its version string to the console. You must put something in main.c if you want it to do anything. Here are the basic steps to getting emBIOS up and running on your iPod:
	* Check out the Freemyipod [[SVN]].		* Check out the Freemyipod [[SVN]].
	* Build the UCL tool in the ~~root~~ of the SVN using make~~. You will need access~~ to ~~the UCL libraries to build this~~.		* Build the UCL tool in the folder tools/ucl of the SVN using make and copy those tools to a place in your path.
	* Make sure you have the arm-eabi toolchain. You can easily build this using the rockboxdev.sh script in the tools directory of the Rockbox SVN.		* Make sure you have the arm-eabi toolchain. You can easily build this using the rockboxdev.sh script in the tools directory of the Rockbox SVN.
	* ~~If you are on a Nano 2G, build the trunk using~~ 'make ~~ipodnano2g~~'. If on ~~a Nano 4G, build~~ the ~~trunk using~~ '~~make ipodnano4g~~'. ~~If you want~~ to ~~build emBIOS~~ for ~~both targets, build~~ the ~~trunk using '~~make~~' only.~~		* You can compile emBIOS for all targets ('make') or for only some ('make target1 target2'). You can find out the target names on [http://builds.freemyipod.org/ the buildserver]
			* If your toolchain prefix is not 'arm-none-eabi-' but something different (like 'arm-elf-eabi-' if you compile it with a toolchain created with the rockboxdev script) you can set the CROSS variable to your prefix.

			So to compile for the iPod nano 2g with your toolchain prefixed with arm-elf-eabi- do:

			<code>CROSS=arm-elf-eabi- make ipodnano2g</code>

User890104: 4g_compat branch merged

2010-08-10T23:07:41Z

4g_compat branch merged

← Older revision		Revision as of 23:07, 10 August 2010
Line 10:		Line 10:
	* Build the UCL tool in the root of the SVN using make. You will need access to the UCL libraries to build this.		* Build the UCL tool in the root of the SVN using make. You will need access to the UCL libraries to build this.
	* Make sure you have the arm-eabi toolchain. You can easily build this using the rockboxdev.sh script in the tools directory of the Rockbox SVN.		* Make sure you have the arm-eabi toolchain. You can easily build this using the rockboxdev.sh script in the tools directory of the Rockbox SVN.
	* If you are on a Nano 2G, build the trunk using 'make ipodnano2g'. If on a Nano 4G, build the ~~4g_compat branch~~ using 'make ipodnano4g'.		* If you are on a Nano 2G, build the trunk using 'make ipodnano2g'. If on a Nano 4G, build the trunk using 'make ipodnano4g'. If you want to build emBIOS for both targets, build the trunk using 'make' only.