STM32F4 Discovery / Core PCB Bootloader Question

Testing/Troubleshooting
1

I have used the software provided by ST to input the bootloader into the Discovery Unit when plugged into the PCB.  I have a very small number of components on the PCB .  (Namely IC1 and IC2 and their capacitors and the R33 resistor network)

 

The problem I found was that the ST Link software would not recognise the bootloader hex file. 

I messed around a bit and the tried the exercise again this time using the Discovery unit on its own. The hex file was recognised and the bootloader apparently loaded. 

 

Is this normal?  I am wondering whether there is a problem due to there being no power on the IC’s.

 

Maybe someone can explain.

 

Regards Robin 

2

I guess that this issue has been solved meanwhile, right?

 

Best Regards, Thorsten.

3

Thorsten

 

I have been re-reading the bootloader articles.  I note that the LED on the STM device has to flash twice when the bootloader is installed.  

 

I would say that that it is flashing three times.  What does this mean?  

 

The reason for this query is that there is no response to MIOS STUDIO after installing Tutorial 5 with shorting pins to ground on J5A.  This makes me doubt whether the bootloader is installed.

 

The ST utility seems to load the bootloader and shows verification.

 

Can I use MIOS Studio to show if the Bootloader is installed?

 

I am getting nowhere fast.

 

Thanks for your help. Robin

4

Hi Robin,

 

sometimes the LED flashes three times, that’s normal and no problem.

 

Since the LED is flashing, it’s ensured that the bootloader is installed properly.

No need to work with the ST Utility anymore.

 

 

no response to MIOS STUDIO after installing Tutorial 5 with shorting pins to ground on J5A

 

Connect a button and toggle it, or just disconnect/connect the cable.

Whenever you are doing this a Note Event should be sent.

 

 

makes me doubt whether the bootloader is installed.

 

very unrelated to the Bootloader.

 

I guess that you are able to select the MIDI IN/OUT port of your core module in MIOS Studio, right?

And the Query button returns some board informations, right?

This would mean that the application is running successfully.

 

Did you already try out other tutorial applications?

 

Best Regards, Thorsten.

5

Thorsten

 

Thanks for the confirmation.  The Query button causes code in both monitor displays. Yes I can select MIOS32 and Juce ports.

 

However I cannot trigger Note Events on J5a for some reason.  I have measured the input voltage of J5B pins with a multimeter, they are about 0.3 volts.

 

Robin

6

Hi Robin,

 

are they even 0.3V if the inputs are not connected to ground?

(they should be around 3V instead since an internal pull-up is activated)

 

Maybe you are checking the wrong pins of the J5* sockets?

5 pins of the “inner” side are Vd + 4 inputs, 5 pins of the “outer” side are ground.

 

Best Regards, Thorsten.

7

Hi Thorsten

 

Yes the pin voltages are correct.  On J5B pins A4,A5,A6 and A7 all measure  approx .3 V to ground.

 

Robin

 

 

They are all connected to the correct STM Discovery Pins

 

 Pin A3 is lower , 0.2V

 

 

PS This morning I got quite excited. I thought I had discovered the problem. In looking at the makefile list after compiling I found that there was no reference to the BOARD variable.  Unfortunately correcting this has made no difference to the voltages on J5

8

Hi Robin,

 

how did you set the environment variables exactly?

 

Here a prebuilt file to doublecheck if it’s working better with correctly set variables:

http://www.ucapps.de/tmp/005_polling_j5_pins.zip

 

Best Regards, Thorsten.

9

Hello Thorsten

 

I used Linux.

 

Here is part of the profile file where I set the Env Variables permanently.

 

export PATH=$PATH:/usr/local/mios32_toolchain/bin

export MIOS32_PATH=~/midibox/mios32/trunk

export MIOS32_BIN_PATH=$MIOS32_PATH/bin

export MIOS32_GCC_PREFIX=arm-none-eabi

export MIOS32_FAMILY=STM32F4xx

export MIOS32_PROCESSOR=STM32F407VG

export MIOS32_LCD=universal

export MIOS32_BOARD=MBHP_CORE_STM32F4

 

 

I realise that you want me to use your project hex file.  I’ll check it out.

 

Robin

10

Thorsten

 

It works!

 

The pin voltages on J5 are about 3V and I have received an event.

 

My toolchain file

 

 /usr/local/mios32_toolchain/bin consists of 27 arm_none_eabi files each with different endings

 

 

Robin

 

Here is the result after compile using my data not yours.  I have now changed the Board env variable to that shown below

 

 

s $ make

rm -f project.hex

Application successfully built for:

Processor: STM32F407VG

Family:    STM32F4xx

Board:     MBHP_CORE_STM32F4DISCOVERY

LCD:       universal

arm-none-eabi-size project_build/project.elf

   text   data    bss    dec    hex filename

  57328    104  16296  73728  12000 project_build/project.elf

20000000 D __ram_start

20004010 B __ram_end

robinfawell@robinoffice ~/midibox/mios32/trunk/apps/tutorials/005_polling_j5_pins $ 

 

  But this doesn’t work!  No events - J5 pins at 0.3V

 

Here is a svn update

 

robinfawell@robinoffice ~/midibox/mios32 $ svn update

Updating ‘.’:

At revision 2084.

robinfawell@robinoffice ~/midibox/mios32 $ 

 

11

I have to report a complete failure in trying to follow the linux gcc toolchain download and file setup.

 

specifically 

 

sudo wget http://www.//www.midibox org/mios32_toolchain/gcc-arm-none-eabi-xxxxxx.tar.bz2

 

and the next line

 

sudo tar zxvf-gcc-arm-none-eabi-xxxxxx.tar.bz2

 

The text asks for xxxxxx to be replaced by the date of the latest tool chain. 

 

I have tried 

 

4_7-2013q3

 

2013q3

 

20130619

 

I have tried adding “linux” after the date. Nothing seems to work.

 

I’m obviously missing something important.

 

However,  I’ve gone back to Win 7 where I can compile correctly.  I have used tutorial 005 and can generate Midi events using shorting links on J5A/B

 

 

If anybody can suggest a solution for the linux problems, I will appreciate the help.

 

 

Robin

12

Hi Robin,

 

why are you still trying to use wget?

We already clarified, that wget is currently not working, and you wrote how you solved this (by directly downloading the file with your webbrowser):

http://discourse.midibox.org/t/topic/18627

 

After download, just unpack the file with “tar zxvf <filename>”

Replace <filename> by the filename of the file that you’ve downloaded - it’s that simple! :wink:

 

Best Regards, Thorsten.

13

Thorsten

 

Thanks for your reply.  I persisted mainly to improve my knowledge of Linux.

 

Robin