API tools faq
paste
Advertisement
Guest User

Untitled

a guest
Jan 10th, 2023
24
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 12.45 KB | None | 0 0
raw download clone embed print report
  1. System Loader V1.1.0
  2. FMU V1.3.19
  3. OSD V1.0.6
  4. POWER V0.0.1
  5. MOTOR_TELEM V1.0.0
  6.  
  7.  
  8. Starting System Loader by user
  9. Force loading firmware to all
  10. SD Bootloader V2.0
  11. SD Flashloader V1.0
  12. System Loader V1.1.0
  13. Read manifest file
  14. Cleared local RO
  15. Loading GCU firmware
  16. Extracted file version 1.3.19
  17. File opened successfully
  18. File verified
  19. Erasing GCU Flash
  20. Writing GCU Flash
  21. Flash verified
  22. Loading WIFI module firmware
  23. WIFI sync success
  24. Loading WIFI firmware
  25. WIFI load success
  26. Loading 4 CAN modules
  27. Motor: Using CAN #0
  28. Motor: resetting address (broadcast)
  29. Motor: unlocking RO (broadcast)
  30. OSD: No rebroadcast. Using CAN #0
  31. OSD: already reset
  32. OSD: activating addressing
  33. OSD: assigning address broadcast
  34. OSD: validating address
  35. OSD: hardware id verified
  36. OSD: device type verified
  37. Power: No rebroadcast. Using CAN #0
  38. Power: already reset
  39. Power: fixed address
  40. Power: validating address
  41. Power: hardware id verified
  42. Power: device type verified
  43. Motor Telem: No rebroadcast. Using CAN #0
  44. Motor Telem: already reset
  45. Motor Telem: fixed address
  46. Motor Telem: validating address
  47. Motor Telem: hardware id verified
  48. Motor Telem: device type verified
  49.  
  50.  
  51. CAN loading OSD
  52. OSD: recording device config
  53. OSD: Already keyed!
  54. OSD: UID: 0xBF8D2914 Bootloader version: 5
  55. OSD: opening and checking firmware file
  56. OSD: preparing firmware load
  57. OSD: transmitting firmware file
  58. OSD: finalizing firmware load
  59. OSD: finished firwmare load
  60.  
  61. CAN loading Power
  62. Power: recording device config
  63. Power: Already keyed!
  64. Power: UID: 0x55261792 Bootloader version: 5
  65. Power: opening and checking firmware file
  66. Power: preparing firmware load
  67. Power: transmitting firmware file
  68. Power: finalizing firmware load
  69. Power: finished firwmare load
  70.  
  71. CAN loading Motor Telem
  72. Motor Telem: recording device config
  73. Motor Telem: Already keyed!
  74. Motor Telem: UID: 0x38347011 Bootloader version: 5
  75. Motor Telem: opening and checking firmware file
  76. Motor Telem: preparing firmware load
  77. Motor Telem: transmitting firmware file
  78. Motor Telem: finalizing firmware load
  79. Motor Telem: finished firwmare load
  80.  
  81. Jumping all modules to application
  82. Assigning Addresses to DJI ESCs...
  83. done!
  84. Set boot flags.
  85. Rebooting to firmware...
  86.  
  87.  
  88.  
  89. FMUv2 ver 0xE : Rev 0 V30
  90. [boot] Fault Log info File No 4 Length 3177 flags:0x01 state:1
  91. [boot] Fault Log is Armed
  92. sercon: Registering CDC/ACM serial driver
  93. sercon: Successfully registered the CDC/ACM serial driver
  94. HW arch: PX4_FMU_V3
  95. HW type: V30
  96. HW version: 0x0009000E
  97. HW revision: 0x00000000
  98. FW git-hash: 27f3ea68a8369bc8b7d2f1899111f8d12910aeb2
  99. FW version: 1.3.2 0 (16974336)
  100. FW git-branch: ff-release/hotfix2
  101. OS: NuttX
  102. OS version: Release 7.28.0 (119275775)
  103. OS git-hash: 1381738a7ca3b66dc6f9bdb946a35a6c7d11ca25
  104. Build datetime: Dec 14 2021 20:47:41
  105. Build uri: localhost
  106. Toolchain: GNU GCC, 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
  107. PX4GUID: 0001000000003832383333385115004c001f
  108. MCU: STM32F42x, rev. 3
  109. [hardfault_log] Fault Log is Armed
  110. INFO [tune_control] Publishing standard tune 1
  111. INFO [param] selected parameter default file /fs/mtd_params
  112. ERROR [parameters] ignoring unrecognised parameter 'FF_IESC_TYPE'
  113. Board defaults: /etc/init.d/rc.board_defaults
  114. WARN [rgbled] no RGB led on bus #2
  115. rgbled1 on I2C bus 1 at 0x39 (bus: 100 KHz, max: 100 KHz)
  116. nsh: rgbled_pwm: command not found
  117. WARN [blinkm] I2C init failed
  118. WARN [blinkm] init failed
  119. INFO [FF_CAN_QUAD] FF CAN Module Started
  120. INFO [FF_CAN_QUAD] CAN initialized.
  121. INFO [FF_CAN_QUAD] CAN registered.
  122. INFO [FF_CAN_QUAD] FF_CANRead Task spawned.
  123. INFO [FF_CAN_QUAD] --------------------------
  124. INFO [FF_CAN_QUAD] Bootloader jumper started.
  125. INFO [FF_CAN_QUAD] ----------------------------
  126. INFO [FF_CAN_QUAD] FF_CAN_ReadeINFO [FF_CAN_QUAD] BootloaderJur-> Thread started.
  127. mp-> sending jump command to CAN ID: 00000009.
  128. INFO [FF_CAN_QUAD] BootloaderJump-> CAN opened for write (blocking).
  129. INFO [FF_CAN_QUAD] BootloaderJump-> Sending jump address value.
  130. INFO [FF_CAN_QUAD] ----------------------------
  131. INFO [FF_CAN_QUAD] BootloaderJump-> sending jump command to CAN ID: 0000000a.
  132. INFO [FF_CAN_QUAD] BootloaderJump-> CAN opened for write (blocking).
  133. INFO [FF_CAN_QUAD] BootloaderJump-> Sending jump address value.
  134. INFO [FF_CAN_QUAD] ----------------------------
  135. INFO [FF_CAN_QUAD] BootloaderJump-> sending jump command to CAN ID: 0000000e.
  136. INFO [FF_CAN_QUAD] BootloaderJump-> CAN opened for write (blocking).
  137. INFO [FF_CAN_QUAD] BootloaderJump-> Sending jump address value.
  138. INFO [FF_CAN_QUAD] Bootloader jumper finished.
  139. INFO [FF_CAN_QUAD] FF_CAN_WriteINFO [FF_CAN_QUAD] FF_CANWrite r-> Thread started.
  140. Task spawned.
  141. INFO [FF_CAN_QUAD] FF_CAN_WriteINFO [FF_CAN_QUAD] FF CAN Modulr-> CAN opened
  142. e Exited
  143. INFO [px4io] default PWM output device
  144. Board sensors: /etc/init.d/rc.board_sensors
  145. WARN [hmc5883] no device on bus 1 (type: 2)
  146. WARN [lis3mdl] no device on bus 2
  147. ERROR [ak09916] driver start failed
  148. IST8310 on I2C bus 1 at 0x0e (bus: 100 KHz, max: 400 KHz)
  149. INFO [ist8310] cross axis cal: [+1.01,+0.05,-0.04|-0.05,+1.01,-0.02|-0.05,-0.03,+1.00]
  150. INFO [ist8310] no device on bus 5
  151. ERROR [ist8310] calibration only feasible against one bus
  152. WARN [hmc5883] no device on bus 2 (type: 1)
  153. WARN [mpu6000] no device on bus #3 (SPI1)
  154. WARN [mpu6000] no device on bus #5 (SPI4)
  155. INFO [mpu9250] Bus probed: 5
  156. MPU9250 on SPI bus 4 at 4 (1000 KHz)
  157. INFO [mpu9250] accel cutoff set to 20.00 Hz
  158. INFO [mpu9250] gyro cutoff set to 20.00 Hz
  159. L3GD20 on SPI bus 4 at 1 (11000 KHz)
  160. LSM303D on SPI bus 4 at 2 (11000 KHz)
  161. INFO [mpu9250] Bus probed: 3
  162. MPU9250 on SPI bus 1 at 4 (1000 KHz)
  163. INFO [mpu9250] accel cutoff set to 20.00 Hz
  164. INFO [mpu9250] gyro cutoff set to 20.00 Hz
  165. WARN [ms5611] no device on bus 1
  166. MS5611_SPI on SPI bus 4 at 3 (20000 KHz)
  167. WARN [ms5611] no device on bus 4
  168. MS5611_SPI on SPI bus 1 at 3 (20000 KHz)
  169. WARN [bst] no devices found
  170. ERROR [param] Parameter UAVCAN_ENABLE not found
  171. INFO [mavlink] mode: Config, data rate: 800000 B/s on /dev/ttyACM0 @ 57600B
  172. Starting Main GPS on /dev/ttyS3
  173. Starting MAVLink on /dev/ttyS1
  174. INFO [mavlink] mode: Normal, data rate: 7200 B/s on /dev/ttyS1 @ 57600B
  175. Starting MAVLink on /dev/ttyS2
  176. INFO [mavlink] mode: Normal, data rate: 7200 B/s on /dev/ttyS2 @ 57600B
  177. Starting MAVLink on /dev/ttyS6
  178. INFO [mavlink] mode: Normal, data rate: 7200 B/s on /dev/ttyS6 @ 57600B
  179. WARN [mavlink] hardware flow control not supported
  180. FF frame selection
  181. Alta Quad selected
  182. ERROR [mavlink] offboard mission init failed (-1)
  183. px4flow [444:100]
  184. INFO [px4flow] scanning I2C buses for device..
  185. ERROR [param] Parameter UAVCAN_ENABLE not found
  186. ERROR [logger] alloc failed
  187. ERROR [logger] failed to instantiate object
  188. USE IO
  189. yes
  190. ------
  191. IO PRESENT
  192. yes
  193. ERROR [mavlink] Maximum MAVLink instance count of 4 reached.
  194. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  195. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  196. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  197. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  198. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  199. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  200. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  201. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  202. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  203. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  204. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  205. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  206. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  207. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  208. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  209. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  210. WARN [mavlink] mavlink for device /dev/ttyS5 is not running
  211.  
  212. NuttShell (NSH)
  213. nsh> ▒ L▒▒▒▒ L▒▒▒▒L▒▒&▒ L▒▒▒N▒
  214. L▒▒▒▒>
  215. iIy1S▒d>▒w?▒-▒9▒2<H}4=▒D▒{▒▒▒▒=▒▒>~▒G▒▒D▒(&B▒?▒
  216. L▒▒▒'▒
  217. J^▒D▒"▒ L▒▒S▒▒ L▒▒▒▒▒ L▒▒▒▒▒ L▒▒>▒▒ L▒▒
  218. X▒FTr*▒▒▒828338QL▒▒▒+!+h▒▒▒▒▒ӽ▒$▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒3▒▒
  219. $▒l6▒▒▒▒▒C▒2a▒'▒▒▒▒''▒▒▒▒w▒▒ N▒▒▒▒▒Hi▒ ▒▒'▒ L^▒ ▒ L▒▒+▒▒ L▒▒▒▒▒ L▒▒▒<▒ L▒▒v▒ L▒▒-V▒ !L▒▒▒▒ "L▒▒▒▒▒>#i|<▒n>^?$▒▒▒,<y▒B=▒zП▒▒@▒={▒▒>}▒G▒D33&B▒B▒ $L▒▒▒u▒ %L▒▒j?▒ &L▒▒X▒▒ 'L▒▒▒▒▒ (L▒PY▒ )L▒▒▒[▒
  220. *J2▒D▒▒▒ +L▒▒M▒▒ ,L▒▒▒2▒ -L▒▒8x▒ .L▒▒
  221.  
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement
Public Pastes
Advertisement
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!