While technically true, one of the huge advantages of the whole STM32 family is that you can attach a debugger, set breakpoints, inspect memory and registers, etc. just like when developing desktop software. However, that all only works over SWD. If you’re planning on developing your own firmware (or a heavily modified rusEfi variant), it would be a godsend to have debugging available.InternetAthiest wrote: ↑Mon Oct 07, 2019 6:33 pm
The STM32F070CBT comes from factory with the capability of flashing firmware via USB without changing the bootloader. This means that I do not need a SWD header.
Sprut - A newbies try to design an ECU
-
- running engine in first post
- Posts: 1495
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Sprut - A newbies try to design an ECU
Re: Sprut - A newbies try to design an ECU
Is there a link to download? Github, etc? Is that KC5? I'm missing many details right now, but others seem to have found things like a schematic.
Welcome to the friendlier side of internet crazy
Re: Sprut - A newbies try to design an ECU
Some other comments, validate your footprints before going for MFG of the board. Print it out 100% scale and put your components on the paper. You'll likely resolve several issues before you have PCB costs and lead time issues.
Enclosure? Heatsink? Do you know you can export to OnShape then you could model other things that are not KC related like an enclosure.
Enclosure? Heatsink? Do you know you can export to OnShape then you could model other things that are not KC related like an enclosure.
Welcome to the friendlier side of internet crazy
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
mck1117 wrote: ↑Tue Oct 08, 2019 10:16 amI agree - the F070CB is not enough chip to run rusEfi. There are a few reasons it isn’t enough:
While the f070cb could absolutely run an engine, it would require a rewrite of the firmware. I would strongly suggest switching to an f405/407 if you intend to run rusEfi on this board. The f407vg is the best supported today, since it’s the one found on the F4 discovery board that plugs in to Frankenso.
For the smallest/cheapest chip with an FPU, you’d have to go up to an STM32F3.
I've looked into some other chips. Essentially if I'd want to have a drop in chip with the current pcb design then the STM32F303CC is the one to use. Otherwise the G4 series has a different pin out but has more flash but at that point I'd rather up size to LQFP64.mck1117 wrote: ↑Tue Oct 08, 2019 10:27 amWhile technically true, one of the huge advantages of the whole STM32 family is that you can attach a debugger, set breakpoints, inspect memory and registers, etc. just like when developing desktop software. However, that all only works over SWD. If you’re planning on developing your own firmware (or a heavily modified rusEfi variant), it would be a godsend to have debugging available.
Now, SWD seems kinda sweet to have but would require the up size. It would also allow me to add status LEDs and CAN without impacting current I/O. Seems worth re-routing for those features/improvments.
I'll update the first post right after posting this.
EDIT: Yes I run KC5 5.1.4
I'll do a paper printout tomorrow, thanks for telling me this tip. I guess it will probably work well as it is but who knows?
Yup, I'll be modelling an enclosure in Inventor 2020 then 3d print it on a Ender 3.
-
- running engine in first post
- Posts: 1495
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Sprut - A newbies try to design an ECU
It looks like you have some free space near the MCU, so it'd be a pretty easy change to swap up to LQFP64 or LQFP100. Since rusEfi has no restrictions on which pins are in use (at least for outputs), the remap is as simple as figuring out which order the signals are on the board, then connecting them to the next available pin in the same order. The F405 comes in LQFP64, and is already supported well since it's the same as an F407.InternetAthiest wrote: ↑Tue Oct 08, 2019 10:21 pmOtherwise the G4 series has a different pin out but has more flash but at that point I'd rather up size to LQFP64.
Now, SWD seems kinda sweet to have but would require the up size. It would also allow me to add status LEDs and CAN without impacting current I/O. Seems worth re-routing for those features/improvments.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Yeah, going to re-route it for LQFP64. Thinking of using the STM32F412RET6 instead.mck1117 wrote: ↑Tue Oct 08, 2019 11:38 pmIt looks like you have some free space near the MCU, so it'd be a pretty easy change to swap up to LQFP64 or LQFP100. Since rusEfi has no restrictions on which pins are in use (at least for outputs), the remap is as simple as figuring out which order the signals are on the board, then connecting them to the next available pin in the same order. The F405 comes in LQFP64, and is already supported well since it's the same as an F407.InternetAthiest wrote: ↑Tue Oct 08, 2019 10:21 pmOtherwise the G4 series has a different pin out but has more flash but at that point I'd rather up size to LQFP64.
Now, SWD seems kinda sweet to have but would require the up size. It would also allow me to add status LEDs and CAN without impacting current I/O. Seems worth re-routing for those features/improvments.
-
- running engine in first post
- Posts: 1495
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Sprut - A newbies try to design an ECU
Any reason for the F412 over the F405/407? The STM32F405RGT6 is only $4 more, and is fully supported by rusEfi out of the box.InternetAthiest wrote: ↑Wed Oct 09, 2019 1:22 amYeah, going to re-route it for LQFP64. Thinking of using the STM32F412RET6 instead.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Avalibility, currently only have access to certain a few selection of STM32s which is why I chose the F070 in the first place.mck1117 wrote: ↑Wed Oct 09, 2019 1:29 amAny reason for the F412 over the F405/407? The STM32F405RGT6 is only $4 more, and is fully supported by rusEfi out of the box.InternetAthiest wrote: ↑Wed Oct 09, 2019 1:22 amYeah, going to re-route it for LQFP64. Thinking of using the STM32F412RET6 instead.
Last edited by InternetAthiest on Wed Oct 09, 2019 2:19 am, edited 2 times in total.
-
- running engine in first post
- Posts: 1495
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Sprut - A newbies try to design an ECU
Does Mouser EU not ship to Sweden? They have a few thousand F405RG in stock.
@960 may have tips for EU sourcing of components.
@960 may have tips for EU sourcing of components.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
The problem lies within who I can order from.
Looked up the pin out for the F412 and F405 and seems like that VCAP_1 is moved one pin to the right and they replaced pin 48 VSS (on the F412) with VCAP_2 which is just a cap to gnd. Might make it compatible as it is not that different.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Just add a 0603 between pin 47 and gnd. On the F412 pin 47 is gnd and on the F405 it's VCAP_2 which connects to gnd
Then add a 0603 for both pin 30 and 31 that connects to gnd. F412 pin 30 is VCAP_1 and pin 31 is gnd. On the F405 pin 30 is pb11 which I can leave floating and pin 31 is VCAP_2. Good solution?
Then add a 0603 for both pin 30 and 31 that connects to gnd. F412 pin 30 is VCAP_1 and pin 31 is gnd. On the F405 pin 30 is pb11 which I can leave floating and pin 31 is VCAP_2. Good solution?
Re: Sprut - A newbies try to design an ECU
-- 14V on input 1 would result in to much current dumped to the 5V rail. Causing 5V rail to be more like 10V, so it would break things. You want something more like 10k for R115.
-- Suggest you look at the notes on Franksenso knock about calculating the XTAL caps. That circuit has like a 50% failure to start. Basically 5 out of 10 assembled frankenso's, the TPIC XTAL doesn't start unless you touch the XTAL package or something similar to get it started. I think you want some extra pads, such that you can add or change components if so required.
-- Suggest putting some critical or key math on the sheets. For example, ADC low pass filter calcs, or knock XTAL loading caps calcs.
-- See VR notes found here https://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger#VR_lower_level_details.2C_formulas.2C_app_notes.2C_etc I think you want a higher voltage capability. AKA 2X 5k ohm 0805 resistors making 10k ohm.
-- I have some really crappy notes about OVP MOSFET vs fly-back typologies at this link. Freaking SF, seems the wiki is broken. Sorry it really sucks, but perhaps you can extract the key info from it. One key note, is that while OVP is more accurate, it also dumps more heat in the ECU. Fly-back dumps more of that heat into the injectors. https://sourceforge.net/p/daecu/code/HEAD/tree/wiki/Injector_driver_theory.wiki
-- Beware thermal management. Plan to add heat sinks to your heat generating chips.
-- See current loop notes http://www.maximintegrated.com/en/app-notes/index.mvp/id/5450 also other notes found here https://rusefi.com/wiki/index.php?title=Manual:Hardware:PCB_design_rules Those notes include handy references like the below.
-- Suggest you look at the notes on Franksenso knock about calculating the XTAL caps. That circuit has like a 50% failure to start. Basically 5 out of 10 assembled frankenso's, the TPIC XTAL doesn't start unless you touch the XTAL package or something similar to get it started. I think you want some extra pads, such that you can add or change components if so required.
-- Suggest putting some critical or key math on the sheets. For example, ADC low pass filter calcs, or knock XTAL loading caps calcs.
-- See VR notes found here https://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger#VR_lower_level_details.2C_formulas.2C_app_notes.2C_etc I think you want a higher voltage capability. AKA 2X 5k ohm 0805 resistors making 10k ohm.
-- I have some really crappy notes about OVP MOSFET vs fly-back typologies at this link. Freaking SF, seems the wiki is broken. Sorry it really sucks, but perhaps you can extract the key info from it. One key note, is that while OVP is more accurate, it also dumps more heat in the ECU. Fly-back dumps more of that heat into the injectors. https://sourceforge.net/p/daecu/code/HEAD/tree/wiki/Injector_driver_theory.wiki
-- Beware thermal management. Plan to add heat sinks to your heat generating chips.
-- See current loop notes http://www.maximintegrated.com/en/app-notes/index.mvp/id/5450 also other notes found here https://rusefi.com/wiki/index.php?title=Manual:Hardware:PCB_design_rules Those notes include handy references like the below.
Welcome to the friendlier side of internet crazy
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Input is only for 5V and those resistors are only there to enable different configurations, much like how frankenso works.
I used the values supplies in the Renesas HIP9011 datasheet which as far as I can tell is exactly the same chip.kb1gtt wrote: ↑Wed Oct 09, 2019 9:32 am-- Suggest you look at the notes on Franksenso knock about calculating the XTAL caps. That circuit has like a 50% failure to start. Basically 5 out of 10 assembled frankenso's, the TPIC XTAL doesn't start unless you touch the XTAL package or something similar to get it started. I think you want some extra pads, such that you can add or change components if so required.
Will do in next update!
I'll upgrade the size to 1206 in that case.kb1gtt wrote: ↑Wed Oct 09, 2019 9:32 am-- See VR notes found here https://rusefi.com/wiki/index.php?title=Manual:Hardware_Trigger#VR_lower_level_details.2C_formulas.2C_app_notes.2C_etc I think you want a higher voltage capability. AKA 2X 5k ohm 0805 resistors making 10k ohm.
OVP are going to be installed on Sprut, has yet to change in the schematics but most if not all DPAK OVP with logic level will fit and work. Fly-back diodes are only there if they are needed for other applications.kb1gtt wrote: ↑Wed Oct 09, 2019 9:32 am-- I have some really crappy notes about OVP MOSFET vs fly-back typologies at this link. Freaking SF, seems the wiki is broken. Sorry it really sucks, but perhaps you can extract the key info from it. One key note, is that while OVP is more accurate, it also dumps more heat in the ECU. Fly-back dumps more of that heat into the injectors. https://sourceforge.net/p/daecu/code/HEAD/tree/wiki/Injector_driver_theory.wiki
Heat generating chips are going to be soldered to the gnd plane. In future PCB's I'll try to heatsink the pcb (if it even works).
I've redesigned Sprut to use a LQFP64 now. But as the deadline for ordering the PCB is tomorrow it will be ordered in the state that it is now with the redesign
Re: Sprut - A newbies try to design an ECU
-- 5V is only 5V until you say oops, then replace the entire board. We've all made mistakes, and a 12V tolerant input is a beneficial feature.
-- HIP9011 and TPIC8108 have a history of headache here. AKA don't believe datasheets. I suggest some pads to allow changes I have have done. The TPIC seems to want the MCU to drive the clock, not an XTAL. If you can get the HIP, then it's probably problem solved.
-- when 1206 is thermally cycled, it has about a 50% failure rate. While 0805's are far closer to 0% failure rate. I suggest double 0805's to prevent stress failures caused by thermal expansion issues.
-- I agree you should allow optional flyback diode. Things like the alternator controls often want the sluggish control.
-- The hi/lo drivers are very limited by heat. The 3A datasheet is more like 0.125A because of thermal issues.
-- HIP9011 and TPIC8108 have a history of headache here. AKA don't believe datasheets. I suggest some pads to allow changes I have have done. The TPIC seems to want the MCU to drive the clock, not an XTAL. If you can get the HIP, then it's probably problem solved.
-- when 1206 is thermally cycled, it has about a 50% failure rate. While 0805's are far closer to 0% failure rate. I suggest double 0805's to prevent stress failures caused by thermal expansion issues.
-- I agree you should allow optional flyback diode. Things like the alternator controls often want the sluggish control.
-- The hi/lo drivers are very limited by heat. The 3A datasheet is more like 0.125A because of thermal issues.
Welcome to the friendlier side of internet crazy
-
- Posts: 32
- Joined: Mon Aug 19, 2019 10:40 pm
- Location: Los Gatos CA USA
Re: Sprut - A newbies try to design an ECU
This is worth repeating. Gate drivers are designed for driving MOSFET gates, not continuous current loads. Gates are basically capacitors, so there is a brief surge of current to charge, then they present a negligible load. For reasonable efficiency, the charge/discharge time is going to be under 5% in most applications. Thus a "1.5A" gate driver might be suitable for a 40mA continuous load.
The same is true for most raw MOSFET ratings. The advertised current is the limit that the part can sustain with perfect conditions, including a perfect heatsink. The advertised voltage rating doesn't take into account the inductive aspects of real-life mounting. The ratings are useful for comparison, but aren't a nominal value for design.
'Protected' parts such as OmniFETs have much more realistic ratings e.g. a 70V clamp part probably has a 120V transistor.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Sorry for not responding until now!
I've ordered a batch of rev 1B boards which should arrive within this month. Now, just an hour after ordering them I found some bugs in the schematic of 1B, these bug are fortunetly fixable with some mod wire and are going to be fixed in 1C.
Rev 1A to Rev 1B changelist:
Rev 1C is essentially going to be the bugfixing version of 1B. I'll order 1C once I've got a running 1B. Currently the changelist for 1C is:
I've ordered a batch of rev 1B boards which should arrive within this month. Now, just an hour after ordering them I found some bugs in the schematic of 1B, these bug are fortunetly fixable with some mod wire and are going to be fixed in 1C.
Rev 1A to Rev 1B changelist:
- Changed MCU to a STM32F412RET with support for the F405
- Changed VR input resistors to 1210 size.
- Added 2 more analog inputs by wiring up the last 2 unsued opamps in the third MCP6004.
- Added another draining output (Protected MOSFET).
- Added 2 more sourcing outputs (DRIVERS) to support up to 6 logical ignition coils with 5v tach and diagnosis light signal.
Rev 1C is essentially going to be the bugfixing version of 1B. I'll order 1C once I've got a running 1B. Currently the changelist for 1C is:
- Replaced TPIC8108 XTAL circuit with clock signal from MCU. Suggested by @kb1gtt.
- Fixed Int/Hold not being connected to MCU. (1B use modwire).
- Added full duplex SPI communication between TPIC8108 and MCU, only had TX line before.
- Change VR input resistors to dual inline 0805 resistors as mentioned by @kb1gtt.
- Added SWD header, (Avalible on 1B with connector attached via mod wires).
- Added status LEDs.
- Added pull down resistors to gate drivers inputs. Enables usage TC4427 instead of NCP81071
They should still work fine for this application as they are only being used as logic signals for VAG coils and tach/dash. I've only got access to the NCP81071 but I do not see/understand why the TC442x series chips are any better for this scenario.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Note that the current rev 1C is not up to the PCB design rules that are in the wiki, this will hopefully be fixed in a later rev.
Going to upload rev 1B schematic and KiCad project files later today.
Going to upload rev 1B schematic and KiCad project files later today.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Here we go again for another update!
I just received the PCBs and the remaining components for making two sprut (REV 1B) and will be soldering it tomorrow. I've just downloaded the whole RusEFI repo and it seems that it will be quite easy and quick to make a board config (Thanks for making it easy! ) and then I'll try to flash it straight on via DFU. As it happens I've been working alot with stm32duino recently while waiting on everything utilising the F412RE and it seems like it should be no big deal to get Speeduino to run on it too.
But before flashing it I'll be testing the PSU without any other components on the board and then gradually add components to finish off circuits and test them.
Will update tomorrow but for now have some pictures!
Dosen't it look pretty
I just received the PCBs and the remaining components for making two sprut (REV 1B) and will be soldering it tomorrow. I've just downloaded the whole RusEFI repo and it seems that it will be quite easy and quick to make a board config (Thanks for making it easy! ) and then I'll try to flash it straight on via DFU. As it happens I've been working alot with stm32duino recently while waiting on everything utilising the F412RE and it seems like it should be no big deal to get Speeduino to run on it too.
But before flashing it I'll be testing the PSU without any other components on the board and then gradually add components to finish off circuits and test them.
Will update tomorrow but for now have some pictures!
Dosen't it look pretty
- AndreyB
- Site Admin
- Posts: 14373
- Joined: Wed Aug 28, 2013 1:28 am
- Location: Jersey City
- Github Username: rusefillc
- Slack: Andrey B
Re: Sprut - A newbies try to design an ECU
I hope it would be easy and hopefully we will see a blinking LED soonInternetAthiest wrote: ↑Wed Oct 30, 2019 10:57 pmI've just downloaded the whole RusEFI repo and it seems that it will be quite easy and quick to make a board config (Thanks for making it easy! ) and then I'll try to flash it straight on via DFU.
Very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
Always looking for C/C++/Java/PHP developers! Please help us see https://rusefi.com/s/howtocontribute
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Some good and some bad news. I've assembled both PCB and all of the circuits work as expected after fixing some minor bugs. Now to the bad news, the MCU won't start and won't connect over USART nor DFU in bootloader mode on either of the PCBs. I can understand why DFU wouldn't work as it requires a functioning HSE but the USART is clocked via the HSI. I've checked if there are any shorts or solderbridges but none are found (Tested with continouity on meter) so if I've not forgot something crucial then it might be that I've damaged the MCUs during soldering. I'll test some more things tomorrow but I've probably damaged the MCUs during soldering with too high heat.
Re: Sprut - A newbies try to design an ECU
Not likely to be hot heat. The chips can handle allot of heat. Generally your PCB will fail long before heat damages the chunk of glass.
Welcome to the friendlier side of internet crazy
- Dron_Gus
- contributor
- Posts: 460
- Joined: Wed Nov 13, 2013 1:11 pm
- Location: S-Pb
- Github Username: dron0gus
Re: Sprut - A newbies try to design an ECU
App note recommends 100k pull-ups on rx and tx lines. While you have pull-downs (at least for PA9, PA10). Not sure if this is mandatory.InternetAthiest wrote: ↑Tue Nov 05, 2019 11:22 pmNow to the bad news, the MCU won't start and won't connect over USART nor DFU in bootloader mode on either of the PCBs. I can understand why DFU wouldn't work as it requires a functioning HSE but the USART is clocked via the HSI. I've checked if there are any shorts or solderbridges but none are found (Tested with continouity on meter) so if I've not forgot something crucial then it might be that I've damaged the MCUs during soldering. I'll test some more things tomorrow but I've probably damaged the MCUs during soldering with too high heat.
Check voltage levels on PA10. Bootloader should set it to output high (while idle).
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
I've checked the voltage levels on BOOT and NRST which seem fine and function as they should (BOOT goes high and NRST goes low when pushed). The IC is correctly aligned with the small circle marking pin 1, which on sprut, is next to Y1 (RTC crystal). All capacitors are in place as specified by the datasheet for the F412.
(NOTE: Everything connected to PA9 and PA10 desoldered!)
Without the USART adapter connected PA9 and PA10 are low, non driven. With the USART adapter connected with the 100k pull-ups PA9 and PA10 are always high when no connection is established as expected. Adapter pulls down RX line to establish connection but MCU does not respond on TX line.
I'll test some more and see if I can figure anything out, but right now I'm thinking of designing a functioning brainboard that only has the necessary parts to have a running F412 and then migrate the design over to sprut 1C when that brainboard works as expected. Should be easier to figure out a working solution that way.
(NOTE: Everything connected to PA9 and PA10 desoldered!)
Without the USART adapter connected PA9 and PA10 are low, non driven. With the USART adapter connected with the 100k pull-ups PA9 and PA10 are always high when no connection is established as expected. Adapter pulls down RX line to establish connection but MCU does not respond on TX line.
I'll test some more and see if I can figure anything out, but right now I'm thinking of designing a functioning brainboard that only has the necessary parts to have a running F412 and then migrate the design over to sprut 1C when that brainboard works as expected. Should be easier to figure out a working solution that way.
-
- Posts: 32
- Joined: Mon Aug 19, 2019 10:40 pm
- Location: Los Gatos CA USA
Re: Sprut - A newbies try to design an ECU
I always designed my boards with a 4 pin "Discovery" programming header -- the one matching the early Discovery board programming SWD pinout. That made checking the functionality of the chip easy.
You might be able to deduce something by putting the STM32 into boot mode e.g. holding down the BOOT1 pushbutton. That enables the output drivers of some pins as described in
https://www.st.com/content/ccc/resource/technical/document/application_note/b9/9b/16/3a/12/1e/40/0c/CD00167594.pdf/files/CD00167594.pdf/jcr:content/translations/en.CD00167594.pdf
You might be able to deduce something by putting the STM32 into boot mode e.g. holding down the BOOT1 pushbutton. That enables the output drivers of some pins as described in
https://www.st.com/content/ccc/resource/technical/document/application_note/b9/9b/16/3a/12/1e/40/0c/CD00167594.pdf/files/CD00167594.pdf/jcr:content/translations/en.CD00167594.pdf
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
All of the measurements in the post above were taken in boot mode. I've yet to get it to communicate correctly with a pc nor uploaded any firmware.DonaldBecker wrote: ↑Thu Nov 07, 2019 4:28 pmI always designed my boards with a 4 pin "Discovery" programming header -- the one matching the early Discovery board programming SWD pinout. That made checking the functionality of the chip easy.
You might be able to deduce something by putting the STM32 into boot mode e.g. holding down the BOOT1 pushbutton. That enables the output drivers of some pins as described in
https://www.st.com/content/ccc/resource/technical/document/application_note/b9/9b/16/3a/12/1e/40/0c/CD00167594.pdf/files/CD00167594.pdf/jcr:content/translations/en.CD00167594.pdf
- Dron_Gus
- contributor
- Posts: 460
- Joined: Wed Nov 13, 2013 1:11 pm
- Location: S-Pb
- Github Username: dron0gus
Re: Sprut - A newbies try to design an ECU
Try swapping Rx and Tx. This always helps.
-
- Posts: 23
- Joined: Thu Sep 26, 2019 9:59 pm
Re: Sprut - A newbies try to design an ECU
Tried with swapping the Rx and Tx, nothing happens. I'm pretty sure my adapter works as I've recently flashed firmware on my 3D printer with it.
-
- Posts: 32
- Joined: Mon Aug 19, 2019 10:40 pm
- Location: Los Gatos CA USA
Re: Sprut - A newbies try to design an ECU
In boot1 update mode pins related to the active interfaces will switch from floating to being actively driven. It's a good way to verify that the processor is working, especially comparing to reset into normal mode.
-
- contributor
- Posts: 435
- Joined: Mon Mar 04, 2019 10:19 pm
- Location: Slovakia
Re: Sprut - A newbies try to design an ECU
..try to disconnect RESET pin after power-up .. ..
.. some Proteus and microRusEFI for sale in Europe ..
-
- running engine in first post
- Posts: 1495
- Joined: Mon Jan 30, 2017 2:05 am
- Location: Seattle-ish
Re: Sprut - A newbies try to design an ECU
Do you have SWD wired? If so you can attach a debugger and see what it's doing (or not doing).