OSC propertyGet bug

Posted by Hugobox at August 19. 2008

Hi!

When I'm compiling the latest firmware 1.5.1 with YAGARTO in the Make,
I observed that many (maybe all) osc propertyGet calls (ex: appled/1/active ) reboots the Make after approx 5 seconds.

Hummm???

Re: OSC propertyGet bug

Posted by Liam Staskawicz at August 19. 2008

Over USB or UDP? I wonder if it's a stack issue. If you jump into osc.c in the SetActive() function, what happens if you increase the amount of stack allocated to those tasks?

Re: OSC propertyGet bug

Posted by Hugobox at August 20. 2008

Over USB, I tried increasing the stacks, but the problem remains. I'll try the new mcbuilder to see if the same happens.

Re: OSC propertyGet bug

Posted by Hugobox at August 20. 2008

With MCbuilder 0.5.0, building fails on heavy without further info (?!?) but succeeds on example OSC-Heavy. But then If I send a few times OSC ex: (/appled/1/active) through USB through MChelper, the Make reboots.

Re: OSC propertyGet bug

Posted by Liam Staskawicz at August 20. 2008

mcbuilder uses the same firmware source, so I wouldn't expect that to be too different. For more build results, try looking at the Build Log from the View menu... I'll look into the rebooting issue...have you checked if this happens with the pre-built heavy-1.5.1 as well?

Re: OSC propertyGet bug

Posted by Hugobox at August 20. 2008

with the prebuilt heavy 1.5.1 its fine. Otherwise, the problem only happens when OSC is sent through USB, not UDP.

Re: OSC propertyGet bug

Posted by Liam Staskawicz at August 20. 2008

Hmm - there's really not much difference between the two versions other than stack usage. I'll poke around a bit, but I'd be very surprised if it weren't a stack issue somewhere.

Sections

OSC propertyGet bug