topic Re: [Bug Report] Beestack v3.0.2 in Wireless MCU

[Bug Report] Beestack v3.0.2

arnogir — Thu, 21 May 2015 12:57:02 GMT

Hello

I use the MAC since many year,

With an old version, the following file:

PLM\Source\TMR\Timer.h define the following:

define gTPMxCnSC_ELSB_c 0x08 /* Edge/level select high bit. */

#define gTPMxCnSC_ELSA_c 0x04 /* Edge/level select low bit. */

This is correct.

But the new version of Beestack v3.0.2 define following:

#define gTPMxCnSC_ELSB_c 0x04 /* Edge/level select high bit. */

#define gTPMxCnSC_ELSA_c 0x02 /* Edge/level select low bit. */

!!! Then this can cause some problem because register definition is well ELSB on bit 3 and ELSA on Bit 2, not on Bit 2 and Bit 1!...

Could you confirm?

:smileyblush:

Re: [Bug Report] Beestack v3.0.2

arnogir — Tue, 26 May 2015 13:08:11 GMT

Anybody can confirm to taken this remark in the next Beestack release?:smileysilly:

Re: [Bug Report] Beestack v3.0.2

AngelC — Tue, 26 May 2015 20:37:36 GMT

Dear Arnaud,

I guess you meant BeeKit 3.0.2 release. However, I could not verify the corresponding hardware. Could you please specify the device you are using? Also, please provide further details about the exact BeeKit’s application template you are using in order to confirm it.

Regards,

AngelC

Re: [Bug Report] Beestack v3.0.2

arnogir — Wed, 27 May 2015 05:19:15 GMT

BeeKit_3_0_2\Codebases\BeeKit HCS08 BeeStack Codebase 3.1.1\PLM\Source\TMR\Timer.h define the following

define gTPMxCnSC_ELSB_c 0x08 /* Edge/level select high bit. */

#define gTPMxCnSC_ELSA_c 0x04 /* Edge/level select low bit. */

The good way is:

#define gTPMxCnSC_ELSB_c 0x04 /* Edge/level select high bit. */

#define gTPMxCnSC_ELSA_c 0x02 /* Edge/level select low bit. */

Re: [Bug Report] Beestack v3.0.2

arnogir — Wed, 27 May 2015 05:23:14 GMT

Sorry,

The error is not in Bestack Codebase 3.1.1 but un MAC codebase 2.6.1:

BeeKit_3_0_2\Codebases\BeeKit HCS08 MAC Codebase 2.6.1\PLM\FreeScale\V01.00\HCS08\Source\TMR

Re: [Bug Report] Beestack v3.0.2

AngelC — Wed, 27 May 2015 19:51:11 GMT

Dear Arnaud,

I just confirmed what you described. I will forward your comments to our developers and have this fixed in future releases. Values should be 0x08 and 0x04 respectively, bits 0 and 1 are not defined. Thanks for pointing that out.

Regards,

AngelC