Disabling debug functions from cross_studio_io.h

Follow

Marcin

• April 12, 2013 12:02

Hello, I'm using  CrossStudio ARM for STM32 development.

I'm using various debug_* functions from cross_studio_io.h, it's working great, but its need constant JTAG connection.
Is there any easy way to disable  those function calls? Maybe some #define or switch in project properties I'm not aware of.

 

 

Marcin

0

• 

  Jon Elliott

  • April 12, 2013 13:30

  Hi Marcin,

  Set the "Linker Options > DebugIO Supported" project property to "No".

  Regards,

  Jon

  0

  Comment actions Permalink
• 

  Marcin

  • April 15, 2013 08:31

  Hello Jon,

  After I change DebugIO Supported to "No " I get a following linking error 
  /usr/share/crossworks_for_arm_2.3/lib/libdebugio_v7m_t_le_eabi.a(libdebugio.o): In function `__do_nvdebug_operation':

  0

  Comment actions Permalink
• 

  Jon Elliott

  • April 15, 2013 09:00

  Hi Marcin,

  That indicates that you are still making calls to the debug I/O library somewhere in your program - the DebugIO Supported property stops the debug I/O functions from being linked in. You should either remove or #ifdef the debug I/O calls, or I guess another solution would be to implement an empty __do_debug_operation function to allow the program to link.

  Regards,

  Jon

  0

  Comment actions Permalink
• 

  Marcin

  • April 15, 2013 09:32

  Ok, that answers my question. 

  Thank You

  0

  Comment actions Permalink
• 

  Bill Fleming

  • May 05, 2023 18:15

  We recently started having problems with this with Crossworks ARM versions after Crossworks ARM 4.8.

  When I set "Debug I/O Implementation" and "Default debug I/O Implementation" to "None" the libdebugio will still get linked. The only way to prevent the functions from being included is to stub all of them out.

  But for example I still see this in my map file showing it is trying to link it. But I can't figure out where it is getting set to link in the project.

  LOAD /usr/share/crossworks_for_arm_4.10/lib/libdebugio_v7em_fpv4_sp_d16_hard_t_le_eabi_small.a

  0

  Comment actions Permalink
• 

  Michael Johnson

  • May 06, 2023 06:44

  The debugio library is always supplied to the linker - we could do better.

  There are weak symbols (__open, __putchar etc) in libc that call the debug library to implement stdio i.e. do you have any printf's in your code.

  0

  Comment actions Permalink
• 

  Bill Fleming

  • May 10, 2023 16:21

  Michael,

  Our uEZ software does use printf and have it redirected.

  Please see ticket #13592 with included project files/map file, etc.

  0

  Comment actions Permalink

Please sign in to leave a comment.