System_printf in SWI - GateMutex assertion failure

Robert Wolfe

Other Parts Discussed in Thread: SYSBIOS

Hello,

I'm getting an unexpected error when making a call to System_printf in a SWI. The SWI runs fine without it, but if adding that in (as needed), it reports the following error after generating the console text specified in the System_printf:

ti.sysbios.gates.GateMutex: line 114: assertion failure: A_badContext: bad calling context. See GateMutex API doc for details.
xdc.runtime.Error.raise: terminating execution

Any help with debugging this would be appreciated.

Robert

IPC 1.22.3.23

SYS/BIOS 6.31.4.27

XDAIS 6.23

XDC 3.20.7.86

over 14 years ago

0 Shreyas Oppanthaya over 14 years ago

Genius 4375 points

Robert,

An explanation of this assert is as follows:

Common causes and workarounds for hitting this Assert:

- Calling printf() from a Hwi or Swi thread.

Use xdc.runtime.System_printf (with SysMin) instead.

- Calling System_printf() from a Hwi or Swi thread when using SysStd.

Use xdc.runtime.SysMin instead of xdc.runtume.SysStd

Use a different type of Gate for BIOS.rtsGateType (ie BIOS.GateHwi or BIOS.GateSwi)

- Calling Memory_alloc() from a Hwi or Swi thread.

Use a different Heap manager

In summary, switching to the 'SysMin' System proxy should fix your problem.

Regards,

Shreyas

0 Shreyas Oppanthaya over 14 years ago in reply to Shreyas Oppanthaya

Genius 4375 points

UPDATE: I've updated my previous post which contained an inaccessible link.

Regards,

Shreyas

0 Robert Wolfe over 14 years ago in reply to Shreyas Oppanthaya

Mastermind 7860 points

Thank you for the reply, and I'm glad to hear there is a solution. But how do I change to the SysMin system proxy?

Robert

0 Shreyas Oppanthaya over 14 years ago in reply to Robert Wolfe

Genius 4375 points

Please ensure that you have the following to your .cfg file:

var System = xdc.useModule('xdc.runtime.System');
var SysMin = xdc.useModule('xdc.runtime.SysMin');
System.SupportProxy = SysMin;

Regards,

Shreyas

0 Robert Wolfe over 14 years ago in reply to Shreyas Oppanthaya

Mastermind 7860 points

I have done as suggested, and no longer get the assertion failure. ;) But can you tell me where the output of the System_printf is going now, since it is no longer sent to the Console window?

Thanks,

Robert

0 Shreyas Oppanthaya over 14 years ago in reply to Robert Wolfe

Genius 4375 points

Using the SysMin module causes all output from System_printf to be placed in an internal SysMin buffer until it is flushed when either:

1) The user calls System_flush() manually causing the buffer to be flushed to the CIO console

2) The application exits

The contents of this buffer (before it has been flushed) can viewed in CCS by visiting the 'xdc.runtime.SysMin' ROV view (Tools -> ROV).

Regards,

Shreyas

0 Georgios Plakaris over 14 years ago in reply to Shreyas Oppanthaya

Prodigy 40 points

Hi,

I run into the same assertion after using an ordinary mutex between a task and an HWI thread.

Using GateHwi instead of Gate should make the trick,

Regards,

Georgios

Processors

Processors forum

System_printf in SWI - GateMutex assertion failure