dipCoreF4 and dipBoardF4, a compact Core.

[Phatline]

Hi...normally the pinout to connec 2 Displays...

:

Where to connect DC on the DipCore?

[Antichambre]

With J15.DC pin ;)

 

Edited December 21, 2020 by Antichambre

[Phatline]

ok could you also check if SC RC of J8-9 are ok on this shematic? (is the symbol the actual one?) ... in the past there where Crossed RC SC lines....

[Antichambre]

If I remember well, the pins I crossed on the first proto were J16.SI and J16.SO. J8/9 seems good on your schematic but pin 40 and 39 are still reversed!!!
39 ->J16.SO
40 ->J16.SI

More than that I added the USB Host, it doesn't appear on your pinout.
Note: USB HOST supports:

• USB MIDI Device.
• USB HID Keyboard and Mouse.

attached the eagle lib.

dipCoreF4_v2b.lib

 

Edited December 23, 2020 by Antichambre

[Phatline]

 

dipCoreF4-v2b-KICAD.zip

i converted it into Kicad.... 3 different symbol sizes of the 52pin.

Edited December 23, 2020 by Phatline

[Phatline]

if i want to use the onboard USB not to be onboard? In sense of routing to a Connector on frontpanel... in order to load new code into it.... i mean the one for flashing new Mios Applications...

is this possible, which are pins to go? (a few of them are host-mode i guess)

[Antichambre]

Sorry not the good lib!
This one is fine:

USB1(old) FS, Device/Host, this is the one you have to use, ID is floating for Device Mode, ID to GND for HOST
41 - USB1.ID = ID pin for USB1
46 - VBUS = VBUS for USB1
43 - USB1.DP = USB1 D+
48 - USB1.DM = USB1 D-

USB2(new) HS in FS Mode, Host only.
44 - USB2.DM = USB2 D-
45 - USB2.DP = USB2 D+
49 - USB2.OC = Input for external overcurrent sensor.
50 - USB2.EN = Ouput for external power switcher

dipCoreF4_v2c.lbr

Edited December 23, 2020 by Antichambre

[Phatline]

ok here is the kicad library for the V2C

dipCoreF4-V2c-kicad.zip

(as 3D Modell i took a IC-Socket + a Dip40 IC on it...)

Edited December 27, 2020 by Phatline

[Antichambre]

Thanks! Wiki updated!
http://www.midibox.org/dokuwiki/doku.php?id=dipcoref4#download

Edited December 28, 2020 by Antichambre

[Phatline]

i made a nother design with your Dipcore as brain (clock2audio2clock)

I need one more LED in this shematic:

every pin which is no connected (yellow cross) - i dont need - so these are possible for LED.

any possible? thx 4 help - mike

[Antichambre]

You can use any pin, they are all GPIO(General Purpose In/Out).
You just need declare the port of the pin as not used (MIOS32_DONT_USE_XXX) and use the GPIO_InitTypeDef.

[Phatline]

ok then i  take J16 RC2 (PA4) and J16 RC1 (PC4)

which are used for SD-Card - which i dont need here. so i gues MIOS32_DONT_USE_SDCARD ?

 

@ Type DEF - is this done like on J10 for example:

MIOS32_BOARD_J10_PinInit(0, MIOS32_BOARD_PIN_MODE_OUTPUT_PP);

MIOS32_BOARD_J10_PinSet (0, 1);

for me Clear how to make it with J5 and J10

 

>>>

MIOS32_BOARD_J16_PinInit(0, MIOS32_BOARD_PIN_MODE_OUTPUT_PP); ???

 

thx

 

[Antichambre]

for J16 which is a SPI port

  MIOS32_DONT_USE_SDCARD
  MIOS32_DONT_USE_SPI0

Init

// common
GPIO_InitTypeDef GPIO_InitStructure;
GPIO_StructInit(&GPIO_InitStructure);
GPIO_InitStructure.GPIO_Speed = GPIO_Speed_50MHz;
GPIO_InitStructure.GPIO_Mode = GPIO_Mode_OUT;
GPIO_InitStructure.GPIO_OType = GPIO_OType_PP;
// J16.RC2 as GPIO (PA4)
GPIO_InitStructure.GPIO_Pin = GPIO_Pin_4;
GPIO_Init(GPIOA, &GPIO_InitStructure);
// J16.RC1 as GPIO (PC4)
GPIO_InitStructure.GPIO_Pin = GPIO_Pin_4;
GPIO_Init(GPIOC, &GPIO_InitStructure);

then to set or clear the pins you can use the macro:

// MIOS32_SYS_STM_PINSET(port, pin_mask, value)
// e.g.
MIOS32_SYS_STM_PINSET(GPIOA, GPIO_Pin_4, 0)
MIOS32_SYS_STM_PINSET(GPIOC, GPIO_Pin_4, 1)

 

[Antichambre]

@Phatline close the VBAT jumper, on the bottom side if you use the pin 32 as 3v3 output.

[Phatline]

18 minutes ago, Antichambre said:

@Phatline close the VBAT jumper, on the bottom side if you use the pin 32 as 3v3 output.

Yes need it for a MCP6002 Rail.... is the jumper on the  BOTTOM of the Dipcore?

[Antichambre]

43 minutes ago, Phatline said:

is the jumper on the  BOTTOM of the Dipcore?

yes VBAT smd jumper, just put a bit of solder to close it.

[Phatline]

hmmm... serios problems here
 

when i connecting the dipcore

via Dipcores-onboards USB-Socket to my Laptop (lenovo thinkpad t440p, linux mint):

i get after a few seconds after booting up a:
 

!! HARD FAULT !!

at PC=0x0801afd4

or it doesnt boot at all

it doesnt matter if the Laptop is on battery only, or with PSU-connected (so it isnt a noisy psu)

I doesnt measured a Voltage Dropdown on the USB-RAIL (measered on the PTC) while Hardfaul accours...

i doesnt Activated "Midi via USB" since config is:

#define MIOS32_USE_MIDI
#define MIOS32_USE_UART
#define MIOS32_USE_UART_MIDI
#define MIOS32_UART_NUM 1
#define MIOS32_UART0_ASSIGNMENT 1 //1=Midi, 0= Disabled, 2= COM
#define MIOS32_UART1_ASSIGNMENT 0
#define MIOS32_UART2_ASSIGNMENT 0
#define MIOS32_UART3_ASSIGNMENT 0

(right?)

it doesnt fault (no time) when i connect the same USB to a Mobilphonecharger (2A)

and it doesnt fault ... when running (almost) the same app  on LPC17    >   CV1 ok that tell us NOT much, because the LPC17 is no STM32 chipset...

... also most of the time the Dipcore isnt regognized via MIOS-Studio  - i have to go into Bootload Mode(via Switch) to upload new code.... (i dont scan any J5 or other GPIOs which could force floating data mess)

--- i updatet today the repo from your github... so its actual ( i cant say if it worked before... its long ago since i codet on a dipcore)

 

i tried different USB ports from my laptop, also the one Port which is a "always on to charge whatever usb) make the same hard fault

 

The app doenst boot up on a windows 10 Desktop PC at all (no time!) (no screen content on the SSD1306)

on a other windows 10 Desktop it boots, but it Hardfaults the same way like on my Linux laptop.

 

i bridget the VBAT! (use SD-Card and SSD1306!!!), because i have to supplay a "motherboard" > CV-1-Shematic.pdf

 

i already had deactivated all SD-Card Routines, and Scan Routines, but the machine hangs on almost "background" tasks... so i turned it on again.

here is the APP i programm...

CV-ONE-V0.zip

 

==============================================================0

 i use the bootloader from here: http://wiki.midibox.org/doku.php?id=dipcoref4 >

(i dont change anything in bootloader via Terminal --- i changed the display settings within the app --- so its almost stock)

http://wiki.midibox.org/lib/exe/fetch.php?media=antichambre:dipcoref4_bootlader.zip

i updatedt today the mios repo from: https://github.com/antichambre/MIOS32

gcc-arm-none-eabi is still from 2013 ( i dont updatet anything there)

and of course the environment variables are set correct:

MIOS32_PATH=~/midibox/mios32
MIOS32_BIN_PATH=$MIOS32_PATH/bin
MIOS32_BOARD=MBHP_DIPCOREF4
MIOS32_FAMILY=STM32F4xx
MIOS32_GCC_PREFIX=arm-none-eabi
MIOS32_PROCESSOR=STM32F405RG
MIOS32_LCD=universal

the app is functional as i said but not on computers... on smartphone chargers i dont get a Error!

 

Edited January 24, 2021 by Phatline

[Antichambre]

Please pull changes from repo and retry...
I did something wron last time but corrected it.

There was an issue with usb decriptor.
 

[Antichambre]

10 hours ago, Phatline said:

i doesnt Activated "Midi via USB" since config is:

#define MIOS32_USE_MIDI
#define MIOS32_USE_UART
#define MIOS32_USE_UART_MIDI
#define MIOS32_UART_NUM 1
#define MIOS32_UART0_ASSIGNMENT 1 //1=Midi, 0= Disabled, 2= COM
#define MIOS32_UART1_ASSIGNMENT 0
#define MIOS32_UART2_ASSIGNMENT 0
#define MIOS32_UART3_ASSIGNMENT 0

(right?)

 

#define MIOS32_UART_NUM 1

This line is enough.

[Phatline]

I updatete the repo, and deletedet the uneccersery  lines in mios-config.

 

its no long test, but on the moment its running without HARD-FAULT, and it is recognized in Mios-studio without Bootload-Mode! thx!

BUT

now Display1 stays dark, it is connected to Pin 33, PB12-J15.CS1   (it was working bevore)

Display 2 is working, it is connected to PIN 27, PC0-J15.CS2

Edited January 24, 2021 by Phatline

[Antichambre]

18 minutes ago, Phatline said:

now Display1 stays dark, it is connected to Pin 33, PB12-J15.CS1   (it was working bevore)

I didn't touch that
Be sure the MIOS32_LCD is universal, I know you put the values in MIOS32_config but try also to set them with booloader updater help, set lcd_type too...

Edited January 24, 2021 by Antichambre

[Phatline]

4 hours ago, Antichambre said:

I didn't touch that
Be sure the MIOS32_LCD is universal, I know you put the values in MIOS32_config but try also to set them with booloader updater help, set lcd_type too...

and i didnt change anything except deleting the Midi-lines in MIOS-Config, and updateting the Repo.

i uploadet the Bootloader app again, to change the Display settings manually, but they are already set, like it was bevore (where it was running), buy changing the type from rotating (which i need) to not rotated for example did not change the problem, or by changing the lcd_num x to 1 (two i had)... . no Picture on Booth SSD1306 when using the bootloader app, one display when use-ing my app.

 

i also restored my mios-config settings as they where before... but still one display!

 

I swapped (mios config side) Y to2, and X to 1 - and now it works.... I dont understand this, it was a  X2 Y1 bevore. (crazy)

 

 

ok later the day one display fault again.... (same code) i measured the "Reset" Resistor (1K) and i had 760OHM... the Reset Voltage was about 2.5V.... on the working Display i had 3.3 Volt - and a Resistance from 980 Ohm.... (1Ks are installed)... so i cleaned  the soldering Points of the display, after removing the FLUX i got a Working LCD and a Voltage from 3.3V .... low impadance Flux - GOOD NIGHT!

Edited January 24, 2021 by Phatline

[zaordsword]

Hi !
There is boards used in micropython like the pyboard. It use a Stm32F405GT6 (see here : https://micropython.org/resources/PYBv11-schematics.pdf)
Do you think it could be possible to flash DIPcoref4 version of mios  over those boards ?

[Phatline]

i guess not

the pyboard uses a 12Mhz external crystal? and Mios32 needs?

look at the Pinout:

http://wiki.midibox.org/lib/exe/fetch.php?media=antichambre:pinout_compare_chart2.png

a quick look at for example the SD-Card Pins - of the pyboard and on Dipcore or Discovery stm32F407VG - says that the use other GPIO to do things...

So yes you may flash that pyboard, but the Mhz might not be right (aka need to replace the oscillator)

So yes you might run MIOS afterwards... but you cant use for example the onboard SD-Card - because it is wired to other pins... you have to DO the work that antichambre did (change the GPIO ports in MIOS, make a new toolchain, and that is a Job for someone who knows what he does -  i would be very happy if i could do that - or someone introduce that skill to me- but i dont have any glue about that)

[Antichambre]

Hi,
Mike is right, not like it is!
Crystal frequency change will oblige to change the configuration of the STM deeply to get its perpherals work at the right speed, the sd card uses quad spi instead of single one it's a new module to write, remap all pins etc etc...
Recompile a new bootloader because finally you will need you own version of MIOS32 to make it run. It's possible if you've got time and knowledge(or still more time to learn it).
BR
Bruno