• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 30 subscribers
  • Views 237 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.

IWR6843AOP: CLI strange behavior

jyl
Intellectual 745 points
Part Number: IWR6843AOP
Other Parts Discussed in Thread: UNIFLASH,

Hello All,

We just received our board, greatly inspired from the IWR6843AOPEVM kit, and we have difficulties to set it up.

We are using the out_of_box_6843_aop project, slightly modified.

This project compiles well under CCS,

We still have difficulties to debug it with XDS debugger, but at least we can load the project onto the EVM using UniFlash and it works as expected.

When we try on our board: programming through the serial port (SOP2=1) works well, but when running the firmware (SOP2=0), we get no output on the CLI serial port, and when we enter any command we just get the echo of the command, plus, and this is what is very strange, the string '20' inserted (characters 0x32 0x30) when there is a 'v' character in the command sent (for example version returns version20), and only in that case.

Switching back and forth between the EVM and our board, I did see the same behavior once on the EVM, which disappeared after touching S3 (SOP2) switch, which might have been not well set...

However I'm no more able to reproduce it on the kit, while it is systematic on our board.

Does it ring any bell to any of you?

If I was able to run the firmware through the debugger maybe I would  observe something useful, but I can't: (error -2062) Unable to halt device

Which is the same error I get on the EVM...

Any suggestion welcome!

Thanks

Jylo

  • 0
    TI__Expert 4448 points

    Hello,

    This does not ring a bell for me. Are you power cycling the device when you switch SOP modes? How is your design different than our EVM? Without more design context, we cannot help effectively. Are you using any different components?

    Kind regards,
    Luke

  • +1 in reply to Luke Rouleau
    Intellectual 745 points

    Hi Luke,

    Actually, I think the problem seems to be just the speed grade of the flash memory.

    Because the MX25R1635FZUIH0 was not available at the time we manufactured the prototype, a MX25R1635FZUIL0 has been mounted instead.

    And the difference is huge, with a max speed falling from 80 to 8 only MHz!

    In the mean time I found the post https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/986342/iwr6843aop-flashing-isssue-mx25r1635fzuil0

    confirming the possible issue. The prototype is now back to the shop for replacing the flash memory.

    What is surprising is that IWR6843AOP was not completely dead, even it was not able to load the firmware...

    Thanks

    Jylo

  • 0 in reply to jyl
    TI__Expert 4448 points

    Good find Jylo!

    I will close this thread after this message, please open another thread if you have further issues. I will also point you to this relevant E2E, which is about using a different FLASH than the one we built into the EVM. This applies to flashes which are functionally identical (not the case in your situation because of the speed downgrade) but come from different manufacturers. The code has a check for the JEDEC ID and if it is not the same flash used in the EVM, this part of the code must be updated. Please keep this in mind while testing the board when you get it back from the shop.

    Regards,
    Luke