Article [#6703] mcapi coreb_msg function fails to print info if the message followed is to long(2011)

[#6703] mcapi coreb_msg function fails to print info if the message followed is to long

Submitted By: Mingquan Pan

Open Date

2011-07-27 01:17:33     Close Date

2011-09-06 02:05:34

Priority:

Medium     Assignee:

steven miao

Status:

Closed     Fixed In Release:

N/A

Found In Release:

2011R1     Release:

Category:

N/A     Board:

N/A

Processor:

ALL     Silicon Revision:

Is this bug repeatable?:

Yes     Resolution:

Fixed

Uboot version or rev.:

    Toolchain version or rev.:

5013

App binary format:

N/A     

Summary: mcapi coreb_msg function fails to print info if the message followed is to long

Details:

coreb_msg fails to print info if the message followed is to long.

like:

coreb_msg("550000endpoint=123456789%i has received: [%s]\n",(int)recv,pbuffer);

It doesn't show the quoted info on the blackfin console.

If shorten 4 chars of the message, then it prints ok.

Follow-ups

--- steven miao                                              2011-08-04 23:59:50

coreb_msg debug buffer has 64 bytes limit. if the message is too long, you can

split it into two messages.

--- Mingquan Pan                                             2011-08-05 02:29:08

Yeah, I can print a long message on two lines, but coreb_meg can't disappear for

the message exceeds its max size, at least it can give out the error number to

tell the failure and reason.

--- steven miao                                              2011-08-05 04:54:37

i'll update the max message size to 128 bytes for long messages.

--- Mingquan Pan                                             2011-09-06 02:05:34

It can now prints:

COREB: 5555555555endpoint=12345678965542 has received 8 byte(s):

[9282726252423222]

So close.

    Files

    Changes

    Commits

    Dependencies

    Duplicates

    Associations

    Tags

File Name     File Type     File Size     Posted By

No Files Were Found

Before You Switch


Switching languages will make ADI Explorer unavailable. Resume your session by switching back to English and reopening ADI Explorer.