Announcement

Collapse
No announcement yet.

cpio.c sample of v1.4

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • cpio.c sample of v1.4

    I am testing cpio sample of v1.4.
    This sample cannot enable the status of cp.
    So, this sample did not work.
    This sample needs calling factory-default before every time running.
    After calling factory-default, the status is enabled.
    I think this sample has the lacking of initialization.
    I don't know what setting does it lack.

  • #2
    Try changing:
    uint32_t outValue = inValue & 1; // this doesn't appear to change anything
    to
    uint32_t outValue = inValue | 1; // this will set it to 1
    or
    uint32_t outValue = inValue ^ 1; // this will toggle (on - off)

    Comment


    • #3
      Thank you reply. I have tested your recommending. But I got same result.
      This cpio-sample makes groups that are named "SampleIn" and "SampleOut" in CPM.
      When the status of "SampleIn" and "SampleOut" are enabled, this sample works well.
      When the status of "SampleIn" and "SampleOut" are disabled, this sample does not work.
      I have to find the way of enabling "SampleIn" and "SampleOut" in initialization.
      So, I posted to this forum.

      Comment


      • #4
        I am doing this in temporary.
        There is initialization part in cpio.c.
        I think this issue is made by multiple initialization.

        First, I run original cpio.c.
        Next, I compile cpio.c without initialization part.
        Next, I write object to MachPortAR.
        cpio.c runs well.

        Comment


        • #5
          The idea behind the demo was to reflect on CP2 the state of CP1, so the original & 1 was correct. However, I see the demo does not work and the importing of the XML is erroring - standby

          Comment


          • #6
            This issue was fixed by new SDK V1200R1.

            I checked cpio sample of v1.6.
            Thank you very much for update.

            Comment


            • #7
              Okay...thanks for letting us know.

              Comment

              Working...
              X