TI E2E Community
Stellaris® ARM® Microcontrollers
Stellaris® ARM® LM3S Microcontrollers Forum
Bootloader setup on LM3S9B96
I'm having difficulties with the bootloader on LM3S9B96.
When I do a soft reset from my application (or using the reset button), the ethernet bootloader works correctly, and I see TCP traffic in Wireshark. However, when I power the device on and trigger the loader, it seems to have a different setup--- my LED test pattern blinks at a different speed (much slower), and I see no Wireshark traffic.
My application is based on the safertos example, and runs at 80MHz, using a 2.5 divider, whereas the bootloader runs at 12.5MHz.
Thanks for any pointers,
Can you clarify a couple of details about your system? Are you using a DK-LM3S9B96 development kit, or are you working with a custom board design? Also, exactly how are you triggering the bootloader? For instance, are you calling a function such as UpdateBOOTP? Did you set up a GPIO to force updates on startup? Also, it sounds like you are using the flash-based bootloader rather than the ROM version. Is this correct?
These details will help me understand what code is executing as the chip comes out of reset and the bootloader is called.
I have some problems about bootloader via ethernet, too. I program with your sample code (C:\StellarisWare_more\boards\dk-lm3s9d96\boot_eth) on LM3S9B92 robotic kit but it not working.
I don't understand about this, TI have no documents and no guide about this.
can you write some guides about this (ethernet bootloader) for every body.
Thanks and BR,
Hi Vui Nguyen,
Actually, we do have a User's Guide for all of our boot loaders, including the Ethernet boot loader: http://www.ti.com/lit/ug/spmu134o/spmu134o.pdf
The default Ethernet boot loader should work if you go through the following process:
Christian, sorry for noob question, I followed your steps with some differences: i have programmed boot_eth to 0x00000000 and boot_demo1 on 0x00001800 (didnt change anything in example configuration) on DK-LM3S9D96 and tried to program boot_demo2 with LM Flash Programmer via ethernet. Packets were transmitting, but after reset my board hanged up: blank screen.It seems, boot_demo2 overwrites bootloader, is it correct? I expected to see boot_demo2 working and wanted to try program boot_demo1 back via ethernet. What did i do wrong?
Kirill Efimovbut after reset my board hanged up: blank screen.It seems, boot_demo2 overwrites bootloader, is it correct?
This is the usual response, when your application did not jump back to bootloader, or some other reasons.
Kirill Efimovi have programmed boot_eth to 0x00000000 and boot_demo1 on 0x00001800
How did you come up with the address 0x1800. This address should be the same from the files below.
#define APP_START_ADDRESS 0x00001800
boot_demo1 linker script file (refer to bootloader user guide). boot_demo1.sct for Keil Uvision
LR_IROM 0x00001800 0x0003f000
All content and materials on this site are provided "as is". TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with regard to these materials, including but not limited to all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement of any third party intellectual property right. TI and its respective suppliers and providers of content make no representations about the suitability of these materials for any purpose and disclaim all warranties and conditions with respect to these materials. No license, either express or implied, by estoppel or otherwise, is granted by TI. Use of the information on this site may require a license from a third party, or a license from TI.
TI is a global semiconductor design and manufacturing company. Innovate with 100,000+ analog ICs andembedded processors, along with software, tools and the industry’s largest sales/support staff.