I don’t know anything about software installation. What should I do next after I finish making sangaboard V0.5? Are there any detailed steps to teach me how to do it step by step?
GitLab also mentioned
The Sangaboard v0.5 has a rpi2040, like the Raspberry Pi Pico board. The Sangaboard has a USB_BOOT button to put the board in bootloader mode as with a normal Pico. I always have to look up exactly how to do that on a Pico. Then you just need to copy the .uf2 firmware file onto the Sangaboard.
The current firmware is not well signposted. I think the version at Index of /sangaboard/sangaboard-firmware/v1.0.3-dev/ will be what you need.
Some pictures of your Sangaboard would be nice to see.
I think you can always get up-to-date versions of the firmware from here:
But it would be good to have some better instructions, and better documentation about the other features of the board such as how to connect up endstops or other I2C components.
Thank you for your reply. I don’t know anything about the software. It would be better to have a specific step with a picture description. But thank you very much.
When you say you ‘made’ the board, where did you get it from?
(When I got mine, the instructions were confusing, and it was unclear what I needed to do on the firmware side of things, but it turned out it already had the right firmware, and I didn’t need to do anything.)
This is something I made myself. The soldering of the chip is a bit difficult, but I don’t know anything about firmware. I want to know what to do next. Can you tell me how to do it specifically?
This is the picture after I connect it directly to the USB. Are there two files in the folder that need to be deleted? Then copy the firmware into this folder?
Soldering that chip yourself is a real challenge!
You do not need to delete any files, just drop the Sangaboard ‘uf2’ file into the external drive that appears when you plug in the Sangaboard in Bootselect mode.
The file will transfer and the board should then disconnect itself.
There should be something wrong with my board. When I put the firmware into the folder, it did disconnect itself, but the drive soon appeared again.
Hmmm. You could try a known basic .uf2, something like the Pico ‘blink’ code. If that works it suggests that the Sangaboard .uf2 is not the right one. I can also check the .uf2 later on a board I have.
If ‘blink’ loads then that unfortunately points to a physical problem with the board. There is no LED to blink on Sangaboard, but you seem to be having an issue with the actual load.
@filip.ayazi might have some ideas.
This seems like an issue with the flash, check that those connections are correct. After loading the firmware it will disconnect and reboot. It should try to load from the flash (if the usb boot button is not pressed) and if that fails it will go back to th firmware upload mode which seems to be happening here.
1 Like
If the Sangaboard is faulty, will it affect the failure of the camera? My camera and the stage are not connected.
No, the camera is completely unrelated to the Sangaboard.
Thank you for your reply. I’m going to buy another V2 camera module to try.
The camera is not connected, what is the problem?
WARNING: Requested an LST from a non-PiCameraStreamer camera
Camera connection problems can be because of the cable. It is easy to crack the wires without it being obvious that the cable is damaged. Seating the cable in the connectors also needs care. The camera cannot be connected or disconnected when the Pi is running, make sure that you shut it down first.
I don’t recognise the exact error message that you have. It could be a communication problem (cable), it could also be an incompatible camera board. Because of the way in which the camera is integrated into the Openflexure software (server version 2) it will only work with a Pi camera v2. Any other Pi camera will not work, and a nominally equivalent camera from a different manufacturer will also probably not work.
Lastly it could be the actual Pi software. It is not uncommon for odd effects to be caused by problems with the SD card. Reinstalling the Openflexure operating system is often worth trying.
Is the V2 camera different from the V2.1 camera? I bought another v2.1 version, but it does work, but why doesn’t V2 work?
Is there a directly installable version of the macos client of OpenFlexure Connect? It seems that it hasn’t been updated for a long time.
I think that building a directly installable version of Openflexure Connect for macos is still a problem. You can easily work without Connect, all it actually does is to search for local microscopes and open browser windows. If you have one microscope on a local network, then you can access it from any browser at microscope:5000 or microscope.local:5000. Whether the .local is trimmed from the address depends on the network.
If you have more than one microscope then with Connect you can see the names each one takes, and which is which. Without it you will need to find the IP address of each microscope and use that with :5000 in a browser window.