SOPC builder module names for a µCLinuy system

[Altera_Forum]

Hi guys, 

 I'm creating an CycloneII system with the SOPC builder, on which later µCLinux must run.  The system contains:  - system clock timer - timer for free use - i2c master port (opencore) - i2s master tx and rx ports (opencore) - ethernet interface to SMSC 91C111 - interface to USB controller ISP1161A1 - CFI flash memory - video controller (frame buffer) - pio ports.  As I've seen in the µCLinux kernel configuration tool in the NIOS IDE, the kernel brings support for the most of these components. So my question is, do I have to use special module names in the SOPC builder? As example for the system timer "sys_clk_timer"? Are there name definitions given in the kernel, which I must use to let the code recognize these modules? If yes, where can I find these definitions?  Thanks in advance

[Altera_Forum]

You don't have to use special name for the devices. 

Just 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.

[Altera_Forum]

--- Quote Start ---  originally posted by hippo@Dec 19 2005, 08:01 PM you don&#39;t have to use special name for the devices. just 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.