Jump to content

STM32F4 Problems


Marxon

Recommended Posts

Hi,

 

unfortunately i have some two problems with my new STM32F4 core module.

I uploaded the actual bootloader 1.015 and Midibox NG 1.029 version.

This ports are wired J16, J8/9, J19, J15A and J15_S.

 

Problem 1:

The event Event Pool Allocation is 24480 of 24576 bytes (99%) exactly like

using the LPC1769 core. Shouldn't be there more bytes available :question:

 

Problem 2:

The LCD does not work (backlight and contrast are ok). 

It is a 2x16 HD44780 display.

I have triple checked the wiring and soldering.

 

 

TK, your help is needed :)

 

Best regards

Marxon

 

 

Link to comment
Share on other sites

OK, open MIOS, clear your terminal screen and send load the Bootloader 1.015 hex file - not the MIDIbox NG application.

 

 

-> What does the terminal say at the very top?

 

 

For exmaple, my STM32F4 core isn't hooked to and LCD or anything else and it says:

[386343.822] Initialize LCD #1
[386343.886] Failed - no response from LCD #1.1
[386343.886] Initialize LCD #2
[386343.950] Failed - no response from LCD #2.1
Link to comment
Share on other sites

Also, I just compiled the MIDIbox NG application for the STM32F4 on my pc using the latest SVN source.

 

You can try it out: http://sneak-thief.com/MIDIboxNG/project.hex

 

It loads fine and gives me the appropriate message for my setup:

 

[387180.219] [MBNG_LCD] no response from CLCD #1.1
[387180.220] [MBNG_LCD] no response from CLCD #2.1
Edited by sneakthief
Link to comment
Share on other sites

After uploading your .hex MIOS gives this output:

 

 

[78833.839] Init DHCP
[78834.846] SD Card connected:
[78835.015] [MBNG_FILE_C:317] WARNING: no CC number expected for EVENT_ENC due to type: Disabled
[78835.443] [MBNG_FILE_C] Event Pool Number of Items: 734
[78835.443] [MBNG_FILE_C] Event Pool Allocation: 24480 of 24576 bytes (99%)
[78835.450] [MBNG_FILE_L] DEFAULT.NGL hasn't been changed; reading labels from existing DEFAULT.BIN file.
[78835.451] [MBNG_FILE_L] 7 labels found in /DEFAULT.BIN file
[78835.456] [MBNG_FILE_S] loading snapshot #13 from /DEFAULT.NGS
Link to comment
Share on other sites

Entering "system" into the terminal gives this:

 

 

[78917.869] Application: MIDIbox NG V1.029
[78917.870] MIDI Monitor: disabled
[78917.870] MIDI Monitor Filters: enabled
[78917.870] MIDI Monitor Tempo Display: disabled
[78917.870] Print AOUT Config: TODO
[78917.870] lcd_type: 0x00 - CLCD
[78917.870] lcd_num_x: 1
[78917.870] lcd_num_y: 1
[78917.870] lcd_width: 16
[78917.870] lcd_height: 2
[78917.870] Event Pool Number of Items: 734
[78917.871] Event Pool Allocation: 24480 of 24576 bytes (99%)
Link to comment
Share on other sites

But what does it say when you ONLY load the bootloader, like I asked above?

 

Mine again:

 

[389537.459] Initialize LCD #1
[389537.523] Failed - no response from LCD #1.1
[389537.524] Initialize LCD #2
[389537.587] Failed - no response from LCD #2.1
[389537.588] 
[389537.588] ====================
[389537.589] Bootloader 1.015
[389537.599] ====================
[389537.602] 
[389537.613] Checking Bootloader...
[389537.633] No mismatches found.
[389537.635] The bootloader is up-to-date!
[389537.651] You can upload another application now!
[389537.673] Or type 'help' in MIOS Terminal for additional options!
Edited by sneakthief
Link to comment
Share on other sites

[79878.592] Initialize LCD #1

[79878.649]

[79878.649] ====================

[79878.649] Bootloader 1.015

[79878.660] ====================

[79878.662]

[79878.674] Checking Bootloader...

[79878.751] No mismatches found.

[79878.754] The bootloader is up-to-date!

[79878.769] You can upload another application now!

[79878.791] Or type 'help' in MIOS Terminal for additional options!

Link to comment
Share on other sites

So, we can see that it's "initialized".

 

I think this output below only shows the stored CLCD config and NOT the actual one because it says the same on mine when I type "system" in the MIDIbox NG application:

 

[78917.870] lcd_type: 0x00 - CLCD
[78917.870] lcd_num_x: 1
[78917.870] lcd_num_y: 1
[78917.870] lcd_width: 16
[78917.870] lcd_height: 2
Edited by sneakthief
Link to comment
Share on other sites

At this point, the only possibilities are:

 

1. Dead CLCD

 

- time to test another CLCD?

 

2. Something weird with the software and/or configuration

 

- das Heisst: keine Ahnung... TK! Wo bist du denn? :P

 

 

3. Bad wiring between the STM32F4, the 74HC595 and the CLCD. Did you try another 74HC595?

 

- time to post a picture of your wiring (both sides, high-res please)

Link to comment
Share on other sites

Damn! Kick me in my ass!

I checked everything... Really everything? 

No, i left out the resistor array which turns out to be a 10k ohm array.

:angry: :angry: :angry:

This might be the problem!

I am going to change it and post result in some minutes...

Link to comment
Share on other sites

Hi Thorsten!

 

Nice that you find the error! :smile:

 

Thank you.

Hopefully I've learned something from this issue and i will do a better troubleshooting next time.

 

 

Here a preliminary version which provides more event pool memory for the STM32F4:

http://www.ucapps.de/mios32/midibox_ng_v1_030_pre1.zip

 

Your preliminary version is working.

Event pool allocations decreased from 99% to 37%.

 

 

Best regards

Marxon

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...