You are on page 1of 3

Flashing through E-sys:

E-sys is the tool used by BMW, in order to flash the software delivered onto the target. Copy the software / container/ .PDX file from server to ODX folder of data directory of local machine Copy the TAL file to TAL folder and FA file specified for the type of target you are using to FA folder similarly Steps to flash target through e-sys: 1. Connect the Ethernet cable(grey color) coming from the central gateway(ZGW) of bench 2. Now go to Start-> Control panel-> Network connection-> Check the LAN connection setting: set the IP to automatic (note :not assigning a static IP) and wait till it shows Limited or no connectivity with yellow exclamation mark 3. Now open the e-sys tool(can download from shared drive of Harman) 4. Go to Data-Handling -> File explorer. Now in that window choose the ODX folder, so that we can see the .PDX file(s/w to be flashed) 5. Choose the .PDX file and right click on it and choose Import PDX option and wait for some time till it gets imported successfully 6. Now hit the connection icon at the left top corner of the screen to establish connection between target and PC. [Check and ensure i. VIN no. is detected, and choose the right target name(F10), before hitting on connect button] 7. Go to Expert Mode->Coding->Read ECU and wait for a list to be appeared in window containing list of devices (like HU, RSE, ZGW, ZBE, Top Amp, MMP etc) in the MOST ring. All the devices should appear properly. If not appeared, hit on Read ECU again 8. Go to TAL PROCESSING->select right TAL file, right FA. 9. Go to ECU tab: select all options [note: swDeploy: for s/w flash, cdDeploy for:coding HU] 10. Click START to start preparing the target!

You can hit the LOG tab to view progress status of the s/w flashing/coding activities and log messages It generally takes 45-50 mins to flash the s/w First the target is taken to boot-loader mode, then the s/w flashing, coding activities start so as to ensure the safety and prevention of the valuable targets from any damages due to unforeseen consequences in midst of flashing

HAPPY FLASHING THROUGH E-SYS!

Taking proper traces to aid developer to debug:


Getting ready to take traces for NBT HU and RSE: IP set to static: 160.48.199.101 1. Download and install the GNLogger tool from ODC server in your PC 2. For intel traces: (For RSE and HU should create 2 separate objects/settings) [Connect Rosenburger cable (black) from HU or RSE to Ethernet (yellow) cable which is connected to PC] i. Go to GNLogger and start the application. ii. Wait for a trace client window to pop up iii. Hit on Add button iv. Edit in order to make the application ready to take intel traces: Connection settings: Name: HU_INTEL ; Type: Socket IP number: 160.48.199.99; Port: 851 ; Protocol: Multiconsole; Debuglevel: 2; Hit on Apply Go to trace client: select GN option Consoles to be enabled: *, B, E,F,L,M,P,R,T,W,Y,f,o,y,z Scopes to be enabled: MOST, NBTMediaMainApp, Connectivity (Wait for all scopes to load up properly and make them persistent by clicking on the icon Flash the scope settings to HU) 3. For jacinto traces: [Serial cable connected to PC from HU or RSE] i. In GNlogger: Name: HU_Jacinto; Type: Serial; Comport:COM1, Speed: 115200, Bits:8, Parity:even;stopbits:1; Handshake: None; Protocol: Multiconsole; Debug level:2 v. vi. vii.

To check for log files check the path provided in: Log directory option in GNLogger under configuration tab Best practice to assign log file suffixes as .11XX To start taking traces hit on start connection and to stop stop connection GNLogger gives us another feature to notify any event at any point of time: while trace capture is on-going, hot the MARK option available and while talking of when the event took place, just mention the MARK no. as MARK 1, MARK n etc

TUI:
It is a replica of iUI-screen on NBT-HU-HMI

These are the basic features that we test for TUI application: Only audio is supported Features tested on it: a. Basic Feature: Start, stop, pause, next, previous, Fast forward, Fast Rewind b. Advance features: Browsing on basis of Artists, Album, Songs, Podcasts, Genres, Composers; Cover art display, playlists, metadata display c. Last User Mode: By taking out device from cradle, source change and ignition cycle Some points to be noted while testing for TUI: video-cable to be attached to cradle in order to get the TUI Screen along with audio through USB To enable TUI: Go to Connected Drive-> Plug In -

WLAN:
allows us to share media files from mobile phones to HU feature not available in RSE Go to Connections-> WLAN-> Enter the passphrase as displayed in HU into Mobile phone to be paired-> The mobile is connected now to HU via WLAN To share media files , you have to enable content sharing (as in SONY) or use Twonky Server Apps (As in Motorola) While testing make sure the Antennae is connected to HU Cover art, meta data, Music Search features are available

A4A Apps:
1. Go to Connected Drive-> BMW apps: the apps like Facebook, twitter, News etc are listed out 2. Before that connect i-Phone(with Micro SIM) to HU via USB port/Snap in Adapter and enable the BMW apps in the iPhone with proper input of credentials of valid accounts in Facebook and Twitter 3. News Apps: It displays the news in HU and READ OUT option can be enabled as well 4. FACEBOOK, TWITTER: the social networking apps are available in HU. You can post Whats in your mind?, see others updates in Facebook, and follow posts in Twitter 5. Mini Buddy Apps: On some activities like opening the door of the car, if the roof top opens, the car speaks out messages notifying the same as Please close the door etc 6. Web Radio is another feature available