I came across with a problem these days!
The problem is that after I writing debian os from microSD card to emmc, beaglebone clould i9 says:
Failed to write to 'state.settings'. ENOSPC: no space left on device, write
and nothing works at all!
So I decide to format the emmc on beaglebone!
Can anyone help me how to get this done?
Maybe you are using the wrong debian version. Currently (12.03.2020) the version "Debian 9.9 2019-08-03 4GB SD IoT" is just usable for microSD card and is not recommended for eMMC flashing. If you want to flash the eMMC you can currently use the version "Debian 9.5 2018-10-07 4GB eMMC IoT Flasher". Unfortunatley, does this version not include the graphical desktop.
Related
I have problem with drivers on my PC. For the first Nvidia X settings are empty(like we can see on screen. I installed drivers with instuctions in https://www.linuxbabe.com/ubuntu/install-nvidia-driver-ubuntu-18-04, but this method doesnt work. I tried on software&updating in additional drivers and nothing change(All time i have: DRIVERS: Intel® UHD Graphics 630 (Coffeelake 3x8 GT2) like second screen
enter image description here
Summary, Ubuntu don't see my second screen after some update. I'm sure my devices are ok because on windows 10 all it's alright.
Maybe somebody have some hints for it?
I'm trying build a linux system on beaglebone black and following to mastering embedded linux programming book, however when I boot my u-boot on beaglebone black, I have received a error: unknown command 'nand' - try 'help'.
Does anybody have any idea of what did I do wrong or did I miss something?
If you are in Chapter 3: All About Bootloaders → U-Boot → Using U-Boot:
This is NOT an example meant to be executed on a BeagleBoneBlack.
It is a generic example of a U-Boot command that possibly could work on hardware that actually has NAND flash. The BBB does not have raw NAND flash, it has an eMMC and a micro-SD card slot.
If that's not where you are in the book, please provide chapter information and what you are trying to achieve.
BTW: please also note that there are errata for this book, especially around U-Boot and the NAND commands. You might want to verify if they apply to your reprint.
The command nand is only available in U-Boot if CONFIG_CMD_NAND=y is configured.
Use make menuconfig for configuration.
Background: We are looking to release a commercial product based on the Android Things OS and Pi 3 hardware. The OS seems to become corrupt over time. Usually after several weeks of continuous testing. By corrupt, the Android screen will no longer appear on startup and putting SD into new hardware does not remedy. We are using an application Factory Image base on the 0.5.1-devpreview created in the Console.
My question: Is there a way to debug or monitor what caused this state in the OS? Direct serial connection?
try to clean the sd card with the diskpart command and start again from scratch.
And to debug, maybe a USB to TTL cable may help. As explained here.
Regards!
I am attempting to repair a bricked Asus X53SV notebook (Asus K53SV board) by reflashing with flashrom from a Raspberry Pi. I've got it all hooked up and flashrom recognizes and reads the chip. However, I cannot determine what type of file the BIOS update is that I downloaded from Asus support site. The update I'm using is K53SVAS.315 for Aptio's Easy Flash. How can I extract the raw BIOS from this file?
After further research, I've determined that the download offered by Asus is not a complete BIOS image file. It cannot be used to reflash the EEPROM directly as it does not contain all of the information required. The built in Easy Flash utility uses this file to update only a portion of the EEPROM. The only officially supported method of repairing a bricked Asus notebook is to send it back to Asus.
I just managed to fix my bricked Asus K53E using instructions from here, yours should be similar. It requires you to download the first part of the flash from the chip and hope that this part is not corrupted.
You have to first dump the bricked flash, then reconstruct the full image by merging it with update file from Asus website using a hex editor as follows:
Reconstructed_Image 0x0 - 0x17FFFF = Bricked_Image 0x0 - 0x17FFFF
Reconstructed_Image 0x180000 - 0x3FFFFF = Update_Image 0x0 - 0x27FFFF
I am using Beaglebone black Rev A.It was running with Debian OS.I was using that in console mode by configuring that with my windows laptop.Today to format my sd card I have accidentally formatted the Beaglebone eMMC. Now when I try to connect it with my laptop it is showing me driver not accepted some error messages.I am new to this.Please help me now how to recover it.
See if below link helps,
http://www.element14.com/community/docs/DOC-67138/l/beaglebone-black-software-image-update-instruction
It has steps for micro SD card as well as eMMC.