View previous topic :: View next topic |
Author |
Message |
belve
Joined: 04 May 2006 Posts: 30
|
Posted: Tue Jan 01, 2013 9:12 pm Post subject: Error when reg_file SIM SST file |
|
|
When I have tried to reg_file(ef_sst_path, 3) during ACTION_APP_INIT an error ERR_RESOURCE_BUSY (0x41) occurred and returned by reg_file func. SIM SST file is EF 6F38.
After the error the ACTION_FILE_APDU event for SIM SST file does not work.
I would like to fake some SST table bytes or bits and pass them to ME on initial stage to get some data from ME for my app while it works. Because some SIM services are not allocated and activated in SIM but support by ME as terminal profile responded. May be need to insert some delay before the first SIM SST file SELECT? Please, what to do? |
|
Back to top |
|
|
pz
Joined: 12 Mar 2004 Posts: 1161
|
|
Back to top |
|
|
belve
Joined: 04 May 2006 Posts: 30
|
Posted: Wed Jan 02, 2013 9:15 am Post subject: |
|
|
In general Yes for call control in the mentioned case. Thank you for the reply and help and I used callback app.
But though it is interesting why SST file was not registered by reg_file() in the ACTION_APP_INIT section. Probably the EF SST is busy in the time of SIM reset. ME requests SST only once during SIM reset. For example if ME sends TEMINAL PROFILE (0x10) the ACTION_TERMINAL_PROFILE (0x09) event is caught by TSIM even though it was not registered before in the ACTION_APP_INIT section. SST file is selected just 0.1 sec before TP but the ACTION_FILE_APDU SST event not occurred at all.
6.484 FROM ME: a0 a4 00 00 02
6.484 FROM ME: 6f 38
6.484 TO SIM: a0 a4 00 00 02
6.484 TO SIM: 6f 38
6.531 FROM SIM: 9f 0f
6.531 TO ME: 9f 0f
6.531
6.531 FROM ME: a0 c0 00 00 0f
6.531 TO SIM: a0 c0 00 00 0f
6.531 FROM SIM: 00 00 00 0d 6f 38 04 00 14 ff ff 01 02 00 00 90 00
6.531 TO ME: 00 00 00 0d 6f 38 04 00 14 ff ff 01 02 00 00 90 00
6.531
6.531 FROM ME: a0 b0 00 00 0d
6.546 TO SIM: a0 b0 00 00 0d
6.546 FROM SIM: ff 3f ff 0f 0f 00 3f 0f 00 0c 00 00 00 90 00
6.593 TO ME: ff 3f ff 0f 0f 00 3f 0f 30 3f 00 00 00 90 00
6.593
6.593 FROM ME: a0 10 00 00 13
6.593 TO SIM: a0 10 00 00 13
6.593 FROM ME: ff ff ff ff 7f 3f 00 df ff 00 00 1f e2 85 0b 02 03 09 00
6.593 ACTION: 0009
6.593 TO SIM: ff ff ff ff 7f 3f 00 df ff 00 00 1f e2 85 0b 02 03 09 00
6.671 FROM SIM: 91 0b
6.671 TO SIM: a0 12 00 00 0b
6.718 FROM SIM: d0 09 81 03 01 26 01 82 02 81 82 90 00 |
|
Back to top |
|
|
pz
Joined: 12 Mar 2004 Posts: 1161
|
Posted: Wed Jan 02, 2013 3:17 pm Post subject: |
|
|
It's possible that EF_SST was done before ACTION_INIT - this is normally not triggered at the RESET time (because a bad app could kill all booting). You may tell kernel to do ACTION_INIT sooner with set_proc_8(PROC_8_CONFIG_INIT_BOOSTER, 1) in ACTION_APP_REGISTER. |
|
Back to top |
|
|
belve
Joined: 04 May 2006 Posts: 30
|
Posted: Wed Jan 02, 2013 3:43 pm Post subject: |
|
|
Ok and thank you once more for the messaging and attention. At the moment BLADOX sw functionality is more than enough to implement my tasks. Nice product. It was just a kind of wish to know more regarding STK features. |
|
Back to top |
|
|
|