User Tools

Site Tools


doc:crazyflie:dev:firmware:deck_memory_format

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
doc:crazyflie:dev:firmware:deck_memory_format [2015-08-05 14:54]
arnaud created
doc:crazyflie:dev:firmware:deck_memory_format [2020-05-12 14:22] (current)
kimberly
Line 1: Line 1:
 +<WRAP center round important 60%>
 +This page has deprecated and moved to the new documentation framework of the main Bitcraze website. Please go to [[https://www.bitcraze.io/documentation/system/]]
 +</WRAP>
 +
 ====== Deck memory format ====== ====== Deck memory format ======
  
Line 30: Line 34:
 The header allows to detect the deck installed and to verify that the deck stack is compatible. The header allows to detect the deck installed and to verify that the deck stack is compatible.
  
-The //UsedPins// value indicates which pins the deck is driving on the expansion port. For example a UART TX pin is driving both high and low when an i2c port is only driving low. For every GPIO on the expantion port one bit indicate if the GPIO can be driven high and one bit if it can be driven low:+The //UsedPins// value indicates which pins the **deck is driving** on the expansion port. For example a UART TX pin is driving both high and low when an i2c port is only driving low. For every GPIO on the expantion port one bit indicate if the GPIO can be driven high and one bit if it can be driven low:
  
 ^ Drive    ^ PC11 ^ PC10 ^ PB7 ^ PB6 ^ PB8 ^ PB5 ^ PB4 ^ PC12 ^ PA2 ^ PA3 ^ PA5 ^ PA6 ^ PA7 ^ P0.11 ^ P0.12 ^ P0.08 ^ ^ Drive    ^ PC11 ^ PC10 ^ PB7 ^ PB6 ^ PB8 ^ PB5 ^ PB4 ^ PC12 ^ PA2 ^ PA3 ^ PA5 ^ PA6 ^ PA7 ^ P0.11 ^ P0.12 ^ P0.08 ^
-**Low**  | 0    | 1    | 2   | 3   | 4   | 5   | 6   | 7    | 8   | 9   | 10  | 11  | 12  | 13    | 14    | 15    | +**Low**  | 0    | 1    | 2   | 3   | 4   | 5   | 6   | 7    | 8   | 9   | 10  | 11  | 12  | 13    | 14    | 15    | 
-**High** | 16   | 17   | 18  | 19  | 20  | 21  | 22  | 23   | 24  | 25  | 26  | 27  | 28  | 29    | 31    | 31    |+**High** | 16   | 17   | 18  | 19  | 20  | 21  | 22  | 23   | 24  | 25  | 26  | 27  | 28  | 29    | 31    | 31    |
  
 For example is a deck has a GPS that has its UART TX on PC11 (push-pull, drives high and low), the //UsedPins// value will be (1<<0) | (1<<16) = 0x00010001. As another example is a deck has an I2C sensor on PB6,PB7 (Open collector, only drives low), the //UsedPins// value is then: (1<<2) | (1<<3) = 0x0000000C For example is a deck has a GPS that has its UART TX on PC11 (push-pull, drives high and low), the //UsedPins// value will be (1<<0) | (1<<16) = 0x00010001. As another example is a deck has an I2C sensor on PB6,PB7 (Open collector, only drives low), the //UsedPins// value is then: (1<<2) | (1<<3) = 0x0000000C
Line 63: Line 67:
 This is an example of OW memory content for the led ring deck. This is an example of OW memory content for the led ring deck.
 <code> <code>
-0000000: eb 00 00 00 00 01 01 44 00 0e 01 09 62 63 4c 65  .......D....bcLe+0000000: eb 00 00 00 00 bc 01 44 00 0e 01 09 62 63 4c 65  .......D....bcLe
 0000010: 64 52 69 6e 67 02 01 62 55                       dRing..bU 0000010: 64 52 69 6e 67 02 01 62 55                       dRing..bU
 </code> </code>
Line 72: Line 76:
     "header": {     "header": {
         "usedPin": 0,         "usedPin": 0,
-        "vid": 1,+        "vid": 188,
         "pid": 1         "pid": 1
     },     },
doc/crazyflie/dev/firmware/deck_memory_format.1438779270.txt.gz · Last modified: 2015-08-05 14:54 by arnaud