CANvu 355 & VeeCAN 320 SDK

Transcription

1 CANvu 355 & VeeCAN 320 SDK INSTALL GUIDE Issue 1 1 P a g e

2 1. Hardware specification Item CPU NAND FLASH SDRAM DISPLAY USB RS232 RS485 CAN2.0B Description Freescale imx 286, running at 454 MHz 128MB 128MB QVGA TFT Host USB 1 port None 2 ports (one isolated) Buzzer 1 Keypad Power 5 keys 10-36VDC with protection 2 P a g e

3 Application Development Environment Overview The development environment consists of two modes one is when using the PC simulator to develop and test applications and the other is used to build the binary files that run on the target platform. Generally the fastest approach is to use the PC Simulator where possible and this includes the use of the CAN Dongle so that the PC Simulator can be hooked up to live CAN data for maximum benefit. The PC Development Environment uses Microsoft Visual Studio as the IDE and the latest SDK has support for VS2008 and VS2010. The Express (Free) versions or the full versions can be used. Once the application has been developed and tested on the PC, the Development Environment used for building the same application that will run on the target is the well known Eclipse IDE coupled with the ARM compiler from CodeSourcery. The information below explains how the tools are installed and set up for use. 3 P a g e

4 Installing Application Development Environment ARM/Linux To assist installation we have created a single.zip file and supporting batch files. Follow these steps. 1. Download the install file from here: The file is around 200MB and should take < 10 minutes to download. 2. Create the SDKC_ROOT folder where you want all the SDKC files to live i.e. d:\source\sdkc. NOTE YOU MUST NOT HAVE SPACES IN ANY OF THE FOLDER NAMES AS THIS WILL CAUSE PROBLEMS WITH THE SCRIPTS. 3. Extract the SDKC_Toolchain.zip file in the SDKC_ROOT folder. This may take a while there s a lot of files! You will then have sub-folders SDKToolchain and Packages in your SDKC_ROOT folder. 4. Double click the SDKC_ROOT\Packages\SetupSDK.bat file 5. Unzip the SDKC_Release.zip file with the basic SDK files (into SDKC_ROOT\SDK). 4 P a g e

5 6. Unzip the SDKC_J1939_Release.zip file with the upgrade J1939 files (into SDKC_ROOT\SDK\ProjectTemplates). You should then have a J1939Starter folder containing the J1939 Source Code project. IMPORTANT NOTE: Please DO NOT edit any files in either of the SDKC_ROOT\SDK\ProjectTemplates or SDKC_ROOT\SDK\ProjectSamples folders. Only edit source files in the SDKC_ROOT\SDK\Projects\YourProjectName folder! Please see the "Creating a New Project" section below. 7. This completes the installation and set up and you should have the following folder structure for your Eclipse Tool Chain installation: 8. Run the SDKC_ROOT\LaunchEclipse.bat file 5 P a g e

6 6 P a g e

7 9. This is the start screen for Eclipse prior to selecting your own project configurations. The Workspace for Eclipse is automatically set to SDKC_ROOT\SDK by the launch batch file. Follow these steps to set-up the example projects. Click on the right-hand icon to go to the Workbench Use File/Import menu item and select General/Existing Projects into Workspace option and click NEXT Using Select Root Directory browse to SDKC_ROOT\SDK \Projects. Eclipse will scan this folder for pre-existing Eclipse projects. You should get a tick box or multiple tick boxes with a tick in as shown here: 7 P a g e

8 Click on Finish and this will add the project(s) into your Workspace and you will see the project(s) shown in the Project Explorer window. The editor within Eclipse can be used to make code changes (or you can edit in Visual Studio if preferred). There is an option in Eclipse to Build Automatically, found in menu item Project/Build Automatically. This is by default enabled, if you turn this option off you can use the Build Project option (right click on Project) to generate a binary release file for loading into the target display. The binary file created will be written into SDKC_ROOT\SDK\Target\app\bin and is used later for copying on to the target. We can offer full target debug support if required, please contact your supplier for more details. 8 P a g e

9 Setting up and using the PC Simulator Environment If you already have an installed Visual C++ Toolchain then you can skip the install.. VS2010 Install Steps Download the VS C from this link. VSC Install to default location (or your chosen location) on your local drive Running the Simulator Open the example VS Express project SDKdemo.vcxproj in the sdk/projects/ folder or use SDKdemo.vcproj if using VS2008. The SDK Basic Demo configuration should build and then you can run in debug to test your installation. If you have a CAN Dongle connected (needs the drivers from the supplied CD-ROM to be installed), you can test to make sure the simulator has found the CAN Dongle by using the menu item Port/CAN. You should see the serial number of your CAN Dongle. You can now modify the project, rebuild and run and see the results! All normal debug features are available including breakpoints, watches etc. If you use breakpoints you may need to restart the App if the CAN traffic ceases as the use of breakpoints can occasionally affect the CAN Dongle operation. NOTES If you add source modules to the project you will need add files manually into the VS project, the Eclipse project will automatically see new source modules and build and link them. The.rc file has been modified from the auto-generated version and if you use the full version of VS and revert back to the Express version you may need to edit the.rc file as below if the.rc file has been regenerated. // modified to allow Express Versions of VSC++ to build the simulator // replace next line //#include "afxres.h" // with these lines #include "windows.h" #ifdef IDC_STATIC #undef IDC_STATIC #endif #define IDC_STATIC (-1) // all static controls 9 P a g e

10 Creating a New Project IMPORTANT NOTE: Please DO NOT edit any files in either of the SDKC_ROOT\SDK\ProjectTemplates or SDKC_ROOT\SDK\ProjectSamples folders. Only edit source files in the SDKC_ROOT\SDK\Projects\YourProjectName folder! The easiest way to start a new empty project is to use our automated process that will create a new folder with your chosen project name within the SDKC_ROOT\SDK\Projects folder. This way all of the tool settings and paths necessary to build and link on both the Visual Studio PC Simulator and the Eclipse tool chains will be correctly set. To create a new project, run the SDKC_ROOT\SDK\Projects\CreateProject.bat. This will give you a set of options allowing you to select the location of the project you want to create your new project from. You will then be asked to select a source project and then to confirm your choices. Once you confirm, your new project will be created. 10 P a g e

11 SDK Files The SDK Files themselves are supplied as a.zip file and when unzipped to your chosen location on your local drive will also create the folder structure for the tool chain installation and the folders below: Folder Descriptions Docs In here you can find the documents that will help you install and use the SDK Linux + Platforms + Portable In here are the essential libraries that are used when building the application. These files should not be changed. Future releases of the SDK may update these files. Projects This is where you will develop the application source code. Each folder within the projects folder is considered as an individual application and we suggest you copy one of the example project folders as the basis of your own custom project. Target 11 P a g e

12 This is where the files and scripts are stored that will be used to update the target. See document SDKC Target Firmware Update Guide for details on how to update the target. Utilities The CANvu350_Tool is used to convert bitmaps and also fonts for use within projects. All applications require.c and.h files to allow bitmaps to be displayed. The user has to edit disp_ext.c and images.h and add the new.c and.h files for them to be used in a project. Please ask for information on how to add and use alternative true type fonts. 12 P a g e