Heisath

@Dee2022 yeah and a fix is already on the way - read the posts above yours  

I did the upgrade from Buster to Bullseye. 
 
As far as steps:
- Backup
- apt update & full-upgrade
- Disable /etc/apt/sources.list.d/armbian.list all entries to stop armbian from upgrading
- Use normal debian upgrade steps -> Change release in /etc/apt/sources.list 
- apt update & full-upgrade
- Restart, validate working system
- Update /etc/apt/sources.list.d/armbian.list with new release (buster->bullseye)
- apt update & full-upgrade
- Should be done. 
 
Take extra care for some new/renamed packages. armbian-bsp-cli-<BOARD> is new. Older armbian-root-* packages dont exist anymore (I think).
 
For me this worked flawless, you might have to fix some dependency problems, and make sure at least some working version of armbian-image-* armbian-dtb-* is installed before rebooting.

Hey. Yeah I noticed this problem already, see https://github.com/armbian/build/pull/4261
Unfortunately I did not get around to fix it last weekend, working on it right now
 
As for future proofing, unless someone has the energy to get the patches mainlined it will break from time to time...
 
 

I will run mvebu tests tomorrow. Sorry for not being available for the meeting, turns out, building a house is a pretty major thing...

I will run mvebu tests tomorrow. Sorry for not being available for the meeting, turns out, building a house is a pretty major thing...

No I do not think so. The hardware is nearly the same - base is just pro with removed devices.

Release Candidate Code Freeze Date: 2022-02-14
Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
Release Planning Meeting Location: Armbian IRC
Release Date: 2022-02-28
Release Branch Link: https://github.com/armbian/build/tree/v22.02
Release Changelog:
 
 
Release Coordinator: @Heisath and hopefully some new person on the team
 
Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
 
Current steps:
- Refine supported/WIP/CSC/etc. board status
- Update maintainer list
- Onboard new maintainers / contributors
- Move Jira issues to new release
- Select release name 
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
 
Pls. ping developers I forgot  

If possible it would be great if all maintainers could send a PR with fixed tag for kernel source.
Follow this PR https://github.com/armbian/build/pull/3500
This would allow for more reproducible builds.
 
This together with Igors suggestion of merging 
https://github.com/armbian/build/pull/3489
https://github.com/armbian/build/pull/3499
could go into a new RC branch.
 
 
@Contributor/Maintainer
 

I created branch with Ebin improvements and PR https://github.com/armbian/build/pull/3498
 
This is still WIP. Feedback + help welcome. 
 
Currently building TF-A fails because:
 
plat/marvell/armada/a3k/common/a3700_common.mk:148: *** "Platform 'a3700' for WTP image tool requires CRYPTOPP_PATH or CRYPTOPP_LIBDIR. Please set CRYPTOPP_PATH or CRYPTOPP_LIBDIR to point to the right directory". Stop.  
 
Got it working, see https://github.com/armbian/build/pull/3498 
Compilation seems to work now. Waiting on feedback from ebin owners.
 
armbianEnv.txt still needs adjustment!

Release candidate has been branched off. Please direct all bugfixes to 'master' AND 'v22.02-RC'.  Please build, test etc. the RC branch. 
 
https://github.com/armbian/build/tree/v22.02-RC

Today is code freeze day. *ice*
I am currently testing mvebu 5.15 + 5.16 - afterwards I will do the code freeze / RC branch.
 
Is anyone still working on something important, that should go into this release / RC ?
 
@private/contributor
@Contributor/Maintainer

Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).
 
I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn

Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).
 
I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn

Reminder! The release meeting is happening this saturday 14:00 UTC+1 (which is 13:00 UTC or 8 am EST or 2 pm CET or 5 am PST (sorry california dudes) or 9 pm CST).
 
I will look through the Jira issues remaining today. Would be great if you could check them too and add the ones you have finished (or are planning to include in 22.02) to the release.
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013 @rpardini @yang @adeepn

I would still go on with the February release, we skipped last one, lets get this one done.
 
Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 
Release meeting earlier than 2022-01-25 is not possible from my calendar.
 
 

I did the upgrade from Buster to Bullseye. 
 
As far as steps:
- Backup
- apt update & full-upgrade
- Disable /etc/apt/sources.list.d/armbian.list all entries to stop armbian from upgrading
- Use normal debian upgrade steps -> Change release in /etc/apt/sources.list 
- apt update & full-upgrade
- Restart, validate working system
- Update /etc/apt/sources.list.d/armbian.list with new release (buster->bullseye)
- apt update & full-upgrade
- Should be done. 
 
Take extra care for some new/renamed packages. armbian-bsp-cli-<BOARD> is new. Older armbian-root-* packages dont exist anymore (I think).
 
For me this worked flawless, you might have to fix some dependency problems, and make sure at least some working version of armbian-image-* armbian-dtb-* is installed before rebooting.

I would still go on with the February release, we skipped last one, lets get this one done.
 
Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 
Release meeting earlier than 2022-01-25 is not possible from my calendar.
 
 

I would still go on with the February release, we skipped last one, lets get this one done.
 
Am targeting 2022-01-29 (Saturday, 29 of January 2022) for release meeting, and then about 4 weeks later 2022-02-25 (Friday, 25 of February 2022) for actual release. 
Release meeting earlier than 2022-01-25 is not possible from my calendar.
 
 

Release Candidate Code Freeze Date: 2022-02-14
Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
Release Planning Meeting Location: Armbian IRC
Release Date: 2022-02-28
Release Branch Link: https://github.com/armbian/build/tree/v22.02
Release Changelog:
 
 
Release Coordinator: @Heisath and hopefully some new person on the team
 
Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
 
Current steps:
- Refine supported/WIP/CSC/etc. board status
- Update maintainer list
- Onboard new maintainers / contributors
- Move Jira issues to new release
- Select release name 
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
 
Pls. ping developers I forgot  

Release Candidate Code Freeze Date: 2022-02-14
Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
Release Planning Meeting Location: Armbian IRC
Release Date: 2022-02-28
Release Branch Link: https://github.com/armbian/build/tree/v22.02
Release Changelog:
 
 
Release Coordinator: @Heisath and hopefully some new person on the team
 
Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
 
Current steps:
- Refine supported/WIP/CSC/etc. board status
- Update maintainer list
- Onboard new maintainers / contributors
- Move Jira issues to new release
- Select release name 
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
 
Pls. ping developers I forgot  

Added to watchlist. If it stays cheap enough, I'll buy it. 
 
Can't guarantee you "Supported" flag, but I will have it running edge and notice problems
 
 

Should be easy enough to grab 5V of the wiring harness for the HDDs. J8 is the place to go for your high power 12V or 5V needs. https://wiki.kobol.io/helios64/sata/#j8-pinout (there is even a picture with the wire harness). 
The GPIO header is not the right place to get high current from .)

Release Candidate Code Freeze Date: 2022-02-14
Release Planning Meeting Date:  2022-01-29 14:00 UTC+1 
Release Planning Meeting Location: Armbian IRC
Release Date: 2022-02-28
Release Branch Link: https://github.com/armbian/build/tree/v22.02
Release Changelog:
 
 
Release Coordinator: @Heisath and hopefully some new person on the team
 
Already creating this release topic for 22.02, to discuss upcoming changes, no longer maintained boards and help new people get into the release / maintain flow.
 
Current steps:
- Refine supported/WIP/CSC/etc. board status
- Update maintainer list
- Onboard new maintainers / contributors
- Move Jira issues to new release
- Select release name 
 
@Igor @Werner @TonyMac32 @martinayotte @piter75 @ning @Myy @balbes150 @sfx2000 @ebin-dev @chwe  @gprovost @aprayoga @lanefu @5kft @JMCC @going @jeanrhum @dolphs @jock @belfastraven @TRS-80 @Bozza @Rich Neese @sgjava @Mangix @tony013  @rpardini
 
Pls. ping developers I forgot  

Arduino solutions will be the only more efficent way going forward. I mean, reading RS232 to SD card is super simple. 
 
Untested code below, it would watch Serial and SoftSerial for incoming data, write it to a file on sd card (in 100 char chunks or on every newline, syncing sd card after every chunk). 
Should be simple enough to adjust for some power down mechanism (and maybe add a button to manually sync data before removing sd card)...
 
#include <SoftwareSerial.h> #include <SD.h> char buffer[100]; int buffer_pos = 0; uint8_t sdavail; #define CurrentBaudrate 115200 SoftwareSerial softSerial = SoftwareSerial(5, 4, false); void setup() { sdavail = SD.begin(SDC_CS); setupScreen(); Serial.begin(CurrentBaudrate); softSerial.begin(CurrentBaudrate); softSerial.listen(); } uint32_t lastTouched = millis(); char msg; void loop() { while (Serial.available() || softSerial.available()) { msg = Serial.available() ? (char)Serial.read() : (char)softSerial.read(); buffer[buffer_pos++] = msg; if (buffer_pos >= sizeof(buffer)) break; } if (msg == '\n' || buffer_pos >= sizeof(buffer)) { writeBuffer(); } } void writeBuffer() { if (sdavail) { File dataFile = SD.open("datalog.txt", FILE_WRITE); if (dataFile) { dataFile.write(buffer, buffer_pos); dataFile.close(); } } buffer_pos = 0; }  

Added to watchlist. If it stays cheap enough, I'll buy it. 
 
Can't guarantee you "Supported" flag, but I will have it running edge and notice problems