Pieter Steendam’s Post

what if i told you setting reliability goals for your org would help you achieve smooth operations, and you can actually do this for free? check it out at nobl9.com

#Streamline your investigations with #ATRIO! Utilizing the powerful #NSRL database, ATRIO filters or matches known software files, saving time and effort. Efficient identification and organized results in the "HASH_RESULTS" folder. #DFIR #DigitalForensics #lawenforcement #ICAC

AVI: AKO and SAML - FQDN blog

AVI: AKO and SAML - FQDN blog

How AXI is able to give better throughput than AHB? AXI is able to give 2x throughput with the help of duplex transfers where as AHB cab do single transfer per a clock cycle. AXI has completely independent channels for read/write, which enables full duplex mode of data transportation. That is to say read and writes can take place simultaneously, giving 2x boost over AHB in any circumstances. However this will ONLY be possible when the slave is able to process 1 read and 1 write operation simultaneously in 1 clock cycle. Which in many cases will be possible, e.g. if the slave is a dual port SRAM which can process 1 read and 1 write transaction simultaneously. In the above example we are considering 1 Master and 1 Slave. But in case of multiple slaves, the master can send read transaction to 1 slave and write to other slave, even if the slave(s) cannot handle more than 1 transactions in single clock cycle. To make more clear, in a system where there is only 1 master and only 1 slave, the slave is unable to process read and write in 1 single clock cycle simultaneously and both master and slave are in single synchronous clock domain with no clock delay between the master and the slave there wont be any difference in performance between AXI and AHB. The AXI will only consume more power and area. But this may not be the scenario in most of the cases as the complexity of the designs are growing day by day. #AXI #ASIC #VLSI #RTL #AMBA #SOCDESIGN #vlsifreshers

AVI: AKO and SAML - FQDN blog

🎁 I just submitted my first CumulusCI contribution of 2024!!! An ISV I'm working with really needed the ability to define one-off custom tasks and flows in a separate file and only load them when needed. This highlighted a limitation of CumulusCI's approach that all configuration lives in the cumulusci.yml file. Teams that create many flows and tasks for one-off scenarios like tests or particular customer configurations can quickly see a proliferation of tasks and flows making discovery more difficult. The pull request I just submitted adds a new --load-yml <path/to/additional.yml> option to the cci flow and cci task commands. If set, the yaml from the file at the path specified will be merged on top of the project's cumulusci.yml configuration only for the context of the command being run. 🏃♂️ I'll be continuing contributions to CumulusCI throughout January. It's a great way to start off the year, especially since it's a doing good by doing good scenario. This single contribution will directly unlock previously unimaginable efficiencies for my client who needs it this week. What ideas do you have for how you could use this new feature? Check out the full PR for details and docs: https://lnkd.in/grVwnBBN

Learn key techniques, tools and tips for testing and debugging #MIPI I3C bus operation in the recent webinar presented by Jonathan Georgino, member of the MIPI I3C Working Group and founder & CTO of Binho. Watch the webinar and download his presentation: https://bit.ly/3PeMCHH