All Activity

I've seen this question asked quite frequently here and all the posts end before there is a solution. I think it's time we had a crystal clear discussion on how it can be done. Not just for my curiosity, but for the people who've asked before and for the people who will ask in the future. The reason: Many hats/shields designed for RaspberryPi would otherwise be compatible with OrangePi if Armbian/u-boot didn't direct the debug output to UART0. UART0 is the most commonly used serial connection for hats/shields designed for RaspberryPi. OrangePi has multiple UART gpio so it would make sense for the O.S. (Armbian) to use the one that least impacts the users ability to actually use their hardware. Debug output is important but not so much so that the user cannot easily disable it.

- Update: Kernel 5.1 Wifi-K510: https://drive.google.com/file/d/1B1LmAylalETcnBEWiPiJHL0MjK5xlIV4/view cd /lib/firmware/brcm/ sudo wget https://github.com/CoreELEC/brcmfmac_sdio-firmware-aml/raw/master/firmware/brcm/fw_bcm4335b0_ag.bin sudo ln -s fw_bcm4335b0_ag.bin brcmfmac4335-sdio.bin sudo reboot now nmcli dev wifi - Image: Updated K510 test image: https://drive.google.com/file/d/1ng0j7BhpMya7vOfQjhxmM0HipQ6_F8Ep/view?usp=sharing - BaseFiles: RK3566-H96-MAX-VENDOR-51-V3:https://drive.google.com/file/d/1_N5jQ6wp3rk5Y4xeZK3sEp-L_o5H6KJv/view?usp=drive_link edit Rockchip U-boot Legacy 4.19 DTS: https://github.com/hqnicolas/u-boot/blob/next-dev-v2024.03/arch/arm/dts/rk3566-h96.dts edit Rockchip U-boot Legacy 4.19 DEFCONFIG: https://github.com/hqnicolas/u-boot/blob/next-dev-v2024.03/configs/h96-rk3566_defconfig RK3566-H96-MAX-LEGACY-51-V3.zip

if your using the build system, you can call "add_packages_to_rootfs" with a simple list of packages (i.e. "add_packages_to_rootfs build-essential"), it will handle the references for you. you can also remove packages with "remove-packages" the same way

@primoitt thanks for those Infos, even if not strictly hardware related , they are usefull for building new distros Could be also interesting open a specific thread related ti repositories issues and leave this for hardware specific

hey @jock @SteeMan focal builded flawlessly! [🐳|🔨] sent 16.83M bytes received 2.18K bytes 33.67M bytes/sec [🐳|🔨] total size is 16.82M speedup is 1.00 [🐳|🔨] '/usr/bin/qemu-arm-static' -> '/armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/usr/bin/qemu-arm-static' [🐳|🌿] Updating initramfs... [ TMPDIR=/tmp update-initramfs -u -k 4.4.194-legacy-rk322x ] [🐳|🔨] update-initramfs: Generating /boot/initrd.img-4.4.194-legacy-rk322x [🐳|🔨] update-initramfs: Armbian: Converting to u-boot format: /boot/uInitrd-4.4.194-legacy-rk322x [🐳|🔨] Image Name: uInitrd [🐳|🔨] Created: Mon May 20 18:33:54 2024 [🐳|🔨] Image Type: ARM Linux RAMDisk Image (gzip compressed) [🐳|🔨] Data Size: 5816136 Bytes = 5679.82 KiB = 5.55 MiB [🐳|🔨] Load Address: 00000000 [🐳|🔨] Entry Point: 00000000 [🐳|🔨] update-initramfs: Armbian: Symlinking /boot/uInitrd-4.4.194-legacy-rk322x to /boot/uInitrd [🐳|🔨] '/boot/uInitrd' -> 'uInitrd-4.4.194-legacy-rk322x' [🐳|🔨] update-initramfs: Armbian: done. [🐳|🌱] Updated initramfs. [ TMPDIR=/tmp update-initramfs -u -k 4.4.194-legacy-rk322x ] [🐳|🔨] '/armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/boot/initrd.img-4.4.194-legacy-rk322x' -> '/armbian/cache/initrd/initrd.img-4.4.194-legacy-rk322x-b45d4cabfa6aaf61a91db4025d6d89c8' [🐳|🔨] '/armbian/.tmp/work-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/initrd.img-4.4.194-legacy-rk322x.4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.manifest' -> '/armbian/cache/initrd/initrd.manifest-4.4.194-legacy-rk322x.last.manifest' [🐳|🌿] Re-enabling [ initramfs-tools hook for kernel ] [🐳|🔨] mode of '/etc/kernel/postinst.d/initramfs-tools' changed from 0644 (rw-r--r--) to 0755 (rwxr-xr-x) [🐳|🌱] Unmounting [ /armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e ] [🐳|🔨] removed '/armbian/.tmp/mount-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/usr/bin/qemu-arm-static' [🐳|🌱] Free SD cache [🐳|🌱] Mount point [ 90% ] [🐳|🌱] Preparing u-boot bootloader [ LOOP=/dev/loop8 - /armbian/output/debs/linux-u-boot-rk322x-box-legacy_24.2.0-trunk_armhf__2022.04-Se4b6-P0e83-H87a3-V5177-B1179-R448a.deb ] [🐳|🌱] Sourcing u-boot install functions [ /armbian/output/debs/linux-u-boot-rk322x-box-legacy_24.2.0-trunk_armhf__2022.04-Se4b6-P0e83-H87a3-V5177-B1179-R448a.deb ] [🐳|🌱] Writing u-boot bootloader [ /dev/loop8 ] [🐳|🌿] Unmounting recursively [ MOUNT - be patient ] [🐳|🌿] Freeing loop device [ /dev/loop8 ] [🐳|🔨] renamed '/armbian/.tmp/rootfs-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.raw' -> '/armbian/.tmp/image-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e/Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img' [🐳|🌱] Done building [ Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img ] [🐳|🌱] SHA256 calculating [ Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img ] [🐳|🌱] Fast-moving file to output/images [ -> Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img (860.00MiB) ] [🐳|🌱] Fast-moving file to output/images [ -> Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.sha (199.00B) ] [🐳|🌱] Fast-moving file to output/images [ -> Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.txt (19.30KiB) ] [🐳|🌿] Unmounting recursively [ SDCARD rootfs finished - be patient ] [🐳|🌿] Done building image [ rk322x-box ] [🐳|🌱] Runtime [ 152:09 min ] [🐳|✨] Repeat Build Options [ ./compile.sh BOARD=rk322x-box BRANCH=legacy BUILD_DESKTOP=no BUILD_MINIMAL=yes INSTALL_HEADERS=yes KERNEL_CONFIGURE=yes KERNEL_KEEP_CONFIG=yes RELEASE=focal ] [🐳|🌱] Cleaning up [ please wait for cleanups to finish ] [🐳|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.log.ans ] [🐳|🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-4c3bbdbb-c207-40e4-aa32-9bf377ebdb5e.log.ans https://paste.armbian.com/log ] ls output/images/ -lah total 741M drwxr-xr-x 2 root root 4.0K May 20 18:34 . drwxr-xr-x 7 root root 4.0K May 20 17:48 .. -rw-rw-r-- 1 root root 860M May 20 18:33 Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img -rw-rw-r-- 1 root root 199 May 20 18:34 Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.sha -rw-rw-r-- 1 root root 20K May 20 18:33 Armbian-unofficial_24.2.0-trunk_Rk322x-box_focal_legacy_4.4.194_minimal.img.txt But there's no linux-headers... 😔😔😔 /armbian/output/debs# ls -lah total 144M drwxr-xr-x 3 root root 4.0K May 20 18:06 . drwxr-xr-x 7 root root 4.0K May 20 17:48 .. -rw-rw-r-- 1 root root 1.6M May 20 18:06 armbian-bsp-cli-rk322x-box-legacy_24.2.0-trunk_armhf__1-PCf77f-V24e2-H68df-Be8be-Rf32b.deb -rw-rw-r-- 1 root root 87M May 20 18:06 armbian-firmware_24.2.0-trunk_all__1-SA6fae-B90f5-R448a.deb -rw-rw-r-- 1 root root 1.4K May 20 18:06 fake-ubuntu-advantage-tools_24.2.0-trunk_all__1-Bfcde-R448a.deb drwxrwxr-x 2 root root 4.0K May 20 18:06 focal -rw-rw-r-- 1 root root 4.9M May 20 18:06 linux-dtb-legacy-rk322x_24.2.0-trunk_armhf__4.4.194-Sf8f4-Dc654-Pb5a2-C999999Hfe66-HK01ba-V014b-B1743-R448a.deb -rw-rw-r-- 1 root root 51M May 20 18:06 linux-image-legacy-rk322x_24.2.0-trunk_armhf__4.4.194-Sf8f4-Dc654-Pb5a2-C999999Hfe66-HK01ba-V014b-B1743-R448a.deb -rw-rw-r-- 1 root root 439K May 20 16:02 linux-u-boot-rk322x-box-legacy_24.2.0-trunk_armhf__2022.04-Se4b6-P0e83-H87a3-V5177-B1179-R448a.deb

This is community maintained software. I'm not aware of anyone else that has that specific box. So you are welcome to track down the issue and submit a PR for a fix.

Results of today: I found no image that would let me boot from EMMC without the micro SD, but when i edit the armbianEnv on the SD to point to the UUID of the EMMC partion with installed os it boots from the EMMC. So my conclusion is that i need to build my own U-Boot.bin to get around the poweron issue with the emmc.

Using a different UART is not really practical with a hat/shield designed to use UART0... It would be better for the system to use one that isn't commonly required by hats/shields to be the debug interface. I'll keep looking around.

nope with original orangepi debian image you dint need to do point 1. Only go to orangepi-config and enable I2C5 M3 there.

@SteeMan oh no... Tried buster here and no good... But looks like the problem is on Debian's repo not Armbian's... [🐳|🔨] deb http://deb.debian.org/debian buster main contrib non-free [🐳|🔨] #deb-src http://deb.debian.org/debian buster main contrib non-free [🐳|🔨] [🐳|🔨] deb http://deb.debian.org/debian buster-updates main contrib non-free [🐳|🔨] #deb-src http://deb.debian.org/debian buster-updates main contrib non-free [🐳|🔨] [🐳|🔨] deb http://deb.debian.org/debian buster-backports main contrib non-free [🐳|🔨] #deb-src http://deb.debian.org/debian buster-backports main contrib non-free [🐳|🔨] [🐳|🔨] deb http://security.debian.org/ buster/updates main contrib non-free [🐳|🔨] #deb-src http://security.debian.org/ buster/updates main contrib non-free [🐳|🌱] Updating package list [ buster ] [🐳|🔨] mkdir: created directory '/armbian/.tmp/rootfs-f7083a9e-91b5-461b-9485-7cb3a8d3f02d/var/cache/apt' [🐳|🔨] mkdir: created directory '/armbian/.tmp/rootfs-f7083a9e-91b5-461b-9485-7cb3a8d3f02d/var/lib/apt/lists' [🐳|🔨] Get:1 http://security.debian.org buster/updates InRelease [34.8 kB] [🐳|🔨] Get:2 http://deb.debian.org/debian buster InRelease [122 kB] [🐳|🔨] Get:3 http://deb.debian.org/debian buster-updates InRelease [56.6 kB] [🐳|🔨] Ign:4 http://deb.debian.org/debian buster-backports InRelease [🐳|🔨] Err:5 http://deb.debian.org/debian buster-backports Release [🐳|🔨] 404 Not Found [IP: 151.101.250.132 80] [🐳|🔨] Get:6 http://mirrors.jevincanders.net/armbian/apt buster InRelease [33.2 kB] [🐳|🔨] Get:7 http://security.debian.org buster/updates/main armhf Packages [590 kB] [🐳|🔨] Get:8 http://security.debian.org buster/updates/main Translation-en [324 kB] [🐳|🔨] Get:9 http://security.debian.org buster/updates/contrib armhf Packages [3,452 B] [🐳|🔨] Get:10 http://security.debian.org buster/updates/contrib Translation-en [1,488 B] [🐳|🔨] Get:11 http://security.debian.org buster/updates/non-free armhf Packages [9,940 B] [🐳|🔨] Get:12 http://security.debian.org buster/updates/non-free Translation-en [24.8 kB] [🐳|🔨] Get:13 http://deb.debian.org/debian buster/main armhf Packages [7,706 kB] [🐳|🔨] Get:14 http://deb.debian.org/debian buster/main Translation-en [5,969 kB] [🐳|🔨] Get:15 http://deb.debian.org/debian buster/contrib armhf Packages [40.1 kB] [🐳|🔨] Get:16 http://deb.debian.org/debian buster/contrib Translation-en [44.2 kB] [🐳|🔨] Get:17 http://deb.debian.org/debian buster/non-free armhf Packages [62.1 kB] [🐳|🔨] Get:18 http://deb.debian.org/debian buster/non-free Translation-en [88.9 kB] [🐳|🔨] Get:19 http://deb.debian.org/debian buster-updates/main armhf Packages [8,784 B] [🐳|🔨] Get:20 http://deb.debian.org/debian buster-updates/main Translation-en [6,915 B] [🐳|🔨] Reading package lists... [🐳|🔨] E: The repository 'http://deb.debian.org/debian buster-backports Release' does not have a Release file. [🐳|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ] [🐳|🔨] Hit:1 http://security.debian.org buster/updates InRelease [🐳|🔨] Hit:2 http://deb.debian.org/debian buster InRelease [🐳|🔨] Hit:3 http://deb.debian.org/debian buster-updates InRelease [🐳|🔨] Ign:4 http://deb.debian.org/debian buster-backports InRelease [🐳|🔨] Err:5 http://deb.debian.org/debian buster-backports Release [🐳|🔨] 404 Not Found [IP: 151.101.250.132 80] [🐳|🔨] Hit:6 http://mirrors.jevincanders.net/armbian/apt buster InRelease [🐳|🔨] Reading package lists... [🐳|🔨] E: The repository 'http://deb.debian.org/debian buster-backports Release' does not have a Release file. [🐳|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ] [🐳|🔨] Hit:1 http://deb.debian.org/debian buster InRelease [🐳|🔨] Hit:2 http://deb.debian.org/debian buster-updates InRelease [🐳|🔨] Ign:3 http://deb.debian.org/debian buster-backports InRelease [🐳|🔨] Hit:4 http://security.debian.org buster/updates InRelease [🐳|🔨] Err:5 http://deb.debian.org/debian buster-backports Release [🐳|🔨] 404 Not Found [IP: 151.101.250.132 80] [🐳|🔨] Hit:6 http://mirrors.jevincanders.net/armbian/apt buster InRelease [🐳|🔨] Reading package lists... [🐳|🔨] E: The repository 'http://deb.debian.org/debian buster-backports Release' does not have a Release file. [🐳|🚸] Command failed, retrying in 5s [ chroot_sdcard_apt_get_update ] [🐳|🚸] Command failed 3 times, giving up [ chroot_sdcard_apt_get_update ] [🐳|💥] Error 1 occurred in main shell [ at /armbian/lib/functions/rootfs/rootfs-create.sh:164 create_new_rootfs_cache_via_debootstrap() --> lib/functions/rootfs/rootfs-create.sh:164 create_new_rootfs_cache() --> lib/functions/rootfs/create-cache.sh:69 do_with_logging() --> lib/functions/logging/section-logging.sh:81 artifact_rootfs_build_from_sources() --> lib/functions/artifacts/artifact-rootfs.sh:80 artifact_build_from_sources() --> lib/functions/artifacts/artifacts-obtain.sh:34 obtain_complete_artifact() --> lib/functions/artifacts/artifacts-obtain.sh:280 build_artifact_for_image() --> lib/functions/artifacts/artifacts-obtain.sh:392 get_or_create_rootfs_cache_chroot_sdcard() --> lib/functions/rootfs/create-cache.sh:83 build_rootfs_and_image() --> lib/functions/main/rootfs-image.sh:14 full_build_packages_rootfs_and_image() --> lib/functions/main/default-build.sh:36 do_with_default_build() --> lib/functions/main/default-build.sh:42 cli_standard_build_run() --> lib/functions/cli/cli-build.sh:25 armbian_cli_run_command() --> lib/functions/cli/utils-cli.sh:136 cli_entrypoint() --> lib/functions/cli/entrypoint.sh:176 main() --> ./compile.sh:50 ] [🐳|💥] Cleaning up [ please wait for cleanups to finish ] [🐳|🌿] Unmounting recursively [ SDCARD - be patient ] [🐳|🌱] Unmounted OK after 2 attempt(s) [ SDCARD ] [🐳|🌿] Unmounting recursively [ MOUNT - be patient ] [🐳|🌿] ANSI log file built; inspect it by running: [ less -RS output/logs/log-build-f7083a9e-91b5-461b-9485-7cb3a8d3f02d.log.ans ] [🐳|🌿] Share log manually (or SHARE_LOG=yes): [ curl --data-binary @output/logs/log-build-f7083a9e-91b5-461b-9485-7cb3a8d3f02d.log.ans https://paste.armbian.com/log ]

Thanks for your advice, this is really helpful. I am switching the board config to use bananapi sun50iw family, and it looks like most of the changes BTT made are already in the list of patches for sunxi-6.6 and sunxi-6.7 (the current config doesn't use 6.8 as edge). I'm making an analysis of the differences. The most obvious change that will be needed is to add the dts file, which is already in 6.7 but will need to be backported for 6.6. Although the device tree in the kernel makes a difference between a Pi and CB1 (SoM), which is also used on a Manta (CNC/3d-printing control board with SoM socket for CB1/CB2).

yes it boot properply if i pull the power xfce version does it correctly when i enter sudo reboot

Hi Referring to https://forum.armbian.com/topic/32667-usb-c-port-doesnt-work-on-pinebook-pro-after-the-latest-update-on-kernel-662/ USB -C is not working. I also tried 6.7.4-edge with no success. Looking for a solution G??gle found this: https://www.linuxquestions.org/questions/slackware-arm-108/pinebook-pro-usb-c-port-not-working-after-kernel-upgrade-4175732886/#google_vignette referring to Megi`s 6.7 kernel. The link was outdated, but the base worked and had versions 6.8 and 6.9. Tried both with a lot of success: USB-C working and the HDMI monitor output as well as Gigabit Ethernet work like a charm again. 😄 The only small issue remaining: Sound is not working (no analog or digital.) (I had a small issue following Megi`s Readme: The board.dtb should replace rk3399-pinebook-pro.dtb in one of the existing dtb trees. I used dtb-6.7.4-edge-rockchip64.) any ideas about the sound issue are greatly appreciated. Sepp

Does it boot properly if you pull the power? Reboot not working correctly is a common issue on these boxes where you don't have a dtb file that is an exact match for your hardware.

stuck on boot screen after software reboot... command sudo reboot on terminal Armbian_community_24.5.0-trunk.563_Aml-s9xx-box_bookworm_current_6.6.30.img.xz this does not happen on the desktop version Armbian_community_24.5.0-trunk.563_Aml-s9xx-box_bookworm_current_6.6.30_xfce_desktop.img.xz

Description Resolving 3d and multimedia extensions confusions. Replacement for: https://github.com/armbian/build/blob/main/extensions/mesa-oibaf.sh https://github.com/armbian/build/blob/main/extensions/rk-multimedia-amazingfate.sh https://github.com/armbian/build/blob/main/extensions/rk-panthor.sh and custom one: https://github.com/armbian/os/blob/main/userpatches/extensions/amazingfated-rk3588.sh How Has This Been Tested? [ ] Made all test images with enabled extension Checklist: [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Description It is known that it is built without errors and works on a test platform. freeze the kernel version v6.6.31 sunxi-6.6: rework patches for current v6.6.31 [ ] short description (copy / paste of PR title) [ ] summary (description relevant for end users) [ ] example of usage (how to see this in function) How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [x] Build & Test on board Bananapi-m64 View the full article

@madeofstown I'd guess it is good to leave the default serial uart console running there as otherwise if things goofs, you may have no means to login onto the board. with the serial console, you can connect a usb-uart serial dongle and login to Armbian on the board. but if you insist you can nevertheless try going into /usr/lib/systemd/system look for those *getty* (e.g. ls *getty*), it would be one of those services. but that for debug output I'm not sure about that though, a google search I'd guess would get some leads e.g. https://superuser.com/questions/351387/how-to-stop-kernel-messages-from-flooding-my-console https://wiki.archlinux.org/title/working_with_the_serial_console I'd suggest to browse that same Orange Pi Zero 3 thread and figure out how to use a different serial uart port, there are probably more than a single uart port available on Orange Pi Zero 2W or Orange Pi Zero 3. using a different serial comm (uart) port is the correct solution in your case and you won't need to be bothered about console messages as they won't be there.

Description Minor fixes: limit creation of git-sources.json file to following commands - targets, debs-to-repo-json, gha-matrix and gha-workflow Solve slowness when building Ubuntu Noble images. Fixes #6531 How Has This Been Tested? Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration. [X] Tested Ubuntu noble rootfs creation speed improvement using ./compile.sh BOARD=khadas-vim4 BRANCH=legacy KERNEL_CONFIGURE=no BUILD_MINIMAL=yes RELEASE=noble ARTIFACT_IGNORE_CACHE=yes rootfs. It reduced build time from 26 minutes down to only 8 minutes. Checklist: Please delete options that are not relevant. [ ] My code follows the style guidelines of this project [ ] I have performed a self-review of my own code [ ] I have commented my code, particularly in hard-to-understand areas [ ] My changes generate no new warnings [ ] Any dependent changes have been merged and published in downstream modules View the full article

Hi everyone, I'm trying build armbian with legacy branch and I need apply patch to u-boot config. If I add my patch in userpatches, buid script ignoring it. If I build current branch, patches aplying

@ag123 Thank you. I was able to apply that patch and now Armbian is running on my OPIZ2W 1.5GB! One more question. I have a LoRa/GNSS hat that requires the use of Serial 0 for communication with the GNSS model. How would I go about disabling Armbian debug outputing to that? I would rather not have to use bodge wires. `gpioinfo` shows me that the 2 pins are used by the kernel. Do I need to recompile the kernel to change this? Seems like a lot of the hats/shields that use Serial need to use Serial0... So I'm thinking there must be a simple way to get it working in Armbian.

Description doas is not compatible with sudo flags. The codebase was checked for sudo-specific uses of this function, but none were found, all cases were in the form of sudo <command>. Replacing it with doas <command> yields the same result. Was extracted from #6576 and can't be merged until it's reverted in #6642 How Has This Been Tested? Used to build images on my machine with extensions that use is_root_or_sudo_prefix Checklist: [x] My code follows the style guidelines of this project [x] I have performed a self-review of my own code [x] I have commented my code, particularly in hard-to-understand areas [x] My changes generate no new warnings View the full article

Reverts armbian/build#6576 View the full article