HN user

BertoldVdb

60 karma
Posts0
Comments38
View on HN
No posts found.

Just put normal test pads next to the tag connect, a bit more spaced out. A bed of nails in the production line connects to that, the tag connect can be used for bench development.

Laser decapping will destroy the die, except if you have a rare package that does not mix glass in the epoxy.

You could still compare the internal structure of the package and bonding, but the die itself is mostly destroyed.

Usually yes, but it is not an EU-wide system. Contact your spectrum regulator and ask for what options are available for private 5G[1]. You can likely get a bit of spectrum in the 1.8GHz guard band, around 2.3GHz, or somewhere between 3.4-5GHz. Price is from free to thousands of euros, depending on the country, transmit power and whether you are using outdoor cells. A private mmWave cell will almost everywhere need to be under an experimental/R&D license (we don't have public mmWave networks).

If you can choose, it's best to take a TDD license, as the duplexer required for FDD base station operation is a relatively expensive device when operating on an uncommon band.

1) Private 4G wasn't really a big thing in EU, but in most countries the license you get is technology neutral and can be used with a 4G base station as well.

PS: Connecting the private LTE to the public telephone network with a publicly reachable number requires a public telecom operator permit in some countries. You will also need to pay for the block of phone numbers. Roaming to the public cellular network requires many extra things which are not cheap or easy to obtain. And of course you need to have a roaming agreement with the other operator.

I worked on this long ago, the main problem with the poor sound quality is that the self-mixing process is non-linear, a good approximation is squaring the output signal.

To improve the quality you can pre-distort the output signal. Taking the square root works quite well, but expands the bandwidth significantly (infinitely, in theory). There is a lot of literature on pre-distortion with bandwidth constraints for telecom power amplifier linearisation. You will also need a linear amplifier to power the array.

The ultrasonic transducers used in this post are very narrowband, having a resonance peak of merely a few 100Hz. You can reduce the Q factor with resistive loading but the output power significantly drops. It seemed these transducers quickly start making an audible whining noise when used for continuous transmission at higher powers. I don't know what caused that, apart from this effect they seemed to hold up for essentially infinite duration.

Using a larger wideband ultrasonic transducer instead of an array of small narrowband transducers again increases the sound quality a lot. We did not find a commercial supplier of such transducer for a reasonable cost, but made some improvised custom electrostatic ones with conductive foil. There is a lot of literature on how to construct ultrasonic transducers but this is not my field.

You will not be able to play bass notes due to physics, the power required would be insane.

That functionality is absolutely non-trivial. There are a few WiFi cores (digital and RF) you can license but they are expensive and the analog part uses a lot of die area. If you look up die shots from the ESP chips, you see that the radio is more than half of the die.

Espressif apparently has their own WiFi implementation, which makes sense as they are a major vendor of very cheap tablet and cell phone WiFi radios. This is likely why they can offer that feature so cheaply.

Bluetooth Low Energy is way simpler BTW.

It's very unlikely IMHO. Both the RISC-V and the M33 are very tiny in die area, compared to for example the 512kB RAM, or even compared to a few bond-pads.

Making a single core with two instruction decoders but a shared register file, caches, prediction logic and ALU would make sense for a very high-end application processor type core, but not for these small devices. You would also need an instruction set license from ARM for that, vs just licensing the M33 netlist.

If you can tolerate some level of false positives you can turn the CRL into a bloom filter and save quite a bit of storage.

While you could make an OpenFlow client that uses this switch chip as the data-plane, it might not be the best as most of the features you would use OpenFlow for would not be able to use the relatively limited hardware fast-path.

There is not much power needed to receive DisplayPort over USB (assuming you already can receive displayport signals or just route them to an external monitor).

You just need to implement an USB billboard device (optional to make it work, but required by the spec IIRC) and signal the correct alternate function. Then DisplayPort signalling will be present on the USB-C plug. Then just connect the right AUX wires to the DisplayPort connector.

I was able to use the rfkill command on a Dell and a Thinkpad with the hardware switch turned off. However I don't know how that was implemented internally, maybe the switch was not connected directly to the mini-pcie slot. I don't have these laptops anymore so I can't check it.

I made the video on the webcams, these are quite modern ones. Nearly all of them have special UVC commands that allow reading and writing the internal CPUs memory (a lot are 8051 based). You can find the register that controls the led GPIO and control it freely. Only on one of them I did not find a way to modify the led behavior without modifying the firmware to add an extra command.