nRF5 action!



  • A quick Google pointed me to https://github.com/AndruPol/nrf52832-recover/blob/master/README.md

    I do have a STM32F103C8T6 laying around. But ATM no time to play with it.

    Maybe that's the €3 solution for unlocking.



  • @omemanti said in [nRF5 action!]Maybe that's the €3 solution for unlocking.

    BMP is enough to unlock. BluePill costs ca. €2 and it's easily convertable to BMP



  • @Omemanti Good find about the BMP to recover the Ebyte module. Can you point me to an aliexpress link? "stm32" "bluepill" are not the magic chinese keywords..


  • Mod


  • Plugin Developer

    I created a BMP, both from a cheap ST-Link and an STM32, and it didn't help me break open those eByte NRF52 units.



  • @alowhum where did you get stuck? Whats your process?



  • @monte do you have final code now ? 🙂



  • @mr_red

    I got to the point where the stm32loader.py runs and outputs:

    Bootloader version 22
    Chip id: 0x410 (STM32 Medium-density)
    Write 256 bytes at 0x8000000
    Write 256 bytes at 0x8000100
    [..snip..]
    Write 256 bytes at 0x8001900
    Write 256 bytes at 0x8001A00
    Read 256 bytes at 0x8000000
    Read 256 bytes at 0x8000100
    [..snip..]
    Read 256 bytes at 0x8001900
    Read 256 bytes at 0x8001A00
    Verification OK

    After that, you're supposed to plug in to the USB directly. I get " USB device not recognized". Zadig doesn't help. It lists it as:

    "Unknown USB Device (Device Descriptor Request Failed)"

    Any ideas?

    Thanks.



  • @ileneken3 have you returned the jumpers back?



  • @toyman
    Unfortunately, yes, I have returned the jumpers to their original settings, and have even tried all 4 combinations.
    I also changed computers, changed OS's, changed cables.

    The board LOOKS like it was well manufactured, but I suppose a bad board is a possibility. Other than that, I can't figure out what could be wrong.



  • @d00616 said in nRF5 action!:

    @Nca78 said in nRF5 Bluetooth action!:

    Does that mean I have to go the long hard way with a bluepill as programmer and openocd ? Anyone has other ideas to unlock and erase the device ?

    Select in to Tools menu "None" Softdevice and then "Burn Bootloader". This raises an error but the device is erased completely.

    I am having the same issue trying to write on a E73 module with read/write protections. I don't have a JLink, but a ST Link-V2 and OpenOCD.
    Do you know how to remove the protections on the E73 with such tools? Thanks.



  • @sebi,
    A couple weeks ago I began exploring deploying E73 modules and had to remove protections. I was successful and now have a working E73 ethernet gateway. Only had ST Link-V2, so I used a "blue pill" I had in inventory to load it with Black Magic Probe. This cleared the protections.

    The instructions I followed to load the BMP are step-by-step at https://github.com/TamojitSaha/STM32f103_Black-Magic-Probe

    The instructions followed to clear protections with BMP also are step-by-step and worked perfect. They are at https://github.com/AndruPol/nrf52832-recover

    In item #4, the program arm-none-eabi-gdb.exe seems to be part of the Arduino tool chain as I found it just by doing a search in file explorer and it was already on my win10 machine. Also, in item #4, (gdb) is the prompt that the program arm-none-eabi-gdb.exe gives. In the first line, change the '/dev/ttyACM0' to your com port. Use 'quit' to exit the program. Also, use 'mon help' to see options.

    There are apparently a number of ways to 'recover' the E73, but this worked easily for me, and was step-by-step.



  • @NeverDie Hoping you can help me with an WTNRF51822-S4AT problem where my stop recognizing interrupt events 2ish days after the last interrupt.

    The buttons sleep for 24 hours, then wake up and send battery level. Even though the interrupt stops triggering, they still send battery level.

    Possible some kind of timer is expiring?

    Any help is appreciated.

    // General settings
    #define SKETCH_NAME "ThinButton"
    #define SENSOR_NAME SKETCH_NAME
    #define SKETCH_VERSION "1.4"
    
    #define MY_NODE_ID 37
    
    
    #define MY_BAUD_RATE 115200
    //#define MY_DEBUG
    
    #define IS_NRF51 
    #define PIR_DETECTION_PIN 3
    #define SHORT_WAIT 50
    #define DEBOUNCE_MS 1000
    
    volatile bool motion_change=false;
    
    #define MY_RADIO_NRF5_ESB
    
    #include <MySensors.h>
    
    #define SLEEP_MS 1000 * 60 * 60 * 24
    
    #define   CHILD_ID_VOLT 1
    MyMessage msgBattery(CHILD_ID_VOLT, V_VOLTAGE);
    
    #define CHILD_ID_BTN 2
    #define BTN_PIN PIR_DETECTION_PIN
    MyMessage msgBtn(CHILD_ID_BTN, V_TRIPPED);
    
    void disableNfc() {  //only applied to nRF52
    
      #ifndef IS_NRF51
        //Make pins 9 and 10 usable as GPIO pins.
        NRF_NFCT->TASKS_DISABLE=1;  //disable NFC
        NRF_NVMC->CONFIG=1;  // Write enable the UICR
        NRF_UICR->NFCPINS=0; //Make pins 9 and 10 usable as GPIO pins.
        NRF_NVMC->CONFIG=0;  // Put the UICR back into read-only mode.
      #endif
    }
    
    void turnOffRadio() {
      NRF_RADIO->TASKS_DISABLE=1;
      while (!(NRF_RADIO->EVENTS_DISABLED)) {}  //until radio is confirmed disabled
    }
    
    void turnOffUarte0() {
      #ifndef IS_NRF51  
        NRF_UARTE0->TASKS_STOPRX = 1;
        NRF_UARTE0->TASKS_STOPTX = 1;
        NRF_UARTE0->TASKS_SUSPEND = 1;
        NRF_UARTE0->ENABLE=0;  //disable UART0
        while (NRF_UARTE0->ENABLE!=0) {};  //wait until UART0 is confirmed disabled.
      #endif
    
      #ifdef IS_NRF51
        NRF_UART0->TASKS_STOPRX = 1;
        NRF_UART0->TASKS_STOPTX = 1;
        NRF_UART0->TASKS_SUSPEND = 1;
        NRF_UART0->ENABLE=0;  //disable UART0
        while (NRF_UART0->ENABLE!=0) {};  //wait until UART0 is confirmed disabled.
      #endif
    }
    
    void turnOffAdc() {
      #ifndef IS_NRF51
        if (NRF_SAADC->ENABLE) { //if enabled, then disable the SAADC
          NRF_SAADC->TASKS_STOP=1;
          while (NRF_SAADC->EVENTS_STOPPED) {} //wait until stopping of SAADC is confirmed
          NRF_SAADC->ENABLE=0;  //disable the SAADC
          while (NRF_SAADC->ENABLE) {} //wait until the disable is confirmed
        }
      #endif
    }
    
    
    void turnOffHighFrequencyClock() {
        NRF_CLOCK->TASKS_HFCLKSTOP = 1;
        while ((NRF_CLOCK->HFCLKSTAT) & 0x0100) {}  //wait as long as HF clock is still running.
    }
    
    
    void mySleepPrepare() {  //turn-off energy drains prior to sleep
      turnOffHighFrequencyClock();
      turnOffRadio();
      turnOffUarte0();
    }
     
    
    void activateLpComp() {
      NRF_LPCOMP->PSEL=4; // monitor AIN0 (i.e. pin P0.02 on nRF52832 PIR Motion Sensor v607).
      while (!(NRF_LPCOMP->PSEL==4)) {} //wait until confirmed
      NRF_LPCOMP->REFSEL=3;  // choose 1/2 VDD as the reference voltage
      while (!(NRF_LPCOMP->REFSEL==3)) {} //wait until confirmed
      NRF_LPCOMP->ANADETECT=0;  //detect CROSS events on PIR detection pin
      while (NRF_LPCOMP->ANADETECT!=0) {} //wait until confirmed
      NRF_LPCOMP->INTENSET=B1000;  //Enable interrupt for CROSS event
      while (!(((NRF_LPCOMP->INTENSET)&B1000)==B1000)) {} //wait until confirmed
      NRF_LPCOMP->ENABLE=1;  //Enable LPCOMP
      while (!(NRF_LPCOMP->ENABLE==1)) {} //wait until confirmed
      NRF_LPCOMP->TASKS_START=1;  //start the LPCOMP
      while (!(NRF_LPCOMP->EVENTS_READY)) {}  //wait until ready
      
      NVIC_SetPriority(LPCOMP_IRQn, 15);
      NVIC_ClearPendingIRQ(LPCOMP_IRQn);
      NVIC_EnableIRQ(LPCOMP_IRQn);
    }
    
    void suspendLpComp() { //suspend getting more interrupts from LPCOMP before the first interrupt can be handled
      if ((NRF_LPCOMP->ENABLE) && (NRF_LPCOMP->EVENTS_READY)) {  //if LPCOMP is enabled
        NRF_LPCOMP->INTENCLR=B0100;  //disable interrupt from LPCOMP
        while (((NRF_LPCOMP->INTENCLR)&B0100)==B0100) {} //wait until confirmed
      }
    }
    
    void resumeLpComp() { //suspend getting interrupts from LPCOMP
      NRF_LPCOMP->INTENSET=B0100;  //Enable interrupt for UP event
      while (((NRF_LPCOMP->INTENSET)&B1000)!=B0100) {} //wait until confirmed
    }
    // setup
    void setup() {
      hwInit();
      hwPinMode(PIR_DETECTION_PIN,INPUT);
    
      disableNfc();  //remove unnecessary energy drains
      turnOffAdc();  //remove unnecessary energy drains
      activateLpComp();
      motion_change=false;
    }
    
    void mySleep(uint32_t ms) {
       mySleepPrepare();  //Take steps to reduce drains on battery current prior to sleeping
       sleep(ms);
    }
    
    
    // presentation
    void presentation() {
      sendSketchInfo(SKETCH_NAME, SKETCH_VERSION);
    
      present(CHILD_ID_VOLT, S_MULTIMETER, SENSOR_NAME);
      wait(SHORT_WAIT);
      present(CHILD_ID_BTN, S_MOTION, SENSOR_NAME);
      wait(SHORT_WAIT);
    }
    
    unsigned long lastTripped = millis();
    
    // loop
    void loop() {
      mySleep(SLEEP_MS);
      
      if(motion_change){
        unsigned long ms = millis();
        long timeDiff = ms - lastTripped; 
        
        if(timeDiff < 0 || timeDiff > 1000){ 
          send(msgBtn.set((uint8_t) 1));
        }
         
        NRF_LPCOMP->EVENTS_CROSS=0;
        motion_change=false;
        lastTripped = millis();
      } else {
        
        send(msgBattery.set(getInternalVoltage(),3));
      }
    }
    
    float getInternalVoltage(){
      return ((float)hwCPUVoltage())/1000.0;
    }
    
    
    #if __CORTEX_M == 0x04
    #define NRF5_RESET_EVENT(event)                                                 \
            event = 0;                                                                   \
            (void)event
    #else
    #define NRF5_RESET_EVENT(event) event = 0
    #endif
    
    
    // This must be in one line
    extern "C" { void LPCOMP_IRQHandler(void) {motion_change=true; NRF5_RESET_EVENT(NRF_LPCOMP->EVENTS_CROSS); NRF_LPCOMP->EVENTS_CROSS=0; MY_HW_RTC->CC[0]=(MY_HW_RTC->COUNTER+2);}}
    

  • Hero Member

    @ncollins

    It has been a while. I may be switching to PIC: https://forum.mysensors.org/topic/10666/anyone-ever-look-into-ezbl-aka-easy-booloader-on-a-pic

    The impression I get is that you just write the new hex file into flash, flip a switch in software, and bang, you switchover to the new firmware without skipping a beat. No need to even reboot.

    I think anything with the best general solution for OTA updates is a better path than doing OTA firmware bootloader one-offs for each MCU. From what I've gathered, it seems PIC may be the only one with the generalized bootloader support that I'm looking for. I haven't tried PIC before, but I'll be receiving a PIC board on Tuesday to test out this new theory. I'm gravitating toward LoRa anyway, so for that I can't leverage anything from NRF5x anyway. LoRa is the closest thing to bulletproof wireless communications that I've found so far. It just works, with fantastic range and coverage while still fitting within FCC requirements.

    PICs tend to consume less energy than both atmega's and nRF5x's while sleeping, so there may be some positive trade-offs to be had there as well.

    I'll miss the tight integration possible with an nRF5x. Maybe someday there will be PICs with integrated LoRa radios? MicroChip makes both separately, so it could conceivably happen. They've already done it with SAM: https://pic-microcontroller.com/microchip-new-ultra-low-power-lora-sip/



  • @neverdie Interesting, thanks for the info



  • @ncollins I had the same problem and sort of "solved" it by having it reboot every 3 hours (or maybe it was 6).

    I don't know how to use the nrf5x stuff anywhere near well enough to actually fix it but it seems to work.



  • @waspie I was actually about to go down that route. Would you mind posting a code snippet for how you're triggering the reboot?



  • @ncollins

    throw this somewhere in your code:

    void reboot() {
      wdt_disable();
      wdt_enable(WDTO_15MS);
      while (1) {}
    }
    

    and then calling the reboot (in the entire loop):

    void loop() {
    
      if (motion_change) {
        motionDetected=!motionDetected;
        if (motionDetected) {
          send(msg.set("1"));  // motion detected
        }
        else {
          digitalWrite(LED_BUILTIN,LOW);  //turn-off LED to signify motion no longer detected
          send(msg.set("0"));  // send all-clear to prepare for future detections
        }    
        
        NRF_LPCOMP->EVENTS_CROSS=0;
        motion_change=false;
      }
      else { //must be a scheduled wake-up.  Time to report voltage as a heartbeat.
        batteryVoltage=((float)hwCPUVoltage())/1000.0;  //take voltage measurement after transmission to hopefully measure lowest voltage that occurs. 
        send(msg_S_MULTIMETER_V_VOLTAGE.set(batteryVoltage,3));  //send battery voltage with 3 decimal places
        time = millis();
        if (time > 14400000 ) {
          reboot();
        }
      }
      mySleep(1200000);  //sleep for 20 minutes
    }```


  • @waspie appreciate it, thank you



  • @NeverDie Interesting. What have pulled you from nrf52 towards PICs?
    Can you post a link on the board you ordered, (or one like that)? Thanks.


  • Hero Member

    @sergio-rius I'm still deciding. What's holding me back from plunging into pic is that. it appears, the pics won't be able to leverage the arduino libraries. For that reason, I think I'm probably better off staying arduino compatible. In the end, it may be less effort to simply write my own OTA firmware update bootloader.



  • @neverdie said in nRF5 action!:

    @Terrence said in Minimalist SAMD21 TQFP32 Pro Mini:

    @NeverDie I love the Feather boards. Currently working with the RFM69 feather. Build in battery connector/charger is very nice to have.

    Have you found a cheaper source than Amazon for buying them?

    where it's just every pin of the SAMD21 mapped to a post, and it's only just the SAMD21 chip on the board. Then I can experiment on breadboard and figure out what I want and what works before finally reducing it to a subsequent PCB.



  • Any charitative soul can help me prepare a black magic probe? I'm following the guides but at some point I can't continue.
    For example, following this one: https://hackaday.io/project/28180-bluetooth-gamepad-phone-case/log/71316-stm32-black-magic-probe-flashing
    I do:

    $ mkdir mbp && cd mbp
    $ wget https://raw.githubusercontent.com/jsnyder/stm32loader/master/stm32loader.py
    $ chmod 774 stm32loader.py
    $ sudo apt install python-pip
    $ pip install pyserial # There I remove '--assume-yes' as this is a wrong parameter
    
    # Then here starts the funk
    $ sudo apt install arm-none-eabi-gdb  # The package does not exist.
    # I found online that it may be already incorporated and my worth a try, so I continue.
    # So I change the boot0 jumper to 1, that it not said in the guide, connect the two boards and plug it into the computer.
    
    $ dmesg | grep tty
    # Nothing.
    
    $ sudo dmesg | tail
    [10680.891711] usb 1-12: Product: STM32 STLink
    [10680.891714] usb 1-12: Manufacturer: STMicroelectronics
    [10680.891716] usb 1-12: SerialNumber: PÿqRpQP2$g
    [11990.202434] usb 1-12: USB disconnect, device number 7
    [11998.926846] usb 1-12: new full-speed USB device number 8 using xhci_hcd
    [11999.076060] usb 1-12: New USB device found, idVendor=0483, idProduct=3748, bcdDevice= 1.00
    [11999.076066] usb 1-12: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [11999.076069] usb 1-12: Product: STM32 STLink
    [11999.076072] usb 1-12: Manufacturer: STMicroelectronics
    [11999.076074] usb 1-12: SerialNumber: PÿqRpQP2$g
    # But no usb port. So I add udev rule.
    
    $ ls -l /dev/stl*
    lrwxrwxrwx 1 root root 15 oct 15 14:32 /dev/stlinkv2_12 -> bus/usb/001/008
    
    $ sudo ./stm32loader.py -p /dev/stlinkv2_12
    Traceback (most recent call last):
      File "./stm32loader.py", line 427, in <module>
        cmd.open(conf['port'], conf['baud'])
      File "./stm32loader.py", line 71, in open
        timeout=5               # set a timeout value, None for waiting forever
      File "/home/sergio/.local/lib/python2.7/site-packages/serial/serialutil.py", line 240, in __init__
        self.open()
      File "/home/sergio/.local/lib/python2.7/site-packages/serial/serialposix.py", line 272, in open
        self._reconfigure_port(force_update=True)
      File "/home/sergio/.local/lib/python2.7/site-packages/serial/serialposix.py", line 326, in _reconfigure_port
        raise SerialException("Could not configure port: {}".format(msg))
    serial.serialutil.SerialException: Could not configure port: (25, 'Inappropriate ioctl for device')
    
    $ sudo apt install gdb-multiarch
    # Same effect.
    

    And here I am. Does anyone knows what kind of magic is required to put inside this little thing? 😏


  • Hardware Contributor

    @Sergio-Rius
    I can't help you with blackmagic probe unfortunately.
    Just personal opinion, I prefer Segger probe.
    For example, Segger EDU mini is cheap. for the price don't bother with clones..

    • very affordable
    • compatible with a lot of IDEs, and when you use it with Segger IDE then you get best integration
    • segger provides lot of tools for debugging for free
    • easy updates and drivers install

    The only cons to a jlink probe could be no additional uart, but I don't need uart for debug&prints (segger ozone and rtt tools), and nor uploading sketch.

    Or a nrf5dk board is a nice alternative too, a little bit more expensive than EDU Mini but you get jlink+devboard+ later you could hook a power profiler kit on it 😉
    Still a jlink mini at hand is quite useful.

    Like I said just personal, I'm sure BMP is nice too, I guess you'll get it working before you can get a jlink 🙂



  • @sergio-rius I too have struggled to flash st-link clone with bmp firmware, but eventually I managed to do it. Unfortunately I don't remember what exactly I did, but I remember that I came to a solution when decided to try another st-link as a destination. If I remember correctly, there are different stm32 chips on these boards and some of them have insufficient amount of flash memory for bmp firmware.

    arm-none-eabi-gdb package is not available in ubuntu's repositories starting from 18.04. You can either download toolchain from eclipse's github archive or try to install older package as described here.

    Also, I used info from this blogs when flashed my st-link:
    http://blog.linuxbits.io/2016/02/15/cheap-chinese-st-link-v-2-programmer-converted-to-black-magic-probe-debugger/
    http://nuft.github.io/arm/2015/08/24/blackmagic-stlink.html

    As for buying stuff, don't forget you can buy ready to use BMP from their creators too 😉


  • Hero Member

    Maybe this will help: I once looked into the Black Magic Probe, but came to the conclusion that it was basically a PC program that they crammed onto the "probe." Therefore, unless I'm mistaken, you could run the very same source software from either a PC or a linux box and get the same results. I don't recall any advantage to running it on the so-called "probe" that the authors picked.



  • @neverdie and how do you suggest connecting SWD and SWCLK lines from MCU to computer, not using the "probe"?



  • @monte I guess he means taking the debugger program to the computer layer and leave only the com channel to a TTL device.



  • @sergio-rius but debugger is running on a computer side anyway, as far as I understand. And BMP is the "thing" that connects it to MCU via SWD.



  • @monte I may be wrong, but from what I understand while reading on it, it seems that the debugger is implemented in the probe. The program you run is an interface.
    I see it like a Ilogger interface that you implement in a program.



  • @sergio-rius well, I guess you are right. I revisited description of BMP and it says, that it runs GBD server on itself and eliminates need for STlink server. So I guess you could do all the same with just an st-link...however it seems that it would require more setup and I don't think that it will be easier than flashing BMP firmware 🙂
    Just a snippet from their wiki:
    "There are a few advantages of the Black Magic Probe. BMP is open-source, meaning that you can look inside it if you need or want to. We are getting support for new ARM Cortex-M based chips on a regular basis, so you are not limited to just the STM32. We have preliminary support for Cortex-A this will result in the ability to use the probe with Raspberry PI and Beagle Bone Black and many others. The Black Magic Probe also supports JTAG not only SWD, because not all microcontrollers use SWD. Also JTAG makes it possible to chain together more than one microcontroller. The GDB server is implemented on the probe itself, this means we do not use some proprietary protocol to talk to your debugger software, making the setup more repeatable and removing the need for custom config files."


  • Hardware Contributor

    "BMP is open-source, meaning that you can look inside it if you need or want to"

    "The GDB server is implemented on the probe itself, this means we do not use some proprietary protocol to talk to your debugger software"

    sounds so useful when you simply want to upload fw and debug 😅
    open-source does not mean better quality than proprietary imho, it can be a burden too. I prefer mature product for working.

    is BMP compatible/integrated with as many IDE as a proprietary probe?
    If for instance someday you want to use it with Segger IDE+nordic sdk, is it compatible? I don't think so.
    I "compared" probes recently and decided to stick to jlink. The second probe in my list is cmsis-dap/daplink, looks nice too, but don't need it (at least, not so far)

    I use many different toolchains and CLI too. So when there is a tool that just needs download and exec to install driver, autoupdates etc, without spending life in CLI, I don't hesitate.

    struggling or working..



  • @scalz well, that's nice that you know what you want and can get it, but that doesn't mean that's suitable for everybody else. That's good to have a choice, but when you need it done, you better find a way to get it done easier and faster.
    So I went to local store, bought second st-link clone for 4$ and then spent a few hours figuring out, how to properly flash it. The day after I could unlock my Ebyte e73 board, with newly acquired BMP.
    If I'd took the route suggested by you, I would spend minimum 30$ and 1-2 weeks of waiting time. And then I would still need to figure out how to work with that proprietary software.
    I am far from experienced programmer, so I can't get use of BMP's full potential, but now I have a very useful tool in my arsenal, that can be used with variety of different chips.
    Also, in my opinion, the main advantage of opensource not the software itself, but a community. Your experience may vary, but I'd say you have better chances finding solution in opensource community, than on commercial software forum, unless you have some kind of paid support subscription.


  • Hero Member

    @monte said in nRF5 action!:

    @neverdie and how do you suggest connecting SWD and SWCLK lines from MCU to computer, not using the "probe"?

    st-link. Roger Clark previously had a youtube video showing this setup, but it looks as though he has since deleted all his videos: https://www.youtube.com/user/synergie8/featured

    Anyhow, I'm not trying to dissuade anyone from using BMP. If you want a probe that has a command line interface built into it, then AFAIK it's still available.


  • Hardware Contributor

    @monte said in nRF5 action!:

    @scalz well, that's nice that you know what you want and can get it, but that doesn't mean that's suitable for everybody else. That's good to have a choice, but when you need it done, you better find a way to get it done easier and faster.

    Why so much impatience 🙂 So many things to tinker.. I mean you can get a jlink in 2days if you need it. I ordered mine while I was waiting for stuff coming from China..and in my case, there is no close-door store for geeks.
    Do you mean you would suggest a nrf5 newcomer to diy a BMP for mcu flashing??

    When I got my jlink, I didn't have to flash it to make it working.. I just had to donwload win drivers, install them, and voilà.
    Which proprietary sw do you think you need to learn?? I don't use any special sw for flashing..just regular IDEs like arduino/vs studio, or more advanced like Segger (free) or Keil. For all these IDEs, I just click on a button to upload fw, simple. There is nordic windows apps, or nrfjlink in CLI too.

    I know the power of oss and its flaws, same for commercial, in practice it's not rare to see communities sitting/waiting for updates (not hard to find examples on github), whereas money makes commercial products live.
    No need to debate on this, it's useless debate I think
    The reality is different here, I think you'll find more subscriptions-free resources on internet about Jlink than BMP, and for a reason 😉 I agree that you'll find lot of howtos save a few bucks by diy-ing and flashing a BMP..
    everyone acts in one's own interest 🙂
    Just to sum up my thought, I think for a newcomer it's easier to get started with a Jlink vs diy probe that you need to flash with what, a probe ??

    Below is a screenshot of a running nrf5 test, stability test.. but for example you can see, I don't use any additional uart for debug printing, and fw is just uploaded by a click in IDE.
    0_1571301587440_Capture.PNG


  • Banned

    This post is deleted!


  • @scalz I'm not trying to dismiss your point, I get it. It just surprises me that you stand against "diy'ing a probe" while still being a part of DIY community which gathered around idea of making things fast and cheap. Why bother with mysensors, if we can buy all the same from Ikea, Xiaomi of Philips, or many other manufacturers, sometimes not even much pricier?
    To sum up what I'm trying to say, and finish this debate. I've spoken about my experience as nrf5 newcomer. And exactly as a newcomer I've found this way being better for me. I don't use Segger, Keil or Windows, nor I am planning to use them in future, and if I will, I would probably be able to afford buying myself a J-link.
    To get "DIY" version of BMP you need either ST-link v2 or any STM32 board, bluepill for example. And to flash one of those you obviously need another ST-link. That's all.
    BMP supports SWO which have it's own specifics compared to RTT, but basically does the same thing.


  • Hero Member



  • @neverdie that seems to be for folks who are against STM32 chips 🙂


  • Hardware Contributor

    @monte
    it's not standing against diy'ing etc..really you didn't understand my point, it's just about user friendly and easily repetable getting started for MySensors nrf5 newcomers, for simply flashing their sketch.. even if a diy BMP is certainly a good probe too. and a genuine BMP is more expensive than a jlink mini. Compare both a jlink vs a blank diy probe, and with a stopwatch, you'll see which method is faster and easier for a noob..

    But ok, I won't insist anymore, if you prefer to get me wrong, really don't mind.. I should better let user with not much xp manage all alone so no debate, as this just makes me less active, see you next year 😁

    Just don't forget future newcomers will read your advices. In the meantime, we'll try to update docs for MySensors nrf5.

    Have fun with your probe



  • @scalz C'mon, would you leave the forum with just one hit? 😄
    In fact I understand your point completely. Open source has become more and more caotic. Internet is atemporal, and often people has the bad habit of not putting the complete date at the top of their "articles" that makes that search engines cannot filter and order properly.
    Everyone has a blog and writes whatever gets out him. The majority of people uses that as a remainder for themselves and... whynot getting reward. So there are zillions of howtos made anyhow. They are not written for helping people.

    If the sources and destination are always one, why there aren't the binaries available and all writeups talk about messing the computer and compiling? I think that's because nowadays people seek praise for having achieved it.

    Scalz point is about economy of time. Because time is money, even if it's spare time, and yes, a paid/proprietary probe becomes cheap, giving the documentation on the internet, today.

    Also the point of view depends in the situation of everyone and its age. Someone at the 5thies feels earlier that it's wasting time, and there comes frustration, and complaining posts, unfortunately 🙄
    Just buy a probe, forget about it until it gets delivered.

    @monte BTW, I was trying to program an stm32 board with a jlink. Not a Jlink. Maybe if there was a way to get an already compiled binary (to avoid all those dependencies errors) and program the jlink with a normal serial ttl...



  • @sergio-rius well, I've gotten majority of my computer knowledge and almost everything I know about programming MCU from such blog posts and articles. Some of them where better, some worse, maybe 10% were complete garbage. But anyhow I can't and won't complain. Because no person is obliged to write something that everyone will understand, and not everyone is naturally born teacher, to prepare information in suitable for wide variety of people way. But all of them were people, who thought it will be helpful to share their experience with others, to show them that this can be done, and maybe give at least hints to how to achieve it. I think there is not much use if you just follow steps, written by someone, without any thought process, or trying understand what you are doing. And thus when you try to achieve something that, won't work from the beginning and guide seems to be outdated, or not complete, you teach yourself and this is most precious in thewhole process.
    I don't think it is correct to blame those, who made a guide for that you can't replicate all the steps. Time goes, libraries an packages evolve, and in few moths fully functional guide can become obsolete if you can't make some adaptations.
    Anyway, here is more recent guide, but written with older ubuntu version in mind. You may look at it, if you want: https://buger.dread.cz/category/stm32.html



  • You know... Great power comes with a great responsibility 😊


  • Hero Member

    I happened just now to notice that ON Semiconductor has released their own (non-Nordic) version of an integrated Bluetooth + ARM Cortex + antenna with all passives:
    https://www.mouser.com/datasheet/2/308/RSL10SIP-D-1511181.pdf

    What's remarkable is that the entire thing, including the antenna and all the passives (which are built into it) is just 8mm x 6mm in size. As a result, it's very easy for them to make a very small sensor beacon:
    alt text

    "The RSL10 SIP features an on−board antenna, RSL10 radio SoC,
    and all necessary passive components in one package to help minimize
    overall system size. Already fully qualified to FCC, CE, and other
    regulatory standards; RSL10 SIP removes the need for additional
    antenna design considerations or RF certifications."

    Personally, I don't currently have the skill to solder anything that small, but maybe with the PCBA services that are becoming available.....

    I post this here merely as an illustration of what's truly possible. I can only guess, but I presume Nordic will probably (?) release something similar in the future. It would be nice not having to rely on module vendors but instead just mount the chip directly.


  • Hero Member

    By the way, maybe the Black Magic Probe can function as a kind of "universal" JTAG interface? For instance, would it work well o an ESP32 and/or anything else that relies on JTAG for debugging and/or burning firmware? Or would an ST JTAG probe work just as well?

    Is this right? I'd prefer to consolidate on a single thing rather than having a different JTAG interface device for every different kind of hardware that might need programming/debugging:

    #274 Free Inline Debugging for ESP32 and Arduino Sketches – 17:46
    — Andreas Spiess


  • Hardware Contributor

    @neverdie
    afaik BMP officially targets ARM mcus, whereas ESP32 is not ARM, it's Tensilica.


  • Hero Member

    @neverdie On the other hand, I bet that tiny RSL10 integrated radio+antenna package has very limited range. What I noticed from the various nRF52840 modules that I've tried is that the smaller the module, the worse the radio range. I haven't yet encountered any exceptions to that generalization.



  • @waspie just to follow up, 24hr reboot() is working perfectly. Appreciate the help.



  • @ncollins good news

    I wonder if this has anything to do with it?
    https://forum.mysensors.org/topic/10705/nrf52-watchdog-problem-myboardnrf5



  • @waspie Given that all of my interrupt nodes stopped triggering after 36 hrs (before your reboot workaround), it has to be related. It’s just weird that my nodes would continue to wake up and broadcast battery level.

    Is the LPCOMP interrupt method dependent on the wdt? Maybe resetting/restarting the wdt every 24hrs would suffice? Or maybe you have to reactivate LPCOMP every 36 hr wdt cycle?


 

237
Online

8.9k
Users

9.6k
Topics

100.8k
Posts