In the past Ive used tokenizer version 2.3 for SBus FCODE development – is it OK to use that same tokenizer for PCI FCode PROM development, or do I need new tokenizer?
Tokenizer Version 2.3 will work, but if you need to write 1275 source compatible FCode for PCI, you’ll need version 3.1 or later. Also, for pre 3.1 versions of tokenizer, you’ll need to use some utility to add the PCI header. Use the Tokenizer (version 3.1) from this site’s Tools page. See /opt/SUNWddk/ddk_3.1/tokenizer/README. 26. I am writing FCode for a bootable device. It appears to me that there are 3 kinds of software that come into play during a boot: kernel, FCode and OS-driver. Can someone briefly explain what each does and the order in which they kick in? At power-on the CPU PROM begins execution. It probes all on-board devices and plug-in cards and thus interprets the code in all FCode PROMs. During the FCode probing process, some FCode PROMs will execute some commands like resetting the device, and so on. But generally, FCode PROMs will generate device properties for their respective devices. When the actual boot begins, the CPU PROM boots over the specified boot-device (an
Related Questions
- What version of Microsoft Office is used in the accessible instructional materials professional development by the San Jose State Universitys Center for Faculty Development?
- In the past I have used Salesmatrix on my desktop computer in the office and also on my laptop. Can I do this with version 4?
- Which version of the Xilinx back-end tools can be used to compile circuits for the PCI Pamette board?
