Error is gone.

I'll try to write configuration files and test it properly later this week.
 

On Monday, October 24, 2016 at 6:01:19 PM UTC+2, Schooner wrote:
>
>
> On 24/10/16 15:36, [email protected] <javascript:> wrote:
>
>
> On 24/10/16 15:05, [email protected] <javascript:> wrote:
>
>
> On 24/10/16 14:24, John Erlandsson wrote:
>
> It actually says revision 4.
>
> -------------------------------------------- cat /proc/cpuinfo 
> --------------------------------------------
> processor       : 0
> model name      : ARMv7 Processor rev 4 (v7l)
> BogoMIPS        : 76.80
> Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva 
> idivt vfpd32 lpae evtstrm crc32
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant     : 0x0
> CPU part        : 0xd03
> CPU revision    : 4
>
> processor       : 1
> model name      : ARMv7 Processor rev 4 (v7l)
> BogoMIPS        : 76.80
> Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva 
> idivt vfpd32 lpae evtstrm crc32
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant     : 0x0
> CPU part        : 0xd03
> CPU revision    : 4
>
> processor       : 2
> model name      : ARMv7 Processor rev 4 (v7l)
> BogoMIPS        : 76.80
> Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva 
> idivt vfpd32 lpae evtstrm crc32
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant     : 0x0
> CPU part        : 0xd03
> CPU revision    : 4
>
> processor       : 3
> model name      : ARMv7 Processor rev 4 (v7l)
> BogoMIPS        : 76.80
> Features        : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva 
> idivt vfpd32 lpae evtstrm crc32
> CPU implementer : 0x41
> CPU architecture: 7
> CPU variant     : 0x0
> CPU part        : 0xd03
> CPU revision    : 4
>
> Hardware        : BCM2709
> Revision        : a02082
>
>
> I was rather suspicious about this revision number, or should I say the 
> one which has already been committed.
>
> However it looks like both are valid and relate to the rpi v3  B
> http://elinux.org/RPi_HardwareHistory
>
> Just depends on the manufacturer
>
> Leave it with me for a while and I will set up both revisions as valid for 
> cpu revision 4 and advise when there is
> a package containing it to test
>
>
> https://github.com/machinekit/machinekit/pull/1085 refers
>
> Will take 30 mins to test build, then needs someone to merge it and 2 - 3 
> hours for package builds to complete.
>
> Probably best to check the repo tomorrow for the new built packages.
>
>
> They are just starting to come through
> Seem to recall that the raspbian package is the last to be built
>
> You should be looking for 
> machinekit-xenomai_0.1.1477321845-1mk.travis.master.git7495c33a 
> <http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-xenomai_0.1.1477321845-1mk.travis.master.git7495c33a%7E1wheezy_amd64.deb>
> ~1raspbian_armhf.deb 
> <http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-xenomai_0.1.1477145680-1mk.travis.master.gitc0fff168%7E1raspbian_armhf.deb>
>
> in deb.machinekit.io/debian/pool/main/m/machinekit/
>
> regards
>
>
> <http://deb.machinekit.io/debian/pool/main/m/machinekit/machinekit-xenomai_0.1.1477145680-1mk.travis.master.gitc0fff168%7E1raspbian_armhf.deb>
>  
>
>
>
>
> Serial          : 00000000376aff9f
>
> -----------------------------------------------------------------------------------------------------------
>
> But I get this error in /var/log/linuxcnc.log when trying to load hal_gpio:
> Oct 23 11:00:23 raspberrypi rtapi:0: rtapi_app_main(hal_gpio): -22 Invalid 
> argument
> Oct 23 11:00:23 raspberrypi msgd:0: hal_lib:1854:rt HAL_GPIO: ERROR: board 
> revision 5 not supported
>
>
> This is just because it defaults to 5 if the rev number is not in the list
>
>
>
> I am not worried about breaking my installation. I would like to try and 
> use a buildroot system eventually. Currently just testing.
>
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
> -- 
> website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
> https://github.com/machinekit
> --- 
> You received this message because you are subscribed to the Google Groups 
> "Machinekit" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected] <javascript:>.
> Visit this group at https://groups.google.com/group/machinekit.
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
website: http://www.machinekit.io blog: http://blog.machinekit.io github: 
https://github.com/machinekit
--- 
You received this message because you are subscribed to the Google Groups 
"Machinekit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
Visit this group at https://groups.google.com/group/machinekit.
For more options, visit https://groups.google.com/d/optout.

Reply via email to