November 2, 2020 at 10:56 PM #42557
Here is my .json file: https://gofile.io/d/jBsX1W
It has been working perfectly up until I tried it now, though I haven’t used the profile page since v085.
I don’t get an error message. It just gives me the “import done!” message, but none of the settings show up.
Thanks for the help.November 2, 2020 at 11:36 PM #42559
I have checked the json file but all the settings in the file are just the default ones except the Analog sync LPF setting of profile 0 which has been changed to 10Mhz.
Do you have other json files?November 2, 2020 at 11:41 PM #42560
Seems I must have messed up and overwritten my .json file with an empty profile. Thanks for confirming, that’s a huge bummer.
But at least it’s not the profile page 🙂November 2, 2020 at 11:46 PM #42561
If you need your settings back on the OSSC then you can flash back to firmware 0.85. If you haven’t saved or imported any settings on the newer firmware then your settings will still be there so you can copy them to the profile editor.November 2, 2020 at 11:50 PM #42563
I’m not sure if I follow, but I have indeed not updated my OSSC from 0.85 yet, and the settings are stored on the OSSC.
How can I export the profiles from my OSSC unto a .json file?November 2, 2020 at 11:57 PM #42564
Oh you are still on firmware 0.85. I thought you already updated to 0.88 and lost all your settings.
I meant manually copy them over by hand. There is currently no way to export from the OSSC.November 3, 2020 at 12:09 AM #42567
Alright, got ya! Hopefully an easier way to save and transfer settings across firmware updates can be implemented with the OSSC Pro.
I appreciate the assistance!November 11, 2020 at 1:40 PM #42760megariParticipant
@paulb_nl, it would be awesome if the web app gained support for importing a binary settings image, exported from the OSSC. I realize it is a feature only rarely needed given the very existence of the web app, but it could be useful in cases where the only copy of the settings are on the OSSC unit itself. Would you kindly consider implementing this, please? 🙂November 11, 2020 at 1:52 PM #42761
That is a great suggestion, would be a very welcome addition.November 13, 2020 at 8:38 PM #42810
@megari Well I have to now. 😛 I have started working on adding binary import support. Thanks for adding the exporting ability to the OSSC.
Is there any program that can easily read 1MB from an sdcard to a file? Most programs just read the entire sdcard size I think.
I suppose it can be done with HxD editor but it is probably too complicated for most people.November 14, 2020 at 3:39 PM #42825uchristoParticipant
dd if=/dev/mmcblk0 of=anyfile.img bs=1M count=1November 15, 2020 at 10:24 PM #42850November 16, 2020 at 2:57 PM #42858uchristoParticipant
How about saving a small bash script? The user once needs to adjust the blockdevice
#/bin/bash FILE=profile_backup_<code>date +"%Y%m%d"</code>.img dd if=/dev/mmcblk0 of=$FILE bs=1M count=1November 16, 2020 at 6:31 PM #42864megariParticipant
@uchristo While using dd is an elegant approach (there are Windows versions available, it seems), the tool is a bit too powerful to recommended to the uninitiated, except in carefully specified and controlled circumstances. A bash script is a step in that direction, but there are still parameters the user might need to change for their system, and therein lies the danger.
@paulb_nl The binary import seems to work fine, assuming the SD card has been read starting from sector 1 (offset 512), where the OSSC begins writing to it. The first sector is reserved for any potential future metadata/CRCs.
I am working on an improved export feature, where a minimal FAT16 filesystem is written on the SD card. No promises yet, though.November 16, 2020 at 7:17 PM #42865
For windows I found that you can use Win32 Disk Imager and just click read and cancel quickly and the first few MBs should have been read 🙂
Can you make it so that exporting also writes the header? Currently the web app produces bin files with a zero filled 512 byte header because the OSSC requires it for importing. So it would be nice if the exported file from the OSSC also has a header.
The app shows an error if the header starts with “OSSC” because it assumes the user drag & dropped a OSSC firmware.
If exporting also writes the header then the bin files for importing and exporting both have a header and then I can make the web app just always skip the first 512 bytes. Currently it only starts reading at 512 offset if the header starts with zeros.
- You must be logged in to reply to this topic.