The FlashDriver folder contains all the files and the library for F021 related work which they are not shown here. They are all needed to be able to EEPROM work. I added CGT.gcc.h last night so I can compile in VectoCAST as well since we use MinGW in there.
Yes we only return a bool to the caller. If they request a write and get a FALSE, it means their request has failed and they have to try again. It is mentioned in the Interface section in AE. Otherwise, we have to return enums instead of Boolean.
So the struct that has the details (see above please) has is called memory operations. The array of type this struct is called jobs and from then jobs is used. Only this struct has memory named.
Sometime we call it a job and sometimes a memory operation. We should probably pick one and be consistent. I think non-volatile memory operation is best.
Files has been modified many times manuallu on my branch as you asked a week or toow before 2020 and by Dara's script on master on 2019 and 2020. It might be me merging files from my branch to master with 2019, since I think his script is running only on master branches.
Files has been modified many times manuallu on my branch as you asked a week or toow before 2020 and by Dara's script on master on 2019 and 2020. It might be me merging files from my branch to master with 2019, since I think his script is running only on master branches.
Files has been modified many times manuallu on my branch as you asked a week or toow before 2020 and by Dara's script on master on 2019 and 2020. It might be me merging files from my branch to master with 2019, since I think his script is running only on master branches.
Files has been modified many times manuallu on my branch as you asked a week or toow before 2020 and by Dara's script on master on 2019 and 2020. It might be me merging files from my branch to master with 2019, since I think his script is running only on master branches.
When the common repo is ready the hash table will be moved there but the function itself remains here since the data types UI and HD are using are different and can't be mixed.
Just as a suggestion, for future it would be helpful to replace the magic numbers with descriptive variables to improve readability here. Will it need to change to support both Standard and Extended CAN?
Can you explain why are you using two threads? One in frame interface and another one in can interface? I would think of a communication system as two threads, one sending information and another waiting to receive a response.
