![]() You should be able to find them in the same place you downloaded the ISO image. You do this by downloading the sha256sum.txt and files. Next, you should make sure that the image file you just downloaded is the real McCoy. If you see inaccuracies in our content, please report the mistake via this form. ![]() If we have made an error or published misleading information, we will correct or clarify the article. Our editors thoroughly review and fact-check every article to ensure that our content meets the highest standards. Our goal is to deliver the most accurate information and the most knowledgeable advice possible in order to help you make smarter buying decisions on tech gear and a wide array of products and services. ZDNET's editorial team writes on behalf of you, our reader. Indeed, we follow strict guidelines that ensure our editorial content is never influenced by advertisers. Neither ZDNET nor the author are compensated for these independent reviews. This helps support our work, but does not affect what we cover or how, and it does not affect the price you pay. When you click through from our site to a retailer and buy a product or service, we may earn affiliate commissions. And we pore over customer reviews to find out what matters to real people who already own and use the products and services we’re assessing. We gather data from the best available sources, including vendor and retailer listings as well as other relevant and independent reviews sites. What I'm guessing is that the timing requirements of msc are very much tighter and running this in a thread is way harder to do reliably.ZDNET's recommendations are based on many hours of testing, research, and comparison shopping. So my question here is that this works nicely in CDC without issues. * Sleep CPU only if there was no interrupt since last loop processing */ Investigating this has something to do with the wait loop and I suspect time around that. On my board (which works with CDC only just fine, BTW) and using substantially the same code for msc on it but in a FreeRTOS thread, this thing gets tons of APP_USBD_EVT_DRV_RESET (anywhere between 5 and constant) and enumerates on Win10 and then goes away and comes back and eventually comes back to a stable state. I get like one USB APP_USBD_EVT_DRV_RESET through usbd_user_ev_handler() and it enumerates immediately and stably on Win 10 showing the USB drive. On the example code on the dev kit, this works fine. ![]() I'm just checking for windows enumeration of the things. ![]() In the end I want to run both CDC and MSC on SD cards but to simplify this what I've done is to run BOTH of these code sets with only msc and that only with the empty device on it. What I've done is to take the example code and port it into my thread that runs the USB. I need to run RTOS on my code for other reasons and mostly because the USB portion is a small part of what I need to do. the example code is bare metal without an RTOS on it. Hard to mix the two but I've got it mostly the same. I don't think I've got a hardware issue here but I'm running the usb_msc_pca10056 example on the dev kit and my own custom code on my custom board. I've got both a PCA10056 dev kit and a custom board. On an nRF52840 using SDK 15.3 and FreeRTOS 10 ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |