The ARM processor architecture is licensed to the silicon vendors, where each of these vendors creates their own derivative that is different from the competitors and not inclined to share common design architecture. Typically, an ARM based hardware platform is design with some proprietary technology, unique to the silicon vendor.
On most ARM based platform, it’s common to have a JTAG interface to support debugging, testing and other development tasks. Other than JTAG, USB is another common interface use by ARM based hardware as connectivity for the development environment, attaching to the development computer with proprietary software support, to serve the following purposes:
· Deploy and update firmware and/or bootloader to the device.
· Deploy OS runtime image to the device and support OS design debugging and testing.
· Deploy application to the device and support application debugging and testing.
Without support resources from the silicon or hardware vendor, it’s a huge and costly challenge to develop Compact 2013 support for an ARM based hardware platform.
When searching for ARM based hardware platform for a Compact 2013 development project, to minimize unnecessary development tasks, cost and schedule, in addition to the device drivers for the required components, include the following Compact 2013 support resources as part of the requirements:
· Bootloader: To launch Compact 2013 OS runtime image from the target device’s local storage.
· Remote bootloader: To download Compact 2013 OS runtime image from the development computer to the target device for testing and debugging.
· KITL: Short for Kernel Independent Transport Layer, KITL is needed to support the debug and remote tools provided as part of Platform Builder for Compact 2013.
· Connectivity (Ethernet or USB): To support OS design and application development.
· Connectivity (USB or JTAG): To download and update firmware/bootloader.
· Serial port: To capture serial debug messages.
Note: While remote bootloader, KITL and serial debug resources are not required components for the final production device, it’s good practice to include these resources in the design, to support debugging and testing tasks. For all device development projects, regardless of the underline OS technology, the software development team is expected to spend much more time to debug the codes than writing new codes. In addition to minimizing cost and development schedule, an efficient and effective debug environment help minimize anxiety and conflicts among team members. From a project management perspective, an efficient debug environment can help identify problem area early in the development process and give more time for the management team to address the problem.
Click here to provide feedback and input