Installation procedure for ISSM 2016

[praveen_r_]

Hi

I am new to the intel softwares.

I have installed the ISSM 2016 in my system.

I am unable to move forward with the code.

whenever I try to build any program I get an error called "error in final launch sequence".

Hoping for response at earliest.

Thank in adavance 

[Jonghak_K_Intel]

Hi Praveen,

 Sorry for this late response.  

 First of all, The message you are getting seems related to GDB. Please make sure to use the GDB included in the ISSM 2016 package.

If using the right GDB doesn't fix the issue, could you please specify your development environment in detail?

 for example, eclipse version and ISSM 2016 version.

Also please  follow the instruction that ISSM 2016 provides in the documents.

Let us know if there's  further questions.

[praveen_r_1]

Hi Jon

Thank you for the reply.. yes the problem was with the gdb. I got it right once i follwed the instruction set..

I am able to code in the ide.. the problem is do you have any sample example code for any simple project or task like enabling the pin as input or output or initialisation of UART. It would be helpful if you provide any one simple code.

Thanks in advance.

[praveen_r_1]

Hi Jon

I am getting the same error has earlier...

Hello world program is not getting executed.

I am attaching the jpg file of the error .. pls get back at the error ..

Let me explain the procedure that i have created the project.

1.go to intel issm in tool bar.

2. selecte intel new intel qmsi/bsp project.(hello world project)

3.Provided with the project name , alond with author name etc.

4.Finish

5.Build the created project.

6.Run as issm

is the procedure correct. if so what is the error????

Thanks in advance

Praveen

[Jonghak_K_Intel]

Hi Praveen,

 Thanks for the report.

 It seems like your D2000 board isn't successfully connected to your host so OpenOCD can't work properly.

Please visit http://zadig.akeo.ie/ and download zadig corresponding to your host OS version.

When D2000 board is connected,

1 . run zadig and click "Option" -> check "List all devices"

2. Find "Mint Field Fab B" and click

3. Install WinUSB Driver.

Then try your work again.

Thank you!

[praveen_r_1]

Hi Jon

I got it right with the hardware settings and able to load the code into the board.

I am getting confused with the pin configuration set up.

/****** code  have written to configure **********/

qm_pmux_select(QM_PIN_ID_0, QM_PMUX_FN_0);        /* pin 0 set has gpio pin*/

    while(1)
    {

    qm_gpio_set_pin(QM_GPIO_0, PIN_OUT);            /*set pin0 to high*/

    qm_gpio_set_pin(QM_GPIO_0, PIN_LOW);            /*make pin0 low*/
    qm_gpio_read_pin(QM_GPIO_0,PIN_OUT);            /*read pin0 value*/

    result=qm_gpio_read_pin(QM_GPIO_0,PIN_OUT);

    }

/*////**** i don have the description of pin_id....

can you help me out..

thank you

[Jonghak_K_Intel]

Hi Praveen,

I am glad that you figured the driver part out and flashed successfully.

Could you tell me what board you are using?

[praveen_r_1]

Hi Jon

board am using is Mint field h79866202.

Can you just provide one instruction to initiate the gpio pin. like making it high and low.

The instruction set available in the sample code is confusing.

eg:  qm_pmux_select(QM_PIN_ID_0, QM_PMUX_FN_0);

Above instruction states pin_id_o can be used has gpio pin based on function selection function_0.

Just provide one example.

Thanks in advance

[Jonghak_K_Intel]

Hi Praveen,

I attached the pin description of D2000 board and you can ask the source you got your board from for the full version of the reference document.

 regarding for example codes you've asked, you already have that with your ISSM 2016 package.

e.g. ) C:\IntelSWTools\ISSM_2016.0.027\firmware\bsp\1.0\examples , you will see lots of example codes in there.

Also, importantly, the QMSI document is available here : C:\IntelSWTools\ISSM_2016.0.027\firmware\bsp\1.0\doc\pdf .

Hope this helps!!

[praveen_r_1]

Hi Jon

I have all the docs you have sent.

Thanks

[praveen_r_1]

Hi jon

what is the difference between pin_id and pin number.

thank you

[praveen_r_1]

Hi jon

Analog to Digital conversion

We  tried accessing  analog values from the sample program.

 connected lm35, temperature sensor which outputs analog values.

 the value that we are getting is not constant, the output value keeps varying.

Even when  10 bit configuration is selected, we get the value of 12 bit resolution with the  varying output values which is not constant.

Actual Result: 1.6a  2.ffe  3.3a  4.ffe  5.75a

Expected Result:1b(27 degree)

GPIO

From the sample programs we were able to enable a single pin. Following is the configuration we tried to enable multiple GPIO pins:

typedef enum { QM_GPIO_0 = 0, QM_GPIO_NUM, QM_GPIO_2 =2, QM_GPIO_NUM1 } qm_gpio_t;

the output result was still working for 1 GPIO pin.

Kindly let us know the configuration to enable multiple GPIO pins.  

[Jonghak_K_Intel]

Hi Praveen,

 We were able to reproduce your issue.

I will escalate this problem with ADC and will get back to you as soon as possible.

Thank you!

[praveen_r_1]

hi john

Regarding the previous post ADC and GPIO.

Every-time when i load the code to the CRB i get error launch ....But when i update the ROM and load the code it gets loaded and works fine.

Is there ant problem if ROM is updated every-time...

Thank you

[Jonghak_K_Intel]

Hi Praveen,

For the ADC problem :

This is a bug with the way the ADC_SAMPLE register is read. The sample is stored in the first 12 bits of the register but bit 11 is always the most significant bit so the sample should be shifted right by 2, 4 or 6 bits for 10, 8 or 6 bit mode. This has been fixed in 1.1.

The following can be added wherever the ADC_SAMPLE register is read to get the correct value:

sample = (QM_ADC[adc].adc_sample >> (2 * ( 3 - resolution[adc])));

Are you still getting Error Launch ? could you please give more details when you get that error message?

[praveen_r_1]

Hi jon

I am clear with the adc problem..

Ya the problem of error launch exists still. It does not occur on a regular basis. The error launch exists when I try to load new program. Again updating the ROM provides the solution.

Is there any disadvantage in updating the ROM again and again.

Regards

Praveen

[Jonghak_K_Intel]

Hi Praveen,

could you give me a screen shot of the error msg?

I don't thik there is a problem updating ROM many times but it doesn't seem normal.

Thank you

[praveen_r_1]

Hi John

I have attached the screen shot of the error.

Regards

Praveen

[Jonghak_K_Intel]

Hi Praveen.

The issue screenshot seems to be related to gdb again.

Please check the configurations below :

1. Check if your gdb configuration is correctly set  : Debug Configurations -> Debugger -> GDB Command : C:\IntelSWTools\ISSM_2016.0.027\tools\debugger\gdb\gdb-ia.exe

2. Run Zadig and set the driver to WinUSB ( instead of FTDI )

3. Look if OpenOCD is connected properly in the OpenOCD perspective in Eclipse.

[praveen_r_1]

Hi Jon

I have checked all the links that you had told me. But the issue arises sometimes and again clearing the ROM solves it. 

Can i know whether free RTOS can be made run in the Quark 2000, or do we have any specific RTOS from intel .

Kindly provide the details at the earliest.

Regards

Praveen

[praveen_r_1]

Hi 

The error exists still.

Thanks