Forum Widgets
Latest Discussions
Configuring Levelx
I am kind of lost about filex vs levelx configuration. My memory is the w25q64jv, it has 8mb being 2048 blocks of 4096 bytes. Configuring levelx: nor_flash->lx_nor_flash_total_blocks = 2048; nor_flash->lx_nor_flash_words_per_block = 128; What I have understood is Levelx uses 1 sector (512b) for control, so 7 sectors are left for data for each block (4096b). Now I computed the total data sectors available: 7 x 2048 = 14336 and have used this amount when formating the media (total_sectors). Is that right?
LevelX with SDCard
I am looking at LevelX to use with an SD Card. I see that LevelX uses the 'spare' byes on each page. It appears that the extra, say, 16 bytes on a 512 byte nominal page means there is actually 528 bytes per page. This accords with my experience with small NAND Serial Data Flash chips where I have direct access to 528 bytes per page. I'm new to using SD Cards so I'm not too familiar with the spec. Are the extra bytes available to read/write? The SD Card I'm using reports 512 bytes per page. I cannot see or find any way to access the extra bytes. I'm using the i.MXRT 1064 with NXP's SDK (fsl_sd.c, fsl_sdmmc.c, etc.) Or, is LevelX not advisable for SD Cards? I understand that at least some SD Cards have wear leveling built in, but I didn't think it was universal. Am I wrong in this assumption?
NetX Duo and AWS
Hi, I am currently using Azure RTOS on my project. I want to connect my device with AWS(Amazon Web Services). I found some sources but, I did not find any examples on STM32 devices. Is there any examples with NetX Duo on AWS? On the other hand I have found examples with FreeRTOS. Do I have to use FreeRTOS to access all features of AWS? Regards
What am I missing? The names of the threads, queues, etc. are prototyped as char*.
But this causes an issue because one shouldn't (it violates sane rules) cast a "const char*" to a "char*". This would be necessary of you use a literal string in the call to the function. I locally changed all the prototypes for the thread create and the issue goes away. But I am wondering why it isn't like that to begin with.STM32 NetX Duo LwM2M Firmware Update
I have a project with STM32 MCU and BG95 LTE module. I use NetX Duo with LwM2M protocol. I am trying to implement FOTA for STM32 with LwM2M protocol. I haven't find resources for that. Is there any example for that? How can I implement that function? (Any suggestions)
Using FileX on internal microcontroller flash
Any support or examples on using FileX on internal microcontroller flash? I know there are complications in writing while executing from flash but some processors have hardware provisions to support this or other work arounds like running from SRAM while programming. I am envisioning this for modest amounts of mainly configuration data or static web pages.suppress incompatible pointer types in Azure RTOS demo program
I am bringing up Azure RTOS on a new ARM M4 platform. Most everything is built and running. I patterned the port closely after the Microchip ATSAME54-XPRO ARM M4 getting stated platform. I removed the Azure IoT main.c and replaced it with the simple demo test program as described on Chapter 6 - Demonstration System for Azure RTOS ThreadX | Microsoft Docs When I compile I am getting this warning/error that do not know how to suppress: Can some one help? ty_module/inc -IC:/ti/workspace_v10_test/getting-started/core/lib/netxduo/addons/azure_iot/azure_iot_security_module/iot-security-module-core/inc -I../lib/ti_start/config -I../lib/ti_start/src -Ic:/ti/simplelink_msp432e4_sdk_4_20_00_12/source/third_party/CMSIS/Include -IC:/ti/workspace_v10_test/getting-started/core/src/. -IC:/ti/workspace_v10_test/getting-started/core/src/azure_iot_mqtt -IC:/ti/workspace_v10_test/getting-started/core/src/azure_iot_nx -IC:/ti/workspace_v10_test/getting-started/core/lib/jsmn/src -I../lib/netx_driver/src -mthumb -mcpu=cortex-m4 -mfloat-abi=hard -mfpu=fpv4-sp-d16 --specs=nano.specs -ffunction-sections -fdata-sections -fno-strict-aliasing -fno-builtin -fshort-enums -Wall -Wextra -Wuninitialized -Wshadow -Wdouble-promotion -Werror -Wno-unused-parameter -Wno-old-style-declaration -O0 -g3 -std=gnu99 -MD -MT app/CMakeFiles/msp432e_azure_iot.dir/maindemo.c.obj -MF app\CMakeFiles\msp432e_azure_iot.dir\maindemo.c.obj.d -o app/CMakeFiles/msp432e_azure_iot.dir/maindemo.c.obj -c ../app/maindemo.c ../app/maindemo.c: In function 'tx_application_define': ../app/maindemo.c:79:36: error: passing argument 2 of '_txe_byte_allocate' from incompatible pointer type [-Werror=incompatible-pointer-types] 79 | tx_byte_allocate(&byte_pool_0, &pointer, DEMO_STACK_SIZE, TX_NO_WAIT); | ^~~~~~~~ | | | CHAR ** {aka char **} In file included from ../app/maindemo.c:10: C:/ti/workspace_v10_test/getting-started/core/lib/threadx/common/inc/tx_api.h:1396:63: note: expected 'void **' but argument is of type 'CHAR **' {aka 'char **'} 1396 | UINT _txe_byte_allocate(TX_BYTE_POOL *pool_ptr, VOID **memory_ptr, ULONG memory_size, ../app/maindemo.c:87:36: error: passing argument 2 of '_txe_byte_allocate' from incompatible pointer type [-Werror=incompatible-pointer-types] 87 | tx_byte_allocate(&byte_pool_0, &pointer, DEMO_STACK_SIZE, TX_NO_WAIT); | ^~~~~~~~ | | | CHAR ** {aka char **} In file included from ../app/maindemo.c:10: C:/ti/workspace_v10_test/getting-started/core/lib/threadx/common/inc/tx_api.h:1396:63: note: expected 'void **' but argument is of type 'CHAR **' {aka 'char **'} 1396 | UINT _txe_byte_allocate(TX_BYTE_POOL *pool_ptr, VOID **memory_ptr, ULONG memory_size, ../app/maindemo.c:97:36: error: passing argument 2 of '_txe_byte_allocate' from incompatible pointer type [-Werror=incompatible-pointer-types] 97 | tx_byte_allocate(&byte_pool_0, &pointer, DEMO_STACK_SIZE, TX_NO_WAIT); | ^~~~~~~~ | | | CHAR ** {aka char **} In file included from ../app/maindemo.c:10: C:/ti/workspace_v10_test/getting-started/core/lib/threadx/common/inc/tx_api.h:1396:63: note: expected 'void **' but argument is of type 'CHAR **' {aka 'char **'} 1396 | UINT _txe_byte_allocate(TX_BYTE_POOL *pool_ptr, VOID **memory_ptr, ULONG memory_size, ../app/maindemo.c:103:36: error: passing argument 2 of '_txe_byte_allocate' from incompatible pointer type [-Werror=incompatible-pointer-types] 103 | tx_byte_allocate(&byte_pool_0, &pointer, DEMO_STACK_SIZE, TX_NO_WAIT); | ^~~~~~~~ | | | CHAR ** {aka char **} In file included from ../app/maindemo.c:10:
