AWS re:Post을(를) 사용하면 다음에 동의하게 됩니다. AWS re:Post 이용 약관
AWS re:Postre:Post

Fuota Session error: FragmentationIndexUnsupported

0

We're facing some issues on the FUOTA session, specifically on the FragSessionSetupReq command which AWS IoT Core issues from the Fragmented Data Block Transportation Specification. Once the multicast setup is ready for a multicast group which include just a single device, we schedule a FUOTA task for that group. Unfortunately, we always get the FragmentationIndexUnsupported error: the FragSession field we get is "0x1F" (FragIndex: 1) Is there any way to set the FragIndex on AWS? Still, how can we set the FragMaxSize, NbFrag and the FragMaxRedundancy? We uploaded several firmware images of different size, and it seems that AWS IoT Core always splits them in fragments of 48 bytes.

주제
사물 인터넷(IoT)
태그
AWS IoT Core
언어
English
OroN
질문됨 일 년 전257회 조회
2개 답변
0

Hi OroN. What device are you using? Does it support only a single fragmentation session and hence an index of 1 exceeds its capacity (in other words, are you saying AWS IoT Core for LoRaWAN sends an index of 1 but you think it should be 0)?

In regards to the fragment and number of fragments, these settings are not currently exposed to the user. However, they change based on the DR inherited from the multicast group.

UPDATE: AWS IoT Core for LoRaWAN uses fragmentation index 0 for unicast FUOTA and fragmentation index 1 for multicast FUOTA.

profile pictureAWS
전문가
Greg_B
답변함 일 년 전
  • OroN
    일 년 전

    Yes we use an embedded device with a Lorawan stack library supporting only one multicast session. The multicast index value is zero due to the following requirements in "Lorawan Remote Multicast Setup specification v1.0.0". Is it possible to set the AWS lorawan multicast index to zero to be compliant to the requirement?

  • Greg_B 전문가
    일 년 전

    You said in your question that the error is FragmentationIndexUnsupported. This relates to fragmentation index and session, not multicast. If your device is using LoRaMAC-node, then the error comes from here: https://github.com/Lora-net/LoRaMac-node/blob/master/src/apps/LoRaMac/common/LmHandler/packages/LmhpFragmentation.c#L373 . I re-tested FUOTA. AWS IoT Core for LoRaWAN correctly used multicast index 0. However, the fragmentation index is 1 when I think it should be 0 for the first session. I have reported it. I will keep you posted.

  • Greg_B 전문가
    일 년 전

    Are you able to modify the device firmware? If so, you could increase FRAGMENTATION_MAX_SESSIONS to get un-blocked for the time being.

  • Greg_B 전문가
    일 년 전

    OK, AWS IoT Core for LoRaWAN uses fragmentation index 0 for unicast FUOTA and fragmentation index 1 for multicast FUOTA.

0

Yes we use an embedded device with a Lorawan stack library supporting only one multicast session. The multicast index value is zero due to the following requirements in "Lorawan Remote Multicast Setup specification v1.0.0"

Enter image description here

Is it possible to set the AWS lorawan multicast index to zero to be compliant to the requirement?

OroN
답변함 일 년 전
  • Greg_B 전문가
    일 년 전

    As per my other comment, the issue is the fragmentation session and index, not multicast.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠