https://devzone.nordicsemi.com/f/nordic-q-a/47592/multitouch-usb-to-hid-over-bluetoothHey guys, i recently bought a nrf52 DK to implement a gateway between a usb touch monitor to a device such as a android or a computer.my approach is recovering the hid raw frame with a raspberry pi and send it by uart to the bluetooth module, and puten-USTelligent Community 13Mon, 27 May 2019 08:52:30 GMThttps://devzone.nordicsemi.com/thread/189238?ContentTypeID=1Mon, 27 May 2019 08:52:30 GMT137ad170-7792-4731-bb38-c0d22fbe4515:8bfda9c4-e872-469a-b54d-9724fdb5c34covrebekk<p>Hi&nbsp;</p> <p>Since you set report count to 1 it seems you are trying to remove the BUTTONS and MOVEMENT reports, and only use the DIGITIZER report. If that is the case you should probably set the INPUT_REP_DIGITIZER_INDEX to 0 rather than 2, since you only have one report in use.&nbsp;<br />The INPUT_REP_REF_DIGITIZER_ID should be 1.&nbsp;</p> <p>If you can also send me the content of your&nbsp;hids_init() function it should be easier to verify if everything is set up correctly (feel free to&nbsp;just attach your main.c file directly, then I got everything).&nbsp;</p> <p>Best regards<br />Torbjørn</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/189007?ContentTypeID=1Fri, 24 May 2019 10:01:28 GMT137ad170-7792-4731-bb38-c0d22fbe4515:72559bd3-4e8c-4ffd-b401-6b38863be370speicherspule<p>Hello,</p> <p>i&#39;m using last version of SDK,&nbsp;15.3.0.&nbsp;</p> <p>i didn&#39;t use the debugger yet,i will try to use it.</p> <p>But i believe this part of the code isn&#39;t initialized in the right way:&nbsp;<pre class="ui-code" data-mode="c_cpp">#define INPUT_REPORT_COUNT 1 /**&lt; Number of input reports in this application. */ #define INPUT_REP_BUTTONS_LEN 3 /**&lt; Length of Mouse Input Report containing button data. */ #define INPUT_REP_MOVEMENT_LEN 3 /**&lt; Length of Mouse Input Report containing movement data. */ #define INPUT_REP_DIGITIZER_LEN 62 #define INPUT_REP_BUTTONS_INDEX 0 /**&lt; Index of Mouse Input Report containing button data. */ #define INPUT_REP_MOVEMENT_INDEX 1 /**&lt; Index of Mouse Input Report containing movement data. */ #define INPUT_REP_DIGITIZER_INDEX 2 #define INPUT_REP_REF_BUTTONS_ID 1 /**&lt; Id of reference to Mouse Input Report containing button data. */ #define INPUT_REP_REF_MOVEMENT_ID 2 /**&lt; Id of reference to Mouse Input Report containing movement data. */ #define INPUT_REP_REF_DIGITIZER_ID 2 /**&lt; Id of reference to Mouse Input Report containing media player data. */ </pre></p> <p>Would you please point me in the right direction to configure this constants?&nbsp;</p> <p></p> <p>Best regards</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/188946?ContentTypeID=1Fri, 24 May 2019 06:42:51 GMT137ad170-7792-4731-bb38-c0d22fbe4515:3aa3fbdd-f9ed-4586-b38b-0db6e421b9a9ovrebekk<p>Hi</p> <p>Which SDK version did you use for the example?</p> <p>Have you tried running the debugger to trace which part of the code is triggering the fatal error?</p> <p>Best regards<br />Torbjørn</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/188945?ContentTypeID=1Fri, 24 May 2019 06:42:01 GMT137ad170-7792-4731-bb38-c0d22fbe4515:eab7f2dc-daad-465c-8eaf-dd0713149699ovrebekk<p>Hi&nbsp;</p> <p>This definitely makes more sense <span class="emoticon" data-url="https://devzone.nordicsemi.com/cfs-file/__key/system/emoji/1f642.svg" title="Slight smile">&#x1f642;</span></p> <p>Best regards<br />Torbjørn</p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/188645?ContentTypeID=1Wed, 22 May 2019 17:14:34 GMT137ad170-7792-4731-bb38-c0d22fbe4515:0d3f73a7-edb1-4e41-a946-d4a7809aaa71speicherspule<p>Attached is my code that i&#39;ve been develop this afternoon. i&#39;ve added data structure and hex hid descriptor and have 2 different pointer positions with the iteration with button0 or button1.</p> <p>I&#39;m getting &quot;</p> <p class="p1"><span class="s1">&lt;warning&gt; app: System reset</span></p> <p class="p1"><span class="s1">&lt;error&gt; app: Fatal error</span></p> <p class="p1"><span class="s1"><br />when connected by UART.&nbsp;<a href="https://devzone.nordicsemi.com/cfs-file/__key/communityserver-discussions-components-files/4/ble_5F00_app_5F00_hids_5F00_mouse.zip">devzone.nordicsemi.com/.../ble_5F00_app_5F00_hids_5F00_mouse.zip</a></span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/188599?ContentTypeID=1Wed, 22 May 2019 13:52:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:47605aa2-eb04-4833-8d56-feaa36e95f4bspeicherspule<p>Dear&nbsp;<span>Torbj&oslash;rn,&nbsp;</span></p> <p><span>Thank you for quick reply. You&#39;re right, the descriptor is wrong.&nbsp;</span></p> <p><span>Now we have&nbsp;</span></p> <p><span>1byte for report id</span></p> <p><span></span></p> <p><span>1byte (3bit value + 5 bis of padding)</span></p> <p><span>2byte x value</span></p> <p><span>2byte y value</span></p> <p><span>1 contact identifier byte</span></p> <p><span></span></p> <p><span>1byte contact counter</span></p> <p><span>1byte + (1+2+2+1)byte*10 + 1byte =&nbsp; 62 byte&nbsp;</span></p> <p><span><pre class="ui-code" data-mode="c_cpp">//-------------------------------------------------------------------------------- // Digitizer Device Page inputReport 02 (Device --&gt; Host) //-------------------------------------------------------------------------------- typedef struct { uint8_t reportId; // Report ID = 0x02 (2) // Collection: CA:TouchScreen CL:Finger uint8_t DIG_TouchScreenFingerTipSwitch : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_1 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_1 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_1 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_1; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_1; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_1; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_2 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_2 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_2 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_2; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_2; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_2; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_3 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_3 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_3 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_3; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_3; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_3; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_4 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_4 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_4 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_4; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_4; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_4; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_5 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_5 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_5 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_5; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_5; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_5; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_6 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_6 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_6 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_6; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_6; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_6; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_7 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_7 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_7 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_7; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_7; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_7; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_8 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_8 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_8 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_8; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_8; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_8; // Usage 0x00010031: Y, Value = 0 to 32767 uint8_t DIG_TouchScreenFingerTipSwitch_9 : 1; // Usage 0x000D0042: Tip Switch, Value = 0 to 1 uint8_t DIG_TouchScreenFingerInRange_9 : 1; // Usage 0x000D0032: In Range, Value = 0 to 1 uint8_t DIG_TouchScreenFingerConfidence_9 : 1; // Usage 0x000D0047: Confidence, Value = 0 to 1 uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t : 1; // Pad uint8_t DIG_TouchScreenFingerContactIdentifier_9; // Usage 0x000D0051: Contact Identifier, Value = 0 to 1 uint16_t GD_TouchScreenFingerX_9; // Usage 0x00010030: X, Value = 0 to 32767 uint16_t GD_TouchScreenFingerY_9; // Usage 0x00010031: Y, Value = 0 to 32767 // Collection: CA:TouchScreen uint8_t DIG_TouchScreenContactCount; // Usage 0x000D0054: Contact Count, Value = 0 to 10 } inputReport02_t;</pre></span></p> <p><span></span></p> <p><span>does it make more sense?</span></p><div style="clear:both;"></div>https://devzone.nordicsemi.com/thread/188569?ContentTypeID=1Wed, 22 May 2019 12:45:19 GMT137ad170-7792-4731-bb38-c0d22fbe4515:a76f6cb8-6ba9-49fb-8bdf-8a731e94639bovrebekk<p>Hi</p> <p>I am a bit confused looking at the struct, and comparing it to the numbers you mention (124 char&#39;s and 62 byte data frame).&nbsp;</p> <p>Correct me if I&#39;m wrong, but the struct sets up 12 similar value groups, each 6 bytes in size (3 one bit values, 5 bits of padding, a one byte contact identifier and two bytes each for X and Y).&nbsp;</p> <p>Then at the end there is one additional byte, which means the full struct should be 12*6 + 1 = 73 bytes in size.&nbsp;</p> <p>Are there too many touch points defined in the descriptor?</p> <p>Do you have an overview of the content of the 124 char UART packet that you are receiving?<br />From the numbers alone it is hard to see how this should match the data structure that you included.&nbsp;</p> <p>Best regards<br />Torbjørn</p><div style="clear:both;"></div>