mirror of
https://github.com/thelsing/knx.git
synced 2025-09-18 17:52:44 +02:00
d90843ba45
* Initial commit * Clean up * Remove display code * Change cmake build * Add SimpleLink SDK for CC13xx/CC26xx as submodule * Remove commented line from build.sh * Working build * Remove SDK submodule * Squashed 'examples/knx-cc1310/coresdk_cc13xx_cc26xx/' content from commit 0d78d32 git-subtree-dir: examples/knx-cc1310/coresdk_cc13xx_cc26xx git-subtree-split: 0d78d3280357416a5c0388148cda13717c9ffaa5 * Add more comments and enable Power_idleFunc() for NoRTOS variant. Internal SDK driver functions which have to wait for something will cause Power_idleFunc to be called instead of doing busy wait. * Move CC1310 platform init around * Optimize a bit more in debug build config as the binary does not fit into 128Kb flash otherwise. * Explicitly list each source/header file in build config. Use linker group to resolve circular dependencies. * Ignore vscode settings.json * Increase stacks size * Only compile CC1310 source code if #define DeviceFamily_CC13X0 * initial commit of CC1310 RF driver with first working RX version * Better handling of buttonUp() across platforms * Start cleanup * continue cleanup * Fix bau2920 compilation * Continue cleanup * Fix compilation in other examples * Fix compilation * htons() and ntohs() only for SAMD and STM32, but not for Linux and ESP8266 and ESP32 * htons(9 and ntohs() needed for CC13x0 * Continue cleanup * Add CC1310 platform to CI * Fix CI * Use more recent toolchain from ARM * Fix travis * Use Ubuntu Focal * Fix toolchain for travis * Fix package name * Fix toolchain * Add libstdc++-dev package * Add newlib packages * Remove commented commands from CI * Fix travis * Fix compilation of knxPython * Clean up linefeeds * Fix RX callback * Move RF CRC16-DNP to bits.cpp * Fix TX * Optimization: do not calc CRC for block1 again in rf_data_link_layer * Make newline optional in printHex * Cleanup. First working version: ETS5 programming of individual address via KNX/RF coupler. * Use LEDs and Buttons to control ProgMode and Flash Erase * Remove settings.json (VScode) * Add README.md * Update README.md * Update README.md * Fix typo |
||
|---|---|---|
| .. | ||
| driverlib.c | ||
| driverlib.elf | ||
| readme.txt | ||
Debugging sessions in IAR Embedded Workbench (IAR) and Code Composer Studio (CCS) can load symbol information covering the code in ROM. Symbols are loaded by selecting the ELF files found in the same folder as this readme.txt file. In addition the source code for the driverlib functions in ROM is found in the driverlib.c file in this folder. Loading ROM code symbols in CCS debug session: - Start a debug session in your project - Select Run > Load > Add Symbols to create additional symbols - Browse to and select each ELF file in this folder in the 'Program file' field - Set the value of 0 in the 'Code offset' field for each ELF file - If you enter a driverlib function in ROM during your debuging session and get this information: 'Can't find a source file at "../<path>/driverlib.c"' you can navigate to the driverlib.c file in this folder by selecting the 'Locate File..' button. Loading ROM code symbols for use in IAR debug session: - In your project select the following before starting debug session: Project > Options.. > Debugger and then select the 'Images'-tab - In the 'Images'-tab do the following for each of the ELF files located in the same folder as this reame.txt file: -- Select the 'Download extra image' box -- Browse to the ELF file in the 'Path:' field -- Set the value of 0 in the 'Offset:' field -- Select the 'Debug info only' box - If you during a debug session enters a driverlib function in ROM you will be notified by this message: 'Could not find following file: ../<path>/driverlib.c' Select the browse button and select the driverlib.c file located in this folder.