mirror of https://github.com/rusefi/openblt.git
Refs #1524. Place the CAN peripheral back into its reset state, before initializing, for XMC1 and XMC4 targets.
git-svn-id: https://svn.code.sf.net/p/openblt/code/trunk@958 5dc33758-31d5-4daf-9ae8-b24bf3d40d73
This commit is contained in:
parent
c71a3e1995
commit
7d2180342b
|
@ -266,6 +266,12 @@ static void BootComCanInit(void)
|
|||
XMC_CAN_NODE_NOMINAL_BIT_TIME_CONFIG_t baud;
|
||||
unsigned long receiveId;
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
* 16 message objects. This is sufficient for this CAN driver.
|
||||
|
|
|
@ -266,6 +266,12 @@ static void BootComCanInit(void)
|
|||
XMC_CAN_NODE_NOMINAL_BIT_TIME_CONFIG_t baud;
|
||||
unsigned long receiveId;
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
* 16 message objects. This is sufficient for this CAN driver.
|
||||
|
|
|
@ -266,6 +266,12 @@ static void BootComCanInit(void)
|
|||
XMC_CAN_NODE_NOMINAL_BIT_TIME_CONFIG_t baud;
|
||||
unsigned long receiveId;
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
* 16 message objects. This is sufficient for this CAN driver.
|
||||
|
|
|
@ -270,6 +270,12 @@ static void BootComCanInit(void)
|
|||
XMC_CAN_NODE_NOMINAL_BIT_TIME_CONFIG_t baud;
|
||||
unsigned long receiveId;
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
* 16 message objects. This is sufficient for this CAN driver.
|
||||
|
|
|
@ -270,6 +270,12 @@ static void BootComCanInit(void)
|
|||
XMC_CAN_NODE_NOMINAL_BIT_TIME_CONFIG_t baud;
|
||||
unsigned long receiveId;
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
* 16 message objects. This is sufficient for this CAN driver.
|
||||
|
|
|
@ -270,6 +270,12 @@ static void BootComCanInit(void)
|
|||
XMC_CAN_NODE_NOMINAL_BIT_TIME_CONFIG_t baud;
|
||||
unsigned long receiveId;
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
* 16 message objects. This is sufficient for this CAN driver.
|
||||
|
|
|
@ -101,6 +101,11 @@ void CanInit(void)
|
|||
* in case a different CAN channel is configured.
|
||||
*/
|
||||
ASSERT_CT((BOOT_COM_CAN_CHANNEL_INDEX >= 0) && (BOOT_COM_CAN_CHANNEL_INDEX <= 1));
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
|
|
|
@ -111,6 +111,12 @@ void CanInit(void)
|
|||
#else
|
||||
ASSERT_CT((BOOT_COM_CAN_CHANNEL_INDEX >= 0) && (BOOT_COM_CAN_CHANNEL_INDEX <= 2));
|
||||
#endif
|
||||
|
||||
/* set the CAN peripheral into the disabled state. the call to XMC_CAN_Init
|
||||
* below enables it again, which consequently brings the peripheral back into
|
||||
* its reset state.
|
||||
*/
|
||||
XMC_CAN_Disable(CAN);
|
||||
|
||||
/* decide on fCAN frequency. it should be in the 5-120MHz range. according to the
|
||||
* datasheet, it must be at least 12MHz if 1 node (channel) is used with up to
|
||||
|
|
Loading…
Reference in New Issue