Wednesday, January 24th 2018, 6:50am UTC+1

You are not logged in.

  • Login
  • Register

Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Date of registration: May 20th 2015

Posts: 8

Location: NJ, USA

Occupation: Embedded Engineer

1

Wednesday, June 10th 2015, 5:47am

STM32F429I-EVAL1 demo for emIDE,emOSIP,emWIN,emFS

After seeing that Seeger has a demo for their products using a demo pcb I have I wanted to try it out before I bought the Keil tool, because this demo has a 4.3LCD screen in it and TCPIP as well.

But I had some problems getting TCPIP up and running with the demo. I opned the demo up in emIDE w/o modifying anything first then I wanted to add IP and Webserver. Well I did not see DHCP ask for an IP and I ran out of RAM very quickly after enabling IP.


1. TCPIP, HTTP & DHCP
a. I enabled IP and web server in SysConf.h (See below) Once I did this I saw WebServer.c was included after I built it and burned.
1.It does not look like DHCP is on, No host with the MAC address listed in IP_Init_X() defined requested an IP from my DHCP server.
** Then I Noticed in SeggerDemo.c where INCLUDED_IP, the next line is grayed out even though in SysConf.h it is defined as 1. And the same things happened for INCLUDED_WEBSERVER.
I attached a pic of this.
I am thinking this is why the pcb did not request an IP from my DHCP server.

Did I miss any other configs for TCPIP to get Web Server running other than whats in SysConf.h?
If not what should I look for next?



2. Next problem is it ran out of RAM very fast, like it was not using the 256Mb external SDRAM that is on the demo pcb. But I see it is calling a function in BSPInit.c to initialize the SDRAM.
To get around this for now I just disabled a bunch of the GUI demos but still just made it under when TCPIP was enabled.
I opened the MAP file and it shows last data placed in RAM location of 0x2001dab4 which is like 121K, that should be well within the internal let alone external.
Does this demo use the external SDRAM by default or do I have to configure it somewhere?
If it does use external why is emIDE telling me it is out of RAM.





3. Is there a user manual for the demos?






Here is where enabled IP and Web Server in SysConf.h

/*********************************************************************
*
* Included middleware components
*
**********************************************************************
*/
#ifndef INCLUDE_GUI
#define INCLUDE_GUI (1)
#endif
#ifndef INCLUDE_IP
#define INCLUDE_IP (1)
#endif
#ifndef INCLUDE_FTP
#define INCLUDE_FTP (0)
#endif
#ifndef INCLUDE_WEBSERVER
#define INCLUDE_WEBSERVER (1)
likeitlowlevel has attached the following image:
  • emIDE_err.png

This post has been edited 1 times, last edit by "likeitlowlevel" (Jun 10th 2015, 6:36am)


SEGGER - Martin

Super Moderator

Date of registration: Jul 1st 2014

Posts: 34

2

Thursday, June 11th 2015, 5:26pm

Dear likeitlowlevel,

Quoted

1.It does not look like DHCP is on, No host with the MAC address listed in IP_Init_X() defined requested an IP from my DHCP server.
** Then I Noticed in SeggerDemo.c where INCLUDED_IP, the next line is grayed out even though in SysConf.h it is defined as 1. And the same things happened for INCLUDED_WEBSERVER.
Having INCLUDE_IP set to 1 in SysConf.h is all you need to include embOS/IP into the Seggerdemo application sample; the eval software package uses DHCP by default.
emIDE's code highlighting is somewhat misleading in this case, as it might fail to highlight properly in certain circumstances.

I have tried to reproduce the problem, but found that my target was assigned an IP address after including embOS/IP in SysConf.h without any further changes to the software package. In a next step, by using a network sniffer such as WireShark, you may check if your target is actually sending a DHCP request. In case you cannot see such request in a sniff, I'd like to ask which jumper settings you are using on your target hardware. On ST's STM32F429I-Eval, JP5 should connect pins 1 and 2 for our software to work properly.

Quoted

2. Next problem is it ran out of RAM very fast, like it was not using the 256Mb external SDRAM that is on the demo pcb.
Your observation is correct: We didn't configure the software to use external SDRAM. As the SDRAM initialization is provided in the package within the device support files, you may still use it to relocate the software's memory pools.

Quoted

3. Is there a user manual for the demos?
Yes, we offer an application note for this purpose. It wasn't available when the package in question was created, but will be included in future releases. You may also download the document via the following link: AN00020_GettingStartedWithSeggerEvalsoftware.pdf

Best regards,
Martin