search

PaxInstruments / PaxInstruments-LabWiz-firmware

Firmware for the Pax Instruments LabWiz board.
0 stars 1 forks source link

CAN conflict? #5

Closed charlespax closed 8 years ago

charlespax commented 8 years ago

Drew noticed a possible issue with the CAN interrupt. In file stm32f103xg.h lines 120 through 123 reference the CAN interrupts. The language sounds like there may be some conflict.

120  USB_HP_CAN1_TX_IRQn         = 19,     /*!< USB Device High Priority or CAN1 TX Interrupts       */
121  USB_LP_CAN1_RX0_IRQn        = 20,     /*!< USB Device Low Priority or CAN1 RX0 Interrupts       */
122  CAN1_RX1_IRQn               = 21,     /*!< CAN1 RX1 Interrupt                                   */
123  CAN1_SCE_IRQn               = 22,     /*!< CAN1 SCE Interrupt

Line 143

  USBWakeUp_IRQn              = 42,     /*!< USB Device WakeUp from suspend through EXTI Line Interrupt */
charlespax commented 8 years ago

Someone on this post states,

RM0008 page 629 In low, medium-, high- and XL-density devices the USB and CAN share a dedicated 512-byte SRAM memory for data transmission and reception, and so they cannot be usedconcurrently (the shared SRAM is accessed through CAN and USB exclusively). The USBand CAN can be used in the same application but not at the same time.

charlespax commented 8 years ago

CAN is no longer on the module header. To interface with can devices a CAN interface chip would be needed on the module. Closing issue.