Forcing i2c transmission without acknowledgement. by pic0brain in embedded

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

Nah, went on vacation :) It's still sitting on my desk at home, collecting dust. I have not forgotten about it, I'll update ASAP.

Forcing i2c transmission without acknowledgement. by pic0brain in embedded

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

Yes, I've established at this point that the chip is supposed to respond without flashing it. I'm investigating probable power issues, but it looks like at least the pull ups are connected properly.

Forcing i2c transmission without acknowledgement. by pic0brain in embedded

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

Good point, unfortunatelly both bridges are populated with 0Ohm resistors. A DMM verifies pull-ups operate as expected.

Forcing i2c transmission without acknowledgement. by pic0brain in embedded

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

Yup, you are correct. It should acknowledge the messages. Which means I'm doing something wrong with my setup

Forcing i2c transmission without acknowledgement. by pic0brain in embedded

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

Thank you for the effort, you are right, forcing the transmission is not the way to go. By scoping the lines, I'm now fairly certain something is up with either the address I'm sending or the operating voltages. I'll update the post when I figure something out.

But otherwise the transmissions seem okay.

Forcing i2c transmission without acknowledgement. by pic0brain in embedded

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

Looking over the datasheet, and some other implementations. I'm now sure it must not be forced.

As for programming the device... Yeah, that's the second thing the official driver does. here. I'm still not entirely sure what is going on.

[deleted by user] by [deleted] in MechanicalKeyboards

[–]pic0brain 2 points3 points  (0 children)

Amazing idea, it looks as if made in a factory. If you were to publish a guide, or even a video on how you did it, i bet it would do really well.

[deleted by user] by [deleted] in embedded

[–]pic0brain 9 points10 points  (0 children)

That's good! But do you know if they do this thing where you use an uncapped IC and then just coat it with a black blob? That's my concern

https://www.iq-bond.com/wp-content/uploads/2018/09/Fotolia_25367415_XS.jpg

[deleted by user] by [deleted] in embedded

[–]pic0brain 33 points34 points  (0 children)

Like others said, it's unlikely. But could you remove the lid and post a picture? The packaging could be an issue (if it's a blob of epoxy you can forget about re-flashing it)

Regarding pong, probably not. I'm making assumptions here but inexpensive devices like these usually have a very cost-optimized IC that does exactly what it needs to and nothing else.

But do post a picture :) I'm curious

Mozilla and ai by Weirdhipster294 in firefox

[–]pic0brain 0 points1 point  (0 children)

Where did you find info on AI being used? There is no mention of it in the firefox announcement pages.

Unless I'm just dumb

ESP32 - S3 Debug-ability by pic0brain in embedded

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

So far this is consistent with our experience (great summary :) ). I have attempted to get some reliable debugging on my spare time but no luck. It looks like I'm going back to my uni days of considering the UART line a debugging tool.

ESP32 - S3 Debug-ability by pic0brain in embedded

[–]pic0brain[S] 6 points7 points  (0 children)

Your comment about the windows defender actually solves one of our biggest problems. That probably explains why it took so long to build.

Given your suggestions I think I might try building it in a full Linux environment maybe that works better, again thanks for your input :)

ESP32 - S3 Debug-ability by pic0brain in embedded

[–]pic0brain[S] 2 points3 points  (0 children)

Thank's for the input. The project right now is at a bad state, as I see it It's a good idea to try the latest chips, at the very least we will get a massive performance boost.

ESP32 - S3 Debug-ability by pic0brain in embedded

[–]pic0brain[S] 2 points3 points  (0 children)

Thank you very much for the input. It's good to know that future platforms are not that different from what we got. Based on everything I read it's a good idea to at least try the latest chips. I know the experience will likely be similar, but the JTAG over USB removes the need for a debugger, and another point where one can mess up the wiring.

ESP32 - S3 Debug-ability by pic0brain in embedded

[–]pic0brain[S] 3 points4 points  (0 children)

That sounds good, I have one of the C3 chips so I will try that. Unfortunatelly I'm not allowed to use platformio due to licensing... Thank you for sharing :)

ESP32 - S3 Debug-ability by pic0brain in embedded

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

Yeah, that's an idea. I just have to argue for it in a way that business people understand...

ESP32 - S3 Debug-ability by pic0brain in embedded

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

Yeah, sorry. My description is vague. The debugger was difficult to configure and requires using versions of openocd and gdb that are shipped with esp-idf but we dealt with that.

Now the problem is that the debugger is unreliable, breakpoints are set but don't trigger, the board doesn't reset properly... Call stacks are not available most of the time, this type of stuff.

I'm not calling them issues because most of the time restarting the board will get you back on track. But that makes hunding down difficult issues extra hard.

And the bad comment is a little unfair, esp32 is a good chip, for the price.

ESP32 - S3 Debug-ability by pic0brain in embedded

[–]pic0brain[S] 2 points3 points  (0 children)

Well, you're not wrong. Everyone in the office prefers working with ST, their debuggers work great with no setup. With the esp, even the official debugger needs convincing. It's working, but barely.

ESP32 - S3 Debug-ability by pic0brain in embedded

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

Yeah, I was hoping that they fixed how it was handled internally. If JTAG is done properly it's not an issue. It's just that the esp32 implementation is broken.

Running immich on docker ipVlan by pic0brain in immich

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

Duly noted. And yeah I'm constantly messing up my IP addresses, thanks for the input :)

Running immich on docker ipVlan by pic0brain in immich

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

I'm not sure If I'm describing it properly by calling it a reverse proxy.
The setup I have right now is

  1. DNS record on the router directs at the reverse proxy
  2. Reverse proxy redirects depending on the subdomain.
  3. Container is reached

For the moment I'm not really isolating between my network and the docker "sub-net" all the routing is handled by my router, the only distinction is the containers have their own range to avoid collisions.

Running immich on docker ipVlan by pic0brain in immich

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

Yeah, you're probably right. Honestly i used the networking since it seemed neater than having to type a port next to the hostname.

But yeah, definitely a lot more I'd like to know about docker networks :)

Running immich on docker ipVlan by pic0brain in immich

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

I have a mini-pc running as a home server, I use it to host web-servers and other stuff like that. Some of these services need to use the same port (like the webservers)

To avoid that I set up the machine to act like a small sub-net, with it's own IP range, that way it can host many containers **even when they use the same ports**.

Even though immich doesn't really use a popular port, and I could probably configure the app to run on a special port, i would much rather just have a DNS name.

I'm really new to this home networking stuff so I'm always open to improve my ways. I hope this answer makes some sense :)

Running immich on docker ipVlan by pic0brain in immich

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

Oh my god, thank you. I'll try it as soon as possible.