Actions
Forum Thread Details
  • Replies 1 reply
  • Subscribers 57 subscribers
  • Views 497 views
  • Users 0 members are here
Related

Increase size of RAMLOG

mdastec

Hi.

I am trying increase the size of my RAMLOG.

In my ./nuttx/nuttx/.config

 

#

# System Logging

#

CONFIG_RAMLOG=y

CONFIG_RAMLOG_SYSLOG=y

CONFIG_RAMLOG_LAST_DMESG=y

# CONFIG_RAMLOG_CONSOLE is not set

CONFIG_RAMLOG_BUFSIZE=3056

# CONFIG_RAMLOG_CRLF is not set

CONFIG_RAMLOG_NONBLOCKING=y

CONFIG_RAMLOG_TRULY_CIRCULAR=y

 

If I change CONFIG_RAMLOG_BUFSIZE to something greater than what the defconfig had (2032)  I get a compile error:

 

LD: nuttx

arm-none-eabi-ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/armv7e-m/libgcc.a(bpabi.o) uses variable-size enums yet the output is to use 32-bit enums; use of enum values across objects may fail

arm-none-eabi-ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/armv7e-m/libgcc.a(_divdi3.o) uses variable-size enums yet the output is to use 32-bit enums; use of enum values across objects may fail

arm-none-eabi-ld: warning: /usr/lib/gcc/arm-none-eabi/4.9.3/armv7e-m/libgcc.a(_udivdi3.o) uses variable-size enums yet the output is to use 32-bit enums; use of enum values across objects may fail

arm-none-eabi-ld: /home/mike/motoModFirmwareBuild/nuttx/nuttx/nuttx section `.ramlog' will not fit in region `sramlog'

arm-none-eabi-ld: region `sramlog' overflowed by 2048 bytes

Makefile:205: recipe for target 'nuttx' failed

 

Does anyone know how I can create a larger circular buffer for dmesg?

 

Thanks,

Mike

  • Also - I tried logging to the console using the following:

     

    # System Logging

    #

    CONFIG_RAMLOG=y

    # CONFIG_RAMLOG_SYSLOG=y

    CONFIG_RAMLOG_LAST_DMESG=y

    CONFIG_RAMLOG_CONSOLE=y

    CONFIG_RAMLOG_BUFSIZE=2032

    # CONFIG_RAMLOG_CRLF is not set

    CONFIG_RAMLOG_NONBLOCKING=y

    CONFIG_RAMLOG_TRULY_CIRCULAR=y

     

    I tried with CONFIG_RAMLOG_SYSLOG=y but nothing came out the nsh>

    The above give a compile error.

     

    Any advice on proper way to config to get debug to the console in stead of or in addition to the ramlog?