AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Nrf52 sdk on segger embedded studio1/8/2024 ![]() This can be disabled using the Text Editor > International > Verify Text File Decoding environment option. Text decoding is now verified when a file is loaded.Fixed incorrect syntax coloring after reloading externally edited file.Fixed incorrect column selection when file contains tabs and there are collapsed folds. ![]() Updated J-Link software to version V7.64c.Add simulator support for 16/64 instructions.Updated default libcxx packages to version 1.06.Fixed LTO support for big-endian targets.Stack Usage window now works without linker relocations section.Updated the GCC/BINUTILS tools build to use the Arm GNU Toolchain 11.2-2022.02 source release.Updated the LLVM/Clang tools build to use the 14.0.0 source release.Fixed quoted zero length command line arguments being discarded when spawning processes.Changed "ARM Architecture" project property default to "None".Add "Analyze Command" project properties.The C++ new operator now calls abort() on failure.Updated segger-cc-ng compiler to version 14.90.1.Updated segger-cc compiler to version 14.0.1.Add existing file now uses the standard native file open dialog on Windows.ANSI escape codes are now removed when copying text to the clipboard from the text build log.Fixed crash when continue to debug used with no executable file.Fixed removal of editor tooltips when mouse cursor moves away.Updated J-Link software to version V7.66c.Add Show Digit Separator to variables and registers windows.Add "Library Heap Locking" project property.Fixed percentage memory used calculation.Fixed Source Navigator/Analyze command lines for libcxx projects.Fixed license manager not allowing ARM and RISC-V licenses to be installed on one J-Link.Updated J-Link software to version V7.66e.Fixed use of "Unwind Tables" with segger-cc compiler.To read more about the DevKit, refer to RuuviLab’s tutorial. A great tool for this is Nordic Semiconductor’s Power Profiler Kit which is compatible with the nRF52-DK evaluation board. Note also that if you’re developing your own firmware, power consumption measurements are recommended so that possible current leaks can be obtained. The DevKit isn’t needed if you’re happy to flash your RuuviTags over-the-air.įor most of the people, DFU OTA (Device Firmware Update Over-the-Air) is enough if no protocol stack or bootloader has to be replaced or no serious debugging is needed. No hassle with a battery while developing because the shield powers the RuuviTag.Safely test different protocol stacks in development (Bluetooth 5 for example, an upcoming feature).The original RuuviTag software can be restored (factory reset).Easy access to all the IO pins found on bottom of the RuuviTag.Debug your firmware via SWD (the nRF52-DK has an integrated Segger J-Link programmer).Use third-party protocol stacks or operating systems (ie.1 x Development shield designed for RuuviTag.1 x Nordic Semiconductor nRF52-DK evaluation kit.The Development Kit is designed for hardcore developers who would like to take their RuuviTag sensors to the limit by flashing and debugging the devices via SWD (Serial-Wire-Debug) bus or use RuuviTag’s extra IO connections on bottom of the circuit board.
0 Comments
Read More
Leave a Reply. |