[Damien]

I would like to know if it is possible to use GPIO when Multos Trust Anchor is used in contact smart card mode (i.e. when it communicates with ISO7816 smart card interface)?

When my student tried he got a MI_ABEND_REASON_FIREWALL_VIOLATION.

Best regards
Damien

[Chris Torr]

Hi, yes it is possible. You will however get an abend if you don’t set the correct access_list bit or if you initialise the GPIO pins more than once between resets, but those wouldn’t be firewall violations. Look for bad array indexing or bad pointers, anything that produces an out of bounds memory read/write.

Regards,
Chris

[Damien]

Dear Chris,

Thank again. It works perfectly. In MUtil, we have to set the parameter during load of ALU.
#pragma attribute(“access_list”,”1003″) in the program was not enough.

I have not tried again my student’s program when he got firewall violation.

BTW, the miDebuggingEnable() should not be called.

Best regards,
Damien

[Chris Torr]

Hi Damien,

If you’re interested to know why, the attributes are part of the debug file (.hzx) and can be picked up by the tools in Smartdeck, e.g. hterm and melcertgen.

MUtil does not read the debug files, only the final release code (.alu files) so you have to specify the ALC parameters manually in MUtil (or in the KMA interface when using live cards).

Regards,
Chris.

[Author]

Posts