Objective Development Forums

Hi John, as addressed that is not what the topic is about and as I said I already use the WD method for device resets. This topic is about how to reset the device externally. That is to say how can one communicate with the device to reset it or call a reset function from the OS. The proposed solutio...

I definitely follow you here. I guess if I developed an app to communicate with my usb descriptor I could simply send a report id to indicate this. I would not really need the bootloader for that at all, this could be done in my normal code area. I already have an out interrupt for my FFB that has p...

in this case that would work, Micha. So how do you call leaveBootloader from a bat file, or exe?

uhh, wow ok "I want to reset my device via a tool or bat file" Can anyone tell me how? Thx to Davie I know know its possible but I'm still looking for a way to do it? Hi Micha, yes I know it can be done in the firmware, but I want to do it via the OS. I use an atmega328 and the bootloader ...

Hi David, could you elaborate please? Or are you saying you just know its possible?

I'm guessing this can be done since the flash app does it. I want to reset my device via a tool or bat file. Is this possible?

I bet because the report size was wrong, you need to calculate the report size when changing it. You proly just happened to find one that matched.

Then you goofed the descriptor, joystick is what you want
0x09, 0x04, // USAGE (Joystick)

If you still have issues post your descriptor.

you can set it in chunks like so. while (!usbInterruptIsReady()){ usbPoll(); } usbSetInterrupt((void *)&reportBuffer + 0, ; while (!usbInterruptIsReady()){ usbPoll(); } usbSetInterrupt((void *)&reportBuffer + 8, ; while (!usbInterruptIsReady()){ usbPoll(); } usbSetInterrupt((void *)&repo...

uchar *data : This is nothing more then a pointer to address in memory. uchar ( unsigned char ) is the size you need to hold that address. Pointers are a big part of C, I suggest you read up on them. uchar len : Here we are setting len to a type uchar ( not a pointer this time ). len will be the len...

well there ya go.

I seem to remember something about the pico chips causing issues. My advice would be to try a atmega8/168/328 and see if it works. If its the chip then you may have to email Christian.

I apologize if I'm out of line here, and I can not say I know whether or not this is an issue. However I'm fairly certain 500 ms is a bit of a long wait in between pulls. I though t the usb expects talk after x ms, otherwise quits.

not with the (s)nes, it uses _dealys no "nop" operations so setting your clock in the project is all you need to do. V-usb will work on a 16 ( later versions only ) I was referring to a 12.1 or so. The usb timing is critical. Slowing down a cock IMO is silly, just use the right crystal... ...

Is the Cristal 12mhz on the dot, the simplest deviation will cause your issue. I would certainly try another, i use HC-49S.