GDBServer : FreeRTOS thread count is unreasonably big ..

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • GDBServer : FreeRTOS thread count is unreasonably big ..

      JLink package v670g.

      Starting GDBServer with freeRTOS pluing on , i get error trace :

      ERROR: FreeRTOS thread count is unreasonably big, not proceeding.

      Now, I cannot say my previous Jlink V652e had the issue, and FreeRTOS plugin was working fine, using same code both versions.

      Also, before this error it traced :

      Source Code

      1. RTOS plugin (API v1.0) loaded successfully
      2. RTOS plugin: Loaded
      3. Received symbol: pxCurrentTCB (0x200050A8)
      4. Received symbol: pxReadyTasksLists (0x200050AC)
      5. Received symbol: xDelayedTaskList1 (0x20005110)
      6. Received symbol: xDelayedTaskList2 (0x20005124)
      7. Received symbol: pxDelayedTaskList (0x20005138)
      8. Received symbol: pxOverflowDelayedTaskList (0x2000513C)
      9. Received symbol: xPendingReadyList (0x20005140)
      10. Received symbol: xTasksWaitingTermination (0x00000000)
      11. Received symbol: xSuspendedTaskList (0x20005154)
      12. Received symbol: uxCurrentNumberOfTasks (0x20005168)
      13. Received symbol: uxTopUsedPriority (0x00000000)
      14. Received symbol: uxTopReadyPriority (0x20005170)
      15. Received symbol: vPortEnableVFP (0x1FFF86BC)
      16. Received symbol: FreeRTOSDebugConfig (0x00000000)
      17. All mandatory symbols successfully loaded.
      Display All


      What is the issue then that I get the thread count error trace above ?
    • Hi,
      Thank you for your inquiry.
      Such an issue is not known to us.

      Could you please provide us with a sample project this is reproducible with?

      Could you please send us a J-Link log file? How to enable:
      wiki.segger.com/J-Link_DLL#Enable_J-Link_Log_File

      Best regards,
      Fabian
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/


      Or you can contact us via e-mail.
    • Hi,
      I got the message.
      Besides the Error message, everything looks good.

      SEGGER - Fabian wrote:

      Could you please provide us with a sample project this is reproducible with?
      So that we can investigate further?

      Best regards,
      Fabian
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/


      Or you can contact us via e-mail.
    • Hello,
      Now I have sent you an archive containing the setup exactly as I use to create this problem / trace (there is nothing more to it beyond it, its complete).
      I described exactly how I start it in the README, and the logs are from it essentially ( I didn't repeat them, but they the same).
    • Hi,
      We will be looking into this as soon as possible.

      Best regards,
      Fabian
      Please read the forum rules before posting: Forum Rules

      Keep in mind, this is not a support forum. Its main purpose is user to user interaction.
      Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
      Should you be entitled to support you can contact us via our support system: segger.com/ticket/


      Or you can contact us via e-mail.