Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Home NTDEV
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

More Info on Driver Writing and Debugging


The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.


Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/


SerCX2 framework doesn't call EVT_SERCX2_PIO_RECEIVE_READ_BUFFER

RonaldRonald Member Posts: 2

Hi OSR community,

I need your help.
Trying to add Receive path in Serial controller driver. After we get the IOCTL_SERIAL_WAIT_ON_MASK and IOCTL_SERIAL_GET_COMMSTATUS from the peripheral driver there should be a IRP_MJ_READ call and correspondingly SerCX2 should call EVT_SERCX2_PIO_RECEIVE_READ_BUFFER. I see the IRP_MJ_READ getting called and returned successful from SerCX2 without any call to the serial controller driver. I'm intimating the SerCX2 about the new data arrival from IsrDPC by calling SerCx2PioReceiveReady(). May I know why is this behavior and please suggest any resolutions.

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 15 Jun 2020 LIVE ONLINE
Writing WDF Drivers 22 June 2020 LIVE ONLINE
Internals & Software Drivers 28 Sept 2020 Dulles, VA