industrialNETworX

Hi HP,

in the Version 2.0 are some new functionalities included. So it would be possible for you tu "upgrade" your project.

:idea: But I would please you to wait a little bit, before you start. There will be a newer version available, soon. In the next version it would be possible to set a priority for the receive frames. Maybe it is interesting for you.

The priority setting being available in the new example is not the CAN bus priority. (low ID = high priority).

You will be able to differentiate two indication priority levels. (2 different IRQ sources). In the standard way each frame is indicated by a low priory indication interrupt. You can now select any combination of the 2048 Standard RX Identifiers to be indicated by a high priority indication interrupt. When using 29 Bit identifiers you will have 8 registers to filter frames for high priority indications.

This priority settings is useful for example for the sync frame which will then be inserted into a high priority reception FIFO and indicated by a seperate IRQ. This offers better reaction times to such frames.

Hope this clears up the priorization possibilities.

When it's done. :wink:

Ok. The Demo is finished and will be tested on the boards it was designed for.

In parallel the documentation is updated.

I think you can expect it the next few days. If any of the tests fail, it might get a little delayed though. So don't hang me, if a delay occurs
8)

Hy,

good news. The new version (V2.100) is now available.

Please follow this link to download this version.

The update includes the following changes:

I finally got to update the CAN version (talking about delays :roll: )

Well, now I have a problem with my interrupt service routine. It is never executed. The Xc is running, I can send CAN-Messages using it, message I send to netX using another CAN-Device are acknowledged, just the ISR is never entered. That means I can't receive messages of course. I do the following to initialize the ISR:

  strcpy(tIntCan.tCfgHd.szIdn,c16IrqName);
  tIntCan.tCfgHd.eTyp = RX_PERIPHERAL_TYPE_INTERRUPT;
  tIntCan.tCfgHd.uInst = ucCanChannelNo;
  tIntCan.uIntNum = uiIrqNumber;
  tIntCan.uPrio = uiIrqPrio;
  tIntCan.eMod = RX_INTERRUPT_MODE_TASK;
  tIntCan.eEoi = RX_INTERRUPT_EOI_AUTO;
  tIntCan.eTrig = RX_INTERRUPT_TRIGGER_RISING_EDGE;
  tIntCan.ePrio = RX_INTERRUPT_PRIORITY_STANDARD;
  tIntCan.eRntr = RX_INTERRUPT_REENTRANCY_DISABLED;


  //Interrupt initialisieren

  if (rX_MemAllocateMemory(&hIntCan,DRV_INTERRUPT_SIZE) != RX_OK) // Get memory 

    Error(ERROR_IF_4);

  // Create the Interrupt Object now 

  if (Drv_IntCreateInterrupt(hIntCan, &tIntCan) != RX_OK)

    Error(ERROR_IF_4);    

  if (Drv_IntInitializeInterrupt(hIntCan,fnIrqXpecCan,(void*)&sCanXcSettings) != RX_OK)

    Error(ERROR_IF_4);  

  // Confirm the interrupt sources

  Drv_XcSetInterrupt(hXpecCan,~MSK_CAN_INTERRUPTS_ENABLE_RES1);

  // Enable the Interrupt

  if (Drv_IntEnableInterrupt(hIntCan) != RX_OK)

    Error(ERROR_IF_4);

The only thing i changed compared to the previous version is the mask used with Drv_XcSetInterrupt. In the earlier version I used ~MSK_CONTROL_RES1, now I'm using ~MSK_CAN_INTERRUPTS_ENABLE_RES1 which encompasses the new interrupt sources as well. Any ideas what I might have to change?

Hi HP,

The following line was used to reset all pending Interrupts on the Interrupt controller of the XC.

 // Confirm the interrupt sources
 Drv_XcSetInterrupt(hXpecCan,~MSK_CAN_INTERRUPTS_ENABLE_RES1); 

The upper 16 Bits are ARM to XC and must be cleared from XC. The lower 16Bits are XC to ARM and must be cleared from ARM side.

So Make sure your are only writing the lower 16 Bits. to perform an EOI on this IRQ controller.

Also make sure to enable the MSYNC Irq from the corresponding XC, as the high priority indications (receptions) are signalled via this IRQ line.

The lowest 12 bits of the IRQ status register must be handled by the COM ISR and the next 4 Bits must be handled in the MSYNC ISR, as it was done in the code provided in the zip package.

Regards

MT

Any additional info on this behaviour?

Hey MT

I tried replacing my used mask with 0x0000FFFF. That doesnt change anything. The listening-only mode that is mentioned in that other topic can't be the problem, because I can send messages using this interface. However, even when sending the ISR is not executed.

I'm not using your project, because I'm working on my own target, and the inputs/outputs might not be compatible. I more or less did the same changes I did when porting the original CAN HAL to rcX. I can send you my project if you want, so you can verify what I did. As I mentioned before, I didnt implement the higher/lower prio frames, nor did I turn on the MMU-Cache, so it should actually be working like it did with the originally ported version.

Hey AJ

After doublechecking our hardware....again....we actually found the error: a ground-net label had a typo in it and thus the pin of a device was not actually connected to ground :oops:

Now everything works fine :wink: