I use the BasicTFTP functions... i cant able to write data above 2000 bytes
....2000 is any limitation?how can i overcome the issue?
please help me


On Tue, Oct 8, 2013 at 5:08 PM, Bellphin Billu <[email protected]>wrote:

> Can i increase the size ov cRambuffer[2048].?Please help me.....
>
>
> On Mon, Oct 7, 2013 at 9:30 PM, <[email protected]> wrote:
>
>> Send lwip-users mailing list submissions to
>>         [email protected]
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>         https://lists.nongnu.org/mailman/listinfo/lwip-users
>> or, via email, send a message with subject or body 'help' to
>>         [email protected]
>>
>> You can reach the person managing the list at
>>         [email protected]
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of lwip-users digest..."
>>
>>
>> Today's Topics:
>>
>>    1. Re: No delay between DHCP discoveries (HA)
>>    2. Re: No delay between DHCP discoveries (Bill Auerbach)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Mon, 7 Oct 2013 01:34:56 -0700 (PDT)
>> From: HA <[email protected]>
>> To: [email protected]
>> Subject: Re: [lwip-users] No delay between DHCP discoveries
>> Message-ID: <[email protected]>
>> Content-Type: text/plain; charset=us-ascii
>>
>> I have to connect some level converters to the Uart to print out debug
>> messages. I did a grep of dhcp_discovery and it was only used inside
>> dhcp.c.
>> This file I have compared with the original and no difference.
>>
>> My thre timers run correctly, I can see it on the scope. Have no idea how
>> the webserver could trigger dhcp_discovery. Will go through the code. Any
>> other ideas?
>>
>>
>>
>> --
>> View this message in context:
>> http://lwip.100.n7.nabble.com/No-delay-between-DHCP-discoveries-tp21927p21938.html
>> Sent from the lwip-users mailing list archive at Nabble.com.
>>
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Mon, 7 Oct 2013 10:52:59 -0400
>> From: "Bill Auerbach" <[email protected]>
>> To: "'Mailing list for lwIP users'" <[email protected]>
>> Subject: Re: [lwip-users] No delay between DHCP discoveries
>> Message-ID: <[email protected]>
>> Content-Type: text/plain;       charset="us-ascii"
>>
>> I would update to the latest (1.4.1).  Your version is 6 or 7 years out of
>> date.  It shouldn't make a difference, but if it does, why debug something
>> that may already be debugged?  Besides, there are *many* bug fixes and
>> features added over those years.
>>
>> -----Original Message-----
>> From: [email protected]
>> [mailto:[email protected]] On
>> Behalf
>> Of HA
>> Sent: Monday, October 07, 2013 4:35 AM
>> To: [email protected]
>> Subject: Re: [lwip-users] No delay between DHCP discoveries
>>
>> I have to connect some level converters to the Uart to print out debug
>> messages. I did a grep of dhcp_discovery and it was only used inside
>> dhcp.c.
>> This file I have compared with the original and no difference.
>>
>> My thre timers run correctly, I can see it on the scope. Have no idea how
>> the webserver could trigger dhcp_discovery. Will go through the code. Any
>> other ideas?
>>
>>
>>
>> --
>> View this message in context:
>>
>> http://lwip.100.n7.nabble.com/No-delay-between-DHCP-discoveries-tp21927p2193
>> 8.html<http://lwip.100.n7.nabble.com/No-delay-between-DHCP-discoveries-tp21927p21938.html>
>> Sent from the lwip-users mailing list archive at Nabble.com.
>>
>> _______________________________________________
>> lwip-users mailing list
>> [email protected]
>> https://lists.nongnu.org/mailman/listinfo/lwip-users
>>
>>
>>
>>
>> ------------------------------
>>
>> _______________________________________________
>> lwip-users mailing list
>> [email protected]
>> https://lists.nongnu.org/mailman/listinfo/lwip-users
>>
>> End of lwip-users Digest, Vol 122, Issue 5
>> ******************************************
>>
>
>
_______________________________________________
lwip-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/lwip-users

Reply via email to