ERIKA Enterprise Forums

I tried the code you sent me, with EE 1.4.3. I just used the Multibus RT-Druid template, the one called \"Serial demo\", when I just replaced the code.c with the one you attached and I adapted the conf.oil to use the demodoard. On the pc-side I used the HyperTerminal (note that I already knew that t...

Hello. before replying your question I need some extra information. What version of Erika are you currently using? The example application you are talking about, is that in pic30-> Flex MultiBus Board->Serial Demo ? In this case, are you using the MultiBus board or the bare flex board? Regards, Chri...

Well, the system reboot is typically due to a bad usage of the micro-controller core (the CPU) or an hardware failure and it absolutely does NOT dependent on the real-time issues like deadline miss. The other causes you mentioned are reasonable. To be more specifically you can refer to the dsPIC ref...

No way to do this with the dsPIC.
I think you should convert the output voltage from 3.3 to 5 on your own.
Look for a voltage converter on the web.
Regards.

The answer is yes. Erika shall not catch any kind of interrupts at all, unless you want erika to do it. Be aware that with this solution you will not use properly the erika kernel, since the erika interrupt handling has been done to have coherency in the task scheduling mechanism. To tell the kernel...

It\'s easy. As you said you have to specify the heap using the C30 option --heap= and this can me done in the .oil adding the LDFLAGS attribute as described below. CPU mySystem { OS myOs { EE_OPT = \"DEBUG\"; CFLAGS = \"\"; LDFLAGS = \"--heap=1024\" }; }; This should help you. Regards, Chris.

Ok, the right way for this is to move your library in the contrib directory of the in the erika installation directory (typically is something link c:\\Evidence\\Evidence\\ee\\contrib ). You should create a new directory in contib with your library according to the make rules adopted by erika. Look ...

Ok, it\'s easy. The primitive you need is ActivateTask(task_id); Here I post the documentation extracted from the Erika Enterprise RefMan. 2.6.1 ActivateTask Synopsis StatusType ActivateTask(TaskType TaskID); Description This primitive activates a task TaskID, putting it in the READY state, or in th...

Sorry, that was because I extracted that code from an old project of mine. The lines that are required for the pwmOC.h are just the following: typedef enum { FCY_2_MHz=2, FCY_40_MHz=40 } fcy_MHz; Anyhow I suggest you to have a look at the pwm interfaces that are well-suited for DC motors driving. He...

Hi! First of all you have to know that the PWM used in the demo-board works via the output compare interface. This is good if you want to drive a servomotor, otherwise you should use the PWM interface of the dsPIC on your own. The code with the API for the PWM with the demo-board should be in ERIKA_...

Ok, don\'t worry for the driver. Use your own version and ...

in bocca al lupo per la tua tesi!

;)

As far as I understood from the last code that you posted you are explicitly using the NACK after the first transmission. What you want, and what you should need, is the following transmission: select_device -> ack_from_device -> read_msb -> ACK -> read_lsb -> NACK. But looking at the code you send ...

Ok, as I said before, if the code works (and it seems that should do) that is fine, but just for testing I dare say. I mean that this is good to be sure that the peripheral you want to communicate with is working properly, but just this! I strongly discourage you to use that code for general purpose...

Uhm... :unsure: I cannot download your code, it seems that it has not been properly uploaded on the server. Anyhow, if you say that it\'s now working that\'s fine ;) , but I suggest to investigate which could be the error. I think it would be better to use the I2C interface instead of doing it by ha...

The code seems to be ok, but there\'s a problem I think in the following statement: I2C2CONbits.ACKDT = 0; //set ACKDT bit to send ACK because the value should be 1 instead of 0. This is due, I think, to the behaviour of the master during the reading phase as described in the detailed Microchip refe...