Posted by: Upender Sandadi (reposting since text formatting got messed up first time)
This is the second entry in the KITL series. In the first entry we learnt aboust basic KITL packet layout. In this we will look at some of the common things we have run across in debugging KITL issues on devices in-house. This covers mostly KITL over ethernet. For KITL over serial and KITL over USB, I would recommend getting a trace and analyzing the KITL traffic using the packet layout information.
Tracing tools:Some of the tools which can be used to capture KITL and debug traffic are:
Image downloads to the device but KITL doesn’t connect to the desktop
Best tools to debug in these scenarios are:
Image downloads but KITL hangs after printing a message which says “Loading nk.exe …”.
Image downloads but KITL hangs after printing a message which says “Loading relsfd.dll …”.
This is definitely not an exhaustive list. Please add to this list if you run into a KITL issue with your custom devices and how you solved it.