STM32H730ZB - SDRAM BANK1 wrong address

[COSEBE]

Hi,

 

I create a new project with STM32CubeIde 1.15.1 (but same with 1.10.1)

I add SDRAM 1 - BANK 1

When I debug this project, after HAL_SDRAM_Init function in MX_FMC_Init(), I can wath the memory in MEMORY BROWSER at address 0x60000000.

But on reference manual, SDRAM should be at 0xC0000000.

I select Default mapping in Bank Mapping :

 

If I select bank swapped, I have my datas at 0xC0000000.

Is it a bug of STM32CubeIDE ?

 

 

[KDJEM.1]

Hello @COSEBE ,

 

Thank you for bringing this issue to our attention.

I reported internally.

The internal ticket 184015 (not accessible by community users) has been opened to confirm and fix the issue.

Thank you for your contribution in STCommunity.

 

Kaouthar

[COSEBE]

Hi Kaouthar,

Did you manage to reproduce the problem?

Is it a known problem?

Should I continu to investigate the problem?

 

[KDJEM.1]

Hi @COSEBE ,

 

I reproduced the problem and I reported internally to our STM32CubeMx team for confirmation and fix.

Also, I checked FMC_SDRAM  example and it works correctly. For that, I recommend you to start with this example.

I think that SDRAM Initialization sequence shared in this FAQ How to set up the FMC peripheral to interface with... - STMicroelectronics Community can help you. 

I will come back to you for more details as soon as possible.

Thank you.

Kaouthar

 

 

[Tesla DeLorean]

Honestly I think this problem is compounded because the Hardware has 0 / 1 signal designations, and then you refer to SDRAM Bank 1 and Bank 2, and the SDRAM chip itself has it's own understanding of "banks", with BA0 / BA1

ie

SDNE0 / SDCKE0 -> SDRAM1 aka BANK 1 -> 0xC0000000

SDNE1 / SDCKE1 -> SDRAM2 aka BANK 2 -> 0xD0000000

Given how systemic this has become, going to hard to rationalize it now..

[COSEBE]

Well, if that, It should be on every STM32H7, but it woks with STM32H7B3.

If that, I should have wrong address 0xC0000000 / 0xD0000000 but not 0xC0000000 / 0x60000000

[Tesla DeLorean]

Well this gets into another set of issues where the H7 family has at least 3 different die and they all behave differently, have different speeds and peripherals and occasionally have incompatible AF Mux settings.

H74x/H75x

H72x/H73x

H7Ax/H7Bx

[COSEBE]

On example project you mentioned :

https://github.com/STMicroelectronics/STM32CubeH7/tree/master/Projects/STM32H743I-EVAL/Examples/FMC/FMC_SDRAM

Without modify anything, in the main file, juste after 

if(HAL_SDRAM_Init(&hsdram, &SDRAM_Timing) != HAL_OK) ==> line 118

I can access at address 0x60000000 instead of 0xD0000000 on memory window of STM32CubeIde 1.15.1

0x60000000 have data

0xD0000000 still have ????????? on memory

[Tesla DeLorean]

Isn't 0x60000000 the NOR FLASH on the STM32H743I-EVAL board?

What about after it's finished SDRAM_Initialization_Sequence() ??

https://github.com/STMicroelectronics/STM32CubeH7/blob/master/Projects/STM32H743I-EVAL/Examples/FMC/FMC_SDRAM/Src/main.c#L125

or 

https://github.com/STMicroelectronics/STM32CubeH7/blob/master/Projects/STM32H743I-EVAL/Examples/FMC/FMC_SDRAM/Src/system_stm32h7xx.c#L367