-
Notifications
You must be signed in to change notification settings - Fork 64
what is wrong with my arduino101? #1809
Comments
have you tried building native zephyr apps and flash them to both x86 and ARC processors separately, and see if you can get that up? For example, if you build a the helloworld app on ARC, and then build the samples/booting/stub app and flash that the x86. At least then it rules out if you have a working board or not. If not, you might try to use the intel A101 recovery tools to flash the original firmware back and then re-flash with Zephyr. |
Yeah, that is interesting that the text line doesn't show up. That does make it seem rather like the ARC image failed to get built or flashed correctly. Possibly it could have to do with the recent changes to ARC build -Os? The version of the ARC image used for ashell probably has more features enabled than usually in your "production mode" builds. I think @jimmy-huang just left but I'll try to talk to him about this tomorrow. |
Do non-ARC apps like just simple Blink.js work OK from ashell? |
Blink.js works fine in Ashell. |
You can flash commit dee11f7 which is prior to the -Os changes and see if you can get ARC working again, if that works, we might need to file bug againist Zephyr because apparently they didn't fix the issue. |
Re-test with commit dee11f7. This issue is still there. |
maybe you can find out which component in ashell that's causing it to not boot, so if you edit src/zjs_ashell.json, and start removing individual components like aio, i2c, or sensor etc, i think these are the only ones that uses the ARC. At least this narrows down to which thing is borking your image. |
another thing you can try is the erase the whole flash filesystem on the a101 using ashell in the cmd prompt, to remove any thing on the FS that could cause the board to boot differently. |
Description
When running ashell on my Arduino101 board, i didn't see
ipm_console0:'Sensor core running ZJS ARC support image'
from/dev/ttyUSB0
, and sensor can't start in ashell. I tried with three arduino101 boards, only one of them met this problem. I have no idea how this happens? and how can I fix it?Test Code
ashell
Actual Result
ashell on bad board:
/dev/ttyUSB0:
/dev/ttyACM0:
Expected Result
ashell on good board:
/dev/ttyUSB0:
/dev/ttyACM0:
The text was updated successfully, but these errors were encountered: