• The bus driver performs the following tasks: Suspends the device's USB port by setting the PORTSUSPEND feature. Completes the device's wait wake IRP with STATUSPOWERSTATEINVALID, if one is pending. Completes the device's idle IRP (IOCTLINTERNALUSBSUBMITIDLENOTIFICATION) with STATUSPOWERSTATEINVALID, if one is pending.
• Atmel START is an innovative online tool for intuitive, graphical configuration of embedded software projects. It lets you select and configure software components, drivers and middleware, as well as complete example projects specifically tailored to the needs of your application.

Subject: USART driver using interrupt method for SAMG55J19 device not working as expected. Application: GSM Modem on USART0. My data length is not fixed.Data is transferring continuously. I want to send the data based on requirement or user selection.Is there any. Tried driver-atmel-bundle-7.0.888.exe - didn't help. Tried plugging samd10-xplained. That one complained about mEDBG CDC. And it shows up with an yellow exclamation mark in the device manager under Ports. But the tool shows up in the Studio (as mEDBG).

Atmel Port Devices Driver Updater

Atmel Ice Driver Windows 10

Hi All,

SOLVED : removing external pullups from two of those pins allowed me to set them as output normally and they work normally. If then put those pullup resistors back, then they do not set as output. This is really odd as they are 100k pullups pulling the gate to the source of a load switching (small) mosfet, which is switching logic level voltages (no more than 3.3V). The pullups are there to stop spurious oscillations on startup for the device.it is a very reproducable bug. The pullups actually cause a hardfault to occur and freeze the application which is absolutely bizzare and does not occur on an nrf51422 which is on the same board, with the same processor and scenario.

Currently i am trying to get some software done, and I am being stumped at the earliest part. I am just trying to set some outputs up on a SAM D09, however this seems to cause it to enter the dummy handler in startup_samd09.c. More specifically, setting more than 5 outputs causes the issue, and i cannot find anything about a limit on outputs anywhere in the documentation for this chip.

if I comment out everything below and including this line 'port_pin_set_config( DONUT_EN, &pin_conf_cmd);' then the problem never occurs, and the rest of the application runs fine. Even in a fresh project if i just run only this code with the port driver from ASF it still goes off into the dummy handler. If i step through every single line of code that is called in all of those functions, it seems to work, but in a normal run, it just fails. compiling with no optimisation does not seem to help the problem either, but causes even more odd behaviour.If i let it run with no optimisation, the disassembly shows memory out of bounds, but if i step through without going to deep, it works fine.

Thanks in advance for your time, I am sure I should not be having this problem.