There is no picture.

Why is there twice a staff wifi ?
i would not use an svi for the guest wifi, this network you want tot isolate, and this is not posible in youre design.  ?

a trunk on hp is an portchannel on cisco.

just put on the trunk between the switches all vlan's tagged, you dont need to have an untagged vlan on the connection.

i made you de couple of diagrams, layer 2 and layer 3 design how to beeld what you want.
layer-2.png
layer-3.png

How large is the space and how many users are there? I'm hoping that the staff wireless VLANs are for two different areas

1) By default the Sonicwall has VLAN1, no matter what you name its subnet. You could just preserve that across all of your equipment rather than have a VLAN 100. To create the other subnets (VLANs) on the Sonicwall, you would create virtual interfaces. Make sure those virtual interfaces are tied to the same interface you're utilizing for your network. That will have the equivalent of VLAN1 being untagged and all of the virtual interfaces being tagged coming out of the Sonicwall.
2) I hope VLANs 4 and 6 are meant for different areas. UNLESS you meant one of those for a purpose other than staff (which you should correct now before building). Also make sure you do not allow VLAN 10 to communicate with the other VLANs. However, you should identify which VLANs should be able to communicate with which. You should also pay attention to your NAT policies. Also.... if you're going to be non-Sonicwall access points, make sure to pay attention to the settings for your zones. You need to specifically disable checks for Sonicpoint devices.
3) Bear in mind Benjamin's last comment. HP switches do not understand Cisco trunks. (Assuming that you will have a Cisco switch in play somewhere, given that you haven't cited an actual Cisco switch)

@soul.. i am trying follow your way i am trying to ping from access switch to the sonicwall but failed.Please advice.

First try pinging from the Aruba to the Sonicwall. Source the ping from several of the vlan interfaces you created. This will insure the Sonicwall has a route back to those subnets.  
If successful, then try from a host on the vlans.
Make sure the access port the host is connected to is assigned to the correctly vlan.
Make sure the Aruba has a default route pointing to the Sonicwall.
Also make sure the host you are pinging is configured with the correct default gateway for the vlan it is in.

@soul..now i simulate using the packet tracer assume that router is my firewall i am getting same result .

1.I can not ping from my access switch to to my SVI in core switch except vlan 2 which is management interface.
2.I can not ping from access switch to router interface.
3.can not ping from router to core switch SVI except uplink.

Share your packet tracer file and the version you are using.

@soul. I just try now actually I am trying to ping from core switch to router also can not and router to core switch also same.

@soul ..my packet tracer is 7.1

Can you attach the packet tracer file you are working on?

@SOUL
attached configuration is for your referenceCore-Switch.txt
Router.txt
Switch.txt

On router:

ip route 192.168.200.0 255.255.255.0 192.168.200.254
ip route 192.168.2.0 255.255.255.0 192.168.200.254
ip route 192.168.6.0 255.255.255.0 192.168.200.254

On switch:
ip default-gateway 192.168.200.254

@Soul

I am following the guide above, i can reach the SVi from switch but i still having issue below:
 
1.Can not ping all the core-switch svi from router
2.from the coreswitch and switch can not ping 192.168.200.1
RouterV2.txt
SwitchV2.txt

Sorry do the followingL

Router:

Don't need this. This subnet is already a connected route:
no ip route 192.168.200.0 255.255.255.0 192.168.200.254

On switch:
ip default-gateway 192.168.2.254

When you ping from the router are you sourcing the ping from Gi0/0? I assume this interface is connect to the Aruba. What is your GI0/1 used for?

On your coreswitch I don't see a port configured for VLAN 200. This should be the port that the router is connected to on Gi0/0.

@SOUL

I solve all the issue with your guides and i modefy the access port from my core-switch to router to access vlan 200 instead of 2 now all the problem solved.

Awesome. Sorry at work and didn't catch that the first time I looked.

@soul

No..problem.I will open another topic for the 4 × ,peplink switch the uplink to core switch.Each accesa switch have two link to core switch as redundentcy .see you in new topic 😁