Are you taking care of relocating your ISR routines or reassign ISR handlers after you switch from bootloader to application? If you’re using ARM are you switching between USER and SVC mode? -Ajay Can you load and start application without involving bootloader? It's quite possible that driver handling hardware init does not work as expected if hw was already configured (i.e. MAC, DMA are already setup and in the middle of operation when application start). Hello,
My project consists of two sub-projects, a bootloader and an application.
My bootloader is programmed at the start of flash, and always starts when
the board is given power. I also have an application project, that through
my bootloader I use FTP to transfer the image to a certain address. Then I
can jump to that address and my application starts. This process works
perfectly fine.
In both my application and my bootloader, I am using lwip version 2.0.2 raw
api for all internet related protocols and applications. These include ftp,
http, telnet, and snmp. The bootloader specifically has ftp, http, and
telnet. The application has ftp, http, telnet, AND snmp. So other than
snmp, these two projects are nearly identical.
The issue I'm having is that when I jump from my bootloader to my
application, lwip crashes my board. The initialization works perfectly
fine, but when I try to ping the board, go to the built in web page, or try
snmp, etc. it completely locks up my board and I am forced to hit the reset
button. What's more interesting is that when I turn on one of the built in
printf debug statements, it prints messages for random traffic. Along with
that, if I turn multiple debug options on, aka, cluttering my console with
debug print statements, my application works exactly as intended, just with
a very high ms (around 60+ when it should be <1).
Just to clarify, my bootloader is working exactly as intended with lwip.
The webpage works, I can ping the board, and use telnet. My application is
exactly the same as my bootloader, it just has snmp added on and a few minor
changes (none that would break lwip since they are unrelated).
Any ideas? What steps could I take to resolve this issue? I'm not sure if
this is a problem with my lwip settings in my application somehow, or an
issue with something else. I find it very strange that lwip on my
bootloader works perfectly yet the lwip on my application does not.
Thanks, Nick
--
View this message in context: http://lwip.100.n7.nabble.com/Bootloader-to-Application-lwip-crash-tp29489.html
Sent from the lwip-users mailing list archive at Nabble.com.
_______________________________________________
lwip-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/lwip-users
+48 721 337 238 |