Problem sending large data buffer with W5500 and ioLibrary
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Ethernet Chips
No replies yet. Be the first to reply.
Join the discussion.
Share projects and connect with makers.
Joined before the site update? first.
New to WIZnet Makers?
We sent a verification link to your address. Open it to activate your account, then log in.
Accounts from this email provider are reviewed by an administrator after verification. Approval usually takes one business day.
Already have an account?
Enter your email address. If it belongs to an account, we'll send a link to set a new password. Members who joined before the site update use this to set their password.
If an account uses that address, we sent a link to set a new password. The link works once and expires in 30 minutes.
Know your password?
Need an account?
RE: Problem sending large data buffer with W5500 and ioLibrary
by Eugeny ·
What
strlen(payload)returns exactly?RE: RE: Problem sending large data buffer with W5500 and ioLibrary
by seands ·
That question got me thinking a bit more about memory. I moved the definition of
payloadinto the global scope and it now works. I am not sure why it didn’t work before though, because shouldn’tsend()be able to see the variables in the scope ofsend_dataif I pass a pointer to it?This bug seems really bizarre - why did it work for a 32 byte buffer and not much higher?
RE: Problem sending large data buffer with W5500 and ioLibrary
by kenearl ·
Hi Seands,
You might want to check if wizchip_init returns 0?