Re: How to build 64bit SDI with MFC? - C / C++ / MFC Discussion Boards

Re: MFC debug version mfc90d.dll issue

kasi146-Jul-10 13:00

kasi14

6-Jul-10 13:00

Thanks Maximilien

can not see progress in the progress Bar

mrby1236-Jul-10 7:51

mrby123

6-Jul-10 7:51

After I add a progess bar on the dialogue box, I added code:
m_progress1.SetRange(0,100);
m_progress1.SetStep(1);
in OnInitDialog(), and m_progress1.SetPos(mmtt);
in the Next(). WHen I tried to run the program, the blue blocks representing the progress can not be seen in the progress bar. In other words, the progress bar is only an empty rectangular grew box when I run the program until finish.

Please help how to make it work.

Thanks

Re: can not see progress in the progress Bar

David Crow6-Jul-10 7:54

David Crow

6-Jul-10 7:54

mrby123 wrote:
...and m_progress1.SetPos(mmtt);
in the Next().

When does Next() get called? What is the value of mmtt?

"One man's wage rise is another man's price increase." - Harold Wilson

"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons

"Man who follows car will be exhausted." - Confucius

Re: can not see progress in the progress Bar

mrby1236-Jul-10 8:19

mrby123

6-Jul-10 8:19

After click the next button in the dialogue box.

Thanks

Re: can not see progress in the progress Bar

Cedric Moonen6-Jul-10 9:54

Cedric Moonen

6-Jul-10 9:54

Are you aware that if you have a lenghty operation in the main thread, UI messages won't be processed until the task is finished ? This means that the UI won't be redrawn and you won't be able to see any progress in the bar until the end of the task (in which case, all messages are processed at once and the progress is full).
A better approach would be to run your lenghty task in a separate thread. I really recommand reading this excellent article[^] about threading.

Cédric Moonen
Software developer

Charting control [v3.0]
OpenGL game tutorial in C++

How to build 64bit SDI with MFC? [modified]

hztj20056-Jul-10 7:24

hztj2005

6-Jul-10 7:24

I need a SDI with MFC in windows sever 2003,vs2005,the CPU is Core 2 Q8200.
I create a SDI with MFC, it can run.
for I need large memory , then I set the configuration x64.
compling error, "MD/switch" off.I set on this switch.
now fatal linking error 1561: entry point need define.
but "theApp" object indeed exist.
(I have a not SDI code in VC,it can run when I set the configuration x64.)
Why?
Please teach me.

Thanks you.

Lee Wen.

modified on Tuesday, July 6, 2010 2:39 PM

Re: How to build 64bit SDI with MFC?

David Crow6-Jul-10 7:52

David Crow

6-Jul-10 7:52

What specific linker error?

Re: How to build 64bit SDI with MFC?

hztj20056-Jul-10 8:29

hztj2005

6-Jul-10 8:29

Thank you!
fatal error Link 1561:need define entry point.

Re: How to build 64bit SDI with MFC?

David Crow6-Jul-10 9:43

David Crow

6-Jul-10 9:43

hztj2005 wrote:
fatal error Link 1561:need define entry point.

Did you see here?

Re: How to build 64bit SDI with MFC?

hztj20057-Jul-10 3:33

hztj2005

7-Jul-10 3:33

fatal error LNK1561: entry point must be defined”

I have build successly,by set the linker/subsystem:windows

Thanks very much.

Winsock problem

masnu6-Jul-10 7:01

masnu

6-Jul-10 7:01

Hi,

I'm trying to enable my ARM development board to communicate with a PC. I can establish a connection and send data from the PC to the micro without any issues. When I try to send data from the micro to the PC, however, my socket doesn't respond to the data. A network analyzer shows that the packet was sent and formated properly. I have tried both TCP and UDP with the same results. Has anyone come across this before?

Thanks.

Re: Winsock problem

Moak6-Jul-10 11:31

Moak

6-Jul-10 11:31

masnu wrote:
When I try to send data from the micro to the PC, however, my socket doesn't respond to the data.

Can you elaborate what you mean by that? Can you connect from the microcontroller to the PC, can you receive data but not send, etc...

Chat in Europe Java | [Coffee]

Now with 24% more Twitter

Re: Winsock problem

masnu7-Jul-10 3:26

masnu

7-Jul-10 3:26

Yes I can connect to the micro and send data from the PC to the micro but not the other way around. My socket is created as follows:

// Create socket
Socket = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);

And then I wait for data:

fd_set	sckt;
timeval	timeout;

// Set two second timeout
timeout.tv_sec	= 2;
timeout.tv_usec = 0;

FD_ZERO( &sckt );
FD_SET( Socket, &sckt );

int nRet = select( 0, &sckt, 0, 0, &timeout );

select always returns 0 indicating a timeout no matter how much data I send from the micro.

Re: Winsock problem [modified]

Moak7-Jul-10 4:32

Moak

7-Jul-10 4:32

If the TCP handshake is successful, you are actually sending packages from the microcontroller to the PC. This lets me wonder if the error you see is on application level, perhaps your socket code is not working properly, could be both client or server side. In the code snippet you provided there is no connect or bind/listen call, so I would not expect the socket to change status.

1) Have you tried connecting to your PC socket application from another PC (or via loopback)?
2) What error code do you get when connecting from microcontroller to PC? Timeout or something else?
3) Have you checked with Wireshark that TCP handshake is fine and packages are properly ACKed?
4) Which TCP stack are you using on the micocontroller (ARM SDK)? Could the problem not be Winsock at all?

Chat in Europe Java | [Coffee]

Now with 24% more Twitter

modified on Wednesday, July 7, 2010 11:05 AM

Re: Winsock problem

masnu7-Jul-10 4:56

masnu

7-Jul-10 4:56

Sorry Moak, I was cutting and pasting and forgot the most important part. Here's the actual code to open and connect:

int CHPCtrl::Connect()
{


	struct sockaddr_in	rmtAddr;
	
//	Create data socket
	m_Socket = socket(AF_INET, SOCK_STREAM, IPPROTO_TCP);

	if ( m_Socket == INVALID_SOCKET )
		return 1;

//	Set client properties
	rmtAddr.sin_family	= AF_INET;
	rmtAddr.sin_addr.s_addr = inet_addr( remoteIP );
	rmtAddr.sin_port	= htons( m_nDevicePort );

//	Connect to remote
	if ( connect( m_Socket, (struct sockaddr *)&rmtAddr, sizeof(rmtAddr) ) == SOCKET_ERROR )
		return 1;


//	Open rx monitor thread
	m_hRxMonitor = (HANDLE)_beginthreadex( 0, 0, RxMonitor, this, CREATE_SUSPENDED, 0 );

	if ( m_hRxMonitor )
	{
		
		m_bConnected = true;
		ResumeThread( m_hRxMonitor );

	} //__if ( m_pReadThread )__

	return 0;

}

And in a separate thread I wait for incoming data:

UINT CHPCtrl::RxMonitor(void *pThis)
{


	CHPCtrl		*pCtrl = (CHPCtrl*)pThis;
	int		bytes_recevied = 0;
	
	fd_set		sckt;
	timeval		timeout;

//	Set two second timeout
	timeout.tv_sec	= 2;
	timeout.tv_usec = 0;

//	Monitor all rx traffic
	while ( pCtrl->m_bConnected )
	{

		FD_ZERO( &sckt );
		FD_SET( pCtrl->m_Socket, &sckt );

		int ret = select( 0, &sckt, 0, 0, &timeout );

		switch ( ret )
		{

			case  SOCKET_ERROR:
				//Handle error 
				break;

			case 0:	//Timeout
				//Handle time out
				break;

			default:
				pCtrl->ReadFromSocket( pCtrl->m_Socket );

		} //__switch ( ret )__

	} //__while ( m_bRunRx )__

//	Shutdown rx comm
	shutdown( pCtrl->m_Socket, SD_RECEIVE );

	return 0;

}

m_Socket is a class variable. I did this so I can send and receive on the same socket without blocking. Please let me know if you see anything wrong with this.

Re: Winsock problem

Moak7-Jul-10 5:05

Moak

7-Jul-10 5:05

Looks good, but I have never used select() on Windows.
Perhaps have a look at the questions I had, they might give you some ideas.

Smile | :)

Chat in Europe Java | [Coffee]

Now with 24% more Twitter

Re: Winsock problem

Parthiban6-Jul-10 18:16

Parthiban

6-Jul-10 18:16

In ARM processor, which BSP r u using? how r u receiving Data? U TCP stack implemented? If u have stack implementation, there should not be problem in sending. If u dont have stack implementation, u have to assemble the packet in the TCP/IP struct and have to send it.

Re: Winsock problem

masnu7-Jul-10 3:30

masnu

7-Jul-10 3:30

I'm not using any BSP and I implemented the TCP stack myself. I am able to establish communication via the 3-way handshaking process and then I assemble the package and send it. I used Wireshark to trap the packets between the PC and the micro and it recognizes it as a valid TCP/IP packet so I'm assuming it's formated properly.

Re: Winsock problem

Emilio Garavaglia7-Jul-10 4:10

Emilio Garavaglia

7-Jul-10 4:10

Please, write international English, not stenography.
We are not chatting with a phone.

2 bugs found.
> recompile ...
65534 bugs found.
D'Oh! | :doh:

Re: Winsock problem

masnu7-Jul-10 4:24

masnu

7-Jul-10 4:24

Please elaborate as to which part of the post wasn't in "international" English and I will be happy to clarify.

Re: Winsock problem

Iain Clarke, Warrior Programmer7-Jul-10 5:33

Iain Clarke, Warrior Programmer

7-Jul-10 5:33

masnu wrote:
Please elaborate as to which part of the post wasn't in "international" English and I will be happy to clarify.

"r"
"u"

Mind you, once translated from text messaging, it was a helpful question / answer.

Iain,

I am one of "those foreigners coming over here and stealing our jobs". Yay me!

Re: Winsock problem solved

masnu7-Jul-10 8:20

masnu

7-Jul-10 8:20

For those of you who are interested I finally figured out what the problem was. When I implemented the TCP/IP stack on the micro I made a mistake in the routine that calculates the IP header checksum. With an invalid checksum Winsock just disregarded the message. Once the correct checksum was sent everything worked fine.

Thanks to all of you for your help. I appreciate it.

Paul

Re: Winsock problem solved

Moak7-Jul-10 8:22

Moak

7-Jul-10 8:22

So it was not a Winsock problem at all. Wink | ;)