Rock64 (armv8/64bit): failing on ASIInitCamera

gulinux

Hi,

I recently purchased an ASI183MM mono and a Rock64 board, that I'm using together with a EFW mini (connected on the ASI camera hub) and INDI.

When I use a 64bit distro (ayufan ubuntu 64bit or armbian), as soon as I connect the camera the INDI driver freezes, and get the following error on the kernel log:


Sep 13 08 rock64 kernel: Unhandled fault: alignment fault (0x92000021) at 0x000000559a47669c

Adding a few debug logs to the INDI driver, I can see that ASIOpenCamera completes successfully, but it hangs on ASIInitCamera call.

Using a 64bit kernel on a 32bit distro does seem to work relatively fine, although it still seem a bit unstable (I have to do a few more tests).

However, I really would love to solve this issue, as the 32bit version is available only for the ayufan distro, which seems slightly more unstable, particularly on network connections.

Thanks,

Marco

chad

Hi Marco，

Your page is so awesome!

I think you can enable the debug log of our camera to find out the true reason.

In your home directory, there is a hide directory called .ZWO, And it has a ASIConfig.xml. Edit it.

Find your camera, and change the DebugPrint value from 00 to 01.

During these operation, please close the application. if not, your modify will be overwritten.

chad@zwo-H310M-S2:.ZWO$ pwd

/home/chad/.ZWO

chad@zwo-H310M-S2:.ZWO$ ls

ASIconfig.xml

chad@zwo-H310M-S2:.ZWO$ cat ASIconfig.xml

<?xml version="1.0" encoding="UTF-8" ?>

<ASI183MM-Pro>

.......

......

</ASI183MM-Pro>

</software>

Then you should get the SDK's log. This will help me figure out what's causing it.

Thanks

Chad

gulinux

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

chad

HI，

please run 'cat /sys/module/usbcore/parameters/usbfs_memory_mb' to make sure the result is 200。

If not, I think it might be the problem.

Thanks

Chad

gulinux

Hi,

I can already open the camera without root (INDI installs the rules automatically), and usbfs_memory_mb shows 200 as you suggested. Still seeing the issue. It's quite weird that it always happens after 17/18 frames :\

I tried also different bandwidth settings (60, 80 and auto).

chad

Hi Marco,

What happens when it's unstable?

If you're still using the Internet, maybe you can try a wired network. Wireless and USB overlap in frequency.

Thanks

Chad

gulinux

It just hangs, INDI shows that exposure control is still busy. I guess it's waiting for the image to be ready from the SDK APIs.

I'll try this evening using eth0 only, right now I'm at work. It might be hard to use the board via eth only though, I hope to find some workaround if that's really the issue...

gulinux

Thanks for the suggestion, but using ethernet only doesn't seem to help at all :(

chad

Hi，

Can you do a test with other program? Like use the ASICap for Linux.

If it also have problems, I think it should be the OS's problem. Then we can decide what to do next. If it works fine, I think it should be the INDI's problem. Maybe we can ask INDI for help.

And Please email to me: chad.cao(at)zwoptical.com , It is more convenient then forum.

Thanks

Chad

rejogc

Hello, I'm also experiencing failures after ASIInitCamera on a Rock64 running Ubuntu 18.04 and SDK V1.13.0821. My result is a 'Bus error' message. Here is a result from dmesg | tail:

Unhandled fault: alignment fault (0x92000021) at 0x00000000353520ec

Unhandled fault: alignment fault (0x92000021) at 0x000000002b6940dc

Unhandled fault: alignment fault (0x92000021) at 0x00000000010eae0c

usb 2-1: USB disconnect, device number 5

usb 4-1: new high-speed USB device number 4 using xhci-hcd

usb 4-1: New USB device found, idVendor=03c3, idProduct=290f

usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

usb 4-1: Product: ASI290MM Mini

usb 4-1: Manufacturer: ZWO

Unhandled fault: alignment fault (0x92000021) at 0x000000003bd5032c

The unhandled faults are from trying to call ASIInitCamera. The usb messages are from me pulling the camera from one usb to another. When I run this code on an Intel PC there's no problem.

gulinux

chad wrote:
Hi，

Can you do a test with other program? Like use the ASICap for Linux.

If it also have problems, I think it should be the OS's problem. Then we can decide what to do next. If it works fine, I think it should be the INDI's problem. Maybe we can ask INDI for help.

And Please email to me: chad.cao(at)zwoptical.com , It is more convenient then forum.

Thanks

Chad

Hi!

I was about to use the email, much more convenient, as you suggested, but maybe it's still better to use the forum for now, since there's someone else experiencing exactly the same issue, it might be of help.

I haven't tried ASICap yet, I will as soon as possible, however it doesn't look like an INDI problem, it just fails on the very first instructions (ASIInitCamera).

It's either a problem in the kernel, or possibly the SDK. I read that the "alignment fault" problem is usually due to a bad/unchecked cast, maybe there's some pointer in the arm64 architecture that doesn't have the same size you expect, maybe could you check if there's any cast inside ASIInitCamera, and that you do the proper pointer size checks?

@rejogc I guess you tried an arm64 distro as well (bionic?). I had better results with the 32bit version. The latest xenial build also seems to work fine, at least for a while (https://github.com/ayufan-rock64/linux-build/releases/tag/0.6.35).

Yesterday I had a full run of ~10000 shots. Today it fails as well, but it might indeed be due to the fact that I switched to wifi this morning (or maybe it's just a very randomic issue, which is quite likely at this point).

Are you able to try other images as well?

chad

Got it, I will test it with a ROCK64 board on my side.

Thanks

Chad

rejogc

@gulinux I'm using Bionic now but I'm going to try the Debian flavors on the Pine64 site. I'm fine with the 32 bit distros if the usb3 speed is there. Maybe that's the way to go for now till the sdk issue works itself out.

gulinux

rejogc wrote:
@gulinux I'm using Bionic now but I'm going to try the Debian flavors on the Pine64 site. I'm fine with the 32 bit distros if the usb3 speed is there. Maybe that's the way to go for now till the sdk issue works itself out.

Well, the speed *is* there. The weird issue though is that I can run a batch of test images (a few thousands) just fine after the first time I install the system, and after that first time, any new sequence stops around 14/18, giving the

usb 5-1: usbfs: usb_submit_urb returned -12

xhci-hcd xhci-hcd.9.auto: Ring expansion failed

error (basically, an out of memory).

I suspected it was my acquisition program at first, but I tried another one, and it still fails the same.

@chad I just looked into trying ASICap, but that's only for x86/x64, not for arm

gulinux

I just did another (remote) test, I noticed that the default installed kernel is a 4.4, but there were more up to date kernels available (on my xenial 16.04, 4.17).

Ran

sudo apt install linux-image-4.17.0-rockchip-ayufan-217-gd02e6236

And apparently it did the trick.

I still have to confirm what happens on the 18.04 version, both 32 and 64 bit, and that it actually works long term, but at least I have a usable configuration now :)

@rejogc does this help you as well?

@chad: one curiosity: apparently setting USB bandwidth too high seem to hang the exposure (on INDI it loops times and times again).

This is not exactly an issue (client should be handling this, and setting bandwidth too high on a power limited board is expected to fail at some point), but I was wondering how does the SDK automatically calculate the bandwidth when the AUTO flag is set (which seems to solve the issue)?

rejogc

@gulinux, Nope that didn't work for me. Maybe it's because my starting point is Ubuntu 18.04 Bionic minimal 64bit Image . You've said you are using a Xenial build. Then you upgraded the kernel from 4.4 to 4.17 no? I'm trying to see if I can replicate your results -- then I would be happy.

@chad, any luck with rock64 testing?

chad

Sorry for the late reply. We have a holiday。

I will try it this week. Please keep in touch.

Thanks

Chad

rejogc

Good news. The SDK works on Debian Stretch. I used this image from the ayufan-rock64 repository:

https://github.com/ayufan-rock64/linux-build/releases/download/0.7.9/stretch-minimal-rock64-0.7.9-1067-arm64.img.xz

My test program just does the following calls:

ASIGetNumOfConnectedCameras

ASIGetCameraProperty

ASIOpenCamera

ASIInitCamera

ASICloseCamera

I will try a few more of those distros and report back

chad

Hi all,

We solved this problem. :)

It is a compilation problem. we need to recompile the SDK.

And we will release a new SDK in recent days, this problem will be fixed in it.

Thanks

Chad

gulinux

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.