Roadmap: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
Line 9: | Line 9: | ||
* Find out what the testpads on the Barracuda PCB do - Identifying [[JTAG]] and [[UART]] would be really helpful here. | * Find out what the testpads on the Barracuda PCB do - Identifying [[JTAG]] and [[UART]] would be really helpful here. | ||
* Get a [[linux]] (console) shell to work on the current firmware to be able to get info about how the official software connects to the hardware. Memory maps, device drivers, | * Get a [[linux]] (console) shell to work on the current firmware to be able to get info about how the official software connects to the hardware. Memory maps, device drivers, etc | ||
* Figure out which pieces are missing to drive the hardware - Does Reciva provide drivers to all hardware ? Is a bootloader provided ? | * Figure out which pieces are missing to drive the hardware - Does Reciva provide drivers to all hardware ? Is a bootloader provided ? |
Revision as of 13:39, 25 October 2006
Roadmap
This list describes the things that would be needed to create a platform on which an alternative firmware implementation could be provided, roughly in the right order.
- Creating an inventory of the components on the Barracuda board and their functions, and gathering technical information about these componentes where available.
- Find out what the testpads on the Barracuda PCB do - Identifying JTAG and UART would be really helpful here.
- Get a linux (console) shell to work on the current firmware to be able to get info about how the official software connects to the hardware. Memory maps, device drivers, etc
- Figure out which pieces are missing to drive the hardware - Does Reciva provide drivers to all hardware ? Is a bootloader provided ?
- Try to put as much pieces of the provided GPL code together to get a basic OS up and running. Find out how much Reciva added or modified of the original software packages.
~