convert some links using script
This commit is contained in:
David Holdeman
parent
4f13f2f411
commit
d0c02b6fd0
|
|
@ -1,13 +1,13 @@
|
|||
STM32F407 firmware
|
||||
```
|
||||
git clone --recurse-submodules https://github.com/rusefi/rusefi
|
||||
git clone --recurse-submodules [https://github.com/rusefi/rusefi](https://github.com/rusefi/rusefi)
|
||||
cd firmware
|
||||
make
|
||||
```
|
||||
|
||||
virtual serial port
|
||||
|
||||
PC application to send commands: https://rusefi.com/build_server/rusefi_bundle.zip
|
||||
PC application to send commands: [rusEFI Firmware bundle](https://rusefi.com/build_server/rusefi_bundle.zip)
|
||||
|
||||
|
||||
https://www.chibios.org/
|
||||
[ChibiOS](https://www.chibios.org/)
|
||||
|
|
@ -47,9 +47,9 @@ Repeat this process for the second throttle, if present.
|
|||
|
||||
# Throttle Tuning
|
||||
|
||||
See https://rusefi.com/forum/viewtopic.php?f=5&t=592&start=150#p32044
|
||||
See [Tuning ETB PID](https://rusefi.com/forum/viewtopic.php?f=5&t=592&start=150#p32044)
|
||||
|
||||
https://www.youtube.com/watch?v=USU0nnekokA
|
||||
[rusEFI ETB PID Autotune](https://www.youtube.com/watch?v=USU0nnekokA)
|
||||
|
||||
## Autotune PID
|
||||
|
||||
|
|
|
|||
|
|
@ -6,6 +6,6 @@ STM32 hard-coded bootloader support CAN firmware update but only on specific har
|
|||
|
||||
[OpenBLT GNU GPL Bootloader](http://www.feaser.com) allows CAN firmware update via any CAN pins. OpenBLT uses it's custom (?) update protocol using two CAN PIDs.
|
||||
|
||||
This was tested using https://www.peak-system.com/PCAN-USB.199.0.html?&L=1 hardware
|
||||
This was tested using [PCAN-USB Interface](https://www.peak-system.com/PCAN-USB.199.0.html?&L=1) hardware
|
||||
|
||||
Open question how popular is PCAN. Looks like https://github.com/moonglow/pcan_cantact turns stm32f042 boards into PCAN. Maybe even https://canable.io/?
|
||||
Open question how popular is PCAN. Looks like [PCAN Firmware](https://github.com/moonglow/pcan_cantact) turns stm32f042 boards into PCAN. Maybe even [Canable](https://canable.io/?)
|
||||
|
|
@ -18,11 +18,11 @@ We've looked into a few other chips but so far have not found a better overall p
|
|||
|
||||
Relevant forum threads:
|
||||
|
||||
S32K148 https://rusefi.com/forum/viewtopic.php?f=13&t=816
|
||||
S32K148 [Is STM32F4 the right chip?](https://rusefi.com/forum/viewtopic.php?f=13&t=816)
|
||||
|
||||
SPC563Mx, MPC563x - this one has some ChibiOS support - https://rusefi.com/forum/viewtopic.php?f=13&t=429
|
||||
SPC563Mx, MPC563x - this one has some ChibiOS support - [What chip is inside Ford EEC*?](https://rusefi.com/forum/viewtopic.php?f=13&t=429)
|
||||
|
||||
TMS570 - https://rusefi.com/forum/viewtopic.php?f=13&t=407 & https://github.com/rusefi/rusefi/issues/89
|
||||
TMS570 - [TMS570](https://rusefi.com/forum/viewtopic.php?f=13&t=407) & [Hello World project for TMS570](https://github.com/rusefi/rusefi/issues/89)
|
||||
|
||||
(in Russian) https://rusefi.com/forum/viewtopic.php?f=8&t=269
|
||||
|
||||
|
|
@ -211,4 +211,4 @@ Unfortunately, most of the chip manufacturers will make you sign a fairly strict
|
|||
9:57
|
||||
Processors like the XGATE that have been used successfully despite relatively modest specs (16 bit, low clock speed) tend to have very well developed secondary timing processors.
|
||||
9:58
|
||||
I look at the Honda ECUs on my bench that came in 1992 model year vehicles and would at least run an engine at 12,000 RPM with nothing more than a chip change. They have a 10Mhz 16/8 bit MCU with no floating point and an ASIC for handling timing tasks.
|
||||
I look at the Honda ECUs on my bench that came in 1992 model year vehicles and would at least run an engine at 12,000 RPM with nothing more than a chip change. They have a 10Mhz 16/8 bit MCU with no floating point and an ASIC for handling timing tasks.
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
https://github.com/rusefi/proteus-M54-adapter
|
||||
[Proteus M54 Adapter](https://github.com/rusefi/proteus-M54-adapter)
|
||||
|
||||
|
||||
For e46 which uses MS42 and MS43, which use M52 older style COP like the image below. NOT for M3 MSS54 or Late E46 with MS45.
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ Anyway looks like there is a working procedure, using DFU and STM32CubeProgramme
|
|||
|
||||
# Command line option
|
||||
|
||||
1) use STM32CubeProgrammer software https://www.st.com/en/development-tools/stm32cubeprog.html
|
||||
1) use STM32CubeProgrammer software [STM32CubeProgrammer]([STM32CubeProgrammer](https://www.st.com/en/development-tools/stm32cubeprog.html))
|
||||
|
||||
2) connect via USB while holding PROG button
|
||||
|
||||
|
|
@ -23,7 +23,7 @@ STM32_Programmer_CLI.exe -c port=usb1 -ob nDBANK=0
|
|||
STM32_Programmer_CLI.exe -c port=usb1 -e all
|
||||
```
|
||||
|
||||
6) download https://github.com/rusefi/rusefi/releases/download/2021.10.08_release/rusefi_bundle_proteus_f7.zip and un-compress and copy rusefi.hex to C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin folder
|
||||
6) download [Proteus F7 Firmware bundle 2021.10.08](https://github.com/rusefi/rusefi/releases/download/2021.10.08_release/rusefi_bundle_proteus_f7.zip) and un-compress and copy rusefi.hex to C:\Program Files\STMicroelectronics\STM32Cube\STM32CubeProgrammer\bin folder
|
||||
|
||||
7) from same command line prompt
|
||||
|
||||
|
|
@ -37,7 +37,7 @@ Done!
|
|||
|
||||
# GUI option
|
||||
|
||||
1) use STM32CubeProgrammer software https://www.st.com/en/development-tools/stm32cubeprog.html
|
||||
1) use STM32CubeProgrammer software [STM32CubeProgrammer]([STM32CubeProgrammer](https://www.st.com/en/development-tools/stm32cubeprog.html))
|
||||
|
||||
2) connect via USB while holding PROG button
|
||||
|
||||
|
|
|
|||
|
|
@ -1,8 +1,8 @@
|
|||
|
||||
|
||||
https://github.com/rusefi/proteus-Honda-K-125-adapter
|
||||
[Proteus Honda K 125 Adapter](https://github.com/rusefi/proteus-Honda-K-125-adapter)
|
||||
|
||||
[Schematics rev A](https://github.com/rusefi/proteus-Honda-K-125-adapter/blob/main/proteus125honda/boards/proteus125honda-a/board/proteus125honda-a-schematic.pdf)
|
||||
[Schematics rev A]([Proteus Honda K 125 Adapter](https://github.com/rusefi/proteus-Honda-K-125-adapter)/blob/main/proteus125honda/boards/proteus125honda-a/board/proteus125honda-a-schematic.pdf)
|
||||
|
||||
|
||||
[Proteus Manual](Proteus-Manual)
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
https://rusefi.com/forum/viewtopic.php?f=4&t=1935
|
||||
[Hellen 121 Nissan Forum Thread](https://rusefi.com/forum/viewtopic.php?f=4&t=1935)
|
||||
|
||||
[Nissan-Xterra-2011](Nissan-Xterra-2011)
|
||||
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
We use special QC firmware
|
||||
1) Download https://github.com/rusefi/rusefi/releases/download/2020.11.27_release/rusefi_bundle_mre_f4_hardware_QC_special_build.zip
|
||||
1) Download [MRE F4 Hardware QC Special Build 2020.11.27](https://github.com/rusefi/rusefi/releases/download/2020.11.27_release/rusefi_bundle_mre_f4_hardware_QC_special_build.zip)
|
||||
1) using Manual DFU mode flash abovementioned 2020 Black Friday rusefi_bundle_mre_f4_hardware_QC_special_build.zip
|
||||
1) disconnect microRusEFI from USB, plug microRusEFI into special test fixture LED board, power special test fixture LED board with +12v
|
||||
1) observe lack of smoke
|
||||
|
|
@ -19,6 +19,6 @@ This procedure does NOT test
|
|||
|
||||
|
||||
|
||||
After the text please flash latest normal release https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_mre_f4.zip
|
||||
After the text please flash latest normal release [MRE F4 Firmware bundle](https://github.com/rusefi/rusefi/releases/latest/download/rusefi_bundle_mre_f4.zip)
|
||||
|
||||
Attach an orange QC sticker to the part of the connector visible outside of the case.
|
||||
|
|
|
|||
Loading…
Reference in New Issue