• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 583 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

cc2541: Not asking for the next index correctly

Chingun Khasar
Intellectual 615 points
Part Number: CC2541
Other Parts Discussed in Thread: CC2541

I first send the image header. Mine is F4D30002392B42424242FFFFFFFF. Then I receive notification for 0000 index from imgBlock, I send it random 20-byte array just to see if it asks for the next index 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000, but it asks for 0100(Then it goes to  0d00, 0F00, 1000, 1100 ...). Why is it doing this? Shouldn't it ask for 0001?

Why is it doing this? Shouldn't it ask for 0001? What happens when it goes higher than FF00? because my image has 4 digit length

  • 0
    TI__Mastermind 25035 points

    Hi, 

    It could be that it is little-endian, so 0100 could be translated to 0001. Let me double check. The TRM also mentions that multi-byte fields are stored little-endian:

    www.ti.com/.../swru191d.pdf

    Best wishes

  • 0
    Intellectual 615 points

    Part Number: CC2541

    I am not understanding some things from the OAD Guide, I was hoping you could explain to me.

    1. I am not receiving the next index after I send the first block.

    • First I send the Image header f4d30002392b4141414100000000. Then I send the first block index (0x0000) followed by 16-byte block, so 18-byte in total.
    • However, I am not receiving the next index no matter how many times I send the first block.

    2. When I send f4d30002392b4141414100000000, does this mean I am trying to update image A?

    3. If it responds me with 0100007C42424242, does this mean it is running image B at the moment? Moreover, what do the first few bytes ("0100007C") mean?

    4. On the OAD Developer's guide, it says that CRC shadow has to be 0xFFFF, but I never had to deal with CRC shadow. How and Where do I set CRC shadow?