 Rym ni'n gweithio'r project wedi gweithio. F7 i ddydd i fynd. Rwy'n gweithio'r baenrifile. Rydyn ni'n gweithio 0-1 i 0. Rydyn ni'n gweithio project, ddylwad, ddylwad, cael ei wneud. Rydyn ni'n gweithio'r gweithio'r ysgolio ysgolio'r gweithio'r cyfysg. Felly yw'r PC wedi'i gwneud yn ysgolio'r gweithio, felly rydyn ni'n rhoi ychydig yn cenderddio. Felly, yna, yn ddod y gweithio'r gweithio'r gweithio. A rydyn ni'n gwneud yw'r newid o'r LID yna. Rydyn ni'n LID yna, a'r LID yna, o'r LID yna. Felly, y LID yna'r LID yna'r ffordd yn ychynig yw'r atas. roedd llwydoed ac oedd gyrsbion newid us ummyn yn gweithio. Rydych yn gyrsbion newid us治 Rydyrd yn gyd-osc gameplay. Rydych yn symg yn du presiwnd o'r laptopol. Rydych yn gyrsbion戰anion newide. Lorddd Yi Yr Rh smallest mwy o'r U Jerry ol Bod dw i'ch gelliso unseridaeth. Byddwch ei ddedd Studies A Wyrdd y dy mattress. ac mae'r hyn yn deallu. Mae'r 2 yma, y dyfodol y gweinidol yn adored y system ffile. Felly gallwch chi'n gweinidol a'r adeiladau i'n gweinidol a'r ffileidol ar ôl fynd yn y Fartos. Felly, y system ffileid yn rhoi'r cyd-dwyllt yn ymddangos y microcontrolu. Yn ymddangos C ymddangos C, bydd ymddangos C yn ymddangos MCU. Yn y PC mae'n gwybod, mae'n ymddangos C ymddangos C ymdangos C ymddangos C ymddangos L. Felly, rhai'r ffunction eisiau yn dda ni'n fath ffathys. Mae'r FFATFS systr yn fath o'r cyflogion, mae'n fathio'r ffathys, mae'r bwyl yma, mae'r cyflogion yn fathio'r cyflogion mae'r fathys yn fathio'r cyflogion. Mae'r ffathys yma yw'r cyflogion mae'n fathio'r cyflogion. Mae'r fathys yma, mae'n eich cyflogion systio, mae'n eich bod yn gweithio'r cyflogion, mae'r ysgolwyr yn gyntaf o'r cyflawni ar gyflawni gweithio'r cyflawni a'r ffaith FFS, a phaith FFS ym mhawr yma i'r ysgolwyr o'r cyflawni'r ffaith FFS. Felly mae'n gweithio'r cyflawni'r cyflawni'r cyflawni'r cyflawni a gennym ni'n gweithio'r ffaith FFS mewn ysgolwyr i'w ffaith FFS. Felly mae'n gweithio'r cyflawni ymgyrchu ac mae'n gweithio'r twfalu o'r cyflawni'r ffaith FFS. Felly mae'n gweithio'r ffaith FFS, i wneud ffaint i'r ffaith FFS. Felly mae'n gweithio'r ffaith FFS sy'n gweithio'r project. So now we need to go and configure our FATFS middleware. So if we open our FATFS and we go into the configuration we need to make sure that certain things are matching our pre-written application code. So I'll go into the FATFS and we need to make sure that Latin one windows is the code page which is correct. The use long file names needs to be disabled which is correct and the long file name unicode needs to be anti-oem which is correct. So all of those parameters are already correct so we don't have to make any changes there. If we scroll a bit further down to the physical device parameters we need to make sure that we're matching the sector size for our quad SPI memory. So we need to make sure our sector size is correct so we need to set it to 4096 and we need to make sure the minimum one is set to the correct size which again is 4096. So that's all we need to do for the definition of our FATFS so we can okay that screen. So what we have to do with the FATFS this is so that we can not have access by two different pieces of hardware or sorry two different applications to one piece of hardware so we now need to use the mutex which is part of the operating system so that each application or each task within the application can use one physical piece of hardware. So there's no way that you would be able to get both tasks using the same item at the same time so the mutex helps us to control which task is using the physical hardware. So in a standard application here the USB will grab the mutex therefore the USB application can now use the resource which is the quad SPI hardware. When the app task wants to use that same piece of hardware there's no mutex for it to grab so it has to sit and wait for the mutex. When the USB task releases the mutex when it's finished using the piece of hardware the mutex becomes available then the waiting task can automatically then grab that mutex and then that task can access the physical piece of hardware so and when the app task has finished it will then also release the mutex so this is how you use one piece of hardware without conflict from two different tasks within a system so so now we need to configure this in the freeRTOS to make sure that this is all set up correctly so we now need to go back into the freeRTOS and go into the timers and semaphores section so this is where the mutexes are located in the RTOS and we need to add a mutex so called QSPI mutex so if we go into our freeRTOS we need to go into timers and semaphores and we need to add a new mutex so it was QSPI mutex with a capital M okay that so that's our mutex added to the system so that's all we need to do now so have a QSPI mutex so we now can say apply an okay and we can now go and generate code again so again the warning is there about the cystic timer so we say yes again so we'll get that warning every time because we're configured to use the cystic timer and not another one-way time base as before we need to apply a patch again so so we will close this instance for now so that we can go and apply the patch to our code as we have done in the past so this one is going to add two .c files for the freeRTOS so we've modified the freeRTOS to add the mutex and the user disk IO is for the FATFS so that we can access the the storage system structure that we want to use in the quad SPI so if we go back to our patch and we can copy these two files across to our working folder what's added inside the disk IO is the or the initialisation and read and write functions for the application to contact the file structure that's in the QSPI so these are all the new instructions now that we have available to us because we've added the FATFS into the system so when we connect it to the system and generate it we will get a new file on our disk to say that FATFS is okay so that's all it's going to do it's just going to write a text file to our disk to say that the FATFS is running correctly so let's go and copy our two files across