Hello Sean,
As the Tower board Reference Manual states, its FlexBus interface's IOs are shared with (and used by) another interface making using FlexBus impossible:
- "Vybrid’s NAND Flash data pins are shared between its NAND Flash controller and FlexBus interface. However, due to lack of dynamical switching between the two interfaces, they are dedicated to NAND Flash in the TWR-VF65GS10."... "Since the two Vybrid’s interfaces, NAND Flash and FlexBus, share pins, and NAND Flash is used on the TWR-VF65GS10 board, the Flexbus pins are not routed to the Tower Elevator and unavailable for any custom connections."
Of course, these 2 interfaces can coexist if:
- it is not expected that they both operate simultaneously,
- layout is done so that "split" connections on the shared IOs do not act as stubs too long for the frequencies used (i.e. signal integrity is OK) for either interface, which is usually achievable if both NAND Flash and FlexBus peripherals are placed on the board close to each other.
Regarding the sample code - both Vybrid development platforms, Tower and Auto, have the FlexBus IOs used for something else, so it looks like, at least for now, you will have to start using the Kinetis' example. Quite possibly both processors have similar FlexBus block designs (maybe somewhat different register names...).
(timesyssupport, may you comment on the Vybrid FlexBus sample code, please?)
Sincerely, Naoum Gitnik.