Jump to content

Chridster1

Members
  • Content Count

    21
  • Joined

  • Last visited

Community Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Morning all, I tried to compile on the TB and it failed to boot again.
  2. It failed to compile on the TB /bin/sh: 1 : lz4c: not found so done sudo apt-get install lz4 and that error went away, might be an idea to add that as a requirement on https://github.com/TinkerBoard/TinkerBoard/wiki/Developer-Guide#kernel-44 Cheers
  3. Hi @tooz Sorry for the late reply, I've been on holiday and only just got back to this now. I've noticed that the new version of Tinker OS https://dlcdnets.asus.com/pub/ASUS/Embedded_IPC/Tinker Board 2/Tinker_Board_2-Debian-Buster-v2.1.6-20220503.zip won't boot once we've made the changes to the kernel as above and flashed. I haven't tried compiling on the Tinkerboard which is my next move. The older version of Tinker OS https://dlcdnets.asus.com/pub/ASUS/Embedded_IPC/Tinker Board 2/Tinker_Board_2-Debian-Buster-v2.0.4-20211222.zip will allow me to update the kernel. I'll let you know how compiling on the TB works out Thanks
  4. Hi @tooz, It's done something cause when I run the following linaro@linaro-alip:/sys/bus$ dmesg|egrep -i 'can0|can1|mcp' [ 2.381288] mcp251x spi1.0: Looking up vdd-supply from device tree [ 2.381301] mcp251x spi1.0: Looking up vdd-supply property in node /spi@ff1d0000/mcp2515@0 failed [ 2.381328] mcp251x spi1.0: Looking up xceiver-supply from device tree [ 2.381339] mcp251x spi1.0: Looking up xceiver-supply property in node /spi@ff1d0000/mcp2515@0 failed I can see the mcp251x output which it hasn't done before. I'll ask our hardware guys to check the pins are wired as above and let you know. Thanks again for the help Chris
  5. Fantastic tooz, Sorry for the confusion. I'll give the above a go now. I2C does work fine on the TB so if I can get SPI then you've made my weekend.
  6. Hiya, sorry yeah the title is wrong, It mentions SPI in the actual body. Can I ammend the title? Cheers
  7. Morning Forum! I have the Tinkerboard 2S and am running Tinker OS v2.0.4. We have a Microchip MCP2515 SPI ( https://ww1.microchip.com/downloads/en/DeviceDoc/MCP2515-Stand-Alone-CAN-Controller-with-SPI-20001801J.pdf ). I've recompiled the kernel and enabled CAN over SPI linaro@linaro-alip:~$ dmesg | grep -i can: [ 2.368374] vcan: Virtual CAN interface driver [ 4.476074] can: controller area network core (rev 20120528 abi 9) [ 4.486845] can: raw protocol (rev 20120528) [ 4.491137] can: broadcast manager protocol (rev 20120528 t) [ 4.496819] can: netlink gateway (rev 20130117) max_hops=1 Has anyone got this working? Everything I see seems to be for the Raspberry pi and doesn't work on TB2S Many thanks
  8. Hi @bozhidartonchev, We have been working on this but have too failed. I've had some success recompiling the kernel manually though. We wanted to develop something using BuildRoot or Yocto but support seems to be lacking. 😕
  9. Hi @tooz Has your development team come back to you about developing BSPs etc for the TS?
  10. So after adding the brackets to the code it does compile and creates the files but when I burn them to SDCard it fails to boot. I've attached the files where the compler fails as a diff I fell like it's close now, it could be adding the brackets is syntatically correct but semantically wrong. Cheers completed_diffs.diff
  11. Good and bad news, It got further but the compilation process died with So looks like its a similar thing
  12. Morning @tooz We've found that kernel/drivers/mfd/fusb302.c Lines 1570 were as follows if (conditions != -(EINPROGRESS)) \ chip->vdm_state = VDM_STATE_ERR; \ chip->vdm_pending = false; \ The compiler threw a warning because the third line ( chip->vdm_pending = false; ) was indented as though it was gaurded, we've added brackets around the two lines ( see below ) and we can now get past that error and continue to compile. I'm waiting to see if it completes now if (conditions != -EINPROGRESS) {\ chip->vdm_state = VDM_STATE_ERR; \ chip->vdm_pending = false; \ }\ Is the second code above correct? Or should I remove the indentation for the chip->vdm_pending = false; Many thanks
  13. I've re-tried to build linux4.19-rk3399-debian10 with the following and it gets a lot further, it does however die on the fusb drivers with the following. Any ideas about this? drivers/mfd/fusb302.c: In function 'auto_vdm_machine': drivers/mfd/fusb302.c:1570:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] error, forbidden warning:fusb302.c:1570 1570 | if (conditions != -EINPROGRESS) \ | ^~ drivers/mfd/fusb302.c:1584:17: note: in expansion of macro 'AUTO_VDM_HANDLE' 1584 | AUTO_VDM_HANDLE(vdm_send_discoveryid, chip, evt, conditions); | ^~~~~~~~~~~~~~~ drivers/mfd/fusb302.c:1584:55: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1584 | AUTO_VDM_HANDLE(vdm_send_discoveryid, chip, evt, conditions); | ^~~~ drivers/mfd/fusb302.c:1572:25: note: in definition of macro 'AUTO_VDM_HANDLE' 1572 | chip->vdm_pending = false; \ | ^~~~ drivers/mfd/fusb302.c:1570:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] error, forbidden warning:fusb302.c:1570 1570 | if (conditions != -EINPROGRESS) \ | ^~ drivers/mfd/fusb302.c:1587:17: note: in expansion of macro 'AUTO_VDM_HANDLE' 1587 | AUTO_VDM_HANDLE(vdm_send_discoverysvid, chip, evt, conditions); | ^~~~~~~~~~~~~~~ drivers/mfd/fusb302.c:1587:57: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1587 | AUTO_VDM_HANDLE(vdm_send_discoverysvid, chip, evt, conditions); | ^~~~ drivers/mfd/fusb302.c:1572:25: note: in definition of macro 'AUTO_VDM_HANDLE' 1572 | chip->vdm_pending = false; \ | ^~~~ drivers/mfd/fusb302.c:1570:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] error, forbidden warning:fusb302.c:1570 1570 | if (conditions != -EINPROGRESS) \ | ^~ drivers/mfd/fusb302.c:1590:17: note: in expansion of macro 'AUTO_VDM_HANDLE' 1590 | AUTO_VDM_HANDLE(vdm_send_discoverymodes, chip, evt, conditions); | ^~~~~~~~~~~~~~~ drivers/mfd/fusb302.c:1590:58: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1590 | AUTO_VDM_HANDLE(vdm_send_discoverymodes, chip, evt, conditions); | ^~~~ drivers/mfd/fusb302.c:1572:25: note: in definition of macro 'AUTO_VDM_HANDLE' 1572 | chip->vdm_pending = false; \ | ^~~~ drivers/mfd/fusb302.c:1570:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] error, forbidden warning:fusb302.c:1570 1570 | if (conditions != -EINPROGRESS) \ | ^~ drivers/mfd/fusb302.c:1593:17: note: in expansion of macro 'AUTO_VDM_HANDLE' 1593 | AUTO_VDM_HANDLE(vdm_send_entermode, chip, evt, conditions); | ^~~~~~~~~~~~~~~ drivers/mfd/fusb302.c:1593:53: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1593 | AUTO_VDM_HANDLE(vdm_send_entermode, chip, evt, conditions); | ^~~~ drivers/mfd/fusb302.c:1572:25: note: in definition of macro 'AUTO_VDM_HANDLE' 1572 | chip->vdm_pending = false; \ | ^~~~ drivers/mfd/fusb302.c:1570:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] error, forbidden warning:fusb302.c:1570 1570 | if (conditions != -EINPROGRESS) \ | ^~ drivers/mfd/fusb302.c:1596:17: note: in expansion of macro 'AUTO_VDM_HANDLE' 1596 | AUTO_VDM_HANDLE(vdm_send_getdpstatus, chip, evt, conditions); | ^~~~~~~~~~~~~~~ drivers/mfd/fusb302.c:1596:55: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1596 | AUTO_VDM_HANDLE(vdm_send_getdpstatus, chip, evt, conditions); | ^~~~ drivers/mfd/fusb302.c:1572:25: note: in definition of macro 'AUTO_VDM_HANDLE' 1572 | chip->vdm_pending = false; \ | ^~~~ drivers/mfd/fusb302.c:1570:17: warning: this 'if' clause does not guard... [-Wmisleading-indentation] error, forbidden warning:fusb302.c:1570 1570 | if (conditions != -EINPROGRESS) \ | ^~ drivers/mfd/fusb302.c:1599:17: note: in expansion of macro 'AUTO_VDM_HANDLE' 1599 | AUTO_VDM_HANDLE(vdm_send_dpconfig, chip, evt, conditions); | ^~~~~~~~~~~~~~~ drivers/mfd/fusb302.c:1599:52: note: ...this statement, but the latter is misleadingly indented as if it were guarded by the 'if' 1599 | AUTO_VDM_HANDLE(vdm_send_dpconfig, chip, evt, conditions); | ^~~~ drivers/mfd/fusb302.c:1572:25: note: in definition of macro 'AUTO_VDM_HANDLE' 1572 | chip->vdm_pending = false; \ | ^~~~ make[2]: *** [scripts/Makefile.build:334: drivers/mfd/fusb302.o] Error 1 make[2]: *** Deleting file 'drivers/mfd/fusb302.o' make[1]: *** [scripts/Makefile.build:637: drivers/mfd] Error 2 make: *** [Makefile:1195: drivers] Error 2
  14. Hi @tooz I've tried installing Ubuntu on AWS and going through the instructions and it fails to compile and I've tried with Debian as per the instructions and it dies again. That's 3 different OSs that fails to compile the code. Is there any plans for Asus to create any sort of BSPs or meta-layers for the TB2S? I saw ths https://tinker-board.asus.com/forum/index.php?/topic/14960-yocto-tinkerboard-meta-rockchip/ post but it never got any answers that was back in 2021 so is probably a dead topic now. Ideally I'm looking for a meta layer provided by Asus tested against the latest LTS version of Yocto ( https://wiki.yoctoproject.org/wiki/Releases ) currently Kirkstone. Is this something that is in the Pipeline or what's available is as good as it gets? Many thanks
  15. Hi @tooz My build environment is openSuSE Leap 15.3 with all the build tools installed listed above. Good news is When I try kernel 4.19 I can build the first part, well it errored at first because.... Should in-fact be make ARCH=arm64 tinker_board_2_defconfig Unfortunetly the next command stills errors with I'm using gcc (SUSE Linux) 7.5.0 The defconfig listed above, do you think that could work if I use it in Buildroot? Also will Asus be creating Board Support Pacakges for the tinkerboard 2S? Thanks for the help thus far Chris
×
×
  • Create New...