Re: [Xenomai-core] NIOS2/Xenomai 2.5.6/Native Skin
'timer' device. I am planing * to deviate the Linux timer interrupt from our 'timer' source, by using a virtual IRQ line, to a) phase align it to other events in the schedule b) make the timer available to Xenomai, and * to implement a read-tsc function and use a spare timer for Xenomai. My Questions: * Are there any implications to Xenomai-services, aside from timed events (i.e. sleep, alarms, timeout functions, ...) which need to be regarded when working on the time source? * Is there any hardware dependent code in Xenomai that relies on the current timer (hrclock, hrtimer) implementation? I.e. can all modifications inside the ADEOS code? I have only identified only ADEOS code so far. Yes, I think that all the hardware dependent code is in the adeos patch. In the adeos patch for NIOS 2 without MMU, you must instantiate with Altera SoPC builder tool a 32-bit timer named hrtimer for clock event and a 64-bit timer named hrclock for clock source. Link between HW and SW is done by the name. Cheers; Patrice thx best regards Martin PS: This discussion should rather happen on xenomai-help or -core, at your will. Maybe those explanations could be of some interest to others. Best regards Martin Elshuber ___ Message sent via/by Gna! http://gna.org/ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core -- Patrice Kadionik. F6KQH / F4CUQ --- +--+ +Tout doit etre aussi simple que possible, pas seulement plus simple + +--+ + Patrice Kadionikhttp://www.enseirb-matmeca.fr/~kadionik + + IMS Laboratoryhttp://www.ims-bordeaux.fr/ + + ENSEIRB-MATMECAhttp://www.enseirb-matmeca.fr+ + PO BOX 99fax : +33 5.56.37.20.23 + + 33402 TALENCE Cedex voice : +33 5.56.84.23.47 + + FRANCEmailto:patrice.kadio...@ims-bordeaux.fr + +--+ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Build tests: analogy, blackfin, rtcan and nios2.
Hi Gilles, Gilles Chanteperdrix a écrit : Hi, Since I started talking about it, I have run build tests fixing a few things here and there. The current status is this (still at the same place: http://sisyphus.hd.free.fr/~gilles/bx): * analogy: I have tried to disable some parts of analogy when compiling on machines without CONFIG_PCI, as compiling parts using PCI on a machine without PCI support, give various levels of warning and even errors depending on the architecture. Doing this, I stumbled across this compilation error: http://sisyphus.hd.free.fr/~gilles/bx/beagle/2.6.28-arm-none-linux-gnueabi-gcc-4.3.3/log.html#1 this is with CONFIG_NI_MIO, but without CONFIG_NI_MITE. So, Alex, could you: - fix that error, if this combination is supposed to make sense - fix the Kconfig/Makefile so that no PCI code is compiled if CONFIG_PCI is not set (I tried and do this myself, but better one who knows than 100 who have to search...). As I said, doing this result in various levels of success depending on the architecture. * blackfin: I finally compiled blackfin! had to build a toolchain for that as the binary-only toolchain from analog.com uses glibc 2.8 and mine is 2.7. However, blackfin does not compile very well, as can be seen by the log: http://sisyphus.hd.free.fr/~gilles/bx/bf537-stamp/2.6.30-bfin-uclinux-gcc-4.1.2/log.html#1 It may happen that my toolchain is buggy or outdated though. * rtcan: on blackfin we seem to have a conflict with rtcan. The warning is about CAN_ERR_MASK, sure blackfin is a bit strange to define this in core headers which are included everywhere. This said, not prefixing a Xenomai symbol with something like XN seems to be asking for trouble. Wolfgang, do you think it would be possible to rename the symbols with such prefix? Or do you share some code with socket-can that you do not want to touch? * nios2: I am lacking some important file needed to even start to compile. You may use this tutorial on how to use Xenomai on NIOS 2 softcore processor: http://uuu.enseirb.fr/~kadionik/nios-xenomai/Xenomai%20on%20NIOS%20II%20Softcore%20Processor.%20A%20step%20by%20step%20Guide.pdf Regards, Pat. Thanks in advance for your efforts. Regards. -- Patrice Kadionik. F6KQH / F4CUQ --- +--+ +Tout doit etre aussi simple que possible, pas seulement plus simple + +--+ + Patrice Kadionik http://www.enseirb.fr/~kadionik + + IMS Laboratory http://www.ims-bordeaux.fr/ + + ENSEIRB http://www.enseirb.fr + + PO BOX 99fax : +33 5.56.37.20.23 + + 33402 TALENCE Cedex voice : +33 5.56.84.23.47 + + FRANCE mailto:patrice.kadio...@ims-bordeaux.fr + +--+ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
Re: [Xenomai-core] Build tests: analogy, blackfin, rtcan and nios2.
Gilles Chanteperdrix a écrit : Hi, Since I started talking about it, I have run build tests fixing a few things here and there. The current status is this (still at the same place: http://sisyphus.hd.free.fr/~gilles/bx): Hi, I've watched your log file for nios2 (http://sisyphus.hd.free.fr/~gilles/bx/nios2/2.6.30-nios2-linux-uclibc-gcc-3.4.6/log.html#1). You have this error because you don't have generated before the HW design for the NIOS softcore processor: after synthesis with the Quartus Altera tools, you finally have a file for programming the FPGA circuit and a .ptf file that gives ASCII informations on your SoPC design (in a xml style...). The error: ./arch/nios2/Makefile:131: *** Run make hwselect SYSPTF=system.ptf first. Stop. is due to lack of this .ptf file. This command generates a .h (nios2.h) file that makes relation between hardware and the Linux kernel (peripheral base address, irq number, peripheral name...) Please find here: http://uuu.enseirb.fr/~kadionik/nios-xenomai/std_1s10.ptf a valid .ptf file for Xenomai port. Juste run : $ make hwselect SYSPTF=path_to_std_1s10.ptf for completing the kernel compilation... Pat. * analogy: I have tried to disable some parts of analogy when compiling on machines without CONFIG_PCI, as compiling parts using PCI on a machine without PCI support, give various levels of warning and even errors depending on the architecture. Doing this, I stumbled across this compilation error: http://sisyphus.hd.free.fr/~gilles/bx/beagle/2.6.28-arm-none-linux-gnueabi-gcc-4.3.3/log.html#1 this is with CONFIG_NI_MIO, but without CONFIG_NI_MITE. So, Alex, could you: - fix that error, if this combination is supposed to make sense - fix the Kconfig/Makefile so that no PCI code is compiled if CONFIG_PCI is not set (I tried and do this myself, but better one who knows than 100 who have to search...). As I said, doing this result in various levels of success depending on the architecture. * blackfin: I finally compiled blackfin! had to build a toolchain for that as the binary-only toolchain from analog.com uses glibc 2.8 and mine is 2.7. However, blackfin does not compile very well, as can be seen by the log: http://sisyphus.hd.free.fr/~gilles/bx/bf537-stamp/2.6.30-bfin-uclinux-gcc-4.1.2/log.html#1 It may happen that my toolchain is buggy or outdated though. * rtcan: on blackfin we seem to have a conflict with rtcan. The warning is about CAN_ERR_MASK, sure blackfin is a bit strange to define this in core headers which are included everywhere. This said, not prefixing a Xenomai symbol with something like XN seems to be asking for trouble. Wolfgang, do you think it would be possible to rename the symbols with such prefix? Or do you share some code with socket-can that you do not want to touch? * nios2: I am lacking some important file needed to even start to compile. Thanks in advance for your efforts. Regards. -- Patrice Kadionik. F6KQH / F4CUQ --- +--+ +Tout doit etre aussi simple que possible, pas seulement plus simple + +--+ + Patrice Kadionik http://www.enseirb.fr/~kadionik + + IMS Laboratory http://www.ims-bordeaux.fr/ + + ENSEIRB http://www.enseirb.fr + + PO BOX 99fax : +33 5.56.37.20.23 + + 33402 TALENCE Cedex voice : +33 5.56.84.23.47 + + FRANCE mailto:patrice.kadio...@ims-bordeaux.fr + +--+ ___ Xenomai-core mailing list Xenomai-core@gna.org https://mail.gna.org/listinfo/xenomai-core
