I have just get a new sd card preinstalled with noobs, now i am thinking where must be something wrong, because it fail with wolfram egnine and some other stuff.
Is it possible to make a recovery of something on the sd card. I don't know about filesystem and commands.
I think I got it.
I hold shift down while booting. But I tought there would be more os to choose from I only got rasbian.
Thanks.
Related
Is it possible to work at Raspberry Pi Pico using Windows 10? My question specified is: do I have to install any Linux distro, for example Raspbian, to be able to work at it? Do I also need to use SD card to work with it?
Just want to receive feedback, cause I'm confused and also kinda new to embedded systems
I may share my experience so far, I'm not an expert and this list does not claim to be complete at all.
The pi pico can be programmed by using
Picomite Basic (found here: https://geoffg.net/picomite.html) which doesnt need anything installed on the PC except a terminal program (I am using Tera Term)
MicroPython (never used it myself, afaik Thonny - found here: https://thonny.org/ is the preferred IDE )
C/C++/ASM This is what I am using, the SDK is available for Windows, Linux and Raspbian (MacOS maybe too?), an excellent guide on how to install it and how to use it is found here: https://datasheets.raspberrypi.com/pico/getting-started-with-pico.pdf
Arduino The Pico can even be used as an arduino device too, a good point to start is here: https://github.com/earlephilhower/arduino-pico
Keep in mind, that the interpreted languages (basic and python) are easier to handle (no big SDK or framework need to be installed on the PC, copying code to the pico is a relative easy step) but at a cost of speed. If you need a lot of cpu power, compiled languages are by far the better choice
To answer your questions, yes, no, and no. You should be able to get going on Windows 10 with just the raspberry pi pico and a micro USB to USB cable.
I got started with mine this weekend - seeing the on-board LED blink finally made me so happy.
The official getting started guide pointed me at this script for getting started on Windows.
It set up docs, examples, visual studio code, and more for me. Between its README and chapter 9 of the getting started guide ("Building on MS Windows"), I was able to get my little light blinking :)
Good luck to you on your embedded journey!
As an alternative, an in addition to #Tommylee2k's helpful insights, you can develop and run Python software for a Pico with absolutely no software needing to be installed on a Windows PC.
At its most basic level, you press the BOOTSEL switch and insert the Pico's USB cable into your PC, and the few MB of space on the Pico appear in your Windows File Explorer as a USB disk drive.
You then write your microPython software using any text editor you prefer. All these general purpose modules are available. And all these Pico-specific modules are available.
You then copy (drag and drop) your Python script to the Pico disk drive and save it as main.py.
The Pico will then run that script on every subsequent power-up. Of course you can re-attach the Pico to your PC and edit the file at a later date.
That is adequate and simple enough. If you want a REPL and friendly editor and console logging and other developer-friendly features, you can install Thonny for free and code more effectively but it is not actually absolutely necessary. It's a bit like driving a car without ABS, without an automatic gearbox and without aircon - it can get you from A to B without problems but there are easier and more comfortable methods.
I wanted to install raspberry pi os and as I was flashing my SD card with the official raspberry pi imager software it gives me the error, "verifying write failed. Content of the SD Card is different from what was written to it." I tried formatting the SD card and flashing it again but it still gave me the same error. How can I get around this?
The issue is most likely your SD card, I would suggest trying a different card.
I am also facing these type of error "ERROR WRITING TO STORAGE". When, I buy new SD card and write on it so they also give the same error , So I can check the actual problem is that to change the Card reader or USB Port so my problem is solved.
So Guys , First check the Card reader.
Thanks,
Gaurav
I just fixed it by using an USB Port on the back of my PC instead of the front. I used a Micro-SD-Card to USB adapter.
I just started working with a Beagle Bone Blue and I have installed the necessary drivers however when I go to http://192.168.7.2/, it say the site cannot be reached because it took too long to respond. I would really appreciate it if someone would help be. Thanks!
I think the kernel image you are using in BeagleBone Blue must be properly booted in the board or if you are using eMMC0 for booting the board,
Check the kernel logs of booting using minicom in Linux or putty/Terraterm in Windows.
Also, check if there is one folder creating as BeagleBone(Getting Started) in Windows after proper booting done.
If you are using Linux, check the same type of folder and verify the internet connectivity.
Try to use new kernel image available from https://beagleboard.org/latest-images
Boot it using sd Card and flash it on the board.
Then, try 192.168.7.2 in the browser.
It will be working if you follow the proper steps.
I hope it helps.
On my Raspberry Pi I am trying to create a symbolic link for a device plugged into the USB port. I have done this before and it worked just fine, but recently I re-flashed the Pi's SD card to start from a clean slate again and now the Symbolic link does not work. I can see it in (/dev/GPS), but when I go to use it nothing happens. To the best of my knowledge I have set it up in exactly the same way. More info on the setup below.
The device in question: Its a Ublox 6M GPS connected to the PI's USB via an FTDI. Because the Pi can assign the FTDI to either /dev/ttyUSB0 or /dev/ttyUSB1 as it sees fit at boot, I need to assign it a symbolic link so my program can always find it irrespoective of what name the OS wants to give it.
So I followed the instructions here to set up the symbolic link. I added the following line to /etc/udev/rules.d/10-local.rules.
ACTION=="add", ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="GPS"
These are the same instructions I followed originally (pre SD card re-flash) and they worked just fine, but now it doesn't work. I have tested the GPS/FTDI by using its OS assigned name and I can get GPS data out, but when I use my symbolic link name it does't work. So that is where the problem seems to be. I've triple checked the idVendor and idProduct values for the FTDI using
udevadm info -a -p $(udevadm info -q path -n /dev/ttyUSB0)
Any ideas? Alternative solutions are welcome.
Thanks,
Ben
I think I've found a solution, but not the answer to the specific question. I still don't know why the above it not working, but I have found that I don't need to create my own symbolic links. The system creates is own in /dev/serial/by-id/. These seem to be working OK for me.
I downloaded the hard float image of Raspbian here:
http://www.raspberrypi.org/downloads
I copied the recommended hard-float image on an SD card and the Raspberry Pi boots fine with it.
Then I downloaded the soft-float version of Raspbian because I need it to get some software running that does not work on the hard-float version. I formatted the SD card again, copied the soft-float image onto it and tried to boot the Raspberry Pi with it.
Problem: the Raspbery Pi doesn't boot with the soft-float version of Raspbian!! I see the green "ACT" LED light up for less than a second. After that only the red power LED is on and nothing happens after that.
I repeated this process a couple of times and redownloaded the images, checked the SHA of the downloaded file, etc. It just doesn't work. The hard-float image always boots up (green "ACT" light flashes rapidly like normal).
Any ideas?
Update: If you have a newer Raspberry Pi with Hynix memory then the older versions of Raspbian will not boot. Specifically you'll need at least the 2013-02-09 Debian 7 (Wheezy) build.
See this post.
Now, the 2013-02-09 Wheezy build is a hard-float version, so you can't use that, but you can update the kernel image of your soft-float version which is actually independent of the Linux OS (I'm told that basically the GPU boots the Raspberry Pi, and it runs the ARM as a kind of co-processor). So, you can run rpi-update to update your kernel, and it should be all OK.
There's a bit of a catch-22 if you don't own any of the older Raspberry Pis that will boot the older images--how can you update the OS if the only Raspberry Pi you have is a newer one which won't boot? In your case it sounds like you have access to an older one, so you're OK. For those who don't, maybe someone will eventually post an updated soft-float version, but until then perhaps you can try the following. I haven't; it's just a theory, but at this point you don't have much to lose :-)
Burn the latest Wheezy image (2012-02-09) to an extra SD card
Mount this SD card on Windows
Copy all the files except *gz ones which correspond to the Linux filesystem. Basically, all the boot images and configuration files
Mount the SD card containing your soft-float image and overwrite the boot image files
Hopefully have a beer to celebrate?
Previous post:
Yes, I had this same problem. I don't know exactly what is wrong, but the start_elf image won't boot, at least with the recent set of Raspberry Pis. I can't believe Raspbian would release something that broken, so I suspect it works for some Raspberry Pis, but not others. What you need to do is:
Burn the hard-float copy of Wheezy to an SD card. You're going to snatch off the boot image (which works) and copy it to the soft float one.
Mount the SD card on a Windows machine. The boot partition is FAT, so you'll be able to see it. Look for the file start.elf. Copy it to your Windows machine.
Burn the soft-float copy of Wheezy to an SD card and mount it on the Windows box.
Replace it's start.elf with the copy from your hard-float one.
Crack open a beer and enjoy.
See my related post.
Just image one card with hard-float(Raspbian “wheezy”), and the other
with soft-float(Soft-float Debian “wheezy”). Plug both into a Windows PC and
copy all files (you can see at all) from the hard-float onto the
soft-float card, replacing existing ones.
Explanation: http://www.raspberrypi.org/archives/3534
P.S. You can, of course, copy those files to a temporary folder first,
swap cards and then replace all files on the soft-float card with
those in the temporary folder.
bootcode.bin
start.elf
fixup.dat
From Raspberry Pi SD card with this Soft-float Debian "wheezy" did not want to boot
When you dd the image, make sure bs=1M...
After trying all the things in the other answers, it was finally the way to make it work on a latest Raspberry Pi out of the box. I've actually found this a good help with several Raspberry Pi applications/code.