Viewing 6 posts - 16 through 21 (of 21 total)
  • Author
    Posts
  • #12011

    andrew.wootton
    Participant

    Sorry to be a trouble, but I’m a bit concerned about doing the firmware change. I’ve installed the LoRa Development Utility (Win version). On the Microchip website there are RN2903 versions 1.0.3 and 1.0.5 available. These are zip files containing hex files. I think you previously mentioned that 1.0.5 doesn’t work with the MULWAN. So I need to load AU_0.97rc7

    With the Sodaq firmware updater on Github (https://github.com/SodaqMoja/RN2483FirmwareUpdater) is a ,h file (HexFileImage2903AU_097rc7.h) but the hex definition is embedded in the C++ .h file. Do I need to strip out these C++ lines to produce pure hex before attempting to upload to the RN2903?

    Thanks, appreciate the help.

    #12013

    LIM PHANG MOH
    Keymaster

    I think you previously mentioned that 1.0.5 doesn’t work with the MULWAN.

    I mentioned not working well generally as mentioned over here.

    With the Sodaq firmware updater on Github (https://github.com/SodaqMoja/RN2483FirmwareUpdater) is a ,h file (HexFileImage2903AU_097rc7.h) but the hex definition is embedded in the C++ .h file. Do I need to strip out these C++ lines to produce pure hex before attempting to upload to the RN2903?

    I went through the code over there. I believe what it does is, instead of using the Microchip utility to upgrade the firmware of the RN2903/RN2483, they load a special code that store the new RN2903 firmware onto the main MCU (on Sodaq, it is the ATSAMD21G18 which has 256 kB of flash, plenty!). This probably because they weren’t able to do it reliably directly from PC to RN2903 or for whatever reason limited by their design. And one more thing, this whole repository code won’t compile for an AVR-8 MCU as it can’t fit the entire code.

    They converted the RN2903 .HEX file into a .h that contains special AU915 firmware (I believe this is not official and Sodaq themselves are big customer of Microchip, hence probably they have a copy of it). We could extract this and reformatted it into a regular .HEX file. But, to be safe, I would recommend asking them for an original copy. Then, we use the Microchip utility to update. I used the software many times and even in the case it lock up, it has a recovery mode that works well.

    So, back to the 1.0.5 or even 1.0.4, I believe that won’t solve your issue as you are running AU915 band which is not officially release under these official 1.0.4 and 1.0.5 release.

    #12973

    albi90
    Participant

    I have been having the exact same issue would be nice if microchip would just use one FW for AU915 and US915 from what I have been reading we just need to flash the FW using the microchip tool, I was trying to do this last night using bridging and SoftSerial but it didn’t play nice, will try tonight to do it directly (didn’t realise we could switch the serial directly to the RN2903).
    FYI looks like you can get FW 1.3 SA which is AU915 from below
    https://github.com/TheThingsNetwork/arduino-device-lib/tree/master/docs

    Will post if it all works.

    • This reply was modified 1 month, 1 week ago by  albi90.
    #12998

    albi90
    Participant

    Ok confirmed flashed and working perfectly on my AU915 network 🙂

    #13000

    LIM PHANG MOH
    Keymaster

    Ok confirmed flashed and working perfectly on my AU915 network 🙂

    Thanks for the update. Till date, no official announcement on the AU915 firmware. Only these unofficial ones.
    Will update the documentation this weekend. It has been hectic the past few months with a kid to take care now.

    #13157

    andrew.wootton
    Participant

    this is good news. I’m about to go away for a couple of weeks, but will give it a try when I get back. Thanks for the info.

Viewing 6 posts - 16 through 21 (of 21 total)

You must be logged in to reply to this topic.