Gaurav-Aggarwal-AWS

I am closing this PR. Feel free to reopen if you need anything from us.

I have changed this PR to draft. Please mark it ready when you are done with the changes. Please also include the details about how are you testing these changes.

For RISC-V, you can try using this QEmu demo - https://github.com/FreeRTOS/FreeRTOS/tree/main/FreeRTOS/Demo/RISC-V-Qemu-virt_GCC. If you do not have a platform to test, how are you developing these changes?

@vishwamartur Please share the testing details. Would you also share the details about how you developed these changes.

As I have not heard back, I am closing this PR. Please feel free to create a new one when you are ready with the changes.

@vishwamartur Would you please share how you tested these changes on 32-bit and 64-bit platforms as the same code is used on both the platforms.

I tested this change [using Qemu](https://github.com/FreeRTOS/FreeRTOS/tree/main/FreeRTOS/Demo/RISC-V-Qemu-virt_GCC) and looks good to me. On a side note, I'd suggest to use the [PR template](https://github.com/FreeRTOS/FreeRTOS-Kernel/blob/main/.github/pull_request_template.md) as it guides you what all information to...

> unless UBaseType_t would be accepted Thank you pointing this out. I agree that we should use UBaseType_t as it is defined correctly based on XLEN. Here is the PR...

> We found that in the SDK, when receiving a message from the server, pContext ->lastPacketTime does not change its value, which means that pContext ->lastPacketTime is always 0; It...

> We want to know what might cause this to happen and whether there is log support for debug on the server side. You can try this - https://docs.aws.amazon.com/iot/latest/developerguide/cloud-watch-logs.html. I'd...