If you have an LPC-Link2 lying around, you can use it to debug/develop on the PineTime dev kit.

First, you need to flash a CMSIS-DAP firmware on the LPC-Link2. NXP has these.

If you're using the wires provided with the PineTime, then you will need to populate the J6 location on the LPC-Link2; it's the only one which expects a pin header. I fitted a 9-pin right-angle header.

Then you have to properly match the PineTime SWD pinout to the J6 header pins. Gnd goes to pin 8, Vcc to pin 1, SWDIO to pin 2 and SWDCLK to pin 3.

Last, you have to put jumpers on both JP1 and JP2 of the LPC-Link2. JP1 will make it boot on its internal firmware and thus act as a CMSIS-DAP probe; JP2 will power the SWD signal buffers. If you forget JP2, OpenOCD will recodgnize the probe but not the PineTime.

Then you need a configuration file for OpenOCD. This file should contain the following:

For those of us getting on in years and small displays harder to read, is the pseudo analog display only an option that can be switched to a simple large font digital time and date?

soyrunner

For reasons unbeknownst to me, the first row of the alphanumeric keyboard (1234....) packed in. Some random letters in the other rows as well.
Any clue on how to solve that as I want the Pinebook to survive at least until the Pro arrives....

(I've initially intended to ask in the Linux-specific sub-forum, but I guess this is not limited to Linux only. Corrections welcome)

To be ready for un-bricking my horrible experiments that are bound to come, I'm slowly working on gathering information on how this wonderful creature boots.

Mrfixit (thanks!) clarified on IRC that the u-Boot bootloader is stored in an off-set on the eMMC, not directly accessible (~not in one of the two actual partitions, I assume).
So my questions would be:
- Where is it exactly?
- How do I find it?
- How do I recognize that I have actually found it?


I have also had a look at the ChromiumOS image, and in it, there are two interesting files in /boot: boot.scr and bootloader.bin.
(disclaimer: I'm away from the PBP and SD card, so I may be misremembering the filenames. Corrections will follow.)
When I run "file boot.scr", this is identified as an u-Boot bootloader image. The other file is simply data.
==> this brings a side-question: can the bootloader then be stored completely in the /boot partition? Or am I misunderstanding the purpose of these two files?

Upon further googling and reading, I've stumbled upon these links:
https://linux-sunxi.org/Bootable_SD_card
https://linux-sunxi.org/Mainline_U-Boot

These suggest specific places on the eMMC for the location of u-boot. I have also noticed that there are "gaps" at the beginning of the mmcblk1 disk and between the two "readable" partitions.
I've tried to copy various amounts of data from the above start locations using dd into a file and then tried to identify them with "file", but had no luck so far.

Am I looking into the wrong place?
Am I applying a completely wrong approach to find and identify u-Boot?

Ultimately, the question can be boiled down to: Once I have a u-Boot binary, where do I put it on the disk?
Apologies if these questions are too dumb, but I sort of figured this might be useful to document somewhere on the forums/wiki.

Will this be possible with an adapter?  Or is there some inherent flaw in wireless charging, e.g. excessive heat ruining the battery?

Hello

I personally am very interested in the PinePhone and would actually buy it as soon as possible, if there wasn't one thing that made it unsuitable as my daily driver; That thing being the width.
The PinePhone is 76.6mm wide according to the wiki.
The highest width that I can comfortably hold in my hand is 67mm.
Which makes the PinePhone far to wide for me to somewhat comfortably use it with one hand.
I personally would be willing to sacrifice in some other aspects like thickness.

I am adding a poll to this thread to hopefully get some vague info on how demanded this feature actually is.

Hello!

Coming from the STM32 and ESP32 world, I'm a total beginner as far as the NRF52 is concerned. For now, I'm still learning the MCU, the tools and the SDK.


The first thing I want to do is to create my development environment that'll allow me to write code, program the chip, debug,... It's based on CLion/CMake, it uses the NRF52-SDK and the tools from J-Link to debug and program.

This is not directly about the PineTime, but I intend to use this when I'm ready to work on the watch directly.

So, I created a little "base project" which contains the bare minimum to build, program and debug a simple blinky application. The project is here and the wiki page that gives more details is here. It might be useful for anyone who is just starting with NRF52.

For now, the master branch contains a simple blinky app, and the branch freertos is the same but using FreeRTOS.

Have fun

As said in the title, I have a disk controller LSI 9208 8i that needed some patch (pcie_rk_delay_bus_scan) to work with kernel Rockchip line 4.4 (the patch is in ayufan's kernel since april). I tried again the mainline and, finally, it works out of the box with the version 5.3.6. By the way, I have not tested Panfrost graphic driver, and I could not make framebuffer console to work.

I can recognize mmcblk1 / ...p1/p2, but I wonder, what are:
mmcblk1boot0
mmcblk1boot1
mmcblk1rpmb
?

Given the 16M size, I assume the last one is the SPI flash? What about the others? (both showing 4M size)
fdisk -l doesn't give me any interesting information.
Are these supposed to be interact-able in any way? 
Or am I just dumb and these are actually still the eMMC?

Hi all experts,
According to my project that needs to be run 24x7 on my rockpro64, there was issue with OS corruption as due to power shutdown the devices was on unexpected power cycle. So i was trying to make the OS to read-only mode.

I followed this link-
https://medium.com/@andreas.schallwig/ho...c0f7be7353

I successfully done that but some system services and my docker service stoped working now.

OS -
Armbian ver5.98

Requirement-
1) I have made one app that needs to be run 24x7 and that is a docker process. So i need to access docker in RO mode.
2) I have also made a system-service(in /etc/systemd/system/my-service) that keeps on monitoring that docker app.
3) There are some file write operation need to be done in "/opt" or any other folder.

Please suggest me way to make the OS to read-only by keeping above 3 requirements.

Thanks.