Sign in
Search lpc2000
Subscribe to lpc2000
lpc2000 by Keywords
2106 | ADC | ARM7 | Atmel | Bootloader | CAN | CrossStudio | CrossWorks | DDS | ECos | Ethernet | ETM | FIFO | FLASH | FPGA | GCC | GDB | GNU | GNUARM | GPIO | I2C | IAP | IAR | JTAG | Kickstart | LCD | Linux | LPC | LPC-E2294 | LPC2000 | LPC2100 | LPC2104 | Lpc2106 | Lpc210x | LPC2114 | LPC2119 | LPC2124 | LPC2129 | Lpc2138 | LPC213x | LPC21xx | LPC2210 | LPC2212 | LPC2214 | LPC2292 | LPC2294 | LPC2xxx | LPC3128 | MCB2100 | Olimex | Philips | PWM | Rowley | RTC | RTOS | SPI | SSP | UART | UART0 | UART1 | ULINK | USB | Watchdog | Wiggler
Ads
Discussion Groups
Discussion Groups | LPC2000 | Re: lpc2368 - CAN2 on port pins 2.7 - 2.8
Discussion group dedicated to the Philips LPC2000 family of ARM MCUs
lpc2368 - CAN2 on port pins 2.7 - 2.8 - ben_fnr - Mar 26 12:54:53 2008
hi am trying to get the second CAN module in the 2368 working with no
luck. Have managed to get the first CAN module running ok though.
Is anyone using the second CAN module, particularly on port pins 2.7 & 2.8
I am currently enabling the peripheral in PCONP, setting the correct
bits in PINSEL4, clearing all the bits in PINSEL10 so the TRACE pins
are disabled and configuring both CAN modules in the same way. I cant
find any other references to the CAN module, so I think I have set all
the relevant bits.
The acceptance filter is in bypass mode.
Before trying to send a message I wait for the status bit for the
transmit buffer to become unlocked and then setup the data bytes and
kick of the transmit.
When using the second CAN module and with nothing connected to the CAN
bus to acknowledge messages I would expect the transmit function to
send one message and then wait forever. This is what happens for the
first CAN module, but not for the CAN second module. I can clearly see
CAN from the first CAN module but not the second.
Perhaps I will mod my PCB and try swapping the second CAN module over
to P0.4 & P0.5 and see if it works then.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
luck. Have managed to get the first CAN module running ok though.
Is anyone using the second CAN module, particularly on port pins 2.7 & 2.8
I am currently enabling the peripheral in PCONP, setting the correct
bits in PINSEL4, clearing all the bits in PINSEL10 so the TRACE pins
are disabled and configuring both CAN modules in the same way. I cant
find any other references to the CAN module, so I think I have set all
the relevant bits.
The acceptance filter is in bypass mode.
Before trying to send a message I wait for the status bit for the
transmit buffer to become unlocked and then setup the data bytes and
kick of the transmit.
When using the second CAN module and with nothing connected to the CAN
bus to acknowledge messages I would expect the transmit function to
send one message and then wait forever. This is what happens for the
first CAN module, but not for the CAN second module. I can clearly see
CAN from the first CAN module but not the second.
Perhaps I will mod my PCB and try swapping the second CAN module over
to P0.4 & P0.5 and see if it works then.
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
Re: lpc2368 - CAN2 on port pins 2.7 - 2.8 - Dezheng Tang - Mar 27 14:15:37 2008
P2.7~8 for CAN2 are shared with ETM. Can you check the
setting of PINSEL10 register?
Tom
--- In l...@yahoogroups.com, "ben_fnr" wrote:
>
> hi am trying to get the second CAN module in the 2368 working with no
> luck. Have managed to get the first CAN module running ok though.
>
> Is anyone using the second CAN module, particularly on port pins 2.7
& 2.8
>
> I am currently enabling the peripheral in PCONP, setting the correct
> bits in PINSEL4, clearing all the bits in PINSEL10 so the TRACE pins
> are disabled and configuring both CAN modules in the same way. I cant
> find any other references to the CAN module, so I think I have set all
> the relevant bits.
>
> The acceptance filter is in bypass mode.
>
> Before trying to send a message I wait for the status bit for the
> transmit buffer to become unlocked and then setup the data bytes and
> kick of the transmit.
>
> When using the second CAN module and with nothing connected to the CAN
> bus to acknowledge messages I would expect the transmit function to
> send one message and then wait forever. This is what happens for the
> first CAN module, but not for the CAN second module. I can clearly see
> CAN from the first CAN module but not the second.
>
> Perhaps I will mod my PCB and try swapping the second CAN module over
> to P0.4 & P0.5 and see if it works then.
>
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )
setting of PINSEL10 register?
Tom
--- In l...@yahoogroups.com, "ben_fnr"
>
> hi am trying to get the second CAN module in the 2368 working with no
> luck. Have managed to get the first CAN module running ok though.
>
> Is anyone using the second CAN module, particularly on port pins 2.7
& 2.8
>
> I am currently enabling the peripheral in PCONP, setting the correct
> bits in PINSEL4, clearing all the bits in PINSEL10 so the TRACE pins
> are disabled and configuring both CAN modules in the same way. I cant
> find any other references to the CAN module, so I think I have set all
> the relevant bits.
>
> The acceptance filter is in bypass mode.
>
> Before trying to send a message I wait for the status bit for the
> transmit buffer to become unlocked and then setup the data bytes and
> kick of the transmit.
>
> When using the second CAN module and with nothing connected to the CAN
> bus to acknowledge messages I would expect the transmit function to
> send one message and then wait forever. This is what happens for the
> first CAN module, but not for the CAN second module. I can clearly see
> CAN from the first CAN module but not the second.
>
> Perhaps I will mod my PCB and try swapping the second CAN module over
> to P0.4 & P0.5 and see if it works then.
>
------------------------------------
(You need to be a member of lpc2000 -- send a blank email to lpc2000-subscribe@yahoogroups.com )