Announcement

Collapse
No announcement yet.

uCAM-III Reset ACK after GET_PICTURE

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • uCAM-III Reset ACK after GET_PICTURE

    Hi,

    I am faced with an odd problem, I get an RESET ACK after a GET_PICTURE CMD @ 115200 baud and 3.3V signaling
    [ucam_get_dev] Fetched Command 0xAA0E0D000000 len 6
    [process_uinit_state] Got the ACK after 6 attempts
    [process_uinit_state] Looking for SYNC from device
    [ucam_get_dev] Fetched Command 0xAA0D00000000 len 6
    [process_uinit_state] Got the SYNC from device, responding with ACK
    [ucam_send_cmd] Sending Command 0xAA0E0D000000
    [process_connected_state] Process Connected State
    [process_connected_state] INITIAL CMD
    [ucam_send_cmd] Sending Command 0xAA0100070707
    [ucam_get_dev] Fetched Command 0xAA0E01010000 len 6
    [process_connected_state] PACKAGE_SIZE CMD
    [ucam_send_cmd] Sending Command 0xAA0608000200
    [ucam_get_dev] Fetched Command 0xAA0E06020000 len 6
    [process_ready_state] Process Ready State
    [process_ready_state] SNAPSHOT CMD
    [ucam_send_cmd] Sending Command 0xAA0500000000
    [ucam_get_dev] Fetched Command 0xAA0E05030000 len 6
    [process_ready_state] GET_PICTURE CMD
    [ucam_send_cmd] Sending Command 0xAA0401000000
    [ucam_get_dev] Fetched Command 0xAA0E08040000 len 6 <----- Why 0xAA0E08 ????
    [process_get_data_state] Process Get Data State
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0 <------ Invalid Data
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0
    [ucam_get_dev] Fetched Command 0xFFFFFFFFFFFF len 0


  • #2
    Any insight on this issue ?

    Comment


    • #3
      Hi retry111,

      What is the supply voltage you provide to the uCAM-III?

      Did you get these results from the uCAM-III DEMO in the workshop 4 IDE and using a Serial-to-USB converter?

      Comment


      • #4
        The supply voltage is 5.2V from a power supply. The results were not obtained via the uCAM-III DEMO, it was obtained via an embedded board communicating with the ucam

        Comment


        • #5
          Do you have any available Serial-to-USB converter? like the uUSB-PA5?

          Can you please simulate the scenario using the uCAM-III demo from the Workshop 4 IDE? Just go to NEW > (on the drop down menu box) OTHER > UCAM-III demo. You will need to connect the uCAM-III to the PC using a Serial-to-USB TTL converter (5V, TX, RX and GND) to send the commands from the uCAM-III demo (PC) to the uCAM-III itself.

          We have already simulated and tested this scenario, but we could not get the same results/issue as in your post. Let us try to isolate the uCAM-III if it is indeed faulty.
          Attached Files
          Last edited by Mark Kevin; 17th October 2017, 02:18 PM.

          Comment


          • #6
            Using the demo, I got the camera working correctly and producing a photo. I am in the process of trying to compare the waveforms between the demo and my device but this will prove quite arduous. Any "low hanging fruit" I can try? I checked the supply voltage, it's in spec.

            Comment


            • #7
              Since we've isolated the problem. I think that you should double-check if your custom board sends/receives the correct serial byte commands. Try using the Serial-to-USB and a serial terminal (you can use the workshop 4 IDE > Tools > Serial Terminal 9600/Serial Terminal 115200) to check your custom board.

              Comment


              • #8
                So I hooked up two serial cables to the TX and RX of the uCAM to capture what it receives and sends out, below is the output: MASTER TX. Is there any way to check what could be the reason for the reset? Is it possible for the camera to send a RESET ACK without a command prompting it to do so, if so under what circumstances could that happen? Anything else you can think of that I can check?

                Click image for larger version  Name:	master_tx.png Views:	3 Size:	17.3 KB ID:	60149

                MASTER RX

                Click image for larger version  Name:	master_rx.png Views:	1 Size:	17.6 KB ID:	60152
                Attached Files
                Last edited by retry111; 23rd October 2017, 04:00 AM.

                Comment

                Working...
                X