Forums

If you used the Ethernet boot loader to flash your board it shouldn't be possible to corrupt the boot loader itself unless there's a latent bug in there somewhere that we've not found. Most likely, the problem is either that you flashed a corrupted image (the boot loader can't tell if the image it writes is valid or not and will attempt to run it as long as the initial stack pointer and PC values at the beginning of the image appear valid. Flashing a bad image to the board can cause the boot loader to become unresponsive since it is the application itself that is responsible for passing control back to the boot loader when it detects the signal telling it to accept a new firmware download) or that the default network settings have been used and those don't work in your current network setup.

If you have flashed a corrupt or incorrect application to the board, the only way out is to use an external JTAG debugger to flash the correct image via LMFlash. Any of our existing evaluation kits can be used as a JTAG adapter. If you don't have another EK, I would recommend you buy an ek-lm3s9b90 or ek-lm3s9b92 since these are shipped with an independent debugger board that can be used to debug any other RDK. If you want to spend less, an ek-lm3s811 board will also work.

1. Connect the EK to the JTAG adapter on your RDK-S2E board. Depending upon the EK board you are using, you may or may not have to use the 20 to 10 pin adapter you have.
2. Connect the EK to a USB port on your computer and power the RDK-S2E board
3. Run LMFlash and select "LM3S6965 Ethernet Evaluation Kit" from the dropdown list under "Quick Set". These settings are compatible with the RDK-S2E board.
4. Click the "Program" tab and select the bin file "C:\StellarisWare\boards\rdk-s2e\ser2enet\gcc\ser2enet.bin". This assumes you have a recent release of StellarisWare installed in the default directory. There are multiple binaries for the application, one for each toolchain, and you can choose any of them - I just picked gcc here as an example.
5. Make sure you DO NOT check "Erase Entire Flash" but check "Erase Necessary Pages". If you get this wrong, you erase the boot loader (which you can recover from by flashing the boot_eth.bin binary at address 0, by the way).
6. Check "Verify After Program" and "Reset MCU After Program".
7. Set "Program Address Offset" to 0x1000. This is VERY IMPORTANT. If you get this wrong, you will either find that the image doesn't boot properly or you will overwrwite the boot loader. Either way, the board won't work after you flash the image.
8. Press "Program" to download the binary to the RDK-S2E board.

After this, you should be back up and running. If your setup parameters got corrupted, you may find that the board is still invisible, in which case you may like to reflash both the boot loader and the main image. The easiest way to do this is to use the above instructions to flash boot_eth.bin at address 0 (rather than 0x1000) and also check "Erase Entire Flash". Once the boot loader is downloaded, you can download the main code image either using the instructions above or via the Ethernet boot loader as before. This will cause all the flash-based setup parameters to return to the default values.