I am using it like this; the bootloader uses lwip and then jumps into the firmware-code. The firmware is a completely different program (even with different lwip-config) and just initializes everything like it had just booted from a power-on.
Be careful about your hardware though! We use microcontrollers by TI and they do not mind being initialized twice but I would imagine that some hardware would need to be carefully reset in order to work. -- Philipp Tölke - T +49 89 999 542 58 - F +49 89 999 542 01 > -----Original Message----- > From: lwip-users [mailto:[email protected]] On > Behalf Of [email protected] > Sent: 3 November, 2016 11:56 > To: Mailing list for lwIP users > Subject: [lwip-users] LwIP bootloader stack deinitialisation > > Hello, > > i'm doing a bootloader for my custom board right now and i'm thinking > about wether i should leave the LwIP stack only in the application or put > it into the bootloader aswell.. > Is it possible to completely deinitialise the whole stack? Because the > application would initialise it again as soon as it boots.. > Has anyone here maybe done something like this before? > > I'm working on a ATSAM4E16C custom board with LwIP 1.4.1. > Regards, > Markus -- *fos4X GmbH | www.fos4x.de <http://www.fos4x.de>* Thalkirchner Str. 210, Geb. 6 | 81371 München | DE Handelsregister | Commercial Register: Amtsgericht München HRB 189 218 Geschäftsführer | Managing Directors: Dr. Lars Hoffmann, Dr. Mathias Müller Unternehmenssitz | Place of Business: München, DE _______________________________________________ lwip-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/lwip-users
