AnsweredAssumed Answered

k60 Ethernet bootloader and MQX go address

Question asked by Greg Davis on Mar 27, 2014
Latest reply on Aug 5, 2014 by Kyle Yang

I have the Ethernet bootloader v2.6.3 and MQX 4.0.2 running on an MK60FX512 board. This application will be using the TFTP feature of the bootloader to upgrade MQX/application; the upgrade will be with a "raw" binary file.


1. I cannot figure out how the "go" address is derived. I was able to determine the "go" address for the binary by generating an s-record version of MQX and looking at the s-records. Can someone explain to me how the "go" address is derived? I thought it was the __boot location but this does not match the address from an objdump of the MQX elf file.


2. How can I make the "go" address fixed so that it stays the same for each new build of MQX? The reason is that in this application the upgrade can be initiated from an RS-232 command line or from an Ethernet network message. The network message only signals to start an upgrade so the "go" address is stored as a bootloader parameter that needs to stay the same for each new version of software.


Thanks in advance for your help.



FNET Bootloader
FNET TCP/IP Stack for MK60FN1
Version 2.6.3
Built Mar 27 2014 at 15:41:31 by CW
Copyright by FNET Community
Interface        : eth0
IPv4 Address     : <manual>
IPv4 Subnet mask :
IPv4 Gateway     :
MAC Address      : 00:04:9f:14:09:09
Link Status      : connected
TX Packets       : 3
RX Packets       : 0
Free Heap        : 14128


Enter 'help' for command list.


Press any key to stop (go):   0
go 0x000177d9



MQX Version     : 4.0.2
BSP Version     : 01
Software Version: 00.00.04



.Setting static IP address............[OK]


IP Address      :
Subnet Address  :
Gateway Address :
Starting Telnet server...............[OK]
Creating shell task..................[OK]


Shell (build: Mar 26 2014)
Copyright (c) 2013 Freescale Semiconductor