SAM9G10 Atmel Corporation, SAM9G10 Datasheet - Page 70

• Manufacturer Part Number: SAM9G10
• Manufacturer: Atmel Corporation

Specifications of SAM9G10

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

11.5.2
11.5.2.1
11.5.2.2
70
70
SAM9G35
SAM9G35
DBGU Serial Port
Supported External Crystal/External Clocks
Xmodem Protocol
Note:
Communication is performed through the DBGU serial port initialized to 115,200 Baud, 8 bits of
data, no parity, 1 stop bit.
The SAM-BA Monitor supports a frequency of 12 MHz to allow DBGU communication for both
external crystal and external clock.
The Send and Receive File commands use the Xmodem protocol to communicate. Any terminal
performing this protocol can be used to send the application file to the target. The size of the
binary file to send depends on the SRAM size embedded in the product. In all cases, the size of
the binary file must be lower than the SRAM size because the Xmodem protocol requires some
SRAM memory in order to work.
The Xmodem protocol supported is the 128-byte length block. This protocol uses a two-charac-
ter CRC16 to guarantee detection of a maximum bit error.
Xmodem protocol with CRC is accurate provided both sender and receiver report successful
transmission. Each block of the transfer looks like:
<SOH><blk #><255-blk #><--128 data bytes--><checksum> in which:
Figure 11-11
• Send a file (S): Send a file to a specified address.
• Receive a file (R): Receive data into a file from a specified address
• Go (G): Jump to a specified address and execute the code.
• Get Version (V): Return the Boot Program version.
– Address: Address in hexadecimal.
– Output: The byte, halfword or word read in hexadecimal followed by ‘>’
– Address: Address in hexadecimal.
– Output: ‘>’
– Address: Address in hexadecimal.
–
– Output: ‘>’
– Address: Address to jump in hexadecimal.
– Output: ‘>’once returned from the program execution. If the executed program does
– Output: version, date and time of ROM code followed by ‘>’.
– <SOH> = 01 hex
– <blk #> = binary number, starts at 01, increments by 1, and wraps 0FFH to 00H (not
– <255-blk #> = 1’s complement of the blk#.
– <checksum> = 2 bytes CRC16
NbOfBytes
not handle the link register at its entry and does not return, the prompt will not be
displayed.
to 01)
There is a time-out on this command which is reached when the prompt ‘>’ appears before the
end of the command execution.
shows a transmission using this protocol.
: Number of bytes in hexadecimal to receive.
11053B–ATARM–22-Sep-11
11053B–ATARM–22-Sep-11