AndrewD
AndrewD
> But i meet a new problem mentioned here @Comet959 I think you will have more success if you look at the repository mentioned by @trabucayre above. I believe it...
> But for `check_image_in_flash` and `copy_image_from_flash_to_ram` its less clear. Is it to allows custom code to check and load firmware for a custom boot mode more or less similar to...
I would also like to rename for `check_image_in_flash` and `copy_image_from_flash_to_ram` but didn't to minimise the diff
@maass-hamburg this does sound very interesting: do you have any examples of a gateware driver that uses this core? We have been using the misoc i2c core for a while...
Thanks, that looks like quite a logical interface and the usage pattern is similar to your zephyr driver which is as I expected. I think we will transition our usage...
I just had another look at this: the next thing that come to mind is support for IRQ so the a message can be queued without polling for completion. For...
Will do, it will just be a few more weeks before I'm back on our project where we intend to use this core.
Probably better to enforce policy like this from the tool doing the sending, target then baking it into the remote device. For example, you could do something like the policy...
Bulk transfers are where CS is asserted, then more than one byte is transferred, then CS is de-assarted. Some usages of spimaster have cs asserted and de-assarted for every byte,...
Yes, looking at the code the documentation doesn't match. Maybe it was this way but the core was changed to fix a specific case?