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

HET IDE simulator vs MOV32

Fred P
Expert 2235 points


Here are a lot of simultaneous strange behavior from the HET IDE simulator (see attached screenshot) with the MOV32 instruction

-Registers A and B miss the 7 LSB
-Data has been written to 0x540 and 0x580 instead of 0x54 and 0x58
-Isn't 0x540 and 0x580 outside the NHET memory?  The assembler would not assemble a MOV32 to 0x540 instruction.
-What we don't see on the screenshot is that nothing at all has been written to 0x80.

I run the 2.6 version.

What is happening in there??

Thanks,

Frederic

  • 0
    Expert 2235 points

    I figured out that A and B registers are 25-bit wide.  I explains the first bullet in my post.  Sorry...

    The other questions still hold...

    Thanks

     

    Frederic

  • 0
    TI__Prodigy 610 points

    Hello Frederic,

    you need to be careful what you specify as the remote address. Each NHET instruction starts at a certain NHET logical address (e.g. 0x1, 0x2, 0x3, ...). These are not the physical addresses. So the instruction at NHET address 0x1 would take up physical addresses 0x10 (program field), 0x14 (control field), 0x18 (data field) and 0x1C (reserved).

    The MOV32 moves its datafield into the datafield of the remote instruction. Basically you need to specify the start address of the remote instruction in terms of NHET logical address and the NHET does reate the correct offset to the datafield in the physical representation. The MOV32 cannot move data to the program or control field.

    Please let me know if this makes it a bit clearer.

    Regards,
    Frank

  • 0 in reply to Frank Noha
    Expert 2235 points

    It does make it clearer.  Thanks.

    Then, does it mean that a good half of NHET memory is missing from the simulator?  Last address is 0x7FC but table 18-1 in TRM shows 0x1FFC as the last address.

    Frederic

  • 0 in reply to Fred P
    TI__Prodigy 610 points

    I can see that this is confusing. Table 18-1 shows a general address assignment which is not specific to a certain device configuration. The device you are using has only capacity for 128 NHET instructions (NHET words). So the logical NHET address can be a max of 0x7F (0x7F0 physical).

    The NHET simulator does only allow access to the amount of memory implemented on a specific device configuration.

     

    Regards,

    Frank