Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - GeorgeIoak

Pages: [1] 2 3 4
1
Introduce yourself / Re: Router cnc whit cubieboar
« on: November 23, 2016, 01:58:07 pm »
You can only run Mach3 on Windows based computers. On a Raspberry Pi, Cubieboard, or other ARM based boards you can run Linux CNC, Machine Kit, or bCNC.

I have run bCNC on a RPi connected over USB to a Smoothieboard,http://smoothieware.org/smoothieboard


3
Cubieboard v2 Images (A20 Based) / Re: Cubian X1 is out ;)
« on: October 09, 2014, 05:45:51 pm »
Do you have a list of what changes there are?

4
About the forum / Re: Simon please collaborate.
« on: February 27, 2014, 04:26:56 pm »
Sorry Lawrence, I meant no disrespect at all. I know first hand what it takes to maintain a site and reply to people. I only made that comment in the off chance that if people wanted to walk away from it I was willing to help out.

5
About the forum / Re: Simon please collaborate.
« on: February 27, 2014, 03:53:39 pm »
If Simon and Lawrence want to drop out of hosting and administering the forum I can offer my site. I'm hoping this site will continue on but if all else fails I'm offering a backup plan for everyone.

6
Cubieboard v3 Hardware (Cubietruck) / Re: ALSA bit-perfect output
« on: January 16, 2014, 12:15:49 pm »
So the master clock frequency properly changed between 44.1kHz and 192kHz?

We're getting closer to solving the driver issues to support this. I think I might have something to share very soon.

7
Cubieboard v3 Hardware (Cubietruck) / Re: ALSA bit-perfect output
« on: January 15, 2014, 10:22:04 am »
I agree with Nikkov. IF the schematic is correct then the resistors must be changed to pass I2S signals to the header but you can probe on the pad of R182 before making any changes to see if you get a Master Clock signal and you can play different sample rate files and see if the master clock changes correctly.

I think even if you get a signal out for I2S the alsa driver still needs to be modified in order to play 24-bit audio files.

8
Cubieboard v3 Hardware (Cubietruck) / Re: ALSA bit-perfect output
« on: January 14, 2014, 11:45:59 am »
We are still working on this issue to support 24-bit audio files. The drivers need to be modified in order to support this. I've confirmed with Allwinner that in theory the hardware can support this but it was never tested. I had a very brief meeting with them at CES and asked for their support. I'm not holding my breath that we'll get help but I am looking for knowledgeable programmers every day in order to get this resolved.

9
There seems to be a problem with only some CB2 and flashing linaro to NAND. What works is if you first flash an older Android, I used version 1.04 and then you are able to flash the linaro image into NAND.

Here’s what the NAND partitions look like when you flash Android 1.06 (boot from SD Card and inspect the NAND)

Code: [Select]
linaro@cubieboard2:~/sunxi-tools$ sudo ./nand-part
check partition table copy 0: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw311
check partition table copy 1: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw311
check partition table copy 2: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw311
check partition table copy 3: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw311
all partition tables are bad!
check partition table copy 0: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw411
check partition table copy 1: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw411
check partition table copy 2: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw411
check partition table copy 3: mbr: version 0xffffffff, magic ÿÿÿÿÿÿÿÿ
magic ÿÿÿÿÿÿÿÿ is not softw411
all partition tables are bad!
linaro@cubieboard2:~/sunxi-tools$


linaro@cubieboard2:~$ sudo cat /proc/partitions
major minor  #blocks  name

  93        0    3989504 nand
179        0    7761920 mmcblk0
179        1      12288 mmcblk0p1
179        2    3858944 mmcblk0p2
After flashing cb_a20_android42_v1.04_8188eu-ddr432-en_US.img, and booting linaro from the SD Card and ran nand-part again. This time the partitions are read.

Code: [Select]
linaro@cubieboard2:~/sunxi-tools$ sudo ./nand-part
check partition table copy 0: mbr: version 0x00000200, magic softw411
magic softw411 is not softw311
check partition table copy 1: mbr: version 0x00000000, magic
magic          is not softw311
check partition table copy 2: mbr: version 0x00000000, magic
magic          is not softw311
check partition table copy 3: mbr: version 0x00000000, magic
magic          is not softw311
all partition tables are bad!
check partition table copy 0: mbr: version 0x00000200, magic softw411
OK
check partition table copy 1: mbr: version 0x00000200, magic softw411
OK
check partition table copy 2: mbr: version 0x00000200, magic softw411
OK
check partition table copy 3: mbr: version 0x00000200, magic softw411
OK
mbr: version 0x00000200, magic softw411
11 partitions
partition  1: class =         DISK, name =   bootloader, partition start =    32768, partition size =    32768 user_type=0
partition  2: class =         DISK, name =          env, partition start =    65536, partition size =    32768 user_type=0
partition  3: class =         DISK, name =         boot, partition start =    98304, partition size =    32768 user_type=0
partition  4: class =         DISK, name =       system, partition start =   131072, partition size =  1048576 user_type=2
partition  5: class =         DISK, name =         data, partition start =  1179648, partition size =  1048576 user_type=2
partition  6: class =         DISK, name =         misc, partition start =  2228224, partition size =    32768 user_type=0
partition  7: class =         DISK, name =     recovery, partition start =  2260992, partition size =    65536 user_type=0
partition  8: class =         DISK, name =        cache, partition start =  2326528, partition size =   655360 user_type=2
partition  9: class =         DISK, name =      private, partition start =  2981888, partition size =    32768 user_type=0
partition 10: class =         DISK, name =       databk, partition start =  3014656, partition size =   524288 user_type=0
partition 11: class =         DISK, name =        UDISK, partition start =  3538944, partition size =  4194304 user_type=0
check partition table copy 0: mbr: version 0x00000200, magic softw411
OK
check partition table copy 1: mbr: version 0x00000200, magic softw411
OK
check partition table copy 2: mbr: version 0x00000200, magic softw411
OK
check partition table copy 3: mbr: version 0x00000200, magic softw411
OK
mbr: version 0x00000200, magic softw411
11 partitions
partition  1: class =         DISK, name =   bootloader, partition start =    32768, partition size =    32768 user_type=0
partition  2: class =         DISK, name =          env, partition start =    65536, partition size =    32768 user_type=0
partition  3: class =         DISK, name =         boot, partition start =    98304, partition size =    32768 user_type=0
partition  4: class =         DISK, name =       system, partition start =   131072, partition size =  1048576 user_type=2
partition  5: class =         DISK, name =         data, partition start =  1179648, partition size =  1048576 user_type=2
partition  6: class =         DISK, name =         misc, partition start =  2228224, partition size =    32768 user_type=0
partition  7: class =         DISK, name =     recovery, partition start =  2260992, partition size =    65536 user_type=0
partition  8: class =         DISK, name =        cache, partition start =  2326528, partition size =   655360 user_type=2
partition  9: class =         DISK, name =      private, partition start =  2981888, partition size =    32768 user_type=0
partition 10: class =         DISK, name =       databk, partition start =  3014656, partition size =   524288 user_type=0
partition 11: class =         DISK, name =        UDISK, partition start =  3538944, partition size =  4194304 user_type=0
For some reason the PhoenixSuit flash took longer than normal but it did work and I’ve confirmed the image boots and I’m able to use it. Normal flashes take ~3 minutes but this time it took close to 7 minutes to flash the linaro image.

10
Cubieboard v3 Hardware (Cubietruck) / Re: ALSA bit-perfect output
« on: December 12, 2013, 06:27:42 pm »
you probably have to define the pins in the fex file and use the proper mux mode in order to get them to work.

Looking at http://dl.cubieforums.com/pdf/A10 EVB Manual.pdf (A10 developer manual) on p37 it states it supports up to 8 channel, 24-bit PCM in HDMI.

I'm at the point now that I'm thinking this could be related to DMA transfers and the driver code was never written to handle greater than 16-bit data. That's just a guess on my part and a hope that someone who actually knows the code will read this and take a look for us.

11
Cubieboard v3 Hardware (Cubietruck) / Re: ALSA bit-perfect output
« on: December 11, 2013, 11:36:51 pm »
CB1 and CB2 do not have the I2S pins exposed on the header so you cannot access I2S on those boards. I think I read that the CT has I2S brought out to the pins but I don't have that schematic open right now to check.

I've been playing with the source code and recompiling getting mixed results. Everything that I've read says that you should be able to have 24-bit on all ports.

12
Cubieboard v3 Hardware (Cubietruck) / Re: ALSA bit-perfect output
« on: December 09, 2013, 04:55:03 pm »
Where are you guys reading that the A20 doesn't support 24-bit audio? If it can output 24-bit on I2S then it can output 24-bit on other digital outputs. HDMI is carrying I2S signals along with the video so this sounds like a software issue to me.

I'm starting to look into this for both A10/A20 but if anyone has some helpful information I would appreciate since I'm more hardware (Much More) than software!

13
About the forum / Re: Forum Suggestions
« on: December 02, 2013, 12:19:26 am »
I recently installed TapaTalk on my mobile phone which is a nice app to read and respond to forums. It would be nice if this forum was accessible with that app. Here's some info about the app and what is required in order for the forum to be accessed with Tapatalk.

http://tapatalk.com/faq.php

If people use a different app I'd like to know!

14
Tips, Tricks and Guides / Re: Cubian Video Kiosk with Mplayer on CB2
« on: December 02, 2013, 12:10:39 am »
I have seen that and plan on the final version not loading and checking the network connection. I see a fair amount of kernel messages so turning those off will help. I haven't messed with this stuff in over 6 months and even then I wasn't a programmer!

If "we're" crating a kiosk type platform my goal is make a super fast boot with a system that doesn't look like it's booting a computer.

15
Tips, Tricks and Guides / Re: Cubian Video Kiosk with Mplayer on CB2
« on: December 01, 2013, 06:52:20 pm »
But since I've already rebooted I'm not able to issue any sudo commands. Do you happen to know a way in?

I took the SD Card out and on another system issued
Code: [Select]
sudo visudo -f /media/cubieboard/etc/sudoers
and added
Code: [Select]
cubie   ALL=(ALL:ALL) ALL
Probably not the safest thing to do but I just wanted to get the system up so I could do some testing.

For those new to slim the file you need to change is
Code: [Select]
sudo nano /etc/slim.conf
and don't forget to remove the # in front of default user and auto_login

Next up is to try and trim things to speed up the boot. Any helpful advice would be appreciated.

 

Pages: [1] 2 3 4