Remote tools Colibri iMX7 Win CE 7

Technical Support
, , ,
1

HI,

We are developing application in Visual studio 2008 on Colibri iMX7D 512 MB using WEC7 BSP Ver 1.1.
We want to use the various remote tools available in Visual studio to debug or monitor our application.

We want to know what are the remote tools supported in WEC7 provided by Toradex ?

Currently we are trying to use Kernel Tracker utility for our application. Does Toradex WinCE 7 image support this and if yes, then how to use it ?

regards
Bipin Kumar

2

Dear @bipin7301,

Thank you for contacting support. Moreover, all the remote tools should work with our WEC7 binary BSP and workspace. But we are not integrated kernel tracker feature with our standard release image. You need to build an image with enabling kernel tracker by using our binary BSP and workspace that you can see in Project → Properties → Build options.

Please feel free to contact us if you have any other questions on this.

3

Thanks for the Response Raja.

We have downloaded the binary BSP and workspace. But while opening workspace it is showing error[ refer attached image for error detail].alt text
We are using visual studio 2008 professional edition.

Regards
Bipin Kumar

4

Dear @bipin7301,

Did you install Windows Embedded Compact 7 Platform builder in order to open OSDesign on Visual studio and build the image? Please keep bInary BSP should under :\WINCE700\platform\TORADEXIMX7BIN and OSDesign under :\WINCE700\OSDesigns\ToradexIMX7_CE7.

5

Thanks for the Response Raja.

It was due to the path error. BSP and OS design was not kept at right locations.
Now we are able to open the workspace.

Regards
Bipin Kumar

6

Hi Raja,

We are able to build the OS image with our build options using workspace and bsp provided by Toradex. However we some queries regarding OS image build and image flashing:

  1. Do we need to set some environment variables for new image build. Currently set environment variables attached in imagealt text

  2. We got the image build output files different from what Toradex provided in its Win CE image folder[ colibri-imx7_winceimage_1.1-20180514 ]. Please refer the attachments for file names of image, eboot and files path.link text
    link text

  3. We have referred the iMX7 WinCE Bring-up | Toradex Developer Center for our image flashing. At the step 10 it flashes the eboot.imx. How to get this eboot.imx? when we build our image, eboot.imx was not generated.

Regards
Bipin Kumar

7

Dear @bipin7301,

Please see our reply for your questions below.

Do we need to set some environment variables for new image build. Currently set environment variables attached in image

No need to add the environment variable. In case if you want to add additional components then you would add there.

We got the image build output files different from what Toradex provided in its Win CE image folder[ colibri-imx7_winceimage_1.1-20180514 ]. Please refer the attachments for file names of image, eboot and files path.

Files are correct, NK.bin will be generated by this build that you can program on the module.

We have referred the iMX7 WinCE Bring-up | Toradex Developer Center for our image flashing. At the step 10 it flashes the eboot.imx. How to get this eboot.imx? when we build our image, eboot.imx was not generated.

eboot.imx will not generate here and also we are not providing binaries for eboot. eboot doesn’t change with the addition or removal of WinCE components. You can use corresponding standard release eboot for the built NK.bin image.

Please let me know if you have any other questions.