Brandon E Taylor

I need to some more debugging, but I was able to get the application to load and run correctly by modifying the following lines in the srecord: S21404000140060000FFFF03000000041005FFEF0098 S214040011800000E80D120118F2020418120218F208 S21404002102051810030300FBFF06143202044118EC S214040031F00702102700000400FAFF0718F0030275 S2140400410500F9FF08184301000410031301010118 S2140400510A081003C0FC0300C40412C80412CC042A S21404006112D00412D40412D80412DC0412E00412CE S214040071E40412E80412EC0412F0041004009004E0...

I currently have an application using MQXv5 that executes just fine unless I relocate the code from a base of 0x0000 to a base of 0xF000 (to accommodate a bootloader) and then jump to the application entry point (__boot) from the bootloader. I am using IAR EWARM 9.10 as my IDE. When jumping to the code from the bootloader, the application raises a hard fault early in the initialization process. More specifically, a hard fault is raised in __iar_data_init3 due to a data access error. The Bus Fault...

I am working on getting the shell_boot and shell_boot_app demos up an running on a custom board with a K66 MCU. I have the shell_boot application running - I am able to use 'erase all' and 'tftpc' to fetch the fnet_firmware.srec file (built from the shell_boot_app project) from my tftp server. When I execute 'go', however, the app appears to hang. One thing I noticed is that I receive the following warning when building the shell_boot_app application: "For the shell_boot application the vector table...