Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Debug / Release Issue #1

Open
dareis08 opened this issue Jun 7, 2016 · 7 comments
Open

Debug / Release Issue #1

dareis08 opened this issue Jun 7, 2016 · 7 comments

Comments

@dareis08
Copy link

dareis08 commented Jun 7, 2016

I can run the driver fine if I put a debug breakpoint somewhere in the code. However when I go to release, or run in Debug without a break-point it hits the "Failed to fetch version" warning. Have you seen this issue before? It seems like a timing thing but I'm not sure.
Thanks,
Darren

@cottsay
Copy link
Member

cottsay commented Jun 8, 2016

I haven't seen this before. Can you post the TSS firmware version you have on your device?

@dareis08
Copy link
Author

dareis08 commented Jun 8, 2016

I solved it. I added a 500 ms delay and the release-build worked. Somehow
the timing was thrown off without giving this initialization delay.
This is a great repo, thanks for sharing!

On Wed, Jun 8, 2016 at 2:53 PM, Scott K Logan [email protected]
wrote:

I haven't seen this before. Can you post the TSS firmware version you have
on your device?


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFrqslFdDxnJUmZM0sHBg-LUTAJ0Mko1ks5qJznLgaJpZM4IwBo-
.

@cottsay
Copy link
Member

cottsay commented Jun 8, 2016

Where exactly did you need the delay? I'd like to look into this further because it shouldn't be needed. Something isn't right.

@dareis08
Copy link
Author

dareis08 commented Jun 8, 2016

in TSSOpenNoLock() after the "return true"

On Wed, Jun 8, 2016 at 3:32 PM, Scott K Logan [email protected]
wrote:

Where exactly did you need the delay? I'd like to look into this further
because it shouldn't be needed. Something isn't right.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFrqsj8fZGhKJ9UaXf4w4-lJQz3N8LXIks5qJ0L3gaJpZM4IwBo-
.

@cottsay
Copy link
Member

cottsay commented Jun 8, 2016

Interesting, thank you.

If you get a chance, try using the code in the fw_updater branch. It has a commit which changes some of this stuff, and I'm interested to hear if it fixes your problem.

--scott

@ghost
Copy link

ghost commented Jun 20, 2016

Having the same issue here. I'm using the fw_updater branch on IMU with 3.0 firmware.

The delay fix did not work for me. I'm guessing the sleep should be added here:

bool TSSUSB::TSSOpenNoLock( )
    {
        if( tssd >= 0 ) 
            return true;
        sleep(1);

@ghost
Copy link

ghost commented Jun 20, 2016

Opps sorry, the following does the fix:

        reset_srv = nh_priv.advertiseService( "reset", &TSSUSB::ResetCB, this );
        factory_srv = nh_priv.advertiseService( "restore_factory_settings", &TSSUSB::FactoryCB, this );
        led_color_srv = nh_priv.advertiseService( "set_led_color", &TSSUSB::LEDColorCB, this );
sleep(1);
        return true;

    }

@ghost ghost mentioned this issue Jun 20, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants