Roadmap
-
The BlackFin 54x (and 52x) have an on-board NAND Flash Controller (NFC). The 54x can boot from NAND Flash. The RadioShark547 will have no NOR flash, only NAND flash. So, we will need two NAND flash ports:
- current eCos has no NAND flash driver
- u-boot must be made aware of the RadioShark547
On nov 28, we did an Alpha release for both packages to the eCos mailing lists
-
The board samples will arrive at Bert's at about dec 15, 2008. They will be due here some days later, untested. I guess I need a few weeks to port U-Boot, and that's not at all pessimistic. Christmas and 'Kareltje' will interfere.
The BFin CPU board (RadioShark) differs from the BFin BF548 EZ-Kit board:
- it has no NOR flash, so boot loader, environment etc must be in NAND
- it has different Ethernet:
- on RFC40, an ne2000 which is in u-boot but looks unused
- on Triton Dev Kit: an SMC18xxx (or whatever) but 16-bit
These differences don't matter:
- it may have different NAND Flash, but the interface is the same
- it has different SDRAM, but with the same config
- it has a BF547 i.s.o. BF548, but that has no consequences
-
Milestone: JTAG support for RFB40
14 months late (01/21/09)
RFB40 will need JTAG support. Two dev-boards that will contain RFB40:
- Triton DevBoard
- RFC40
Both will have a JTAG connector, and connect to the JTAG chain on RFB40 through the 200-DIMM connector.
Triton DevBoard is phased out now we have RFC40.
Steps:
- adapt uCLinux jtag; BF547 is the only component on the chain
- (adapt uCLinux jtag to understand the components and the chain on Triton DevBoard)
-
The eCos port must mimic the U-Boot port.
There already is a BF54x variant with GPIO, interrupt, etc.
The AFE and FPGA will require much work. There is no implementation yet for I2C/I2S/SPI, for the display, for the touchscreen, etc. USB is yet another chapter - not in this milestone.
-
-
Since we target our efforts at a BlackFin, XScale-specific software has moved to the second rank.
-
-
* select a VM * get the VM to run on the BlackFin * support/emulate MIDP so we can run the org.rfidguardian.ME package * adapt org.rfidguardian so it runs sensibly on the RFID Guardian
