RIt's cool, was checking around, and I saw a lot of tags so I decided to look it up
TNice, what's your technical background? What do you do for work/school?
AHi @techielew
I am working on a smart cat collar project based on Samd21
I am working on a smart cat collar project based on Samd21
T- Please tell me you have a picture of that
- Can you post said picture in #projects-and-self-promotion?
- Lol
ASorry I can’t share the picture
AI have cats. What is the goal of the product?
ATo track and train them for not going into specific zones
Tlike a shock collar?
ANo No
No shocking at all
No shocking at all
Thaha, okay. so what are the components of the system?
Tbesides SAMD21
AYo I need this. I have cats that need to stop walking into my room. Don't need their cat hair in my bed.
THey @abhishek awasthi, I've been doing some research on the difference between Yocto and buildroot. Any pointers?
TI'm trying to evaluate when makes sense to use which
A... yocto is a bit more complicated when compared to builroot .. .. so like if one would start their journey ...i would suggest to start from buildroot environment ... understanding the basics of build process ... majour things are menuconfig there so can start fast and get their hands dirty ... where yocto would require a good learning curve in comparison ... at the end if you have a specific application and have selected the soc for it ..then check upon the vendor build documentation to understand the depth of details provided ...sometime they will tell you the preferred build environment ...and following that would be a good option... if you consider the build time ... buildroot might give you quicker results ... but it may start taking time upon further devlopements ...where as yocto would take a good amounts of time for initial builds but then for further build the build time reduces significantly ...
for the beginning explore buildroot ... once you feel comfortable with the environment ..you may shift to yocto ...
for the beginning explore buildroot ... once you feel comfortable with the environment ..you may shift to yocto ...
TIs it just that buildroot is smaller? More compact, meaning shorter/less time to compile?
Aits more specific to the board .. so lets say you have build for a board using buildroot and not you want to build the same for another board .. it would again take all the resources where as in a yocto project its more portable .. you can switch easily
Aand yes buildroot is way smaller in comparison to yocto .. yocto can go around 50 gigs easily ..
THi,
This is Tahenan,
A Graduate Student in US trying jobs in Firmware/Embedded Development
This is Tahenan,
A Graduate Student in US trying jobs in Firmware/Embedded Development
TWhat's up, @tahenan. Welcome! Check out the #jobs channel and feel free to ping @Marcweb. Do you have any specific industries or roles you're looking to fill? Leave your deets here: jobsLooking for Work? Comment Here...
Discord
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
TThanks, I'm assuming you've implemented both in commercial projects, correct?
The general sentiment I've been getting from those I talk to is buildroot is common for more resource-constrained consumer electronics-type devices and Yocto is for bigger, more feature rich platforms.
Would be interested to hear from you or anyone else who has experience with either
The general sentiment I've been getting from those I talk to is buildroot is common for more resource-constrained consumer electronics-type devices and Yocto is for bigger, more feature rich platforms.
Would be interested to hear from you or anyone else who has experience with either
Aso apparently i havent got the commercial projects upon buildroot or yocto .. i have done one where i had build packages from scratch and complie then to make embedded linux ..busybox based environment ...
A... also like one can think buildroot and yocto like how we have kicad and altium ... i mean both of them does the job ... one is just a bit more on the professional side ...and more resources ...
Ai mean we all tinker around and learn ...
AHi
PHi welcome
HHello Everyone, I'm a hardware engineer based in Dubai, just discovered this server from LinkedIn post.
AThank you @Phoenix
I have done internship at some startup which is based in Bengaluru, Karnataka, India. Interested in Embedded system development (From requirement gathering till product delivery).
Currently looking for an opportunity to learn and grow.
I have done internship at some startup which is based in Bengaluru, Karnataka, India. Interested in Embedded system development (From requirement gathering till product delivery).
Currently looking for an opportunity to learn and grow.
TWhat's up @hemalchevli. Welcome. What type of projects are you working on?
HCurrently working on Jetson carrier board at work and some ESP32 based projects at home
Pnice, is your internship related to iot ? what's the startup about
TWell if that isn't the range of hardware ahha
GIve worked with basys 3 artix 7 dev board and mini lattice board......just got my self started with fpga's......sure would love to share my work here and will join the office hours........thanks for the invite 
Gcurrently im working on a foc based bldc controller....for now ive used a stm32 but in future i would love seeing it having a fpga
GHappy to meet you @Navadeep
NHere you go @Padmalaya Rawal! I see dots getting connected hahaa
NCheers @gKarthikSai.
JGreat @gKarthikSai, you can always share your projects and any challenge you face in the process
S
UHow do you decide whether to use synchronous or asynchronous finite-state machines in the context of FPGA? Is it true that hybrid approaches that combine synchronous and asynchronous are possible? @Navadeep and other FPGA users. Any thoughts or input?
T@gKarthikSai
GAbout the hybrid approach I'm not sure
GWith synchronous FSM you have to be careful of time delay for the clock speed.....in asynchronous there is no clock there are no boundaries or restrictions
NI suppose by synchronous youre referring to syncing with the clock signal. If so, it's all about the clock.
- Do you want the event to happen at definite clock cycle intervals? - go woty synchronous
- If the requirement is to have an external input form the user, an event occurrence in the process itself like or a flag or interrupt and control the state machine transition based on these, then you have asynchronous.
NIf time sensitive events, asynchronous can be faster as there is no need to wait for the next clock edge to come. It should be feasible to implement hybrid. I am curious now - will try it out. One way is to have synchronous FSM running along with async to override it. I am quite fuzzy about time delay and how to healthily override.
NSomething exactly like MCU running a task and interrupt getting raised and serviced.
UHi @gKarthikSai Thank you so much!
UI have very little experience so far and that too with interfacing memory controllers (RAM, Flash) with FPGA. So thinking in that context. I'd be happy to explore more from you on the hybrid approach
AHybrid approaches I haven't worked on majorly synchronous fpga time critical
UEven I'm curious from the time, I got to know from conversations in the team. I then decided to confirm with our community!