SAM9263 Atmel Corporation, SAM9263 Datasheet - Page 1061

• Manufacturer Part Number: SAM9263
• Manufacturer: Atmel Corporation

Specifications of SAM9263

• Flash (kbytes): 0 Kbytes
• Pin Count: 324
• Max. Operating Frequency: 240 MHz
• Cpu: ARM926
• Hardware Qtouch Acquisition: No
• Max I/o Pins: 160
• Ext Interrupts: 160
• Usb Transceiver: 3
• Usb Speed: Full Speed
• Usb Interface: Host, Device
• Spi: 2
• Twi (i2c): 1
• Uart: 4
• Can: 1
• Ssc: 2
• Ethernet: 1
• Sd / Emmc: 2
• Graphic Lcd: Yes
• Video Decoder: No
• Camera Interface: Yes
• Resistive Touch Screen: No
• Temp. Sensor: No
• Crypto Engine: No
• Sram (kbytes): 96
• Self Program Memory: NO
• External Bus Interface: 2
• Dram Memory: sdram
• Nand Interface: Yes
• Picopower: No
• Temp. Range (deg C): -40 to 85
• I/o Supply Class: 1.8/3.3
• Fpu: No
• Mpu / Mmu: No / Yes
• Timers: 3
• Output Compare Channels: 3
• Input Capture Channels: 3
• Pwm Channels: 4
• 32khz Rtc: Yes
• Calibrated Rc Oscillator: No

50.2.5
50.2.5.1
50.2.6
50.2.6.1
50.2.6.2
50.2.6.3
6249I–ATARM–3-Oct-11
Bus Matrix
CAN
Problem with Locked Transfers
CAN: Low Power Mode and Error Frame
CAN: Low Power Mode and Pending Transmit Messages
CAN: Contents of Mailbox 0 can be sent Even if Mailbox is Disabled
Locked transfers are not correctly handled by the Bus Matrix and can lead to a system freeze-
up.
This does not concern ARM locked transfers.
Avoid other Bus Matrix masters locked transfers.
If the Low Power Mode is activated while the CAN is generating an error frame, this error frame
may be shortened.
None
No pending transmit messages may be sent once the CAN Controller enters Low-power Mode.
Check that all messages have been sent by reading the related Flags before entering Low-
power Mode.
When a transmit request (on a mailbox other than mailbox 0) is done simultaneously with the RX
line going low, the CAN may send the contents of mailbox 0 even if this mailbox is disabled or
has been set in reception.
The contents of mailbox 0 are sent, followed by the mailbox which is supposed to be sent.
Note that this is unlikely to happen and only occurs with a high bus load.
In this case, when the CAN attempts to send mailbox 0, the mailbox 0 ID is used for arbitration.
If arbitration is lost, the send request for mailbox 0 is canceled, else the contents of mailbox 0
are sent. The original transmit request is correctly handled afterwards.
Two workarounds:
1. Do not use mailbox 0 and program an unused identifier (example: 0x7FF) which will not
2. Use only mailbox 0 to transmit and no other mailboxes. In this case, there will be no
Problem Fix/Workaround
Problem Fix/Workaround
Problem Fix/Workaround
Problem Fix / Workaround:
Or:
affect the CAN bus. The spurious emission may happen but the impact on the bus will
be minimized.
spurious emission on the CAN bus.
AT91SAM9263
1061