Honored Contributor
Honored Contributorjust use the default name given by spoc_builder.
the kernel building process use hwselect.pl to generate nios2_system.h, which match the ports address.
make arch=nios2nommu o=/usr/local/src/nios2/build/kernel cross_compile=nios2-elf- hwselect stsptf=/usr/local/src/nios2/build/yoursystem.ptf
the system timer should be a default , full featured timer.
you should have a sdram or ddr sdram device to run the program.
you should also have a jtag or uart for console to debug.
it looks like you will write or debug kernel drivers.
it is strongly recommanded that you build the tools chain and develop on linux platform.
<div align='right'><{post_snapback}> (index.php?act=findpost&pid=11653)
--- quote end ---
--- Quote End --- Hi hippo, this may be the way, if you use only Altera components. But I connected as an example the Philips USB controller ISP6111A1 via an user logic interface (over the tristate bus). So the question is now, which name should I give this component. I asked also the Altera support site and got a very good hint, here is the original text: Hi Stefan, The name of component should be not related to kernel recognition. The class of component is the key of kernel to recognize. For example component lan91c111 belongs to class altera_avalon_lan91c111 and it will be translated to enet and the nios2_system.h will contain the statements:# undef na_lan91c111 # undef na_lan91c111 # define na_enet 0x????????# define na_enet_irq ? The sys_clk_timer has the similar situation. The uclinux is ported by Microtronix corporation. You can consult them for more detail information. The website of http://www.microtronix.com (http://www.microtronix.com). Regards, David So it seems, that the class name of the components must fit with required_class_name in the given scripts of folder ..\arch\nios2nommu\scripts\nios2_system.h\ to create the needed defines for using of µCLinux drivers. Additional some script modifications may be neccessary.
