{"payload":{"feedbackUrl":"https://github.com/orgs/community/discussions/53140","repo":{"id":322263570,"defaultBranch":"master","name":"ubxlib","ownerLogin":"u-blox","currentUserCanPush":false,"isFork":false,"isEmpty":false,"createdAt":"2020-12-17T10:45:00.000Z","ownerAvatar":"https://avatars.githubusercontent.com/u/8056698?v=4","public":true,"private":false,"isOrgOwned":true},"refInfo":{"name":"","listCacheKey":"v0:1714498108.0","currentOid":""},"activityList":{"items":[{"before":"79e808eb8be3095b4f94efcffba97515ba1870bd","after":"ffa9636be40b22cd5fca48902b6c4320787bc00e","ref":"refs/heads/master","pushedAt":"2024-04-30T17:33:29.000Z","pushType":"push","commitsCount":6,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Documentation change only: correct function name.","shortMessageHtmlLink":"Documentation change only: correct function name."}},{"before":null,"after":"55b83315f77912b1798353739f4b55f4a899faeb","ref":"refs/heads/preview_platform_stm32u5_rmea","pushedAt":"2024-04-30T17:28:28.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Platform change for STM32 only: add support for STM32U5 on STM32Cube.\n\nThe STM32U5 MCU, which is already supported via Zephyr, is now also supported on the STM32Cube platform.\n\nCURRENT LIMITATIONS:\n- I2C and SPI are not yet implemented,\n- there appears to be a bug in the ST-provided CMSIS layer for ThreadX in that it does not free memory when a dynamic task is terminated, hence you will likely run out of memory; this is being progressed in https://github.com/STMicroelectronics/STM32CubeU5/issues/48.\n\nEXISTING STM32Cube USERS PLEASE NOTE: the guts of stm32f4.mk is moved up a directory-level and renamed to stm32.mk; it is included in stm32f4.mk so you _should_ notice no difference.\n\nTwo configurations are supported: the default STM32U5 integration from ST, which now uses ThreadX as the underlying OS, and a configuration which continues to use FreeRTOS as the underlying OS (i.e. as STM32F4 does).  In order to make this possible all OS operations for STM32U5 builds go through CMSIS (V2).  See the README.md files under the stm32cube platform directory for details of how the two differ and what limitations you may find.","shortMessageHtmlLink":"Platform change for STM32 only: add support for STM32U5 on STM32Cube."}},{"before":"f8efe433350165f4049ba0c48368d32a3242737d","after":null,"ref":"refs/heads/preview_fix_tick_wrap_2_rmea","pushedAt":"2024-04-24T21:08:15.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":"f774a0b58e0e182b9748f2b3820a3ccfd0186307","after":"79e808eb8be3095b4f94efcffba97515ba1870bd","ref":"refs/heads/master","pushedAt":"2024-04-23T14:37:06.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"MAJOR CHANGE: uTimeout API. (#1143)\n\nMAJOR CHANGE: uTimeout API.\r\n\r\nIN CASE OF COMPILATION FAILURE: if you have copied an existing ubxlib .c file to create your own file, you may find it fails to compile after merging this commit: this is because, in our internal .c files, we do not include ubxlib.h, we bring in only the required headers, and so your .c file will be missing u_timeout.h.  To fix this you should #include \"u_timeout.h\" nearish the top of the inclusions in your .c file, above where you would include things like u_at_client.h, below where you would include u_error_common.h (see the modified .c files in this commit for the pattern).\r\n\r\nA new common API, uTimeout, is added and all timeouts are routed through it. This API performs time comparisons with unsigned 32-bit arithmetic to ensure that timeouts expire correctly if they happen to cross the 32-bit wrap point, which will occur every 50 days for a millisecond tick; otherwise there were instances where a timeout could potentially get \"stuck\" for 25 days (the unsigned 32-bit wrap length for a millisecond tick).\r\n\r\nThe implementation of the API includes the ability to speed up the apparent wrap-rate of the underlying tick; this is used on test instance 23 (which includes cellular, GNSS and short-range module types) to give it a good thrashing.\r\n\r\nOur thanks to warasilapm for raising this issue and _my_ thanks to mazgch for providing the solution.","shortMessageHtmlLink":"MAJOR CHANGE: uTimeout API. (#1143)"}},{"before":"3e11bfda0ecf5e99e491eeb72a4b45848d5836f5","after":"f774a0b58e0e182b9748f2b3820a3ccfd0186307","ref":"refs/heads/master","pushedAt":"2024-04-23T07:58:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"IMPORTANT FIX FOR STM32Cube CMSIS 1: correct default max task priority. (#1149)\n\nIn commit 3e11bfda0ecf5e99e491eeb72a4b45848d5836f5 the CMSIS 1 task priority for STM32Cube should have been reduced by one also; it is now.","shortMessageHtmlLink":"IMPORTANT FIX FOR STM32Cube CMSIS 1: correct default max task priorit…"}},{"before":"2380fe51699407a6fdf526be542abc5d94ff18fa","after":"3e11bfda0ecf5e99e491eeb72a4b45848d5836f5","ref":"refs/heads/master","pushedAt":"2024-04-21T22:50:54.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"IMPORTANT FIX FOR STM32Cube/nRF-SDK: correct default max task priority. (#1148)\n\nFollow up to the previous commit (2380fe51699407a6fdf526be542abc5d94ff18fa): the same thing applies for STM32Cube and nRF-SDK since they both use FreeRTOS.","shortMessageHtmlLink":"IMPORTANT FIX FOR STM32Cube/nRF-SDK: correct default max task priorit…"}},{"before":"a2d986e2944141176eedaee6dc4be87be7eea57b","after":"2380fe51699407a6fdf526be542abc5d94ff18fa","ref":"refs/heads/master","pushedAt":"2024-04-20T23:48:42.000Z","pushType":"push","commitsCount":15,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"IMPORTANT FIX FOR ESP-IDF: correct default max task priority. (#1147)\n\nFor the ESP-IDF platform we set U_CFG_OS_PRIORITY_MAX to 25, a value chosen to match the default value of configMAX_PRIORITIES in FreeRTOSConfig.h, which is [still] 25.  However, we were out by one: configMAX_PRIORITIES is the maximum _number_ of priorities, rather than the maximum priority; the maximum priority is configMAX_PRIORITIES - 1, U_CFG_OS_PRIORITY_MAX should be 24.  The ubxlib code has used this value forever and a day without any apparent problem but in ESP-IDF version 5.2 an assert now goes off:\r\n\r\ncomponents/freertos/FreeRTOS-Kernel/tasks.c:1061: assert failed: prvInitialiseNewTask tasks.c:1061 (uxPriority < ( 25 ))\r\n\r\nIf you see this assert, this is the fix.\r\n\r\nOur thanks to michaelboeding for finding the problem and testing the fix.","shortMessageHtmlLink":"IMPORTANT FIX FOR ESP-IDF: correct default max task priority. (#1147)"}},{"before":"d251066533655c493360f54dbbb5e5333e0b72c4","after":"1f29112f1fc14b9d673115fa83483d76bbc61f07","ref":"refs/heads/preview_feature_cell_ppp_usb_rmea","pushedAt":"2024-04-12T08:55:24.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Add ability to print PPP-level exchange: define U_PORT_PPP_PRINT_ENABLE to do so.","shortMessageHtmlLink":"Add ability to print PPP-level exchange: define U_PORT_PPP_PRINT_ENAB…"}},{"before":"f040ce449e5d677699fd53b3155046b18908c3f3","after":null,"ref":"refs/heads/early_preview_feature_cell_ppp_usb_rmea","pushedAt":"2024-04-10T21:20:45.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":null,"after":"d251066533655c493360f54dbbb5e5333e0b72c4","ref":"refs/heads/preview_feature_cell_ppp_usb_rmea","pushedAt":"2024-04-10T21:14:39.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Cellular PPP change only: PPP over different port.\n\nThe current implementation of PPP runs over CMUX, ensuring that AT commands and GNSS commands can continue while the PPP link is running.  However, u-blox cellular modules do not support use of CMUX on USB connections; one is intended to use different USB end-points for PPP, AT and GNSS traffic.  This is a problem when using a u-blox module [one that supports AT commands over USB] and only a USB connection is available to the MCU.\n\nWith this commit, support is provided for running the PPP interface over a different port to that of the AT interface, which could be a USB end-point, and hence a PPP connection can now be made when only a USB connection to the module is available; see examplePppLinuxSockets() for how to do it.","shortMessageHtmlLink":"Cellular PPP change only: PPP over different port."}},{"before":null,"after":"f040ce449e5d677699fd53b3155046b18908c3f3","ref":"refs/heads/early_preview_feature_cell_ppp_usb_rmea","pushedAt":"2024-04-09T17:30:31.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Cellular PPP change only: PPP over different port.\n\nThe current implementation of PPP runs over CMUX, ensuring that AT commands and GNSS commands can continue while the PPP link is running.  However, u-blox cellular modules do not support use of CMUX on USB connections; one is intended to use different USB end-points for PPP, AT and GNSS traffic.  This is a problem when one is using a u-blox module [one that supports AT commands over USB] and only a USB connection is available to the MCU.\n\nWith this commit, support is provided for running the PPP interface over a different port to that of the AT interface, which could be a USB end-point, and hence a PPP connection can now be made when only a USB connection to the module is available.\n\nTest: 24.1 28 examplePppLinuxSockets","shortMessageHtmlLink":"Cellular PPP change only: PPP over different port."}},{"before":"8b2e457d668804e0622bac25bf0cf73ab56fc48d","after":"f8efe433350165f4049ba0c48368d32a3242737d","ref":"refs/heads/preview_fix_tick_wrap_2_rmea","pushedAt":"2024-04-04T16:22:55.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Initial changes after review.\n\nTest: 1 2 4.1 4.2 4.3.0 4.3.1 4.4.0 4.4.1 5.1.0 5.1.1 5.2.0 5.2.1 5.3 5.4 6.1.0 6.1.1 6.2.0 6.2.1 7 8","shortMessageHtmlLink":"Initial changes after review."}},{"before":"bf58552af5d4c29422fc1c383861245a64d0a439","after":null,"ref":"refs/heads/preview_fix_sock_clean_up_rmea","pushedAt":"2024-04-04T12:30:56.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":"3323b9be7709ce3f898a07e4e812290dfc39f227","after":null,"ref":"refs/heads/preview_feature_sock_forget_rmea","pushedAt":"2024-04-04T12:30:49.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":"57e31bf14862212604fd2a900c3bcf15c9d0fa60","after":null,"ref":"refs/heads/preview_feature_gnss_ucenter_script_rmea","pushedAt":"2024-04-04T12:30:42.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":"01f1aac17dc52e32293f651afee5668a33eeba51","after":null,"ref":"refs/heads/preview_fix_tick_wrap_rmea","pushedAt":"2024-04-04T12:30:29.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":"e7bb366a56a1efc726afec2f5fcfa4c09d0eabaa","after":"8b2e457d668804e0622bac25bf0cf73ab56fc48d","ref":"refs/heads/preview_fix_tick_wrap_2_rmea","pushedAt":"2024-04-04T12:22:15.000Z","pushType":"force_push","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"MAJOR CHANGE: uTimeout API.\n\nA new common API, uTimeout, is added and all timeouts are routed through it.  This API performs time comparisons correctly with unsigned 32 bit arithmetic to ensure that timeouts expire correctly if they happen to cross the 32-bit wrap point, which will occur every 50 days for a millisecond tick; otherwise there were instances where a timeout could potentially get \"stuck\" for 25 days (the unsigned 32-bit wrap length for a millisecond tick).\n\nThe implementation of the API includes the ability to speed up the apparent wrap-rate of the underlying tick; this is used on test instance 23 (which includes cellular, GNSS and short-range module types) to give it a good thrashing.\n\nOur thanks to warasilapm for raising this issue and _my_ thanks to mazgch for providing the solution.","shortMessageHtmlLink":"MAJOR CHANGE: uTimeout API."}},{"before":null,"after":"e7bb366a56a1efc726afec2f5fcfa4c09d0eabaa","ref":"refs/heads/preview_fix_tick_wrap_2_rmea","pushedAt":"2024-04-04T12:08:09.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"MAJOR CHANGE: uTimeout API.\n\nA new common API, uTimeout, is added and all timeouts are routed through it.  This API performs time comparisons correctly with unsigned 32 bit arithmetic to ensure that timeouts expire correctly if they happen to cross the 32-bit wrap point, which will occur every 50 days for a millisecond tick; otherwise there were instances where a timeout could potentially get \"stuck\" for 25 days (the unsigned 32-bit wrap length for a millisecond tick).\n\nThe implementation of the API includes the ability to speed up the apparent wrap-rate of the underlying tick; this is used on test instance 23 (which includes cellular, GNSS and short-range module types) to give it a good thrashing.\n\nOur thanks to warasilapm for raising this issue and _my_ thanks to mazgch for providing the solution.\n\nTest: 1 2 4.1 4.2 4.3.0 4.3.0=1 4.4.0 4.4.1 5.1.0 5.1.1 5.2.0 5.2.1 5.3 5.4 6.1.0 6.1.1 6.2.0 6.2.1 7 8 23","shortMessageHtmlLink":"MAJOR CHANGE: uTimeout API."}},{"before":"3cf5348e22fddd185f878eea49e3bb7526cccdf7","after":"01f1aac17dc52e32293f651afee5668a33eeba51","ref":"refs/heads/preview_fix_tick_wrap_rmea","pushedAt":"2024-04-04T00:06:31.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Iteration N: Michael's iteration.\n\nA new common API, the wrap-safe `uTimeout` API, is added and all timeouts are routed through it.  The implementation of the API includes the ability to speed up the apparent wrap-rate of the underlying tick; this will be used on one of our test instances to give it a good thrashing.","shortMessageHtmlLink":"Iteration N: Michael's iteration."}},{"before":"c2251b77fb44c302d507599050bcd8e75f1d9edf","after":"a2d986e2944141176eedaee6dc4be87be7eea57b","ref":"refs/heads/master","pushedAt":"2024-03-29T08:49:09.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Documentation change only: what to do if you don't know what a named pipe is.","shortMessageHtmlLink":"Documentation change only: what to do if you don't know what a named …"}},{"before":"050e8edb9cb95e874602f8a52134a5e0812d59f3","after":"c2251b77fb44c302d507599050bcd8e75f1d9edf","ref":"refs/heads/master","pushedAt":"2024-03-29T00:44:30.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Minor fix to u_device_serial.c. (#1138)\n\nThe return value of the default function serialDefaultEventCallbackFilterGet() in u_device_serial.c was being cast to an int32_t when it should be cast to a uint32_t, potentially resulting in a warning under some compilers. This is now fixed.","shortMessageHtmlLink":"Minor fix to u_device_serial.c. (#1138)"}},{"before":"20f6dbdff3997b639f2de2a917ba8f3a79ce2d6f","after":null,"ref":"refs/heads/preview_cell_ppp_rmea","pushedAt":"2024-03-29T00:42:14.000Z","pushType":"branch_deletion","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"}},{"before":"3da65fc6f19b1a5c410a3a8f0232462ab78b0ebe","after":"050e8edb9cb95e874602f8a52134a5e0812d59f3","ref":"refs/heads/master","pushedAt":"2024-03-28T22:39:40.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Doxygen fix only.","shortMessageHtmlLink":"Doxygen fix only."}},{"before":"b7e8edc93f4e1311a942a33b8dbedb77f2bfd2dd","after":"3da65fc6f19b1a5c410a3a8f0232462ab78b0ebe","ref":"refs/heads/master","pushedAt":"2024-03-28T22:16:41.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Updated example for cellular only: clearer eDRX outcome. (#1135)\n\nThe E-DRX example for cellular expects that, once E-DRX has been set, the module will emit a URC indicating the assigned E-DRX settings. This works internally on the ubxlib test system however it doesn't seem to be a reliable indication for a live network: likely it depends on the network and when the radio connection is released. So as not to confuse customers, the example is now updated to call the uCellPwrGetEDrx() API to determine the truth if the callback happens not to be called.\r\n\r\nThanks to elektron314 for spotting this.","shortMessageHtmlLink":"Updated example for cellular only: clearer eDRX outcome. (#1135)"}},{"before":"66627474fbb6435d71c73802ac1b829189280835","after":"b7e8edc93f4e1311a942a33b8dbedb77f2bfd2dd","ref":"refs/heads/master","pushedAt":"2024-03-28T09:02:07.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Cell uCPU platform change only: ARMCC fix for gmtime_r() prototype. (#1134)\n\nThe cellular uCPU platform, which uses ARMCC, doesn't have an implementation of gmtime_r(), our own version needs to be brought in and hence the prototype for it needs to be added to u_port_clib_platform_specific.h.","shortMessageHtmlLink":"Cell uCPU platform change only: ARMCC fix for gmtime_r() prototype. (…"}},{"before":"239c5b9b076958f1eaf1b7e85f4f5067c0bb84f9","after":"3cf5348e22fddd185f878eea49e3bb7526cccdf7","ref":"refs/heads/preview_fix_tick_wrap_rmea","pushedAt":"2024-03-28T00:23:38.000Z","pushType":"push","commitsCount":2,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Align straggler keepGoingCallback() in u_device_private_cell.c to the new pattern, align distance/time calculation in u_geofence.c, move in-line functions to be defined in a header file (u_port.h) in order that the compiler can in-line then (rather than the linker being left to do so) and add `Ms` to the end of the function names to be clear on the units of the parameters.","shortMessageHtmlLink":"Align straggler keepGoingCallback() in u_device_private_cell.c to the…"}},{"before":"857e2a6641d747302bc0bcdbce9930965e99b65e","after":"66627474fbb6435d71c73802ac1b829189280835","ref":"refs/heads/master","pushedAt":"2024-03-27T20:58:20.000Z","pushType":"push","commitsCount":4,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Cell uCPU platform change only: ARMCC V6 fix for time_t not found. (#1130)\n\nOn GCC, MSVC and Xtensa toolchains, time.h gets included via one of the \"normal\" headers, while it does not under ARMCC v6; this is now fixed for the cell uCPU platform.","shortMessageHtmlLink":"Cell uCPU platform change only: ARMCC V6 fix for time_t not found. (#…"}},{"before":"2dd46e25078b7c1b519674acc46330982cd0b8da","after":"857e2a6641d747302bc0bcdbce9930965e99b65e","ref":"refs/heads/master","pushedAt":"2024-03-26T14:31:09.000Z","pushType":"push","commitsCount":3,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Sockets API addition: uSockForgetAll() (#1128)\n\nA function is added, uSockForgetAll(), which will cause this code to forget about all sockets, returning to a state as if none were ever opened. This is useful in a VERY SPECIFIC circumstance: when using sockets with a cellular module and that module has entered 3GPP power saving, losing all RAM contents and hence all sockets. Calling uSockForgetAll() will serve to match the state of this code with that of the module in that situation.","shortMessageHtmlLink":"Sockets API addition: uSockForgetAll() (#1128)"}},{"before":"33351089dc6af89c5fad115b1a6261e059e8e6c7","after":"2dd46e25078b7c1b519674acc46330982cd0b8da","ref":"refs/heads/master","pushedAt":"2024-03-22T22:37:48.000Z","pushType":"push","commitsCount":1,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Documentation only: where -1 should be used for UART, SPI and I2C pins.\n\nExplain in a lot more places where -1 should be used for UART, SPI and I2C pins, which is:\n\n- when on Zephyr, for all of them, since all pins (and whether UART flow control is on or off) are set in the device tree,\n- when on Windows or Linux, for the UART TXD and RXD pins (the RTS/CTS \"pins\" act as flow control flags: -1 for no flow control, a positive number for flow control),\n- when on Linux, for the I2C and SPI pins (irrelevant for Windows of course).","shortMessageHtmlLink":"Documentation only: where -1 should be used for UART, SPI and I2C pins."}},{"before":null,"after":"3323b9be7709ce3f898a07e4e812290dfc39f227","ref":"refs/heads/preview_feature_sock_forget_rmea","pushedAt":"2024-03-22T16:01:15.000Z","pushType":"branch_creation","commitsCount":0,"pusher":{"login":"RobMeades","name":"Rob Meades","path":"/RobMeades","primaryAvatarUrl":"https://avatars.githubusercontent.com/u/6726745?s=80&v=4"},"commit":{"message":"Sockets API addition: uSockForgetAll()\n\nA function is added, uSockForgetAll(), which will cause this code to forget about all sockets, returning to a state as if none were ever opened.  This is useful in a VERY SPECIFIC circumstance: when using sockets with a cellular module and that module has entered 3GPP power saving, losing all RAM contents and hence all sockets.  Calling uSockForgetAll() will serve to match the state of this code with that of the module in that situation.","shortMessageHtmlLink":"Sockets API addition: uSockForgetAll()"}}],"hasNextPage":true,"hasPreviousPage":false,"activityType":"all","actor":null,"timePeriod":"all","sort":"DESC","perPage":30,"cursor":"djE6ks8AAAAEPkWNFAA","startCursor":null,"endCursor":null}},"title":"Activity · u-blox/ubxlib"}