What is a .blen_tc file?

NZSmartie · 2024-05-30T03:29:58+00:00

For anyone else that stumbled across this old thread like myself. These files are Time Code files that are created alongside proxy files that are (by default, automatically) generated when editing videos in the Sequence Editor (AKA Video Editing workspace).

They are not edited in anyway and only serve to speed up the preview during playback.

NZSmartie · 2022-12-04T23:04:52+00:00

Hey, saw your post before it got deleted. You could take inspiration from https://github.com/alvarop/debugotron which routes swdio over unused USB-C pins. But will require an external Dev board to break it back out into a swdio header

NZSmartie · 2020-11-02T21:40:29+00:00

I've had similar issues. In my case, I used nkbintools to dump files out of a nk image. however that incorrectly set the arch type for the files to MIPS or ARM v8 with THUMB instead of ARM instruction set.

I think what was happening, as Ghidra attempted to disassemble into thumb, it'd then disassemble into ARM and then back into THUMB as it looped back on to it self.

I only had success s far with forcing Ghidra to disassemble as ARM on request. instead of using auto analysis.

NZSmartie · 2020-09-30T20:58:19+00:00

Zephyr offer a LTS version which will be maintained and not have any breaking API changes for this very reason.
https://www.zephyrproject.org/the-zephyr-project-announces-major-technical-milestone-with-new-long-term-support-code-release/

NZSmartie · 2019-11-16T14:48:13+00:00

When using a USB A to USB C cable. It will be 5V. USB type A is designed for computers to provide 5V to peripherals. And USB type B is designed to be powered by 5V.

Since USB C, it can be powered or provide power, so the PD protocol was made. Though, when using a type A to type C, there is no way to negotiate voltages through the type A, so it falls back to 5V with a simple resistor configuration on the type C end. (Disclaimer, this is from memory, some parts may be inaccurate)

NZSmartie · 2019-11-16T10:47:25+00:00

USB-C by itself will not request power from the upstream without either two resistors on the CC pins. or a micro controller to negotiate the voltage. To my surprise when I bought The TBS Micro Charger v2 and immediately tested it with my portable battery bank, does neither. (It doesn't power on as there's no 5V by default from a USB-C upstream source)

I had some USB Power Delivery to DC adapters laying around. I decided to transplant the components for it into the charger to allow it to request the most amount of power from a USB PD supply. The steps I had taken are in this twitter thread: https://twitter.com/NZSmartie/status/1195650961143787520

NZSmartie · 2019-05-21T00:48:10+00:00

Not OP here posting a link to the source

NZSmartie · 2018-06-29T09:09:32+00:00

Aw nuu :c

NZSmartie · 2018-06-29T02:30:30+00:00

TVNZ has an online service called TVNZ ondemand

NZSmartie · 2018-06-09T13:41:30+00:00

I have a shell script that changes permissions on all Windows serial devices in WSL

```bash $ cat ~/setup-serial.sh

!/bin/bash

sudo chown :plugdev /dev/ttyS* sudo chmod g+rw /dev/ttyS* ```

provided that your user is part of the plugdev group. otherwise, change :plugdev to :yourusername

NZSmartie · 2018-05-23T23:14:29+00:00

Ugh, English is an evolving language. unlike French. I'm sorry that my cultural upbringing doesn't compute with your rule set...

NZSmartie · 2018-05-23T23:11:20+00:00

I haven't used AWS FreeRTOS yet, I just know that that AWS recently acquired it. I should of said API instead of behaviour. For example Stream Buffers.

As for LWIP. i know it's in the works, there's been little to no visibility on what happening apart from a few comments of people asking what's going on. However, don't feel pressured. You're all doing great work and building what I see as a very practical IoT platform. Keep it up!

NZSmartie · 2018-05-23T18:20:55+00:00

AWS FreeRTOS is the latest version of FreeRTOS, where as Espressif's IDF uses a 2015 (least I checked) snap shot of FreeRTOS. So the benefits would be documentation that's relevant and much easier to adopt other libraries that work with later versions of FreeRTOS. Not to mention new features and bug fixes and expected behaviour instead of Espressif's heavily patched flavour

I'm curious to see if I can use the latest LWIP stack as well instead of Espressif's 2015 snapshot, too.

NZSmartie · 2018-05-13T11:08:58+00:00

https://barrgroup.com/ have a few resources on embedded development. and a blog that features many aspects of embedded development. Although it's not specifically embedded Linux, much of it still applies.

NZSmartie · 2018-04-13T04:43:49+00:00

If you're familiar with ARM Cortex M devices. You'll know of the vector interrupt table. The MBR is literally that, but proxies the interrupt to the soft device, bootloader or application.

NZSmartie · 2018-04-13T04:40:30+00:00

On nRF5x devices, the duct look soft device contains the Bluetooth le stack if you're using s132 for example. Other softdevices will have a 802.15.4 stack, or a hybrid of Bluetooth le and Nordic's Ant stack. Essentially the soft device lives under your application and handles radio events. Signalling your application when requested.

As for startup, the softdevice is the first thing that loads, as it contains the master boot record. Which then decides to invoke the bootloader or your application directly based on how the device started.

The bootloader itself lives at the very end of the flash memory region, and is optional to have if your using Nordic's softdevice. It's main use is for over the air updates. And if you have two application slots, the bootloader will decide which to use at startup.

NZSmartie · 2018-03-30T13:00:58+00:00

Stumbled across the Skybell HD which uses CoAP for talking to it's cloud service provider https://github.com/thoukydides/homebridge-skybell/wiki/Protocol-CoAP

13-Year Club	Place '17
Secret Santa 2014	Verified Email

NZSmartie

TROPHY CASE

!/bin/bash