where is printout >>>USBHIDParser::out_data coming from

[Garug]

Hi, working with USBHost_t36.h and Teensy 4.1. It is likely I activated the printout somehow half year ago, but can not figure where.

On terminal I get constant printout

>>>USBHIDParser::out_data
>>>USBHIDParser::out_data
>>>USBHIDParser::out_data
>>>USBHIDParser::out_data
>>>USBHIDParser::out_data

Any idea where this is coming from and how to deactivate it

 

[BriComp]

Forum Rule: Always post complete source code & details to reproduce any issue!

 

[Garug]

Yeah, so you would want to see the 5000 lines of code, to solve an issue that hopefully is clear from >>>USBHIDParser:ut_data

I do not think the problem is on my code. I think that comes from some library where I activated some debug printout but can not find where, I was hoping someone would recognise the >>>USBHIDParser:ut_data

 

[shawn]

Have you tried grepping through all your code and libraries for the string “out_data”?

 

[wwatson]

In the USBHost_t36 library find hid.cpp. make sure line #253 is commented out:

void USBHIDParser::out_data(const Transfer_t *transfer)
{
	[COLOR="#FF0000"]//Serial.printf(">>>USBHIDParser::out_data\n");[/COLOR]
	println("USBHIDParser:out_data called (instance)");
	// A packet completed. lets mark it as done and call back
	// to top reports handler.  We unmark our checkmark to
	// handle case where they may want to queue up another one. 
	if (transfer->buffer == tx1) txstate &= ~1;
	if (transfer->buffer == tx2) txstate &= ~2;
	if (topusage_drivers[0]) {
		topusage_drivers[0]->hid_process_out_data(transfer);
	}
}

Only found this instance of that debug output...

 

[Garug]

Thanks, it must be that, will verify tomorrow