Manual Do Software Philips

7/29/2019 Manual Do Software Philips

1/29

WISP

USER MANUAL

Date: 9/22/2013

Version: 2.4.2

Doc nr: UM 02177

Authors:

Richard de la HayeHarold Steinbusch

Innovation Centre Eindhoven

Building A410 2.23

Prof. Holstlaan 4

P.O. Box 80021

5600 JZ Eindhoven

The Netherlands

Telephone : +31 40 27 22090

Fax: +31 40 27 23440


2/29

WISP User Manual

Email: [email protected]

[email protected]

Page 2 of 29
mailto:[email protected]:[email protected]:[email protected]:[email protected]


3/29

WISP User Manual

Table of contents

LIST OF SHORTCUT KEYS.........................................................................................................................4

TABLE OF FIGURES.....................................................................................................................................4

TABLE OF TABLES ......................................................................................................................................4

REQUIREMENTS...........................................................................................................................................6

INTENDED AUDIENCE.................................................................................................................................6

1 WHAT IS WISP?...........................................................................................................................................7

1.1 WHATISNEEDEDTOWORKWITH WISP...................................................................................................7

1.2 INSTALLING WISP.....................................................................................................................................7

1.3 I2C CONNECTION.......................................................................................................................................7

2 WISP ........................................................................................................................................................... ...8

2.1 GRAPHICAL USERINTERFACE...................................................................................................................8

2.2 MENU.........................................................................................................................................................9

2.2.1 File.....................................................................................................................................................9

2.2.2 View.................................................................................................................................................10

2.2.3 Settings............................................................................................................................................10

2.2.4 Help.................................................................................................................................................11

3 MANUAL ISP PROGRAMMING..............................................................................................................12

3.1 GENERALSETTINGS.................................................................................................................................12

3.1.1 Flash selection.................................................................................................................................12

3.1.2 Mode byte........................................................................................................................................12

3.1.3 Delay time........................................................................................................................................12

3.1.4 ROM status......................................................................................................................................123.2 ISP FUNCTIONS........................................................................................................................................13

3.2.1 Enter ISP mode................................................................................................................................13

3.2.2 Erase flash.......................................................................................................................................14

3.2.3 Write flash.......................................................................................................................................16

3.2.4 Verify flash.......................................................................................................................................18

4 AUTOMATIC ISP PROGRAMMING......................................................................................................21

5 DSP PROGRAMMING...............................................................................................................................22

A. DDS HEX FILE FORMAT........................................................................................................................24

B. COMMAND LINE PARAMETERS.........................................................................................................26

C. TROUBLESHOOTING.............................................................................................................................27

Page 3 of 29


4/29

WISP User Manual

List of shortcut keysCtrl-A..............................................................................................................................................11

Ctrl-I................................................................................................................................................10

Ctrl-M........................................................................................................................................10, 21

Ctrl-Q................................................................................................................................................9

Table of figures

FIGURE 1 - WISP USER INTERFACE.........................................................................................................8

FIGURE 2 - ISP STATUS DISPLAY..............................................................................................................9

FIGURE 3 - STATUS BAR..............................................................................................................................9

FIGURE 4 - WISP MENU................................................................................................................................9

FIGURE 5 - I2C CONFIGURATION SETTINGS......................................................................................10

FIGURE 6 - GENERAL WISP SETTINGS.................................................................................................12

FIGURE 7 - ENTER ISP MODE...................................................................................................................13

FIGURE 8 - ERASING FLASH MEMORY.................................................................................................14

FIGURE 9 - BLANK CHECK OPTION.......................................................................................................15

FIGURE 10 - AUTO VERIFY OPTION.......................................................................................................16

FIGURE 11 PROGRAMMING FLASH MEMORY................................................................................16

FIGURE 12 NO INTEL HEX FILE LOADED.........................................................................................17

FIGURE 13 - INTEL HEX FILE LOADED.................................................................................................17

FIGURE 14 - VERIFYING FLASH MEMORY..........................................................................................19

FIGURE 15 AUTOMATIC ISP PROGRAMMING INTERFACE........................................................21

FIGURE 16 - WISP DSP PROGRAMMING...............................................................................................22

FIGURE 17 - DSP PROGRAMMING SUCCESSFUL...............................................................................22

FIGURE 18 - DSP PROGRAMMING FAILED..........................................................................................23

FIGURE 19 - DDS HEX FILE HEADER.....................................................................................................24

Table of tables

Page 4 of 29


5/29

WISP User Manual

TABLE 1 - COMMAND LINE I2C SETTINGS..........................................................................................10

TABLE 2 - COMMAND LINE ENTER ISP MODE...................................................................................13

TABLE 3 - SECTOR NUMBERS..................................................................................................................14

TABLE 4 - COMMAND LINE ERASE FLASH..........................................................................................15

TABLE 5 - COMMAND LINE WRITE FLASH.........................................................................................18

TABLE 6 - VERIFY ADDRESSES ..............................................................................................................19

TABLE 7 - COMMAND LINE VERIFY FLASH........................................................................................20

TABLE 8 - COMMAND LINE PROGRAM DSP........................................................................................23

Page 5 of 29


6/29

WISP User Manual

History

Date Applied changes Version

27-4-2002 Document creation Draft

15-8-2002 Update for version 2.0 Final 2.0

12-2-2003 Update for version 2.4 Draft 2.414-2-2003 Update after review Final 2.4

Abbreviations

Abbreviation Explanation

WISP Windows In System Programming

ISP In System Programming

DSP Digital Sound Processor

SSD Stereo Sound Decoder

[INSTALLDIR] C:\Program Files\I2C DeviceHandling\WISP\

ReferencesRef. 1 - WIC32 User Manual

Ref. 2 - The I2C-Bus specification(http://www.semiconductors.philips.com/acrobat/various/I2C_BUS_SPECIFICATION_3.pdf)

Requirements PC with the Windows operating system. WISP has been tested on:Windows 95 English

Windows 98 English / Simplified Chinese / Traditional Chinese /

Japanese

Windows NT 4.0 English

Windows 2000 English / Simplified Chinese

Windows XP English

At least 10 Mb of hard disk space

At least 32 Mb RAM memory (Recommended 64 Mb or more)

For single master interface a parallel port is needed. (LPT setting = Bi-directional)

For TraciiXL and Connii interface a USB port is needed.

Intended AudienceThis user manual is intended for all users that plan to use WISP in order to program the flash

memory or to upload software into the DSP.

Page 6 of 29


7/29

WISP User Manual

1 What is WISP?WISP is an abbreviation of Window In System Programming and can be used to program the flash

memories of the Painter and the DSP of the Stereo Sound Device of the UOC III. The

communication with the UOC III is realized using the I2C protocol.

WISP has two interfaces:

1 Graphical User Interface

2 Command line Interface

Both interfaces will be discussed in the remainder of the document. For help about command line

options it is also possible to use:

WISP /h

WISP /?

WISP /help

See appendix B for a list of all command line options.

1.1 What is needed to work with WISPIn order to work with WISP several things must be in order:

A correctly installed WISP application

A properly working I2C connection

A single master interface

A Connii interface

A TraciiXL interface

A Intel Hex file for programming flash memory

A .pro and .yco for programming the DSP

1.2 Installing WISPThe WISP application is part of the I2C DeviceHandling installation. Run Setup.exe to install

WISP. Follow the instruction on the screen. Since this setup uses only standard setup screens,

further details are not discussed. When the setup finishes successfully the PC must be restarted.

1.3 I 2C ConnectionMake sure all cables are connected properly and that the I2C bus is connected to the parallel printer

port (ECP) of the PC. For more information no I2C see Ref. 2

Page 7 of 29


8/29

WISP User Manual

2 WISP

2.1 Graphical User InterfaceUsing ISP to program the flashes makes a subset of functions available to communicate with the

UOC III. These functions are Entering ISP, Erasing, Programming, and Verifying the flash.

The tool uses four easy steps to program the flash memory. These steps are:

1 Set the device into ISP mode so that the flashes can be erased, programmed and verified.

2 Erase the flash memories

3 Write the hex file containing program and character code to the flash memories

4 Verify that the data is uploaded correctly.

After selecting one of the four functions the User Interface will show the appropriate controls

associated with that function. Set the parameters to the desired values and press Send. The data

is now transmitted to the device.

Figure 1 - WISP User Interface

The first selection to be made is whether WISP is used for the Picasso 100 or the Picasso 10.

Selecting one of the options lets WISP know what kind of device you are planning to address. The

only difference is the address ranges that are used to perform the four ISP functions.

Page 8 of 29

1

2

3

4


9/29

WISP User Manual

The current status of actions being performed is shown in the ISP status box. The time it takes to

perform the selected function is shown at the bottom of the ISP status frame as Elapsed time.

Figure 2 - ISP status display

The status bar indicates the I2C status with the help of two leds. Green indicates communication is

Ok and red indicates a communication problem. The I2C status is not continuously updated but

only after read or write commands.

The second indication on the status bar is the communication speed in kilobits per second. This

speed can be changed in the I2C Configuration window (see paragraph 2.2.3.1)

Furthermore messages concerning I2C and instructions of what to do next are also displayed on the

status bar.

Figure 3 - Status bar

2.2 MenuStart the application by selecting the WISP option from the menu Programs I2C Devicehandling

or by double-clicking the shortcut on the desktop. The application starts and the WISP interface is

shown. WISP can also be started from the Tools menu in WIC32 (see Ref. 1 - WIC32 UserManual)

Figure 4 - WISP menu

2.2.1 File

TheFile menu only contains the optionExit (Ctrl-Q). SelectingExitcloses the WISP application.

When WISP is exited the settings in the User Interface are saved and will be restored the next time

WISP is started again. Settings that are saved are:

1. Picasso type selection2. The delay times of the four ISP functions

3. Auto Verify checked or unchecked

4. Blank Check checked or unchecked

5. Show Page Data checked or unchecked

6. Automatic ISP programming checked or unchecked

7. DSP file selection

8. DSP verify checked or unchecked

Command line options:WISP /q

WISP /quit

Page 9 of 29

ISP Status box

Elapsed time


10/29

WISP User Manual

This command line option exits the WISP application

2.2.2 View

The View menu contains the optionAutomatic mode on / off (Ctrl-M). This shows or hides the User

Interface for automatically erasing, programming, and verifying the flash memories. For more

information see the explanation in paragraph 4.

2.2.3 Settings

2.2.3.1 I2C Configuration

When WISP is started check the I2C configuration to make sure that the communication parameters

are set correctly for your setup.

Press Ctrl-Ior

Select menu Settings I2C Configuration

Figure 5 - I2C configuration settings

All settings should be correct by default, but changes can be made whenever necessary. For

instance when the PC interface is different.

Command line options:

WISP /SLA=sla [/BITRATE=b] [/INTERFACE=i] [/PORT=p]

Setting the I2C communication via the command line

/SLA Device address to communicate with device(52 for ISP, B0 for SSD)

Mandatory

/BITRATE Bit rate of communication in kilobits per

second

Optional.

Default is 100 kbits/sec

/INTERFACE PC interface (singlemaster, multimaster,

hardwareless, conni, tracii

Optional.

Default issinglemaster

/PORT PC port (lpt1, lpt2, lpt3, or usb) Optional.

Default is lpt1

Table 1 - Command line I2C settings

Example:

Communication with ISP using a singlemaster interface on parallel port 1 and speed 100 kbits/sec.

WISP /SLA=52 /BITRATE=100 /INTERFACE=singlemaster /PORT=lpt1

Page 10 of 29


11/29

WISP User Manual

Communication with SSD using a connii interface on usb port and speed 400 kbits/sec.WISP /SLA=B0 /BITRATE=400 /INTERFACE=connii /PORT=usb

2.2.3.2 Set default values

This option can be selected from the menu Settings Set default values. Selecting this option sets

all values back to their default values. Delay times are set to the default value

Address ranges are set to the default value

Pin code is set to the default value

2.2.4 Help

The Help menu contains the optionAbout WISP (Ctrl-A). This provides information about the

WISP version.

Page 11 of 29


12/29

WISP User Manual

3 Manual ISP programming

3.1 General settingsThe General frame is used for all four ISP functions.

Figure 6 - General WISP settings

3.1.1 Flash selectionThe combo box Flash Selection determines on which flash the ISP function is going to act.These are the selections that can be made:

1. Program (Erase, Write, Verify)

2. Character (Erase, Write, Verify)

3. PK26 (Erase, Write, Verify)

4. All (Erase, Write, Verify)

5. Manual (Enter ISP Mode, Erase, Write, Verify)

3.1.2 Mode byte

The textbox Mode byte contains a hexadecimal number that sets the UOC III into the right mode

before the actual data is written. The Mode byte textbox is normally filled in automatically. Only

when the Flash Selection is set to Manual the Mode byte can be changed.

3.1.3 Delay time

The last setting in the General frame is the textbox Delay time. This is a minimal delay time in

milliseconds necessary to perform the ISP function. This time can be changed whenever it seems

necessary to delay an ISP action less or more. The values are saved when WISP is exited and

restored when WISP is started again.

Select the menu option Settings Set default values to return to the default delay times.

3.1.4 ROM status

The texts at the bottom of the General frame are meant for displaying the status when the flash is

being verified after an erase or write action. In case of success Ok is displayed in a green color,

otherwise Failed in a red color for each flash part separately.

Page 12 of 29


13/29

WISP User Manual

3.2 ISP functions

3.2.1 Enter ISP mode

Before any of the other ISP functions can be used the UOC III has to be set into ISP mode. This

can be achieved by sending the correct pin code. The default pin code is 55.

After Entering ISP mode it becomes possible to perform the other functions Erase, Write, andVerify.

Figure 7 - Enter ISP mode

To Enter ISP mode:

1. Press the Enter ISP Modebutton

2. Set the correct Pin code value (default value should be correct)3. Press the Sendbutton

Select the menu option Settings Set default values to return to the default pin code.


WISP /TASK=enter_isp [/PIN=x] [/DELAY=d]

Enter ISP mode via the command line

/TASK Determines which task WISP has to perform. Mandatory

Task: enter_isp/PIN The pin to address on the UOC III to put it into

ISP mode

Optional.

Default is 55

/DELAY The delay time in milliseconds after the task is

executed.

Optional.

Default is 0 ms

Table 2 - Command line Enter ISP mode

Example:

Setting the UOC III device into ISP mode.WISP /TASK=enter_isp

Setting the UOC III device into ISP mode using all parameters

WISP /TASK=enter_isp /PIN=55 /DELAY=10

Page 13 of 29

1

2

3


14/29

WISP User Manual

3.2.2 Erase flash

3.2.2.1 Erasing

Erasing the flash clears all programmed data of the flash selected in the Flash selection. Erasing

means setting the flash contents to FF.

Figure 8 - Erasing flash memory

To erase a flash memory:

1. Select the Erase Flash button

2. Select the flash to erase from the Flash selection combo box

3. Set the erase parameters (Start sector and end sector are only available when Manual isselected in the Flash selection combo box).

4. Press the Send button

Only when the Flash selection is set to Manual all the erase parameters can be changed. The

sector start address and sector end address can be inputted. When the parameters are not consistent

with the mode byte selection or contain an invalid value the parameters are corrected automatically

when possible.

Flash selection Maximum number of

sectors (Picasso 100)

Maximum number of

sectors (Picasso 10)

Program 6 (sector 0 till 5) 4 (sector 0 till 3)Character 1 (sector 0) 1 (sector 0)

PK26 1 (sector 7) 1 (sector 5)

All 9 (sector 0 till 8) 6 (sector 0 till 5)

Table 3 - Sector numbers

If both parameters are filled in, all sectors in that range are erased up to and including the end

sector. When the end sector is left empty only the sector filled in in the start sector is erased.

Erasing is always performed sector by sector.

Select the menu option Settings Set default values to return to the default sector values.

Page 14 of 29

1

2

3

4


15/29

WISP User Manual


WISP /TASK=erase_** [/DELAY=d]

WISP /TASK=erase /MODE=m /STARTSECTOR=ss /ENDSECTOR=ee [/DELAY=d](** = prog, char, pk26, or all)

Erase flash memory via the command line


Task: erase_prog,

erase_char,

erase_pk26,

erase_all,

erase

/MODE Sets the UOC III device into the erase mode Mandatory for manual

erase

/STARTSECTOR Sets the beginning of the flash sector range to

erase

Mandatory for manual

erase

/ENDSECTOR Sets the end of the flash sector range to erase Mandatory for manualerase

/DELAY The delay time in milliseconds between each

erase command and after the task is executed.

Optional.

Default is 400 ms

Table 4 - Command line Erase flash

Example:

Erasing all flash sectorsWISP /TASK=erase_all

Erasing only the Character flash with a longer delayWISP /TASK=erase_char /DELAY=500

Manually erasing the Program flash sectors 1, 2, and 3 with a default delay timeWISP /TASK=erase_prog /STARTSECTOR=1 /ENDSECTOR=3

3.2.2.2 Blank check

When the Blank Check on/off option is checked WISP first verifies if the ROM selected in

Flash selection is already empty. When the flash is empty (Verify Ok) the Erase command is not

send. When the flash is not empty (Verify Failed) the flash is erased.

Figure 9 - Blank check option

Page 15 of 29

Blank check


16/29

WISP User Manual

3.2.2.3 Auto verify

When the Auto Verify option is checked in the ISP status frame the Erase is followed by an

automatic verification. When the flash is correctly erased the ROM status shows Ok, otherwise

Failed

Figure 10 - Auto Verify option

3.2.3 Write flash

3.2.3.1 Writing

Writing to the UOC III can only be performed page by page. One page is equal to 256 bytes of

data. This data is read from an Intel Hex file that is created by the DDS Promt tool. This Intel Hex

file normally contains all the data for the Program ROM, the PK26 ROM, and the Character ROM.

When data of, for instance, the Character ROM is not available in the Intel Hex file the Flash

selection will not show the selection for the Character ROM.

An option of the DDS Promt tool is to create the Intel Hex file with or without a comment section.

When the comment section is left out, WISP cannot determine how large the flash memories are

and a flash size of 192Kb is assumed for the Picasso 100 and 128Kb for the Picasso 10.

The blocks of data are extracted from the Intel Hex file, converted to pages, and the page addresses

are set equal to the address information that is located in the comment section of the Intel Hex file

(when available). For more information on the Intel Hex file comment section see chapterA.

Figure 11 Programming flash memory

Page 16 of 29

Auto Verify

13

2

4


17/29

WISP User Manual

To program a flash memory:

1. Select the Write Flash button

2. Select the flash to write from the Flash selection combo box

3. Load the Intel Hex file by pressing the Browse button


Pressing the Browse button opens a dialog to select the Intel Hex file. When an Intel Hex file

is selected the data is loaded. Loading progress is shown in the status bar. Below the Browse

button is indicated, No data loaded when the Intel Hex file is not loaded yet, and Data is

loaded successfully [] when an Intel Hex file has been loaded.

Figure 12 No Intel Hex file loaded

Figure 13 - Intel Hex file loaded

When you want to view the data page by page select the Show page data checkbox. The

scrollbar scrolls through the pages of the flash that is selected in the Flash selection control.

Uncheck the Show page data checkbox to hide the page data again.

3.2.3.2 Auto Verify

When the Auto Verify option is checked the Write action is followed by an automatic

verification. When the flash is correctly programmed the ROM status shows Ok, otherwise

Failed. See also Figure 10 - Auto Verify option

Page 17 of 29


18/29

WISP User Manual


WISP /TASK=write_** /FILE=[drive:\][path\]filename.HEX [/DELAY=d]

WISP /TASK=write /MODE=mm /FILE=[drive:\][path\]filename.HEX [/DELAY=d](** = prog, char, pk26, or all)

Write flash memory via the command line


Task: write_prog,

write_char,

write_pk26,

write_all,

write

/FILE Sets the location of Intel Hex file Mandatory

/MODE Sets the UOC III device into the write mode Mandatory for manual

write


write command.

Optional.

Default is 1 ms

Table 5 - Command line Write flash

Example:

Writing all flash memoriesWISP /TASK=write_all /FILE=[INSTALLDIR]\DDS File\HS_Workbnch_v13.hex

Writing only the Character flash with a longer delayWISP /TASK=write_char /FILE=[INSTALLDIR]\DDS File\HS_Workbnch_v13.hex

/DELAY=15

Manually writing the Program flash with a default delay timeWISP /TASK=write /FILE=[INSTALLDIR]\DDS File\ HS_Workbnch_v13.hex /MODE=80

3.2.4 Verify flash

3.2.4.1 Verifying

The verify function can be used at two moments:

1. After the flash has been erased to verify if the flash is erased correctly.

2. After the flash has been written to verify if the flash is programmed correctly.

All parameters are filled in automatically again, except when Manual is selected in the Flash

selection. Now it is possible to change the range of verification.

Page 18 of 29


19/29

WISP User Manual

Figure 14 - Verifying flash memory

To verify a flash memory:

1. Select the Verify Flash button

2. Select the flash to verify from the Flash selection combo box

3. Set the verify parameters (Start address and stop address are only available when Manual

is selected in the Flash selection combo box).


Only when the Flash selection is set to Manual all the verify parameters can be changed. Enter

the address range by specifying a start and stop address. When the addresses are not consistent with

the Mode byte selection they are corrected automatically when possible.

Flash selection Address ranges

(Picasso 100)

Address ranges

(Picasso 10)

Program 0000h 2FFFh 0000h 1FFFh

Character 0000h 07FFh 0000h 07FFh

PK26 3100h 31FFh 2100h 21FFh

Table 6 - Verify addresses

Select the menu option Settings Set default values to return to the default address values.

NOTE:When WISP is started and no Intel hex file has been loaded, WISP assumes that the flashes are

erased and will verify them as such. This means when the flashes are programmed and the

corresponding Intel hex file is not loaded, WISP will report Verify Failed on a Verify action.

To solve this load the correct Intel Hex file and verify the flash again.


WISP /TASK=verify_** [/DELAY=d]

WISP /TASK=verify /MODE=mm /STARTADDR=ssss /ENDADDR=eeee [/DELAY=d]

WISP /LOAD=[Path:\]filename.hex(** = prog, char, pk26, or all)

Page 19 of 29

1

4

3

2


20/29

WISP User Manual

Verify flash memory via the command line


Task: verify_prog,

verify_char,

verify_pk26,

verify

/MODE Sets the UOC III device into the verify mode Mandatory for manual

verify

/STARTADDR Address to start verification from Mandatory for manual

verify

/ENDADDR Address to end verification at Mandatory for manual

verify


write command.

Optional.

Default is 10 ms

Table 7 - Command line Verify flash

Example:

Verifying only the Character flash with a longer delay (assumed is that the flash is erased)WISP /TASK=verify_char /DELAY=15

Manually verifying the Program flash from address 010Fh till 01FFh with a default delay time

(assumed is that the flash is erased)WISP /TASK=verify /MODE=C0 /STARTADDR=010F /ENDADDR=01FF

Load Intel hex file first to verify if this data has been programmed correctly in the Character flashWISP /LOAD=[INSTALLDIR]\DDS Files\HS_workbnch_v13.hexWISP /TASK=verify_char

Page 20 of 29


21/29

WISP User Manual

4 Automatic ISP ProgrammingIn order to activate Automatic ISP programming:

1. Press Ctrl-M

2. Select the menu option View Automatic mode on / off

The User Interface changes and shows only two buttons now, which are Browse and Auto

Execute. The Automatic ISP programming is only available for the Picasso 10.

Figure 15 Automatic ISP Programming interface

The Blank check on/off and Auto verify on/off options can be selected or deselected as on the

Manual ISP programming interface. The differences between the interfaces are:

1. The General section shows the status for the Erase and Write actions separately

2. Page data cannot be viewed. There is only the indication that the data is loaded.

3. All ISP actions are performed automatically. First flashes are erased, verified for correct

erase, programmed with the loaded data, and then verified for correct programming.

All default settings are used to perform the Automatic ISP programming. See Table 2, Table 4,

Table 5, and Table 7 for the default settings.

Open the Intel Hex file by selecting the Browsebutton. The loading progress is indicated on

the status bar. When the data is loaded select or deselect the Blank check on/off and Auto verify

on/off. After that, pressing the Auto Execute button starts the automatic execution of Erase,

Write, and Verify. The statuses of erase and write success or failures are indicated in the General

frame.

Page 21 of 29


22/29

WISP User Manual

5 DSP programmingIn order to get sound out of the Stereo Sound Decoder it has to be programmed, because at this

moment the code is stored in RAM memory. The consequence of this is that each time the set is

powered off the DSP must be programmed again. From Picasso 10 N1B and later it is not

necessary to program the DSP, but when the software needs to be updated it is still possible toprogram the DSP.

Figure 16 - WISP DSP programming

To start programming WISP must know what file it must upload. Press the Browse button and

select either the .YCO or .PRO file. Both .YCO and .PRO must be in the same directory, because

for programming both files are needed.

After this press Start Upload and the DSP programming starts indicated by a progress bar. If for

some reason the programming must stop press the Stop Upload button and programming is

aborted.

When the option Verify after upload is selected the programmed DSP is verified. When the

verification is successful Verify: Ok is shown in a green color. When the verification fails the

text Verify: Failed is shown in a red color

Figure 17 - DSP programming successful

Page 22 of 29


23/29

WISP User Manual

Figure 18 - DSP programming failed

Programming of the DSP can fail because of an I2C communication error or the actual

programming of the DSP failed.


WISP /TASK=dsp_program /DSPFILE=[drive:\][path\]filename [/DSPVERIFY]

Program DSP via the command line

/TASK Determines which task WISP has to perform. MandatoryTask: dsp_program

/DSPFILE Path to the .YCO and .PRO file Mandatory

/DSPVERIFY Start verification after DSP is programmed Optional

Table 8 - Command line Program DSP

Example:

Program DSPWISP /TASK=dsp_program /DSPFILE=[INSTALLDIR]\DSP Files\Hercules.pro

Program DSP and verifyWISP /TASK= dsp_program /DSPFILE=[INSTALLDIR]\DSP Files\Hercules.pro

/DSPVERIFY

Page 23 of 29


24/29

WISP User Manual

A.DDS hex file formatThe DDS Promt tool outputs a hex file containing a comment section and a data section. When the

comment section has been removed from the hex file WISP assumes a 192Kb flash size.

When WISP reads the hex file it divides the data into blocks:

Program block Lower Character block

Upper Character block

PK26 block

Each block of data can be written to the addresses as indicated in the comment section of the hex

file. For instance see example below:

Creation Record for Hercules192k_Ske_Mar072002.hex - PROMT Version 4.8File created on 07/03/2002 at 11.57.19 by CST, PhilipsBuffer's checksum = 03F0EC1C over range 0 - 60FFFMemory map used

Common + Bank 0 00000000H - 0000FFFFH, GTVSKY_011221.hexBank 1 00010000H - 00017FFFH, GTVSKY_011221.hexBank 2 00018000H - 0001FFFFH, GTVSKY_011221.hexBank 3 00020000H - 00027FFFH, GTVSKY_011221.hexBank 4 00028000H - 0002FFFFH, GTVSKY_011221.hex

Lower Character Set 00040000H - 00043FFFH, Font1l.ihxUpper Character Set 00050000H - 00053FFFH, Font1u.ihxPacket 26 00060000H - 00060FFFH, Font1pkt.ihxMerged File - Hercules192k_Ske_Mar072002.hex

Device - Hercules192kProject - Hercules192kStartstamp0373033323030323008456273657C65637139323B600endstampEnd of creation record for file Hercules192k_Ske_Mar072002.hex

Figure 19 - DDS hex file header

The Program ROM data can be written to the address range 00000 2FFFF.

The Lower Character ROM data can be written to the address range 40000 43FFFF

The Upper Character ROM data can be written to the address range 50000 53FFFF

The PK26 ROM data can be written to the address range 60000 60FFFF

An Intel HEX file is composed of any number of HEX records. Each record is made up of five

fields that are arranged in the following format:

:llaaaatt[dd...]cc

Each group of letters corresponds to a different field, and each letter represents a single

hexadecimal digit. Each field is composed of at least two hexadecimal digits-which make up a

byte-as described below:

: is the colon that starts every Intel HEX record.

ll is the record-length field that represents the number of data bytes (dd) in the record.

aaaa is the address field that represents the starting address for subsequent data in the record.

Page 24 of 29


25/29

WISP User Manual

tt is the field that represents the HEX record type, which may be one of the following:

00 - data record

01 - end-of-file record

02 - extended segment address record

03 start segment address record

04 - extended linear address record

05 start linear address record

dd is a data field that represents one byte of data. A record may have multiple data bytes. The

number of data bytes in the record must match the number specified by the ll field.

cc is the checksum field that represents the checksum of the record. The checksum is calculated by

summing the values of all hexadecimal digit pairs in the record modulo 256 and taking the two's

complement.

Page 25 of 29


26/29

WISP User Manual

B.Command line parameters

HELP

WISP /hWISP /?WISP /help

CHANGE I2C SETTTINGS

WISP /SLA=sla [/BITRATE=b] [/INTERFACE=i] [/PORT=p]

ENTER ISP MODE

WISP /TASK=enter_isp [/PIN=x] [/DELAY=d]

ERASE FLASH

WISP /TASK=erase_** [/DELAY=d]WISP /TASK=erase /MODE=m /STARTSECTOR=ss /ENDSECTOR=ee [/DELAY=d](** = prog, char, pk26, or all)

WRITE FLASH

WISP /TASK=write_** /FILE=[drive:\][path\]filename.HEX [/DELAY=d]WISP /TASK=write /MODE=mm /FILE=[drive:\][path\]filename.HEX [/DELAY=d](** = prog, char, pk26, or all)

VERIFY FLASH

WISP /TASK=verify_** [/DELAY=d]WISP /TASK=verify /MODE=mm /STARTADDR=ssss /ENDADDR=eeee [/DELAY=d]

LOAD INTEL HEX FILE

WISP /LOAD=[Path:\]filename.hex

PROGRAM DSP

WISP /TASK=dsp_program /DSPFILE=[drive:\][path\]filename [/DSPVERIFY]

EXIT WISP

WISP /qWISP /quit

Page 26 of 29


27/29

WISP User Manual

C.Troubleshooting

I2C

Errors about I2C are logged in I2cErrLog.txt in the WISP directory

GENERAL

Error reading file. Check access rights on directory and file.

The file cannot be opened for reading. Check if you have access rights in this directory and access

right to read the file.

Error parsing file. File is corrupt or may have an incorrect format.

The file is opened successfully, but now the content of the file is not correctly formatted or the

content is corrupt. Try to open the file again or replace the file with the file that is delivered with

the installation. Make sure the file is in the correct format.

Error creating device configuration file.

On the first start-up of WISP the application needs to write in the directory where WISP is

installed. Make sure this is possible.

Invalid mode byte. Please change to other value.

This message is likely to appear when Manual is selected in the Flash selection combo box.

The mode byte is not valid. Enter another value.

Mode byte / parameter combination not valid. Check if mode byte is correctthen press Send.

The manual selected parameters are not consistent with the Mode byte selection. Change the

parameter values or the mode byte then press Send again.

Internal error. Unknown flash selection.

The selection made in the combo box Flash Selection was not expected by WISP and can

therefore not be handled. This message should never occur. Contact your WISP distributor when

this message is displayed.

Internal error. Unknown function selected.

The selection made in the combo box Flash Selection in combination with the Mode byte value

was not expected by WISP and can therefore not be handled. This message should never occur.

Contact your WISP distributor when this message is displayed.

Internal error. Unknown record type.

The Intel Hex file contains a record type that is not expected by WISP. This message should never

occur. Contact your WISP distributor when this message is displayed.

ENTER ISP

Device may already be in ISP mode. Are you sure you want to send commandagain?

The Enter ISP command has already been sent since WISP was started. When the TV set has not

been switched off in the meantime it is not recommended to send the Enter ISP command again.

Page 27 of 29


28/29

WISP User Manual

ISP WRITE

Picasso 10 is selected and a Picasso 100 file is loaded. Writing this data tothe Program ROM will always result in a verify failure.

This message is shown on two occasions. First when the Picasso selection option is set to

Picasso 10 and a Picasso 100 Intel Hex file is loaded. The second possibility is when a Picasso 100

Intel Hex file is loaded and the Picasso selection option is set to Picasso 10.

Picasso 100 is selected and a Picasso 10 file is loaded. Writing this data tothe Program ROM will always result in a verify failure.

This message is shown on two occasions. First when the Picasso selection option is set to

Picasso 100 and a Picasso 10 Intel Hex file is loaded. The second possibility is when a Picasso 10

Intel Hex file is loaded and the Picasso selection option is set to Picasso 100.

No data loaded.

Before programming of the flash memory can start you have to load an Intel Hex file.

PROGRAM DSP

Loading of the .yco file failed.

An error occurred during reading of the .yco data. Check that it is a valid .yco file and that the file

is not corrupt.

Loading of the .pro file failed.

An error occurred during reading of the .pro data. Check that it is a valid .pro file and that the file is

not corrupt.

Starting of the DSP failed.

DSP did not start up. No sound can be heard now. Reprogram the DSP.

Uploading of the data failed.

During programming of the DSP an error occurred. Reprogram the DSP.

Reset of the DSP failed.

DSP could not be stopped. Reprogram the DSP. It may be necessary to power down the TV set and

turn it on again.

Unable to locate Y-mem file in specified directory.

The .yco file cannot be found in the same directory as the .pro file. Both files must also have the

same name.

Unable to locate P-mem file in specified directory.

The .pro file cannot be found in the same directory as the .yco file. Both files must also have the

same name.

Selected file is not a valid Y-Memory file.

The .yco file is not recognized by WISP to be a valid .yco file. WISP checks the comment section

of the .yco file.

Selected file is not a valid P-Memory file.

The .pro file is not recognized by WISP to be a valid .pro file. WISP checks the comment section

of the .pro file.

Page 28 of 29


29/29

WISP User Manual

Verified data does not match uploaded data. Verify failed.

Verification of the DSP failed. Data that was programmed is not the same during verification.

Reprogram the DSP.

COMMAND LINE

Unable to find WispConsole.exe in application directory.

The output window (WISPConsole) that shows the status of what WISP is doing cannot be started,

since the WispConsole.exe file cannot be found in the WISP directory.

Manual Do Software Philips

Documents

Transcript of Manual Do Software Philips