Hello,

I am trying to cross-compile for rock64 on fedora31 on x86.
libfdt-devel i686   1.4.7-2
aarch64-linux-gnu-2.30-6.fc29.x86_64 (why is this appearing ??)

What I get are multiple copies of fdt which seem to be behind :
/usr/include/libfdt_env.h:71:30 : error conflicting types for fdt64_t
  typedef uint64_t FDT_BITWISE fdt64_t;

The above disappears when /usr/include/*fdt*.h   "disappear" as per a
thread suggestion:
https://github.com/m01/rock64-arch-linux-build/issues/3
leads to this:
https://bugs.debian.org/cgi-bin/bugrepor...bug=888789
tools/libfdt_wrap.c : 149:11: fatal errorython.h :no such file or directory
#include <Python.h>



Thx in advance,
blocked contractor

Hello,

Currently I am using my Pinebook Pro with the default Debian Desktop installation - without any encryption. I am moderately paranoid about
security (an occupational hazzard I guess) and would like to run the Pinebook the way I run my other notebooks - with an encrypted LVM configured in the same
way the official Debian installer sets it up. I have not yet bought an SSD for the Pinebook, but I would like most buy the intel SSD listed as compatible. 

Is anybody already using a similar setup and could describe how he/she got it working? I guess without an installer one would have to set up the SSD with cryptsetup manually, debootstrap an operating system on it (Debian) and then configure grub. So in theory it should be possible already. But these are a lot of steps and this setup would not include the customized builds from Mr. Fixit. What I would like (User Story, meant as a suggestion for improvement) would a repository which I could simply add to my apt-sources and then install and update via that repository. 

Yours sincerely
Stefan

# Set up a STM32 bluepill as blackmagic probe

There exist a very nice solution to flash the PineTime called [Blackmagic](https://1bitsquared.com/products/black-magic-probe) probe.
Rather than connecting with OpenOCD or JLink to the probe you can just open the debugger gdb and connect to the PineTime.

The Blackmagic probe was an crowdfunding development and the source is available on Github and crucially there are also versions for other hardware than the blackmagic probe device. If you regularly work or develop with embedded devices it is probably worth to buy the original Blackmagic probe. If you are new and want to try things before spending more money there is an inexpensive option.

You can flash the blackmagic binary to a device generally called [STM32 bluepill](https://circuitdigest.com/microcontrolle...g-usb-port), a small ARM M3 micro controller board which is widely available for cheap.

This approach works, it however comes with it's own challenges:
1. A practical issue, the blackmagic.bin is larger than 64k but the flash memory of the bluepill is officially only 64k. The thing is unofficially the chip actually supports 128k but there seems to be a production selection process and you cannot be sure if your device supports 128k.
2. To flash the STM32 bluepill you need a st-link or serial flash device or something, but you want the blackmagic probe because you don't have that
3. The chip on the STM32 bluepill is called STM32F103C8T6. There are quite a lot of cheap(er) chinese clones of this chip out there often called CS32F103C8T6 and there can be problems with those.

So as a beginner, what to do ?
Searching on ebay I found one product in the UK that helped with the problems above.

[Link to STM32 bluepill on ebay](https://www.ebay.co.uk/itm/Genuine-STM32...Sw~bFWGQ18)

The seller claims to use the original chip, but crucially also one that supports 128k. Also and this is important, the seller has uploaded the Ardoino (Maple) bootloaded already. This means you can access the bluepill with the USB port right away and do not need another connection.

Obviously I don't know the seller and can't give any assurance that it always workes, but it did work in my case.

I would guess that you can find similar offers in other countries.

So, if you have a STM32 bluepill tha has already the [bootloader](https://github.com/rogerclarkmelbourne/A...Bootloader) installed then you can follow these steps to convert the STM32 bluepill into a blackmagic probe.

1. Install `dfu-util` if you don't have it already
2. Download [blackmagic binary](https://github.com/blacksphere/blackmagi...g-Firmware). For the bluepill the `st-link` variant is required. You can download the latest nightly from [here](http://builds.blacksphere.co.nz/blackmag...stlink.bin).
3. Connect the bluepill with an usb cable and check the dmesg for the connection message. Then check with `dfu-util -l` how it is listed.
4. In my case the device showed three lines, the only difference is the alt(ernative) flag from ( 0..2). For this guide you need alternative 2. The flag `-a 2` stands for alternative 2
5. Check the device ID. Mine was 1eaf:003 but I have seen other IDs in other guides. If you have a different ID you have to adjust the command in the next step
6. flash the blackmagic binary with this command:

```
sudo dfu-util -d 1eaf:003 -a 2 -D blackmagic-stlink.bin
```

__Note: in other guides you see a variant of this command with a flag `-s` and the address where to flash the binary. This is the function of the alternatives here and not required here__


It might be required to press the reset button on the board shortly before flashing

You should see a progress bar and then a happy result.

7. Reset the board.
8. The commands `lsusb` and `dfu-util -l` show the new device.
9. The gdb debugger is available as `/dev/ttyACM0`
10. See here for a [gdb getting started guide](https://github.com/blacksphere/blackmagi...ng-Started)

Sorry for the markdown format, The forum formatting seems not to be supported by Pandoc

Has anyone had any luck improving the performance of gvim on PBP? I'm finding it to be exceptionally slow when I make my window fullscreen, as compared to running vim in a Terminal and making it fullscreen. Anyone have any simple fixes I can try? (I'm really attached to gvim's desert theme..)

I ordered an ANSI PBP and included the NVMe adapter in that order.

Got my Shipment on Monday but there was NOT a package with the NVMe adapter. Might the adapter have been installed in the PBP during build time?

Did not really want to open up the machine yet, so asking if that might be the case.

If not, how do I get the adapter if it did not actually ship with the computer.

Thx.


Sent from my iPad using Tapatalk

Hello all!

I have had my PBP for about 48 hours now and am really impressed.  Everything seems to work with the exception of the audio system following wake from suspend.  First noticed it with YouTube in the Chromium browser, and in my troubleshooting efforts, tried just a standard mp3.  I can play the mp3 fine, put the PBP to sleep via the lid or the power button.  When it wakes I have no audio when I try to play the file.  I can tell there is some high pitch noise and some clicks from the speakers, but that is it.

Based on some related posts here, I tried reinstalling pulseaudio using the --reinstall flag on the apt install command line but that did not change the behavior.  My next step is to install another operating system and see if the behavior is present there as well.

Thanks for any assistance you can provide!

Tom

Hey all,

Last month I posted a simple zram-swap script that I wrote for my PBP on IRC for people to use. I took some time to package it and make it "release worthy" and pushed it to github with updates today: https://github.com/foundObjects/zram-swap

This makes a huge difference if you're memory constrained on your PBP, and even if you aren't I encourage you to check it out simply to avoid the NAND wear of swapping to your eMMC when you eventually do need to swap.

I also added a fixed-size swap feature for people who know ahead of time exactly how much swap they want, so if you're doing something like building GCC with -lto on the PBP and need 10+G swap I've got you covered: just set "_zram_fixed_size=10G" in the /etc/default/zram-swap config file along with your prefered swap algorithm and you're good to go. Yes, you can use lzo-rle.

README.md:

Hello all,

I work in computer forensics and I am looking forward to purchasing and using a PinePhone both for general privacy sake as well as my desire to learn how to create forensic images of Linux smartphones and then perform forensic analysis of the resulting forensic images.

Currently, my smartphone forensic software includes Cellebrite (www.cellebrite.com) and MOBILedit Forensic Express (www.mobiledit.com/forensic-express).

For imaging iPhones, smartphone forensic software basically invokes iTunes to create a "mobile backup" of the iPhone being imaged; the resulting image is a logical image, not a physical image, though.  In order to generate a physical image of an iPhone, one must jailbreak the iPhone first.

For imaging Android phones, smartphone forensic software will first install an "agent" on the Android phone; the installed agent will then export out files to external media, sometimes through the use of the Android Debugging Bridge.  Similar to iPhones, one cannot generate a physical image of an Android phone unless one can root the Android phone first.

I am curious to see if traditional workstation imaging software will be able to generate forensic images of the PinePhone.

For example, I oftentimes use Guymager (https://guymager.sourceforge.io/) to generate forensic images of workstation hard drives.  Typically I will use a Live USB running a "free-to-use" Forensic Linux distribution such as Paladin (https://sumuri.com/software/paladin/).  I am able to boot the target workstation to the Linux distribution, which gets loaded to the target workstation's RAM and will not mount the internal hard drive, or only mount the target workstation's internal hard drive as read only.

I am new to this forum so I do not know if there are any other fellow forensic practitioners here, but if there is interest, I will update everyone with my forensic imaging and analysis progress once I get a PinePhone.

Hello PBP community,

This post to show my PBP speaker mod, 1st try.

I'll test some other speakers in the future, because while replacements are better than original, I still haven't found what I'm hearing for.

My appreciation of the stock speakers:
Bad sound, no bass at all, makes me feel cranky and uneasy, very disagreable.
2/10

New speakers: GHXAMP 20MM 4 Ohms 2 W

Average-to-good sound, little bass, would use to watch movies and listen to music if no other choice
7/10

Replacement went well, except for 1 thing: new speakers were about 2mm thicker than old ones. I had to move them farther from the sides a little, removing sidewalls in the process. I can confirm that while the BPB material feels like metal, it's plated over some plastic core. 2 sided tape was used to fix them in place. See attachments for replacement process pics.

In the process, I had to open the PBP for the 4th time. I'm afraid this isn't PBP friendly. Will have to imagine some bottom panel replacement hack soon. Would be nice to have a more thinkerer friendly choice shell design for next PBP iterations, even at the price of a thicker laptop. What should matter most is rigidity, stiffness and weight. Not trying to copy Mac Book laptop designs, which are, by the way, computers made for never being opened.

Sound test:

Attached Files

  0.jpg (Size: 193.57 KB / Downloads: 884)
  1.jpg (Size: 256.18 KB / Downloads: 848)

Hello everybody!

Could you give me your opinion for the feasibility of a little project? I'm a software developer, very familiar with open source, but totally unfamiliar with any hardware tinkering, soldering etc. I can put a plug in a socket, and that's it :-)

For an elderly friend, I'd like to have a watch that shows the time, and which at several times of the day beeps, or vibrates, and shows a message "Please take your medicine now!" and requires some kind of complex action to switch the alarm off. (This could be tapping three times on a button.)

This is more about IoT than "smart". My friend does not use a smartphone, and does not want one. The fact that it wouldn't be connected to a phone or to any kind of network - that's a big advantage here, and the long battery life of the PinePhone looks very attractive.

So, instead of getting an expensive smartwatch and spending days to deactivate everything, I'd love to get a PineTime and spend weeks of tinkering with it. Embedded Rust sounds fun! I'm not pressed for time. If I can get this to work somewhen in 2020 I'm happy. (Until then, there are other reminders in place for my friend.)

My question to you: Does this sound like a feasible plan? Can the PineTime beep or buzz? (On the wiki I only read about the vibration motor.) Can I develop for this watch without soldering - be it by connecting/holding wires, by Bluetooth (no matter if it's slow), by emulators?

Thank you for reading!