Forum - Recent Threads

mipi dsi support

satds — Fri, 03 Feb 2023 04:50:27 GMT

On warp7 board, I am trying to enable mipi dsi display in u-boot, but looks like mipi dsi controller support is not available, can you guide me on that?

Debugging and integration of 3rd party modules in Warp7?

gabustag — Tue, 30 Jun 2020 10:25:31 GMT

Hello,

i would like to know few things.

1. is there a document /video tutorial about " how to debug Warp7"?

2. if i want to add my own 3rd party sensors how can i

1. get low level drivers for the same ( for example SPI, UART) and if it is possible, do we have low level configurator/generator for the same for fast development?

Regards

Addi

How to use CPU-Board only (configuring efuses)

mreif — Tue, 09 Apr 2019 12:01:59 GMT

Hi guys,

i need help to run the CPU-Board without the IO-Board. As far as i understand the situation this does simply not work because the Jumpers on the IO-Board are not present the the CPU-Board goes into serial Bootloader-Mode.

So my solution would be to set the efuses in a way that the board does always boot into emmc except the jumpers are set so that the serial bootloader could be used.

I already broke one board by setting the wrong fuses and i would like some help an the matter.

So far i found out that the the documentation on the fuses can be found here: IMX7DRM but i have trouble understanding it correctly.

I also know that i can burn the fuses in u-boot with the command "fuse prog".

Can someone tell me which fuse i would have to burn and how the excat command would look like?

Thank you very much!

Warp 7 Expansion Ports

orenrocco — Wed, 03 Apr 2019 14:14:21 GMT

How do I access the access the expansion ports, are they GPIOs, and in addition what are their addresses?

Please help ASAP

Is there any way to get non Allegro .brd layout design files for the WaRP 7 development board?

caha0068 — Fri, 07 Dec 2018 15:24:36 GMT

It is impossible to convert and work with the files using an editor that is not Cadence Allegro and that is not very supportive of an open source schema. If we could get an ASCII version at the very least, that would be nice.

USB Mass Storage can't be detected as /dev/sdb

elem2018 — Tue, 28 Aug 2018 08:37:53 GMT

Hello,

I followed the following instructions: (switch 2 is on the low position)

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

For flashing kernel and rootfs, the eMMC space needs to be mounted, we will use uboot ums command for that.

+ expand source view plain

=> ums 0 mmc 0

Checking the emmc device...In most cases the emmc device will be sdb unless you have multiple mass storage device connected to your PC.

+ expand source view plain

$ ls /dev/sd*

After typing ums 0 mmc 0, I can see one USB device (Netchip usb download gadget) is detected in VM Ubuntu 14.04. Dmesg gives the following messages:

...

[ 997.389492] usb 1-1: new high-speed USB device number 2 using ehci-pci

[ 997.649479] usb 1-1: New USB device found, idVendor=0525, idProduct=a4a5

[ 997.649489] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 997.649492] usb 1-1: Product: USB download gadget

[ 997.649493] usb 1-1: Manufacturer: FSL

[ 997.712231] usb-storage 1-1:1.0: USB Mass Storage device detected

[ 997.717282] usb-storage 1-1:1.0: Quirks match for vid 0525 pid a4a5: 10000

[ 997.717444] scsi host33: usb-storage 1-1:1.0

[ 997.725268] usbcore: registered new interface driver usb-storage

[ 997.740037] usbcore: registered new interface driver uas

[ 1020.196637] usb 1-1: reset high-speed USB device number 2 using ehci-pci

[ 4042.905267] hrtimer: interrupt took 11121686 ns

....

it is clear that the usb download gadget is found, but fdisk -l doesn't show the /dev/sdb

$ sudo fdisk -l

Disk /dev/sda: 536.9 GB, 536870912000 bytes

255 heads, 63 sectors/track, 65270 cylinders, total 1048576000 sectors

Units = sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk identifier: 0x000928fe

Device Boot Start End Blocks Id System

/dev/sda1 * 2048 1031798783 515898368 83 Linux

/dev/sda2 1031800830 1048573951 8386561 5 Extended

/dev/sda5 1031800832 1048573951 8386560 82 Linux swap / Solaris

Would you please tell me how can I get the usb download gadget detected as /dev/sdb ?

In Google unfortunately I can't find any solution. Any hint will be appreciated.

Thanks

Elem

Android 5.0 support on WaRP7?

bittobyto — Tue, 05 Dec 2017 18:52:30 GMT

I've read through the user manuals for the WaRP7 and found a section referencing 'Android Testing'. This part of the manual displays images of Android OS running off the WaRP7's LCD module (sold separately). It's stated on the product page for the board that an Android BSP is optional but I've only been able to find fragments of the BSP on the GitHub page. Does anyone know if this is finished and if so which repositories I can find them?

I haven't been able to get the LCD module to display anything as of late so any pointers on how one would get an image file (.img) of Android flashed onto the eMMC of this board I'd appreciate the assistance!

LPDDR3 Routing: Strobe lines longer than clock lines on the same layer?

noeliascotti — Wed, 04 Oct 2017 11:56:33 GMT

Hello! I was analyzing the LPDDR3 routing with the Allegro Free Physical Viewer. I saw weird things... There are strobe lines longer than clock lines, for example strobe0 836 mils and clock 413 mils on the same layer L4. I understand that max strobe length is clock length - 10 mils.

There is one address line with 273 mils and another one with 434 mils on the same layer L2.

I don't understand this, how is it possible?

How to enable camera module ov5640 drivers and display in warp7

vinod@vinay — Mon, 19 Jun 2017 12:57:07 GMT

Hi,

I am new to the warp7 So I just configured the configurations in menuconfig Tool as provided information in the attached reference document but I am getting the errors while building the image. Find the attachment for reference guide and error logs are as below. So please help me how to make it work.

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

ERROR: linux-warp7-4.1-r0 do_compile: oe_runmake failed
ERROR: linux-warp7-4.1-r0 do_compile: Function failed: do_compile (log file is located at /u/ee209785/yocto1/build/tmp/work/imx7s_warp-poky-linux-gnueabi/linux-warp7/4.1-r0/temp/log.do_compile.2684)
ERROR: Logfile of failure stored in: /u/ee209785/yocto1/build/tmp/work/imx7s_warp-poky-linux-gnueabi/linux-warp7/4.1-r0/temp/log.do_compile.2684
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 2 zImage CC=arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm -fuse-ld=bfd LD=arm-poky-linux-gnueabi-ld.bfd   LOADADDR=0x80008000
|   CHK     include/config/kernel.release
|   GEN     ./Makefile
|   CHK     include/generated/uapi/linux/version.h
|   CHK     include/generated/utsrelease.h
|   Using /u/ee209785/yocto1/build/tmp/work-shared/imx7s-warp/kernel-source as source for kernel
| make[3]: `include/generated/mach-types.h' is up to date.
|   CHK     include/generated/bounds.h
|   CHK     include/generated/asm-offsets.h
|   CALL    /u/ee209785/yocto1/build/tmp/work-shared/imx7s-warp/kernel-source/scripts/checksyscalls.sh
|   CHK     include/generated/compile.h
|   CHK     kernel/config_data.h
|   LINK    vmlinux
|   LD      vmlinux.o
|   MODPOST vmlinux.o
|   GEN     .version
|   CHK     include/generated/compile.h
|   UPD     include/generated/compile.h
|   CC      init/version.o
|   LD      init/built-in.o
| drivers/built-in.o: In function `start_preview':
| vf610_adc.c:(.text+0x1ebf14): undefined reference to `foreground_sdc_select'
| vf610_adc.c:(.text+0x1ebf34): undefined reference to `bg_overlay_sdc_select'
| drivers/built-in.o: In function `stop_preview':
| vf610_adc.c:(.text+0x1ec18c): undefined reference to `bg_overlay_sdc_deselect'
| vf610_adc.c:(.text+0x1ec198): undefined reference to `foreground_sdc_deselect'
| drivers/built-in.o: In function `ioctl_dev_exit':
| vf610_adc.c:(.text+0x1f26bc): undefined reference to `mipi_csi2_get_info'
| vf610_adc.c:(.text+0x1f26c8): undefined reference to `mipi_csi2_get_status'
| vf610_adc.c:(.text+0x1f26e0): undefined reference to `mipi_csi2_disable'
| drivers/built-in.o: In function `ov5640_init_mode':
| vf610_adc.c:(.text+0x1f2ab8): undefined reference to `mipi_csi2_get_info'
| vf610_adc.c:(.text+0x1f2ac4): undefined reference to `mipi_csi2_get_status'
| vf610_adc.c:(.text+0x1f2ad4): undefined reference to `mipi_csi2_get_status'
| vf610_adc.c:(.text+0x1f2ae4): undefined reference to `mipi_csi2_set_lanes'
| vf610_adc.c:(.text+0x1f2b24): undefined reference to `mipi_csi2_set_datatype'
| vf610_adc.c:(.text+0x1f2fb4): undefined reference to `mipi_csi2_dphy_status'
| vf610_adc.c:(.text+0x1f2fcc): undefined reference to `mipi_csi2_dphy_status'
| vf610_adc.c:(.text+0x1f2ff4): undefined reference to `mipi_csi2_get_error1'
| vf610_adc.c:(.text+0x1f300c): undefined reference to `mipi_csi2_get_error1'
| vf610_adc.c:(.text+0x1f3054): undefined reference to `mipi_csi2_enable'
| vf610_adc.c:(.text+0x1f315c): undefined reference to `mipi_csi2_reset'
| vf610_adc.c:(.text+0x1f316c): undefined reference to `mipi_csi2_set_datatype'
| drivers/built-in.o: In function `ioctl_dev_init':
| vf610_adc.c:(.text+0x1f3960): undefined reference to `mipi_csi2_get_info'
| vf610_adc.c:(.text+0x1f396c): undefined reference to `mipi_csi2_enable'
| make[2]: *** [vmlinux] Error 1
| make[1]: *** [sub-make] Error 2
| make: *** [__sub-make] Error 2
| ERROR: oe_runmake failed
| ERROR: Function failed: do_compile (log file is located at /u/ee209785/yocto1/build/tmp/work/imx7s_warp-poky-linux-gnueabi/linux-warp7/4.1-r0/temp/log.do_compile.2684)
ERROR: Task 52 (/u/ee209785/yocto1/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-warp7_4.1.bb, do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2582 tasks of which 2581 didn't need to be rerun and 1 failed.
No currently running tasks (1305 of 2602)

Summary: 1 task failed:
/u/ee209785/yocto1/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-warp7_4.1.bb, do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Thanks with regards

Vinod Hulagabali

Attachments:

community.element14.com/.../i.MX_5F00_Linux_5F00_Reference_5F00_Manual.pdf

i.MX_Linux_Reference_Manual.pdf

how to enable wifi in warp&?

nayanabhagavan@gmail.com — Fri, 16 Jun 2017 09:56:57 GMT

i have problem in enabling wifi

Problem with updating linux on warp7

idzik15 — Thu, 01 Jun 2017 21:56:29 GMT

Hello everyone!

I have a problem with my warp7 board.

I've already read every topic or post I could find on the Internet.

I did everything like in this tutorial: Warp7 Yocto : Part2 : Flashing Warp7 binaries or user guide from github.

Unfortunately I could not flash new kernel to my warp7. I am using Ubuntu on VirutalBox as a host computer.

The problem shows up when I try to mount eMMC space, using uboot ums command for that. (=> ums 0 mmc 0)

It works but only partly. My host computer detects some memory mounted after "ums" command. But something is not right. And when I am trying to flash kernel some problems show up.

Warp7's eMMC memory shows up as a sdb device.

At first when I tried to flash kernel it showd that "no mdeium found".

Then "no such device or address" even tho when I checked by diffrent commands you can see that there are 3 partitions.

I even checked that on Windows and on OS X. Both systems showed one partition "boot imx7s-"

I don't know what I am missing and where the problem is

I wanted to flash new kernel to have enable wifi.

Here are some photos:

If anyone can help me solving this problem I will be so, so grateful!

Android BSP?

wayzel — Sun, 21 May 2017 19:42:28 GMT

Hi,

Where is the Android BSP for the Warp7 SOM? The last we heard this was expected in December 2016. Any updates? Will this in fact ever be provided?

Official Warp7 DTS for running both the A7 and M4

aes_gcs — Sun, 07 May 2017 21:25:35 GMT

Hello,

Is there an officially supported DTS/DTB for running both the A7 and M4? Looks like the stock imx7s-warp.dts does NOT have M4 support. In the forums I see some claims that it would be supported by last November, however I dont see any follow though. Some other users tinkering around seem to have gotten it working, but the details are lacking. Is this going to be officially supported?

Thanks!

what's the part number of LCD

zhanglei2015xx — Fri, 07 Apr 2017 15:29:22 GMT

what's the part number of LCD

Larger lithium ion battery for Warp7?

hrogge — Thu, 09 Mar 2017 11:55:53 GMT

Hi,

is there any reason not to attach a larger lithium ion battery pack to the Warp7 board, e.g. when using the board with attached USB and/or click-shield equipment?

Henning Rogge

warp7 u-boot update

wumu — Fri, 03 Mar 2017 09:28:51 GMT

hi,I am trying to update the u-boot of the warp7,I fallowed the exactly step in the: https://github.com/WaRP7/WaRP7-User-Guide/blob/master/04-Chapter/U-boot.adoc

the original u-boot information is：

U-Boot 2016.07-00091-ge6b4241 (Aug 22 2016 - 10:56:52 +0800)

CPU:   Freescale i.MX7S rev1.2 at 792MHz
CPU:   Extended Commercial temperature grade (-20C to 105C) at 47C
Reset cause: POR
Board: WARP7
DRAM: 512 MiB
MMC:   FSL_SDHC: 0
In:    serial
Out:   serial
Err:   serial
Net:   CPU Net Initialization Failed
No ethernet found.
Hit any key to stop autoboot: 0

then i use the command: sudo ./imx_usb u-boot.imx

the newly u-boot infromation is:

U-Boot 2016.07 (Mar 03 2017 - 16:55:17 +0800)

CPU: Freescale i.MX7S rev1.2 at 792MHz

CPU: Extended Commercial temperature grade (-20C to 105C) at 51C

Reset cause: PORtop autoboot: 6

Board: WARP7

I2C: ready

DRAM: 512 MiB

PMIC: PFUZE3000 DEV_ID=0x30 REV_ID=0x11

MMC: FSL_SDHC: 0

In: serial

Out: serial

Err: serial

Net: CPU Net Initialization Failed

No ethernet found.

Hit any key to stop autoboot: 0

then i fallowed the comand:

=> env default -f -a 
=> saveenv

Run the DFU command:

=> dfu 0 mmc 0

and sudo dfu-util -D u-boot.imx -a boot

then the u-boot showed the message:

#DOWNLOAD … OK Ctrl+C to exit …

then i powered off the warp7,put WaRP7 board into normal boot mode,reboot again,the updated u-boot information is :

nothing changed??? why?

WaRP7 Wearable Development Platform Power Consumption

griff0417 — Thu, 19 Jan 2017 20:51:22 GMT

Does anyone have information in regards to power consumption of the WaRP7 while running the provided Linux BSP? In Idle or suspended state?

Thanks in advance,

Jason

Need to create boot partition on eMMC in Warp7 board

vnr1992 — Wed, 07 Dec 2016 06:16:03 GMT

Hi All,

I accidentally deleted all partitions except U-Boot portion of the MMC on Warp 7 board.

I am getting UBoot prompt but not able to find a way to create boot partition and boot up the WaRP7 board.

Can anyone know how can I handle this situation?

Thanks,

Vivek

Node.js on WaRP7

vshymanskyy — Mon, 05 Dec 2016 14:24:45 GMT

There is https://github.com/imyller/meta-nodejs layer package. How to get this onto my Warp7 with minimum efforts?

WaRP7 board layouts, drawings or dimensions

kickofighto — Tue, 29 Nov 2016 14:56:17 GMT

I'm wondering what PCB design software the supplied *.brd files were produced in? Not Eagle by the looks of things...

I need to make a different IO/daughter board and a snug fitting enclosure for a product we are developing and need some critical dimensions.

If possible it would be really helpful to get a .dxf, .dwg or other generic cad output of the component footprints for the community to use.

Thanks!

Warp7 USB-OTG

arre — Fri, 25 Nov 2016 10:17:50 GMT

Hi,

Using the Warp7 USB OTG port in OTG mode: The port is not supplying 5V power when the board is fed from the battery, although this seems forseen in the schematic
- Is it possible a devicetree change is required to make the port work in OTG mode (the battery charger IC has I2C comms)?
  - => This is essential to try to connect any USB device to the board.
  - => This seems a pretty basic thing to try, so this must have been done by someone I would think?

Thanks for any feedback on this!

Kind regards,

Arnout

Warp7 camera support

arre — Fri, 25 Nov 2016 10:16:01 GMT

Hi,

As also asked in the generic topic (but I think deserves a seperate post), the stock image, nor even the latest dev images do not seem to detect the onboard camera. (and there is no documentation available whatsoever for it)

=> When is an image planned to be released that supports this camera?

Thanks for your feedback

Cost of just the WaRP7 SoM?

mfauci — Thu, 03 Nov 2016 16:48:02 GMT

Interesting product. We're working on a project that we were planning to use the C.H.I.P. SoM for. C.H.I.P. costs is $16. By way of comparison, we were wondering what the cost of just the WaRP SoM is - without the kit?

Warp7 Uboot make error

yashchabria — Tue, 01 Nov 2016 21:17:09 GMT

Hi!

I am getting :

lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch

Kbuild:43: recipe for target 'lib/asm-offsets.s' failed

make[1]: *** [lib/asm-offsets.s] Error 1

Makefile:1283: recipe for target 'prepare0' failed

When trying to compile the Warp7 Uboot

yash@ubuntu:~/Documents/nxp$ git clone https://github.com/Freescale/u-boot-fslc.git

Cloning into 'u-boot-fslc'...

remote: Counting objects: 433462, done.

remote: Compressing objects: 100% (4091/4091), done.

remote: Total 433462 (delta 2910), reused 2 (delta 2), pack-reused 429340

Receiving objects: 100% (433462/433462), 107.39 MiB | 1.32 MiB/s, done.

Resolving deltas: 100% (345453/345453), done.

Checking connectivity... done.

yash@ubuntu:~/Documents/nxp$ cd u-boot-fslc/

yash@ubuntu:~/Documents/nxp/u-boot-fslc$ git checkout -b my_nxp_ub origin/2016.11+fslc

Branch my_nxp_ub set up to track remote branch 2016.11+fslc from origin.

Switched to a new branch 'my_nxp_ub'

yash@ubuntu:~/Documents/nxp/u-boot-fslc$ make mrproper

yash@ubuntu:~/Documents/nxp/u-boot-fslc$ make warp7_config

HOSTCC scripts/basic/fixdep

HOSTCC scripts/kconfig/conf.o

SHIPPED scripts/kconfig/zconf.tab.c

SHIPPED scripts/kconfig/zconf.lex.c

SHIPPED scripts/kconfig/zconf.hash.c

HOSTCC scripts/kconfig/zconf.tab.o

HOSTLD scripts/kconfig/conf

# configuration written to .config

yash@ubuntu:~/Documents/nxp/u-boot-fslc$ make

scripts/kconfig/conf --silentoldconfig Kconfig

CHK include/config.h

UPD include/config.h

CFG u-boot.cfg

GEN include/autoconf.mk

GEN include/autoconf.mk.dep

CHK include/config/uboot.release

UPD include/config/uboot.release

CHK include/generated/version_autogenerated.h

UPD include/generated/version_autogenerated.h

CHK include/generated/timestamp_autogenerated.h

UPD include/generated/timestamp_autogenerated.h

CC lib/asm-offsets.s

lib/asm-offsets.c:1:0: error: bad value (armv5) for -march= switch

Kbuild:43: recipe for target 'lib/asm-offsets.s' failed

make[1]: *** [lib/asm-offsets.s] Error 1

Makefile:1283: recipe for target 'prepare0' failed

make: *** [prepare0] Error 2

Reducing power on Warp7?

jpostman — Wed, 19 Oct 2016 20:48:52 GMT

Right now the power consumption of the board seems pretty high both when on and idle (~340mW) as well as when in suspend to memory (~80mW).

1. Is there a known method for reducing the board power?

2. Are there any plans for Warp7 to support LPSR mode?