[SOLVED] Debugging the RPi Pico - Minimum requirements

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

  • [SOLVED] Debugging the RPi Pico - Minimum requirements

    Hello,

    I wish to debug the provided sample project for the Pico board. I see on the Wiki page that the a JLink HW v11 is required to debug the board. I have a JLink EDU v10.1 that I bought a few years ago. I can see that it supports SWD. Will I be able to use it as well or do the HW v11 boards have some significant improvements? I am unable to find any sellers who have stock of the EDU or EDU Mini. Am I eligible as a hobbyist to buy one or do I have to be a student?

    Regards,
    Szoshi
  • Hi Szoshi,

    szoshi wrote:

    Will I be able to use it as well or do the HW v11 boards have some significant improvements?
    The RP2040 was added for J-Link V10 as well, so you should be able to use the J-Link EDU V10.1 to connect to it.

    szoshi wrote:

    I am unable to find any sellers who have stock of the EDU or EDU Mini.
    Please find information about this here: segger.com/products/debug-prob…ons-licensing-and-support

    szoshi wrote:

    Am I eligible as a hobbyist to buy one or do I have to be a student?
    You can find the details about this on the page I linked above.
    In short: As long as the J-Link EDU is used in a non-commercial context only, you are eligible.
    This includes non-profit hobbyist projects.

    BR
    Fabian
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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,

    thanks for the reply. I can confirm that the debugging went very smoothly with the 10.1 hardware version.

    I am now trying to figure out what clock rate my Pico is running at. A simple pin toggle generates a clock of around 300 kHz. One half of the wave takes around 7 assembly instructions so I am placing the clock around 4 MHz. Is that correct? How can I set the desired clock rate in the Segger Blinky project for example?

    Regards,
    Szoshi
  • Hi Szoshi,
    What kind of clock are you referring to? The CPU clock?
    If so, you can either read out the responsible register (see RP2040 manual) or you could use the
    "TestCSpeed <RamAddr>" command of the J-Link Commander:
    wiki.segger.com/J-Link_Commander#TestCSpeed

    To find out how to set the desired CPU clock for the RP2040,
    I would suggest to refer to the RP2040 manual and/or contact the Rasberry Pi support.

    Best regards,
    Fabian
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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, it seems that the code is being executed from the Flash which makes it so slow. I am using the SRAM example now but am noticing no speed improvements. Are there any settings for the SRAM examples?
  • Ok, I have figured out what was wrong. In the provided examples, the MCU is not configured to run from XOSC. As a result, it is powered by the slower and less accurate ROSC which leads to the above mentioned performance hit. I don't know if I am allowed to post links here but maybe someone can add that functionality to the provided examples to enable running the RP2040 / Pico at higher clock rates.
  • Hi,

    Good to hear that you are up and running again.
    I will forward your suggestion internally.
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    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.