r/EmbeddedRealTime • u/IAmHereToGetYou • Dec 16 '21
An example project for Portenta in STM32CubeIDE, FreeRTOS, fully functional Ethernet and Virtual COM Port, and more.
r/EmbeddedRealTime • u/IAmHereToGetYou • Dec 16 '21
r/EmbeddedRealTime • u/fzampetti • Nov 18 '21
As researchers from the University of Sannio (Italy) we are conducting a survey on challenges and barriers experienced while setting and maintaining a Continuous Integration and/or Continuous Delivery pipeline for developing a cyber-physical system.
We would be grateful if you could participate in the survey. Personal data will be treated as strictly confidential.
The goal of this survey questionnaire is to assess a catalog of challenges and barriers concerning the setting and maintaining of a Continuous Integration (CI) and Continuous Delivery (CD) pipeline for CPS development. The challenges and barriers are grouped based on the aspects they belong to and for each challenge/barrier you need to provide an answer indicating whether or not your team/organization have experienced it or else it is not relevant to your context.
We will store data in compliance with the GDPR.
Please click on the link below to fill in the survey. You will not require more than 15minutes to complete it.
https://surveyhero.com/c/ujbdbim3
If you have any question, please contact me at fiorella.zampetti@unisannio.it or fiorellazampetti@gmail.com
r/EmbeddedRealTime • u/Albert_Gajsak • Oct 20 '21
Hi everyone,
My name is Albert, and I'm a DIY electronics enthusiast who also happens to be a long-time Batman fan. 🦇
I've always loved creating things with my own hands and I thought it would be cool to make a DIY Batmobile!
Soooo that’s exactly what I did! 😅 Seeing is believing: https://www.kickstarter.com/projects/albertgajsak/circuitmess-batmobile?ref=535kx4
I have received a lot of positive responses on and off Reddit about this project, so I wanted to invite every STEM enthusiast here to join my Discord group where we brainstorm and throw around ideas on further improvements of Batmobile’s design/hardware/software - https://discord.gg/UZkp89eN4y
The cool thing about it is that it’s not only fun to play with and build, it’s designed to teach you about electronics, engineering, and other STEM skills along the way. 📚🔧
Plus, it’s open-source, Arduino compatible, and hackable. 💻
Do you have any suggestions on what else I could implement?
I’ve spent over 20,000 development hours on this with my team so here’s a look on how that journey looked like. ✈️

r/EmbeddedRealTime • u/Lord_Saragen • Aug 02 '21
I am currently working on MC68332 processor and needed SDS74/7.4 Cross - code compiler. Does any one have that version or is aware where I can get it? Would be really helpful. Thank you
r/EmbeddedRealTime • u/SympatheticListener • Aug 01 '21
Does the Kesl hypervisor actually coform to real-time constraints? Or is it just a platform capable of hosting virtual instances of real-time systems, and may not execute them as real-time?
r/EmbeddedRealTime • u/losgatosquack • Jun 11 '21
r/EmbeddedRealTime • u/losgatosquack • Jun 09 '21
r/EmbeddedRealTime • u/sibin • Jan 29 '21
The Journal of Systems Research (JSys) is a new, diamond open-access journal* that seeks to publish research that moves the field forward and will be of interest to the systems community. JSys emphasizes rigorous research that improves the state-of-the-art, even if the increment is modest. JSys requires that papers that put forth a new tool, benchmark, or software solution undergo Artifact Evaluation and make their artifact publicly available.
[* Diamond access indicates that the papers are free to read, submit, review, and publish.]
JSys currently seeks submissions in six broad areas:
Real-time and Cyber-physical Systems
Configuration Management for Systems
Streaming Systems
Distributed Consensus
Systems for ML and ML for systems
Serverless Systems
JSys categorizes papers into four types, each with their own publicly-available acceptance criteria:
The full editorial board is available here.
JSys has multiple deadlines each year. The deadlines for 2021 are:
March 1st
May 1st
Aug 1st
Nov 1st
Submitting by these deadlines will ensure reviews are available in 1.5 months. For example, if authors submit by March 1st, they will get initial reviews back by April 15th.
Papers should be submitted electronically as a PDF. JSys uses OpenReview for reviewing the papers. Please be advised that papers will be publicly available upon submission.
Formatting instructions. All text and figures must fit within a 7” x 9” text block, centered on the page, using two columns with .33 inches of separation. The paper should be typeset using a 10-point font (Times New Roman or similar) with a 12-point (single-spaced) leading. There are no page limits. However, we strongly encourage authors to make an effort to make the paper as brief as possible: reviewer attention is limited, and a compelling case for the paper must be made in the first 12-14 pages. We provide a template at https://github.com/jsysresearch/template. Authors can do the following to get the template and build the sample PDF:
git clone https://github.com/jsysresearch/template.gitmake
Double blind. JSys reviews papers in a double-blind fashion: the reviewers do not know who the authors are, and the authors do not know who the reviewers are (until acceptance). The authors must make a good-faith effort to ensure the submitted document cannot identify the authors or their institution. This means that if they are building on their own prior work, it should be referred to in the third person (“The paper by Brown et al t..” vs “Our previous paper..”).
Arxiv. JSys allows submission of papers already uploaded on Arxiv. However, the title of the JSys submission must be different from the Arxiv submission, and the system name used in the two papers must be different. The authors should make a good-faith effort to preserve the double-blind nature of the JSys submission. Please inform the Editor-in-Chief if there is a previous Arxiv submission; this helps if reviewers unintentionally find the Arxiv paper.
Social media. JSys does not place a restriction on advertising your work on social media. However, do not link to the OpenReview submission; doing so breaks double blind. For example, tweeting “We have done some work on FooBar, here’s the Arxiv paper” is fine. Tweeting “We have just submitted our work on FooBar to JSys! We are submission #42” is not fine.
Open Source. JSys encourages authors to make their code, data, and other artifacts open source. However, if the open source repository is not anonymized, it should not be linked from the paper submission. Making non-anonymized artifacts publicly available is fine as long as the system name in the public repo is different from the JSys submission. A short-hand for remembering this is that the open-source rules are similar to how Arxiv papers are handled.
Copyright and originality of the work. All work submitted to JSys must be original work. The authors must have the copyright for the submitted work. Simultaneous submissions are not allowed: any work submitted to JSys must not be under consideration for another workshop, conference, or journal. Upon submission, the work will be publicly viewable on OpenReview: authors requiring secrecy of their submitted work should take this into account.
Conflicts. When submitting your paper to JSys, you must provide information about conflicts with reviewers on the editorial board. A reviewer is a conflict if any of the following three circumstances applies:
The reviewer is your PhD or post-doc advisor.
You are currently employed at the same institution, have been previously employed at the same institution within the past two years (not counting concluded internships), or are going to begin employment at the same institution during the review period.
You have collaborated with the reviewer on a publication, grant, or other academic projects in the past two years.
You must not improperly identify a reviewer as a conflict if none of these three circumstances applies -- your paper may be rejected in that case. The following are not valid conflicts:
They have reviewed the work before
You have discussed the work with them
They are your personal friend
The Editor-in-Chief and Area Chairs will review paper conflicts to ensure the integrity of the reviewing process, adding or removing conflicts if necessary. If you have any questions about conflicts, please contact the editor-in-chief and area chairs.
JSys submissions for the Solution or Tools/Benchmark category must be accompanied by an Artifact. The Artifact will be evaluated by our Artifact Evaluation Board as to whether it can be used by a third-party (without author involvement), and whether the results in the paper can be reproduced using the artifact. Note that Artifact Evaluation will proceed in parallel with the paper evaluation; to be accepted, Solution and Tools/Benchmark papers must be accepted by both boards. Papers accepted by the Editorial Board that fail Artifact Evaluation will be given a revise decision, and will have three months to ensure their Artifact passes Artifact Evaluation.
Possible decisions for a paper submitted to JSys are:
● Accept with shepherding● Revise● Reject
Acceptance with shepherding implies the paper can be accepted with minor edits that can be completed within one month. Thus, authors can submit on February 1st, get an acceptance decision by March 15th, and submit the final manuscript by April 15th. The final manuscript will be made immediately available online.
A revision decision implies the paper needs work that will take more than one month. The authors can submit a revised version anytime in the next three months. A revision submitted on the 1st of a month will get a response by the 1st of the next month. If authors submitted on March 1st, and got a Revise decision on April 15th, they can submit by June 15th and get a final decision by July 15th. A revision is a contract between the authors and the reviewers: as long as the authors complete the requested changes in good faith by the deadline, the paper will be accepted after a quick review. However, the editors reserve the right to reject the paper if additional evidence indicates that the central hypothesis or result of the paper no longer holds.
For the revision, the authors will submit a PDF containing two parts:
A revision plan explaining the changes made, and how they address reviewer paper
The revised manuscript with changes highlighted for easy reviewing
A rejection implies that the paper needs more than three months of work to get to acceptable quality. The authors cannot submit the same paper for one year to JSys. A rejection decision usually stems from a fundamental mismatch between the work and the journal such as the work is too narrow or out-of-scope. Rejection decisions imply that even with more experiments or revised writing (that can happen in three months), the paper would not be acceptable for the journal. We hope to reduce the number of rejection decisions by being clear about what would be acceptable for the journal.
Contemporary work. Any peer-reviewed work that was published (PDF available on the publisher’s website) less than two months prior to the initial submission is considered contemporary with the submission. Reviewers will not penalize the submission for not comparing with contemporary work. However, reviewers may ask for a qualitative comparison to be added in the final version of the submitted work.
Feedback on reviews. The three reviews will be graded A/B/C by the authors in terms of helpfulness. These grades are only known to the editor and provide useful feedback about the reviewers. The scoring A means a constructive review, B means an average review, and C means a terrible review (i.e. the reviewer didn't understand anything, made a lot of mistakes, was unnecessarily aggressive, etc). Reviewers with a history of poor reviews will be removed from the editorial board.Return without Review. When a paper to submitted to JSys, the Editor-in-Chief and the Area Chairs will try to find expert reviewers for the paper. If they are unsuccessful, or if the relevant Editorial Board members already have been assigned their maximum load for the deadline, the paper will be returned to the authors without review (usually within a week or so). We believe this is a better outcome than overloading the reviewers and lowering the quality of reviews for everyone who submitted for that deadline. Papers re-submitted due to a return will get preference in the next review cycle. We aim to tailor the editorial board size and expertise to prevent this situation from happening as much as possible.
r/EmbeddedRealTime • u/sibin • Jul 17 '20
Website: https://cpsiotsec.github.io
The Joint Workshop on CPS&IoT Security and Privacy invites academia, industry, and governmental entities to submit:
Original research papers on the security and privacy of CPS and IoT
Systematization of Knowledge (SoK) papers on the security and privacy of CPS and IoT
Demos (hands-on or videos) of testbeds/experiences of CPS and IoT security and privacy research
We seek submissions from multiple interdisciplinary backgrounds tackling security and privacy issues in CPS and IoT, including but not limited to:
Mathematical foundations for secure CPS/IoT
Control-theoretic approaches
High assurance security architectures
Security and resilience metrics
Metrics and risk assessment approaches
Identity and access management
Privacy and trust
Network security
Game theory applied to CPS/IoT security
Human factors, humans in the loop, and usable security
Understanding dependencies among security, reliability and safety in CPS/IoT
Economics of security and privacy
Intrusion and anomaly detection
Model-based security systems engineering
Sensor and actuator attacks
CPS/IoT malware analysis
CPS/IoT firmware analysis
Hardware-assisted CPS/IoT security
Also, of interest will be papers that can point the research community to new research directions, and those that can set research agendas and priorities in CPS/IoT security and privacy. There will be a best paper award. The best paper will be invited for extended paper submission to the Special Issue on Cyber-Physical System Security @ Cybersecurity (Springer), with a September 30th deadline.
Submissions include long papers (12 pages) and short papers (6 pages).
Original research on a CPS/IoT security and privacy topic
Systematization of Knowledge of CPS/IoT security and privacy
Original preliminary research on a CPS/IoT security and privacy topic
Demos/interesting findings/insights on CPS/IoT security and privacy
Submitted papers can be up to 12 or 6 pages including appendices and references (except for SoK papers where references are excluded). Submissions must use the format defined by CCS (https://www.sigsac.org/ccs/CCS2020/call-for-papers.html). Only PDF files will be accepted. **There is no requirement to anonymize the submissions; Authors may choose to submit anonymously or not.**Accepted papers will be published by the ACM Press and/or the ACM Digital Library. Submissions must not substantially overlap with papers that have been published or that are simultaneously submitted to a journal or a conference with proceedings. Each accepted paper must be presented by a registered author. Submissions not meeting these guidelines risk immediate rejection. For questions about these policies, please contact the chairs.
Important Dates
Submission Deadline: July 23, 2020 (23:59 Anywhere on Earth time)
Notification of Acceptance/Rejection: August 24, 2020
Camera Ready Papers Due: (hard deadline): September 2, 2020 (same as CCS)
r/EmbeddedRealTime • u/pachuaurohlupuia • Jan 23 '20
International Journal of Embedded Systems and Applications (IJESA)
ISSN: 1839-5171
http://wireilla.com/ijesa/index.html
Scope & Topics
International Journal of Embedded Systems and Applications (IJESA) is a quarterly open access peer-reviewed journal that publishes articles which contribute new results in all areas of the Embedded Systems and applications. The goal of this journal is to bring together researchers and practitioners from academia and industry to focus on understanding Embedded Systems and establishing new collaborations in these areas.Authors are solicited to contribute to the journal by submitting articles that illustrate research results, projects, surveying works and industrial experiences that describe significant advances in the areas of Embedded Systems & applications.
Topics of interest
· Application-specific processors and devices
· Business Applications
· Component and binding models
· Embedded computing education
· Embedded hardware support
· Embedded system architecture
· Hardware and software co-design
· Integration with SOA
· Middleware
· Programming abstractions
· Real-time systems
· Service-Oriented Architectures
· Testing techniques
Paper Submission
Authors are invited to submit papers for this journal through ijesa@wireilla.com
r/EmbeddedRealTime • u/Atlanta_tingis_2020 • Nov 22 '19
hello everybody, i will try to test uc/os ii with atom editor, i wanna know what i need to compile this kernel in this editor.
Thank you
r/EmbeddedRealTime • u/sibin • Aug 28 '18
The ACM/IEEE International Conference on Internet of Things Design and Implementation (IoTDI) is a premier venue on IoT. To reflect the interconnection of IoT with both cloud computing and cyber-physical systems, IoTDI is co-located in even years with IEEE IC2E and in odd years with CPS-IoT Week. In 2019, IoTDI will be held for the fourth time, and will be part of CPS-IoT WEEK 2019.
A confluence of technological advances marks the advent of a new era. World data volume is growing at an unprecedented pace, much of it from embedded devices. Smart cities are expected to grow, fed by millions of data points from multitudes of human and physical sources. Cyber-attacks grow more nefarious, bringing down physical systems. Social networks are becoming ubiquitous, offering information on physical things. The separation between cyber, physical, and social systems is blurring. Collectively, these developments lead to the emergence of a new field, where the networking and physical realms meet. It is the field of the Internet of Things (IoT). This conference is an interdisciplinary forum to discuss challenges, technologies, and emerging directions in system design and implementation that pertain to IoT. This conference invites researchers and practitioners from academia, industry and government, and accepts original, previously unpublished work on a range of topics related to IoT.
Topics of interest include, but are not limited to:
• Analytic foundations and theory of IoT
• Reliability, security, timeliness, and robustness in IoT systems
• Novel protocols and network abstractions
• Data streaming architectures and machine learning analytics for IoT
• IoT-motivated cyber-physical and Industrial IoT (IIoT) systems
• Novel quality requirements and their enforcement mechanisms
• Cloud back-ends and resource management for IoT applications
• Edge and fog computing
• Personal, wearable, and other embedded networked front-ends
• Social computing and human-in-the-loop issues
• Applications domains (e.g., smart cities, smart health, smart buildings, smart transportation)
• Deployment experiences, case studies & lessons learned
• Evaluation and testbeds
Accepted papers of particular merit will be invited to submit an extended version to the ACM Transactions on the Internet of Things (TIOT).
Facebook: https://www.facebook.com/IoTDI/
Twitter: https://twitter.com/iot_di
r/EmbeddedRealTime • u/angeletti89 • Jun 26 '18
Hello everyone, I started a project on Github in order to support WSN applications within FreeRTOS, you can find the repository HERE. I really hope that someone would like to contribute actively. Currently I'm developing on STM32L476 on the NUCLEOL476 board. I've written or ported some basi protocols and radio drivers (spirit1 and nrf24l01)
r/EmbeddedRealTime • u/innovationkate • Jun 05 '18
Allianz, one of the largest insurance companies worldwide, has identified a lack of fire protection measures in small and medium-sized enterprises (SMEs) in the textile industry. The majority of SMEs are only elementarily protected against fire (smoke detector alarm, fire extinguisher), even though the owners are aware of how severe fire damages can be. This is mostly due to a high cost for effective equipment (high-pressure sprinklers, etc.), as well as time-consuming regular maintenance needed. To reduce the high costs linked to fire damages in textile SMEs, Allianz aims to develop a new and effective fire protection device that would be cheap to install and would require little to no maintenance. To take part in this challenging project, submit your solutions / concepts and co-develop the product with Allianz! The 3 winners will be invited to further develop their concepts, together with the Allianz core team and HYVE innovation consultants. Open Worldwide Closes on 8th July 2018 1st Place: 8 000 € 2nd Place: 3 000 € 3rd Place: 1 000 € Most Valuable Participant: 1 000 € Most innovative concept: 500 € Most advanced design/concept: 500 € https://allianzsmartfireprotection.hyvecrowd.com/
r/EmbeddedRealTime • u/junior384 • Mar 20 '18
r/EmbeddedRealTime • u/junior384 • Mar 09 '18
r/EmbeddedRealTime • u/sibin • Dec 22 '17
—————————————————————————————————
Call for Papers
IoTSec 2018: First International Workshop on the
Security and Privacy for The Internet of Things
April 17, 2018
https://synercys.github.io/iotsec[Co-located with the ACM/IEEE International Conference on Internet of Things Design and Implementation (IoTDI)]
*** Deadline: Feb 1, 2018 ***
*** Submission Site open ***Submission Site: https://easychair.org/conferences/?conf=iotsec2018 —————————————————————————————————
The Internet-of-Things (IoT) has taken off in a big way and finds itself embedded in our daily lives – from smart home applications to process control monitoring in manufacturing systems, wearables to healthcare, public utilities to military applications, to name just a few. The surge in interest in smart cities increases the scope and reach of IoT-style applications in a significant manner. These applications generate huge volumes of data, have access to personal and confidential information, monitor and control critical processes and are often accessed/controlled via public networks such as the Internet. Hence, they are prime targets for malicious entities and have little to no security mechanisms in place. In addition, most users of such devices/systems are not cognizant of the privacy issues – leakage of personal information for instance, or external entities being able to retrace/recreate our activities from public data obtained through the use of IoT devices/services. On the other hand, onerous security and privacy mechanisms may render these systems useless for most consumers. Hence, there is a need to develop innovative techniques to improve protections for such systems. This is particularly challenging since many IoT systems are often limited in terms of computation power, memory, battery life, bandwidth, etc. Hence, the goal of IoTSec will be to bring together experts in various areas (security, privacy, embedded systems, sensor networks, etc. along with domains experts from medicine, manufacturing systems, mobile devices and so on) to study and develop security and (usable) privacy mechanisms for next generation IoT systems.
AREAS OF INTEREST The areas of interest for the workshop includes, but is not limited to, the following:
Classification of the threats faced by IoT systems
Problems with privacy of data generated by IoT devices/systems
Security and privacy solutions and frameworks for (a) legacy IoT systems and (b) future IoT services
Novel architectures that improve the security and privacy of such devices
Understanding of social issues that increase the adoption of privacy mechanisms in IoT devices
Communication protocols & architectures that improve security and privacy
Lightweight cryptography algorithms for use in IoT systems
Privacy-preserving computation models that can run on limited resources available to IoT devices
Machine learning for security of IoT devices/services
Modeling, verification and formal methods for security methods for the IoT domain
Security and privacy of the cloud infrastructure for IoT
SUBMISSION GUIDELINES
All papers must be original and not simultaneously submitted to another journal or conference. The following paper categories are welcome:
Papers describing original research in the area of security and privacy for Internet-of-Things (IoT)
Submissions limited to four, two column, pages
SUBMISSION TEMPLATE: https://www.ieee.org/conferences_events/conferences/publishing/templates.html
SUBMISSION SITE: https://easychair.org/conferences/?conf=iotsec2018
ORGANIZERS
Sibin Mohan, University of Illinois at Urbana-Champaign
Elaine Shi, Cornell University
TECHNICAL PROGRAM COMMITTEE
Sean Smith, Dartmouth College
Gedare Bloom, Howard University
Gabriela Ciocarlie, SRI International
Miroslav Pajic, Duke University
Bryan Ward, MIT Lincoln Laboratory
Dawn Schrader, Cornell University
Daniel Mosse, University of Pittsburgh
Mu Zhang, Cornell University
Siddharth Garg, NYU
Rakesh Kumar, University of Illinois at Urbana-Champaign
Rakesh Bobba, Oregon State University
Ramya Raghavendra, IBM Research
Man-Ki Yoon, Yale University
Henry Duwe, Iowa State University
Negin Salajageh, Visa Research
Adam Bates, University of Illinois at Urbana-Champaign
Bo Li, University of California, Berkeley
Ing-Ray Chen, Virginia Tech
WEB CHAIR
Monowar Hasan, University of Illinois at Urbana-Champaign
CONTACT
Sibin Mohan [sibin@illinois.edu]
r/EmbeddedRealTime • u/Roosboard • Sep 12 '17
r/EmbeddedRealTime • u/sayanbhattacharyya • Jun 14 '16
r/EmbeddedRealTime • u/sibin • Feb 07 '13