Assert in a custom module

Clement FR

Genius 4750 points

Other Parts Discussed in Thread: SYSBIOS

Hello everyone,

(target C6678, CCS 5.5, BIOS 1.25, XDCTools 3.25)

I built a custom timestamp module here (http://e2e.ti.com/support/embedded/bios/f/355/t/303799.aspx)

and now I want to use asserts in it.

So in my Timestamp.xdc I have now

import xdc.runtime.Assert;
import xdc.runtime.Diags;

module Timestamp inherits ti.sysbios.interfaces.ITimestamp
{

   config Assert.Id A_TimestampError = {
        msg: "A_TimestampError : this is a timestamp test Error."
    };
}

but unfortunately when I build it : here's what I get

xdc --xdcpath="<mypath>/xdctools_3_25_03_72/packages;<mypath>/bios_6_35_04_50/packages;" all

making package.mak (because of package.bld) ...

js: "D:/CoralieDev/ccsv5/xdctools_3_25_03_72/packages/xdc/bld/BuildEnvironment.xs", line 146: TypeError: Cannot find function hasReportedError in object [object Object].

xdctools_3_23_04_60\gmake.exe: *** No rule to make target `package.mak', needed by `.interfaces'. Stop.

I'm a bit confused about this error message.

Also I have two versions of XDC (3.23 and 3.25) installed. How can I make sure it uses xdc 3.25 ?

When I run xdc -n I see that the version 3.23 is used.

Thank you

Clement

over 11 years ago

0 Raja over 11 years ago

TI__Guru* 81335 points

Hi Clement,

I think if you remove or rename old xdc and use the 3.25.2.70 xdctools instead, the problem should go away.

Please refer the similar threads on XDC below, which may help you to solve your issue.

http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/295990.aspx

Thanks.

0 Clement FR over 11 years ago in reply to Raja

Genius 4750 points

Hi Rajasakeran,

I fixed the xdc 3.25 vs xdc 3.23 issue.

I have an import issue and I don't get why it doesn't work.

Here's my command

"<mypath>\xdctools_3_25_03_72\xdc" --xdcpath="<mypath>/bios_6_35_04_50/packages;<mypath>/xdctools_3_25_03_72/packages;" all

I get the following error

<...> Timestamp.xdc line 8: no viable alternative at input 'import'
error: compilation of package.xdc failed: parser failed.

In timestamp.xdc line 8

I have import xdc.runtime.Assert
and in my cmd there is the path to xdctools_3_25_03_72/packages;
so it should be able to find it.

I don't get what the error is.

Clement

0 Clement FR over 11 years ago in reply to Clement FR

Genius 4750 points

Ok I found a workaround

I deleted the line import xdc.runtime.Assert

and in the code instead of Assert.Id I put xdc.runtime.Assert.Id

and it works now.

Still, I don't why the 'import' thingy failed.

Clement

0 Sasha Slijepcevic over 11 years ago in reply to Clement FR

TI__Mastermind 37985 points

Clement,
the error message you are seeing about 'import' is usually the result of the import statements and the module declarations being in a wrong order. Can you post your complete XDC spec file (the version of it that fails) or at least all the lines at the beginning of it until the line
module Timestamp inherits ... ?

0 Clement FR over 11 years ago in reply to Sasha Slijepcevic

Genius 4750 points

Sasha,

It only has

import xdc.runtime.Assert;
import xdc.runtime.Diags;

@ModuleStartup
module Timestamp inherits ...

0 Sasha Slijepcevic over 11 years ago in reply to Clement FR

TI__Mastermind 37985 points

No comments or anything? The error message in a previous post was in line 8.

0 Clement FR over 11 years ago in reply to Sasha Slijepcevic

Genius 4750 points

I'm no longer at work and am no on holidays
so I won't get access to the file before january 6th.
I'll follow up on this thread until the end of the usual work week though.

From what I recall I have a comment similar to this

/*!
 *  ======== Timestamp ========
 *  Example implementation of ITimestampProvider
 */

before

import xdc.runtime.Assert;
import xdc.runtime.Diags;

module Timestamp inherits ti.sysbios.interfaces.ITimestamp
{

   config Assert.Id A_TimestampError = {
        msg: "A_TimestampError : this is a timestamp test Error."
    };
}

The line 8 is where the first 'import' is.

Clement

0 Sasha Slijepcevic over 11 years ago in reply to Clement FR

TI__Mastermind 37985 points

That type of comment that starts with '/*!' has to come after imports and the optional package declaration. We haven't documented that well,but I'll add it on my todo list.

0 Clement FR over 11 years ago in reply to Sasha Slijepcevic

Genius 4750 points

Hello Sasha,

I'm back.

Yes I had comments before the '"import"

I tried without them and it works now.

It's a nasty bug indeed.

Thank you for your help.

Clement

Processors

Processors forum

Assert in a custom module