How about other dev boards?

Hardware inside and outside of the ECU
Post Reply
dobrin
contributor
contributor
Posts: 3
Joined: Wed Nov 20, 2013 7:52 am

How about other dev boards?

Post by dobrin »

Hello,

I have a question about HW.
Can you please check if this PCB https://www.olimex.com/Products/ARM/ST/STM32-E407/open-source-hardware have all components needed to join this project.
According to me, it's more advanced version of stm32f4Discovery, but I want second opinion to this :-)

Thanks!
User avatar
AndreyB
Site Admin
Posts: 14328
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: How about other dev boards?

Post by AndreyB »

While this olimex board has pretty much the same chip, it probably has different pinout. You will need to modify at least one file - http://svn.code.sf.net/p/rusefi/code/trunk/firmware/chibios/boards/ST_STM32F4_DISCOVERY/board.c

ChibiIOS probably have the board file for this board, but you would need to take care of replacing the board files locally. The pre-compiled version of the firmware would not work for you. Also, the PCBs which are designed to snap on right on the discovery would not snap on - again, different pinout.

So, you should answer the question: is the hassle of the minor incompatibility worth olimex board benefits?
You can go with either olimex which does have it's benefits the pros like better power supply, or you can choose the easier and cheaper option of stm32f4dicovery :)
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
User avatar
kb1gtt
contributor
contributor
Posts: 3758
Joined: Tue Sep 10, 2013 1:42 am
Location: ME of USA

Re: How about other dev boards?

Post by kb1gtt »

Upon a quick look, I'd say it appears to be mostly there. I'll try to take a closer look. As noted there would be some need for software configuration changes. I don't see any real issues on a quick look.
Welcome to the friendlier side of internet crazy :)
User avatar
acab
provoker
provoker
Posts: 263
Joined: Wed Dec 18, 2013 7:27 pm
Location: Minsk, BY

Re: How about other dev boards?

Post by acab »

I use WaveShare Port407Z.

Work fine =)

Image
TheHeckler
Posts: 8
Joined: Mon Sep 30, 2013 1:33 am

Re: How about other dev boards?

Post by TheHeckler »

It also seems that in several instances the STM32F3 series is better suited for automotive ( mixed signal ) use than the F4.

I know the power of the F4 is tempting but it sure looks like there are more useable features on the F3 and the discovery board is even cheaper.

http://www.st.com/web/en/catalog/tools/FM116/SC959/SS1532/PF254044

This chip's 39 analog inputs lets us include current monitors for injector and ignition drive and other drivers as well as the normal engine sensors.

Configurable analog gain stages, lots of complex timers. The F3 seems a better fit than the F4 series.
User avatar
AndreyB
Site Admin
Posts: 14328
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City
Github Username: rusefillc
Slack: Andrey B

Re: How about other dev boards?

Post by AndreyB »

TheHeckler wrote:The F3 seems a better fit than the F4 series.
Could be.

For me as a developer the FPU is a huge factor. I crave to work with floats since they are the most natural way of doing math. As far as I know F4 - as an example of Cortex M4F core - is a rare example of a microcontroller with FPU. Let's hope that while we are working on the hardware & software a better chip would appear. I am doing all I can to not depend on any particular chip :)
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
TheHeckler
Posts: 8
Joined: Mon Sep 30, 2013 1:33 am

Re: How about other dev boards?

Post by TheHeckler »

The F3 has floating point also/

Key Features

STM32F303VC
Core: ARM®Cortex™-M4 32-bit CPU with FPU (72 MHz max), single-cycle multiplication and HW division, 90 DMIPS (from CCM) /1.25 DMIPS/MHz (Dhrystone 2.1) performance at 0 wait state memory access, DSP instruction and MPU (memory protection unit)
Operating conditions:
VDD, VDDAvoltage range: 2.0 V to 3.6 V
Memories
128 to 256 Kbytes of Flash memory
Up to 40 Kbytes of SRAM, with HW parity check implemented on the first 16 Kbytes.
Routine booster: 8 Kbytes of SRAM on instruction and data bus, with HW parity check (CCM)
CRC calculation unit
Reset and supply management
Power-on/Power-down reset (POR/PDR)
Programmable voltage detector (PVD)
Low power modes: Sleep, Stop and Standby
VBATsupply for RTC and backup registers
Clock management
4 to 32 MHz crystal oscillator
32 kHz oscillator for RTC with calibration
Internal 8 MHz RC with x 16 PLL option
Internal 40 kHz oscillator
Up to 87 fast I/Os
All mappable on external interrupt vectors
Several 5 V-tolerant
12-channel DMA controller
Four ADCs 0.20 μS (up to 39 channels) with selectable resolution of 12/10/8/6 bits, 0 to 3.6 V conversion range, separate analog supply from 2 to 3.6 V
Two 12-bit DAC channels with analog supply from 2.4 to 3.6 V
Seven fast rail-to-rail analog comparators with analog supply from 2 to 3.6 V Take care of the hall effect sensors
Four operational amplifiers that can be used in PGA mode, all terminals accessible with analog supply from 2.4 to 3.6 V Extend the useable range of sensors if needed
Up to 24 capacitive sensing channels supporting touchkey, linear and rotary touch sensors Static proof User interface
Up to 13 timers Injector control
One 32-bit timer and two 16-bit timers with up to 4 IC/OC/PWM or pulse counter and quadrature (incremental) encoder input Pulsewheel sensing
Two 16-bit 6-channel advanced-control timers, with up to 6 PWM channels, deadtime generation and emergency stop
One 16-bit timer with 2 IC/OCs, 1 OCN/PWM, deadtime generation and emergency stop
Two 16-bit timers with IC/OC/OCN/PWM, deadtime generation and emergency stop
Two watchdog timers (independent, window)
SysTick timer: 24-bit downcounter
Two 16-bit basic timers to drive the DAC
Calendar RTC with Alarm, periodic wakeup from Stop/Standby
Communication interfaces
CAN interface (2.0B Active)
Two I2C Fast mode plus (1 Mbit/s) with 20 mA current sink, SMBus/PMBus, wakeup from STOP
Up to five USART/UARTs (ISO 7816 interface, LIN, IrDA, modem control)
Up to three SPIs, two with multiplexed half/full duplex I2S interface, 4 to 16 programmable bit frames
USB 2.0 full speed interface
Infrared transmitter
Serial wire debug, Cortex-M4 with FPU ETM, JTAG
96-bit unique ID
Post Reply