<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">printf("data test return %04x\n", memTestDataBus(0x68000002));<br><br> <br> printf("addr bus test return %04x\n", memTestAddressBus(0x68000000, 1024*1024));</blockquote><div><br></div><div>memtest all passed at application mode,</div><div><br></div><div>when SRAM init function moves to
<span class="gmail-im">bsp_start_hook_1 then not work</span></div><div><span class="gmail-im">Can i do init_main_osc in bsp_start_hook_1?</span>
</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jun 18, 2019 at 1:25 PM Christian Mauderer <<a href="mailto:christian.mauderer@embedded-brains.de">christian.mauderer@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 18/06/2019 07:17, Jython wrote:<br>
> void SRAM_fsmc_setup(void)<br>
> {<br>
> unsigned char FSMC_Bank;<br>
> int i = 0;<br>
> <br>
> // enable port clk<br>
> RCC_AHB1ENR |= 0x0f << 3;<br>
> RCC_AHB3ENR |= 1; // enable fsmc clock<br>
> <br>
> // af A0-A18<br>
> stm32f4_gpio_config temp = STM32F4_PIN_FSMC(5, 0,<br>
> STM32F4_GPIO_AF_FSMC);<br>
> <br>
> <br>
> for(i = 0; i < 6; i++) //pf0-5<br>
> {<br>
> <br>
> <br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(5, i);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(5, i);<br>
> stm32f4_gpio_set_config(&temp);<br>
> }<br>
> <br>
> // A6 PF12<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(5, 12);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(5, 12);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // A7 PF13<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(5, 13);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(5, 13);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // A8 PF14<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(5, 14);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(5, 14);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // A9 PF15<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(5, 15);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(5, 15);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> <br>
> // PG0-5 A10-A15<br>
> for(i = 0; i < 6; i++)<br>
> {<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(6, i);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(6, i);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> }<br>
> <br>
> <br>
> // a16 - pd11<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 11);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 11);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> //A17<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 12);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 12);<br>
> stm32f4_gpio_set_config(&temp);<br>
> //A18<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 13);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 13);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // address bus end<br>
> <br>
> <br>
> // dbus setting<br>
> // D0 PD14<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 14);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 14);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // D1 PD15<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 15);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 15);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // D2 PD0<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 0);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 0);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // D3 PD1<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 1);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 1);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> // D4-12 Pe7<br>
> for(i = 4; i < 13; i++)<br>
> {<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(4, i+3);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(4, i+3);<br>
> stm32f4_gpio_set_config(&temp);<br>
> }<br>
> <br>
> // d13 14 15 pd8<br>
> for(i = 13; i < 16; i++)<br>
> {<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, i-5);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, i-5);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> }<br>
> <br>
> <br>
> //pg10 ne3<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(6, 10);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(6, 10);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> //NBL pe0 pe1<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(4, 0);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(4, 0);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(4, 1);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(4, 1);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> //pd4 NOE<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 4);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 4);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> //pd5 NWE<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 5);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 5);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> //pd6 NWAIT<br>
> temp.fields.pin_first = STM32F4_GPIO_PIN(3, 6);<br>
> temp.fields.pin_last = STM32F4_GPIO_PIN(3, 6);<br>
> stm32f4_gpio_set_config(&temp);<br>
> <br>
> <br>
> <br>
> //The SRAM is connected to the second FSMC BANK (NE2)<br>
> FSMC_Bank = 1;<br>
> <br>
> STM32_FSMC_BCR3 |= 1<<12;<br>
> STM32_FSMC_BCR3 |= 1<<4; //16bit<br>
> <br>
> //<br>
> STM32_FSMC_BTR3 |= 1<<8; // Data-phase duration DATAST <br>
> //STM32_FSMC_BTR3 |= ~(uint32_t)(1<<4);<br>
> //STM32_FSMC_BTR3 &= ~(uint32_t)1;<br>
> STM32_FSMC_BTR3 &= 0xffffff00;<br>
> <br>
> <br>
> STM32_FSMC_BWTR3 = 0x0FFFFFFF;<br>
> STM32_FSMC_BCR3 |= 1; //memory bank enable<br>
> <br>
> #if 0<br>
> /<br>
> FSMC_Bank1->BTCR[FSMC_Bank+1] = (FSMC_BTR2_ADDSET_1) |<br>
> (FSMC_BTR2_DATAST_0 | FSMC_BTR2_DATAST_1);<br>
> <br>
> <br>
> <br>
> #endif<br>
> }<br>
> <br>
> <br>
> it is my later application code, i will try it , thanks! <br>
<br>
You noted that there is a stm32f4_gpio_set_config_array function too<br>
that could be used to initialize more than one pin?<br>
<br>
If you have some debugger available it would be good to check the<br>
stm32f4_gpio_set_config. It enables some clocks which uses a interrupt<br>
disable / enable. That should work but I'm not 100% sure.<br>
<br>
Please take a look at the STM initialization code too whether someone<br>
disables clocks or pins again later.<br>
<br>
For your application code: You could switch back to the default linker<br>
command file and add the mem test.<br>
<br>
> <br>
> On Tue, Jun 18, 2019 at 1:09 PM Christian Mauderer<br>
> <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>> wrote:<br>
> <br>
> On 18/06/2019 03:25, Jython wrote:<br>
> > my linkscmd is<br>
> <a href="https://gist.github.com/goog/aad6dae4c418255dd6fb2b23bf2e6f08" rel="noreferrer" target="_blank">https://gist.github.com/goog/aad6dae4c418255dd6fb2b23bf2e6f08</a><br>
> ><br>
> > void BSP_START_TEXT_SECTION bsp_start_hook_1(void)<br>
> > {<br>
> > SRAM_fsmc_setup();<br>
> > bsp_start_copy_sections();<br>
> > bsp_start_clear_bss();<br>
> ><br>
> > /* At this point we can use objects outside the .start<br>
> section */<br>
> > }<br>
> ><br>
> ><br>
> > but now my code run disordered<br>
> <br>
> Which one?<br>
> <br>
> The SRAM_fsmc_setup()? In that case please note that you are in a very<br>
> early initialization step. So most system services won't work and global<br>
> variables are not initialized yet.<br>
> <br>
> Or your later application code? In that case: Did you do a memory test<br>
> to check your RAM initialization? For example the routines from Michael<br>
> Barr from here work well:<br>
> <a href="http://www.esacademy.com/en/library/technical-articles-and-documents/miscellaneous/software-based-memory-testing.html" rel="noreferrer" target="_blank">http://www.esacademy.com/en/library/technical-articles-and-documents/miscellaneous/software-based-memory-testing.html</a><br>
> <br>
> ><br>
> > On Mon, Jun 17, 2019 at 2:45 PM Christian Mauderer<br>
> > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>> wrote:<br>
> ><br>
> > If you put any sections into the external RAM that need<br>
> initialization,<br>
> > you have to init the RAM before the BSP copies it's sections.<br>
> The STM32<br>
> > BSP copies it's sections in bsp_start_hook_1(). So either put<br>
> it in<br>
> > bsp_start_hook_0 or in bsp_start_hook_1 before the<br>
> copy_section calls.<br>
> > Attention: You can't use much in these functions. They are in<br>
> a very<br>
> > early initialization stage. So be careful what you put there.<br>
> ><br>
> > If you only want malloc to allocate memory from there, there<br>
> might is a<br>
> > later point where you can do that.<br>
> ><br>
> > On 17/06/2019 08:32, Jython wrote:<br>
> > > Thank you and the example! that is to say put extern sram<br>
> init in<br>
> > > bsp_start( void ) function?<br>
> > ><br>
> > > On Mon, Jun 17, 2019 at 1:04 PM Christian Mauderer<br>
> > > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>> wrote:<br>
> > ><br>
> > > On 17/06/2019 03:05, Jython wrote:<br>
> > > > STM32:<br>
> > > > 112KB at 2000 0000<br>
> > > > 16KB at 2001 C000<br>
> > > ><br>
> > > > external sram : 1MB at 0x68000000<br>
> > > ><br>
> > > > does MEMORY layout support RAM2?<br>
> > ><br>
> > > Hello Jython,<br>
> > ><br>
> > > you can distribute the regions to the two RAMs. For example<br>
> > this BSP<br>
> > > does that:<br>
> > ><br>
> > > <br>
> > <br>
> <a href="https://git.rtems.org/rtems/tree/bsps/arm/lpc32xx/start/linkcmds.lpc32xx_phycore" rel="noreferrer" target="_blank">https://git.rtems.org/rtems/tree/bsps/arm/lpc32xx/start/linkcmds.lpc32xx_phycore</a><br>
> > ><br>
> > > Please note that you have to take a detailed look at what is<br>
> > used till<br>
> > > your external RAM initialization run and what not. But<br>
> if you<br>
> > put your<br>
> > > external RAM initialization in an early enough step, you<br>
> > shouldn't get<br>
> > > problems with that.<br>
> > ><br>
> > > Best regards<br>
> > ><br>
> > > Christian<br>
> > ><br>
> > > ><br>
> > > > On Fri, Jun 14, 2019 at 10:13 PM Christian Mauderer<br>
> > > > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>>> wrote:<br>
> > > ><br>
> > > > If you have already added the chip and it is<br>
> initialized<br>
> > > during startup,<br>
> > > > you most likely have to add a section for it in<br>
> your linker<br>
> > > command<br>
> > > > file. Depending on where your internal RAM is<br>
> located and<br>
> > > where the<br>
> > > > external one is: If they are continuous that can<br>
> be enough.<br>
> > > ><br>
> > > > Best regards<br>
> > > ><br>
> > > > Christian<br>
> > > ><br>
> > > > On 14/06/2019 04:42, Jython wrote:<br>
> > > > > we have added 1M ram by FSMC, and want to<br>
> manage it by<br>
> > > system malloc<br>
> > > > > controler<br>
> > > > ><br>
> > > > > On Fri, Jun 14, 2019 at 10:26 AM Mr. Andrei Chichak<br>
> > > > <<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>><br>
> > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>>><br>
> > > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>><br>
> > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>>>><br>
> > > > > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>><br>
> > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>>><br>
> > > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>><br>
> > <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>><br>
> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a> <mailto:<a href="mailto:groups@chichak.ca" target="_blank">groups@chichak.ca</a>>>>>>> wrote:<br>
> > > > ><br>
> > > > > A 407 doesn’t normally have external RAM.<br>
> > > > ><br>
> > > > > ARMs have flash at 0 and the 407 has RAM at<br>
> 0x2000<br>
> > 0000<br>
> > > as you<br>
> > > > > discussed earlier.<br>
> > > > ><br>
> > > > > If you want to work with external flash or RAM,<br>
> > you have<br>
> > > to set up<br>
> > > > > the FSMC or FMC to support it, but that isn’t a<br>
> > part of<br>
> > > the dev<br>
> > > > > board that Sebastian used for the BSP port.<br>
> > > > ><br>
> > > > > The external memory is going to be very specific<br>
> > to your<br>
> > > board.<br>
> > > > > Which board are you working with?<br>
> > > > ><br>
> > > > > A<br>
> > > > ><br>
> > > > > > On 2019-June-13, at 06:23, Christian Mauderer<br>
> > > > > <<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>><br>
> > > > > <br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>>>> wrote:<br>
> > > > > ><br>
> > > > > > On 05/06/2019 02:55, Jython wrote:<br>
> > > > > >> Hello!<br>
> > > > > >><br>
> > > > > >> 2. In the normal (non-debugging)<br>
> case, the<br>
> > linker<br>
> > > > script still<br>
> > > > > >> places the<br>
> > > > > >><br>
> > > > > >> .text section near zero, but places the<br>
> > start of the<br>
> > > > .data and<br>
> > > > > .bss<br>
> > > > > >> sections at the start location of the<br>
> MPC555's<br>
> > > internal<br>
> > > > RAM. The<br>
> > > > > >> system startup code then configures<br>
> the external<br>
> > > RAM just<br>
> > > > > after the<br>
> > > > > >> internal RAM in memory, forming one<br>
> large block<br>
> > > from the<br>
> > > > two RAM<br>
> > > > > >> devices.<br>
> > > > > >><br>
> > > > > >> from<br>
> <a href="https://devel.rtems.org/wiki/TBR/BSP/Ss555" rel="noreferrer" target="_blank">https://devel.rtems.org/wiki/TBR/BSP/Ss555</a><br>
> > > > > >><br>
> > > > > >> but i dont know how to configure the external<br>
> > RAM just<br>
> > > > after the<br>
> > > > > >> internal RAM in memory?<br>
> > > > > >> hope you could give me some guide!<br>
> > > > > >> <br>
> > > > > >><br>
> > > > > ><br>
> > > > > > Hello Jython,<br>
> > > > > ><br>
> > > > > > the documentation you linked is for an<br>
> MPC. But your<br>
> > > subject<br>
> > > > line<br>
> > > > > > mentions an STM32. What controller / BSP<br>
> are you<br>
> > using?<br>
> > > > > ><br>
> > > > > > Best regards<br>
> > > > > ><br>
> > > > > > Christian Mauderer<br>
> > > > > > --<br>
> > > > > > --------------------------------------------<br>
> > > > > > embedded brains GmbH<br>
> > > > > > Herr Christian Mauderer<br>
> > > > > > Dornierstr. 4<br>
> > > > > > D-82178 Puchheim<br>
> > > > > > Germany<br>
> > > > > > email:<br>
> <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>><br>
> > > > > <br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>>><br>
> > > > > > Phone: +49-89-18 94 741 - 18<br>
> > > > > > Fax: +49-89-18 94 741 - 08<br>
> > > > > > PGP: Public key available on request.<br>
> > > > > ><br>
> > > > > > Diese Nachricht ist keine geschäftliche<br>
> > Mitteilung im<br>
> > > Sinne<br>
> > > > des EHUG.<br>
> > > > > ><br>
> _______________________________________________<br>
> > > > > > users mailing list<br>
> > > > > > <a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>><br>
> > > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>>><br>
> > > > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>><br>
> > > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>>>><br>
> > > > > > <a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
> > > > ><br>
> > > > ><br>
> > > > > _______________________________________________<br>
> > > > > users mailing list<br>
> > > > > <a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>><br>
> > > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>><br>
> > <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>><br>
> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a> <mailto:<a href="mailto:users@rtems.org" target="_blank">users@rtems.org</a>>>>><br>
> > > > > <a href="http://lists.rtems.org/mailman/listinfo/users" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/users</a><br>
> > > > ><br>
> > > ><br>
> > > > --<br>
> > > > --------------------------------------------<br>
> > > > embedded brains GmbH<br>
> > > > Herr Christian Mauderer<br>
> > > > Dornierstr. 4<br>
> > > > D-82178 Puchheim<br>
> > > > Germany<br>
> > > > email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>>><br>
> > > > Phone: +49-89-18 94 741 - 18<br>
> > > > Fax: +49-89-18 94 741 - 08<br>
> > > > PGP: Public key available on request.<br>
> > > ><br>
> > > > Diese Nachricht ist keine geschäftliche Mitteilung<br>
> im Sinne<br>
> > > des EHUG.<br>
> > > ><br>
> > ><br>
> > > --<br>
> > > --------------------------------------------<br>
> > > embedded brains GmbH<br>
> > > Herr Christian Mauderer<br>
> > > Dornierstr. 4<br>
> > > D-82178 Puchheim<br>
> > > Germany<br>
> > > email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>>><br>
> > > Phone: +49-89-18 94 741 - 18<br>
> > > Fax: +49-89-18 94 741 - 08<br>
> > > PGP: Public key available on request.<br>
> > ><br>
> > > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne<br>
> > des EHUG.<br>
> > ><br>
> ><br>
> > --<br>
> > --------------------------------------------<br>
> > embedded brains GmbH<br>
> > Herr Christian Mauderer<br>
> > Dornierstr. 4<br>
> > D-82178 Puchheim<br>
> > Germany<br>
> > email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> > <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>>><br>
> > Phone: +49-89-18 94 741 - 18<br>
> > Fax: +49-89-18 94 741 - 08<br>
> > PGP: Public key available on request.<br>
> ><br>
> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne<br>
> des EHUG.<br>
> ><br>
> <br>
> -- <br>
> --------------------------------------------<br>
> embedded brains GmbH<br>
> Herr Christian Mauderer<br>
> Dornierstr. 4<br>
> D-82178 Puchheim<br>
> Germany<br>
> email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
> <mailto:<a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a>><br>
> Phone: +49-89-18 94 741 - 18<br>
> Fax: +49-89-18 94 741 - 08<br>
> PGP: Public key available on request.<br>
> <br>
> Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
> <br>
<br>
-- <br>
--------------------------------------------<br>
embedded brains GmbH<br>
Herr Christian Mauderer<br>
Dornierstr. 4<br>
D-82178 Puchheim<br>
Germany<br>
email: <a href="mailto:christian.mauderer@embedded-brains.de" target="_blank">christian.mauderer@embedded-brains.de</a><br>
Phone: +49-89-18 94 741 - 18<br>
Fax: +49-89-18 94 741 - 08<br>
PGP: Public key available on request.<br>
<br>
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.<br>
<br>
<br>
</blockquote></div>