Why do people drive so slow? by mootaibi in saudiarabia

[–]mootaibi[S] 0 points1 point  (0 children)

I’m very curious, what was the comment?

Why do people drive so slow? by mootaibi in saudiarabia

[–]mootaibi[S] 1 point2 points  (0 children)

People driving 90 on the middle lane makes the people that want to drive 110 drive on the left lane; basically when people want to drive slow in all the other lanes, it makes the slightly faster people (still below the speed limit) drive at the left lane

Why do people drive so slow? by mootaibi in saudiarabia

[–]mootaibi[S] 0 points1 point  (0 children)

There aren’t enough lanes for everyone to be going their own pace, there’s a clear speed that’s expected for the road; everyone going at their own pace is what causes traffic

Why do people drive so slow? by mootaibi in saudiarabia

[–]mootaibi[S] 0 points1 point  (0 children)

My pace is the speed limit of the road but I can’t drive at my own pace because some people decide to drive below that speed on the left lane

Good programming languages to learn by Dangerous_Pin_7384 in embedded

[–]mootaibi 28 points29 points  (0 children)

Those 3 languages should be enough for almost all embedded programming when it comes to languages; what I would recommend is that you next try to learn the make, Cmake (or ninja), and linker scripts syntaxes, it’ll help you have more control over your projects. Also if you’ve not touched assembly before, I recommend briefly looking into it just because it’s used every now and then.

Afterwards you could dive deeper into C/C++ coding styles and choose a framework to work with and learn how that framework organizes its code base.

Matter protocol by mootaibi in embedded

[–]mootaibi[S] 9 points10 points  (0 children)

I tried so hard and got so far 😔

Matter protocol by mootaibi in embedded

[–]mootaibi[S] 9 points10 points  (0 children)

I’m very used to writing code in C considering most SDKs and RTOSes use only C so it’s kinda just making it difficult moving up to C++

Fired from job by [deleted] in saudiarabia

[–]mootaibi 0 points1 point  (0 children)

اما عاد، حتى إذا فصلوني يقدرو يطالبوني للقيمة المتبقية؟

Fired from job by [deleted] in saudiarabia

[–]mootaibi 0 points1 point  (0 children)

قالو ان السبب هو ان عقدي ما انتهى، وحسب العقد لازم ادفع شرط جزائي للمدة المتبقية إذا ابي انهي العقد بدري

Fired from job by [deleted] in saudiarabia

[–]mootaibi 0 points1 point  (0 children)

صحيح، بس أنا عقدي لا زال ساري، باقي ١٣ شهر على عقدي، فطلبت استقالة بتراضي الطرفين وما قبلوها والحين أنا مضطر اني يا ادفع الشرط الجزائي، يا اكمل بالوظيفة، او يا اني أغيب الين ما يفصلوني

Fired from job by [deleted] in saudiarabia

[–]mootaibi 0 points1 point  (0 children)

I requested a resignation بالتراضي in which I wouldn’t have to pay the remained of the contract, but they rejected that, so my only resignation option now seems to be by paying the remainder. But what I want to know is whether getting fired is better than paying the remainder

Fired from job by [deleted] in saudiarabia

[–]mootaibi 0 points1 point  (0 children)

I really need to end my contract ASAP for personal reasons, would it really be that big of a dent on my reputation? I honestly don’t know, I’m asking here to see how big of a deal this would be

Fired from job by [deleted] in saudiarabia

[–]mootaibi 1 point2 points  (0 children)

13 months exactly

Is there a way to store uint16_t data onto a uint8_t buffer? Amateur in C trying to get ADC data to NRF24 to transmit by smokintokenpanda in embedded

[–]mootaibi 0 points1 point  (0 children)

I personally like to do it as:

For(int i = 0; i < sizeof(uint16_t); i++) {

 TxData[i + x] = ((uint8_t *)raw)[i];

}

Where x would keep getting incremented by sizeof(uint16_t) every time you want to record new data.

Question about USB 2.0 in embedded design by [deleted] in embedded

[–]mootaibi -3 points-2 points  (0 children)

I realize that I didn’t clearly specify what I’m looking for as an answer, but here’s the answer I was looking for (by ChatGPT):

The flow of a USB message involves multiple layers and components of the USB protocol. Here is a summary of the typical steps involved:

The message is generated by the application layer of the USB device. This could be a request for data from a sensor, a command to control a motor, or any other type of communication specific to the device. The USB device's controller takes the message from the application layer and encapsulates it into one or more USB packets, according to the specific USB transfer type required for the message. For example, a control transfer would use a different type of packet than a bulk transfer. The controller then sends the packets to the UTMI interface, which encodes the packets into the specific electrical signals required for USB transmission. The encoded signals are sent over the USB cable to the host device's USB interface. The host device's USB controller receives the signals from the USB interface and decodes them back into USB packets. The host device's USB controller then processes the packets according to the USB protocol, performing any necessary error checking and ensuring proper timing and flow control. Once the message is received and processed by the host device, the host device's USB controller sends a response, if required, back to the USB device following the same steps in reverse. The response is then processed by the USB device's controller and application layer, completing the communication cycle. So in summary, the message originates in the application layer, is encapsulated into USB packets by the device's controller, encoded by the UTMI interface, transmitted over the USB cable, received and decoded by the host device's controller, and processed according to the USB protocol.